Topic: Release medium specifics

I would like to see increased release medium specifics.

I'm thinking particularly of:

vinyl: weight, colour
digital media: format, bit rate

Dicogs has fields for such info.

It would be nice to be able to see, for example, whether there is a 180g release of a particular vinyl or a lossless version of a digital-only track.

Thoughts?

Re: Release medium specifics

I agree at least with the vinyl part. I'm not sure about the bitrate, mostly because I don't want to have to add 6 releases in different formats for every bandcamp download...

Re: Release medium specifics

Yeah, bitrate etc makes no sense.

Re: Release medium specifics

I would prefer to be able to specify the format, bitrate and bit depth but we should be able to specify multiple media formats and bitrates on single release.

IMHO this information is important because some releases in high bitrate lossless formats are considered to be a "luxury" version. (for example FLAC 24 bit, 192 kHz)
Other releases are more or less demo. (for example MP3 128 kbps)

Re: Release medium specifics

reosarevok wrote:

I agree at least with the vinyl part. I'm not sure about the bitrate, mostly because I don't want to have to add 6 releases in different formats for every bandcamp download...

We could simplify this by adding a list of available bitrates/file extensions within 1 release. Everything else would be the same otherwise, so I don't see why this couldn't be a solution (unless certain bitrates or formats were only sold on certain sites or to certain geographic regions).

Re: Release medium specifics

Lixobix wrote:

digital media: format, bit rate

Dicogs has fields for such info.

Discogs has also ruled that multiple releases that only differ in bit rate or digital format are not allowed, because even they see sense sometimes.

on the vinyl, I would prefer just the option to state it's coloured, not specify the colour, I don't really want multiple releases that differ only in how one person describes some colour (as seen on discogs).

I would like the vinyl to be expanded to include: picture disc, flexi disc, lathe-cut, shellac, coloured vinyl, 6", 8" 9" & 11"

I'd also like 20 naked nubile girls and a never-ending supply of beer

Re: Release medium specifics

pabouk wrote:

I would prefer to be able to specify the format, bitrate and bit depth but we should be able to specify multiple media formats and bitrates on single release.

IMHO this information is important because some releases in high bitrate lossless formats are considered to be a "luxury" version. (for example FLAC 24 bit, 192 kHz)
Other releases are more or less demo. (for example MP3 128 kbps)

Exactly my point. Nice to know what's available.

HibiscusKazeneko wrote:
reosarevok wrote:

I agree at least with the vinyl part. I'm not sure about the bitrate, mostly because I don't want to have to add 6 releases in different formats for every bandcamp download...

We could simplify this by adding a list of available bitrates/file extensions within 1 release. Everything else would be the same otherwise, so I don't see why this couldn't be a solution (unless certain bitrates or formats were only sold on certain sites or to certain geographic regions).

I like this idea, although it would be a bigger structural change than simply adding extra medium kinds. Certainly, adding multiple releases for different bitrates/formats is overkill. In one sense, the information could be put in release annotation, but I think it should have more prominence and be an easily searchable feature e.g. you could find which releases by artist x are available in 24/96 digital. However, I would not consider each bit rate/format a distinct release.


mudcrow wrote:
Lixobix wrote:

digital media: format, bit rate

Dicogs has fields for such info.

Discogs has also ruled that multiple releases that only differ in bit rate or digital format are not allowed, because even they see sense sometimes.

See above.

mudcrow wrote:

on the vinyl, I would prefer just the option to state it's coloured, not specify the colour, I don't really want multiple releases that differ only in how one person describes some colour (as seen on discogs).

I suppose so, but what about when there is say a red, blue, and black version?

mudcrow wrote:

I would like the vinyl to be expanded to include: picture disc, flexi disc, lathe-cut, shellac, coloured vinyl, 6", 8" 9" & 11"

Yep.

mudcrow wrote:

I'd also like 20 naked nubile girls and a never-ending supply of beer

Wouldn't we all :)

Re: Release medium specifics

I'm not saying knowing the bitrate is useless information to have; I'm saying it's little use (compared to its cost of maintenance) to have it in a /structured/ relational manner. We have annotations for this type of thing.

There are too many formats. Bitrate is, at the margin, an arbitrary number. Part of the beauty of digital is that this doesn't /have/ to be standardised like was required for CD, vinyl. But that also reduces its utility in a structured database. The digital formats and birates things are released in will (and have) changed rapidly over time and it will be difficult to keep up. Different online retailers can release the same thing in different bitrates/formats/DRM. It sounds like a good idea at first, but on the balance I am convinced that it is absolutely not. If you only store one bitrate/format, which one do you store? If you want to capture that some version is a "premium" version with high bitrate, then presumably you're wanting to also capture the "regular" version with the lower bitrate for comparative purposes - this is already breaking the Discogs rule.

9 (edited by HibiscusKazeneko 2012-05-01 07:01:56)

Re: Release medium specifics

mudcrow wrote:

on the vinyl, I would prefer just the option to state it's coloured, not specify the colour, I don't really want multiple releases that differ only in how one person describes some colour (as seen on discogs).

I would like the vinyl to be expanded to include: picture disc, flexi disc, lathe-cut, shellac, coloured vinyl, 6", 8" 9" & 11"

That reminds me: I was just messing around with some releases that featured EnhancedCD content; should we add a category for such? Since it's burned onto a physical disc, it wouldn't really qualify as digital media. Same for CD+G and CD-Plus and similar formats, there should be a place other than the annotation box to stipulate what kinds of non-audio content is bundled with releases.

Re: Release medium specifics

voiceinsideyou wrote:

I'm not saying knowing the bitrate is useless information to have; I'm saying it's little use (compared to its cost of maintenance) to have it in a /structured/ relational manner. We have annotations for this type of thing.

Having no experience in relation to database design/maintenance I will take your word for it, but I would have though adding some sort of check box feature, just for DM, which contained most common bitrates/formats would not be too difficult to implement at some point in the future. But I accept your point and know that there is more important work to be done at the moment.

voiceinsideyou wrote:

There are too many formats. Bitrate is, at the margin, an arbitrary number. Part of the beauty of digital is that this doesn't /have/ to be standardised like was required for CD, vinyl. But that also reduces its utility in a structured database. The digital formats and birates things are released in will (and have) changed rapidly over time and it will be difficult to keep up. Different online retailers can release the same thing in different bitrates/formats/DRM. It sounds like a good idea at first, but on the balance I am convinced that it is absolutely not. If you only store one bitrate/format, which one do you store? If you want to capture that some version is a "premium" version with high bitrate, then presumably you're wanting to also capture the "regular" version with the lower bitrate for comparative purposes - this is already breaking the Discogs rule.

To my knowledge, the only ones widely used are MP3 (192, 320), AAC (128, 256), lossless 44.1khz (FLAC, Wav, ALAC), 48khz, 24/96 and 24/192 (FLAC, WAV). Is that too many? I think digital is standardised, just on multiple levels.

I think it's pretty much just Apple releasing in AAC and ALAC at the moment, and I can't remember seeing any MP3 release in anything other than 192 or 320 for a while, except perhaps the odd 256.

With lossless, once you discount the format (which doesn't affect the sound), you have four levels. Moreover, AFIK we cannot record higher than 192 at the moment, and older recordings will be limited to whichever sample rate was used at the time.

I don't honestly believe lossy has anywhere to go. I mean AAC still hasn't been adopted as the industry standard despite being generally accepted to be superior to MP3, so I don't foresee any new lossy formats or rates appearing anywhere in the near future. Same for lossless.

The only change we are seeing in DM is the increasing distribution of studio masters, but the formats and bit rates themselves seem to have solidified. To that extent I think now is a good time to integrate such information. At the very least to specify where there has been a lossless release.

HibiscusKazeneko wrote:
mudcrow wrote:

on the vinyl, I would prefer just the option to state it's coloured, not specify the colour, I don't really want multiple releases that differ only in how one person describes some colour (as seen on discogs).

I would like the vinyl to be expanded to include: picture disc, flexi disc, lathe-cut, shellac, coloured vinyl, 6", 8" 9" & 11"

That reminds me: I was just messing around with some releases that featured EnhancedCD content; should we add a category for such? Since it's burned onto a physical disc, it wouldn't really qualify as digital media. Same for CD+G and CD-Plus and similar formats, there should be a place other than the annotation box to stipulate what kinds of non-audio content is bundled with releases.

I'm curious as to why more formats have not been added across the board.

Since DVD track lists are allowed I principally see no reason not to include ECD as well. However, unlike DVDs the extra material is not on a separate medium, so would you append it to the end of the track list? I think on some ECDs there's a video or two that are actually specified as track x or y so that may be doable. Then again, you run into the problem of adding video tracks to the database, which is not meant to be done. DVD is allowed on the basis that the audio can be ripped, so perhaps the same principle could be applied. Don't know of the other two formats.

This brings up another thought I've been having: Splitting mediums. By this I mean adding some distinction between different parts of a single medium, e.g. where two albums have been re issued on 1 cd. Would be nice to see clearly in the database that there are two distinct entities within a medium, and would be very useful for tagging purposes. Other examples where this would apply:

Two releases on 1 USB stick: http://musicbrainz.org/release/d3c9ff76 … 73d2c9eba7
Separating bonus material from the actual album

Re: Release medium specifics

Lixobix wrote:

I can't remember seeing any MP3 release in anything other than 192 or 320 for a while, except perhaps the odd 256.

Bandcamp is mp3 320, mp3 V0 VBR, FLAC, AAC, Ogg Vorbis and ALAC

12

Re: Release medium specifics

Maybe instead of bitrate, putting "lossless / lossy" flag might be helpful for some people. But, other than that I don't feel bitrate is a logical option to include anywhere.

Re: Release medium specifics

Lixobix wrote:

Two releases on 1 USB stick: http://musicbrainz.org/release/d3c9ff76 … 73d2c9eba7
Separating bonus material from the actual album

Ditto that.
I personally own this release (it cost me nearly $100, but it was well worth it) and know there's more bonus content (e.g. an executable photo gallery) that I cannot outline under the current system unless I add it as an annotation.

Re: Release medium specifics

reosarevok wrote:
Lixobix wrote:

I can't remember seeing any MP3 release in anything other than 192 or 320 for a while, except perhaps the odd 256.

Bandcamp is mp3 320, mp3 V0 VBR, FLAC, AAC, Ogg Vorbis and ALAC

Fair point. Yes, there are a lot of other lossy formats about but I think the majority of vendors (Itunes, Amazon, labels) use those I stated. You could alway have an option for 'other'.


ym wrote:

Maybe instead of bitrate, putting "lossless / lossy" flag might be helpful for some people. But, other than that I don't feel bitrate is a logical option to include anywhere.

This would be a step in the right direction. However, I'm seeing more and more high-res releases, and I think these should be distinguished.

HibiscusKazeneko wrote:
Lixobix wrote:

Two releases on 1 USB stick: http://musicbrainz.org/release/d3c9ff76 … 73d2c9eba7
Separating bonus material from the actual album

Ditto that.
I personally own this release (it cost me nearly $100, but it was well worth it) and know there's more bonus content (e.g. an executable photo gallery) that I cannot outline under the current system unless I add it as an annotation.

This is the same problem as with ECDs. I think currently MB is against adding info about video, pics or other material anywhere but in the annotation (with the exception of audio ripped from DVDs). However, I'm beginning to think such material should be included directly in the database.

Re: Release medium specifics

Lixobix wrote:
reosarevok wrote:

Bandcamp is mp3 320, mp3 V0 VBR, FLAC, AAC, Ogg Vorbis and ALAC

Fair point. Yes, there are a lot of other lossy formats about but I think the majority of vendors (Itunes, Amazon, labels) use those I stated. You could alway have an option for 'other'.

ym wrote:

Maybe instead of bitrate, putting "lossless / lossy" flag might be helpful for some people. But, other than that I don't feel bitrate is a logical option to include anywhere.

This would be a step in the right direction. However, I'm seeing more and more high-res releases, and I think these should be distinguished.

Yes losless / lossy is probably the most important information about the digital format but I agree with Lixobix that the bitrate should be stored.

IMHO we should be able to optionally store this information and the relevant part of the UI could be initially hidden (something like the artist credit editor) to not confuse inexperienced editors.

* bitrate
* codec
* number of channels (or channels setup)
* sampling frequency
* bit depth

IMHO the bitrate should be a numeric field for which the web UI would offer the most common values (like 96, 128, 192, 256, 320) besides being able to enter arbitrary number.
I do not think it is wise to create a possibly long list of predefined combinations which would serve only for mainstream releases.

16

Re: Release medium specifics

pabouk wrote:

IMHO we should be able to optionally store this information and the relevant part of the UI could be initially hidden (something like the artist credit editor) to not confuse inexperienced editors.

* bitrate
* codec
* number of channels (or channels setup)
* sampling frequency
* bit depth

IMHO the bitrate should be a numeric field for which the web UI would offer the most common values (like 96, 128, 192, 256, 320) besides being able to enter arbitrary number.
I do not think it is wise to create a possibly long list of predefined combinations which would serve only for mainstream releases.

I think having something like http://wiki.musicbrainz.org/Paid_Downlo … nship_Type AR, can be nice. Something like;
"can be purchased for download at URL, in {lossless|lossy} format"
but I still don't feel entering different technical file details is a wise thing to do.

Re: Release medium specifics

A relationship link would still mean you couldn't search directly for hi-res releases. Some regard them as very different to standard lossless or CD, just as different as vinyl.

18 (edited by ym 2012-05-02 18:16:59)

Re: Release medium specifics

if your problem is to be able to search, just include anything in annotation and use http://musicbrainz.org/doc/Indexed_Search_Syntax

Re: Release medium specifics

ym wrote:

if your problem is to be able to search, just include anything in annotation and use http://musicbrainz.org/doc/Indexed_Search_Syntax

Thanks. Hadn't tried using that feature before. Still, it is a bit fiddly and might be a bit confusing for new users. And I think the point still stands that some regard higher bit rate releases as distinct. For example see here: http://www.smashingpumpkins.com/reissues The hi-res version is more expensive than the standard lossless version. That may even suggest it is a unique release.

20

Re: Release medium specifics

Lixobix wrote:
ym wrote:

if your problem is to be able to search, just include anything in annotation and use http://musicbrainz.org/doc/Indexed_Search_Syntax

Thanks. Hadn't tried using that feature before. Still, it is a bit fiddly and might be a bit confusing for new users. And I think the point still stands that some regard higher bit rate releases as distinct. For example see here: http://www.smashingpumpkins.com/reissues The hi-res version is more expensive than the standard lossless version. That may even suggest it is a unique release.

If you think it needs a new release, it's another issue, but if you think there will be no need for a new release for small technical changes, then you can just create a fancy looking annotation that telling the technical details in different sources.
All in all they are still using a digital file for transporting the music. Bitrate or any other technical difference doesn't change how it is transported.
Actually I was doing same thing long ago for the CD releases to enter SPARS codes (like AAD etc.). These bitrates are the same logic IMO.

Re: Release medium specifics

Annotation field is not structured and it does not enforce unified format of contained information thus it is not suitable for reliable search.

I noticed that the number of channels was not discussed here. Of course music with more than two channels (stereo) is rare but it could be so different that I think that this information should be recorded in MB.

22

Re: Release medium specifics

pabouk wrote:

Annotation field is not structured and it does not enforce unified format of contained information thus it is not suitable for reliable search.

You can have headings, lists, URLs etc. (see http://wiki.musicbrainz.org/Annotation) in Annotations and they are really successful at search results. In fact Musicbrainz is currently using and wants their users to use it as "Sub Optimal Credits".
I don't understand completely what you mean by "reliable"?

pabouk wrote:

I noticed that the number of channels was not discussed here. Of course music with more than two channels (stereo) is rare but it could be so different that I think that this information should be recorded in MB.

Multi channel releases can be entered seperately, MB has support for different formats like SACD, DVDA, etc. See http://wiki.musicbrainz.org/Release/Format , but if you are talking about multi-channel digital files. I've never seen any of those sold online. If there are lots of those online maybe there can be a medium type for that, because I think it's much more important than bitrate or such technical details.

Re: Release medium specifics

ym wrote:
Lixobix wrote:
ym wrote:

if your problem is to be able to search, just include anything in annotation and use http://musicbrainz.org/doc/Indexed_Search_Syntax

Thanks. Hadn't tried using that feature before. Still, it is a bit fiddly and might be a bit confusing for new users. And I think the point still stands that some regard higher bit rate releases as distinct. For example see here: http://www.smashingpumpkins.com/reissues The hi-res version is more expensive than the standard lossless version. That may even suggest it is a unique release.

If you think it needs a new release, it's another issue, but if you think there will be no need for a new release for small technical changes, then you can just create a fancy looking annotation that telling the technical details in different sources.

For the sake of argument, suppose the above release was available at amazon. You could add the release to MB and it would be exactly the same as the MP3 release, except it would have a different ASIN. Problem is that someone editing would see the two releases and think they are dupes, and they would be right under current schema. But in reality they are two distinct release with different prices. The fact that the price is different MUST mean the things are different. The seller knows that, the buyer knows that, so why does MB not know that?

ym wrote:

All in all they are still using a digital file for transporting the music. Bitrate or any other technical difference doesn't change how it is transported.

Digital files are not a mode of transportation, they ARE the music. CDs are a mode of transporting digital files. The end result, when you put the CD into your computer or CD player (which is a form of computer) is that you have those digital files.

Supposing you downloaded 44.1khz lossless files and bought the CD, you would have the same digital files in the end. On the other had, if you buy the CD and 96khz lossless you end up with two different sets of files.

When talking about the actual music you hear, in the first example the end result both ways is exactly the same. But MB distinguishes between the two releases. In the second example, the music you hear from the 96khz download is different to the CD and the 44.1khz download, but MB won't recognise it as unique from the 44.1khz download, even though it says the CD and the 44.1khz download, which sound exactly the same, are both unique things.

That's the crux of the problem. Is makes no sense to say that two things that sound exactly the same are different but two things that sound different are exactly the same.

ym wrote:

Actually I was doing same thing long ago for the CD releases to enter SPARS codes (like AAD etc.). These bitrates are the same logic IMO.

This is not the same at all. MB would accept a new release whenever the SPARS code is different because, presumably, each new SPARS code would mean a new release, whether with a different catalog, barcode or just date.

pabouk wrote:

Annotation field is not structured and it does not enforce unified format of contained information thus it is not suitable for reliable search.

I think pabouk is saying there is not a consistent rule as to how thing are written in the annotation field, making searches inaccurate. For example, some releases will say 24/96, others 24bit 96khz, others 24 bit audio etc. So if somebody has phrased the information in a different way it won't show up in the search. And there are no guidelines saying how it should be written

pabouk wrote:

I noticed that the number of channels was not discussed here. Of course music with more than two channels (stereo) is rare but it could be so different that I think that this information should be recorded in MB.

With physical releases, they are at least given distinct releases, but searchability would be nice. Are there any multi-channel dm releases? Because these would currently be undistinguishable from stereo DM.

I suppose one fix to the above problems is to use the disambiguation field for the release, but this seems to be stretching it's intended use.

Another point, going back to the Smashing Pumpkins remaster, is that if both the original DM release and the remastered DM release are added they look identical apart from the date. Neither will have a catalog or barcode (as with all DM, possibly) so how do you prevent them from being merged?

24

Re: Release medium specifics

Lixobix wrote:
ym wrote:
Lixobix wrote:

Thanks. Hadn't tried using that feature before. Still, it is a bit fiddly and might be a bit confusing for new users. And I think the point still stands that some regard higher bit rate releases as distinct. For example see here: http://www.smashingpumpkins.com/reissues The hi-res version is more expensive than the standard lossless version. That may even suggest it is a unique release.

If you think it needs a new release, it's another issue, but if you think there will be no need for a new release for small technical changes, then you can just create a fancy looking annotation that telling the technical details in different sources.

For the sake of argument, suppose the above release was available at amazon. You could add the release to MB and it would be exactly the same as the MP3 release, except it would have a different ASIN. Problem is that someone editing would see the two releases and think they are dupes, and they would be right under current schema. But in reality they are two distinct release with different prices. The fact that the price is different MUST mean the things are different. The seller knows that, the buyer knows that, so why does MB not know that?

Actually MB does this seperation by the Barcodes. Each of those sold items should have different barcodes which will result in different releases in MB. The only problem is that you cannot tell the technical difference unless adding it to annotation.

Lixobix wrote:
ym wrote:

All in all they are still using a digital file for transporting the music. Bitrate or any other technical difference doesn't change how it is transported.

Digital files are not a mode of transportation, they ARE the music. CDs are a mode of transporting digital files. The end result, when you put the CD into your computer or CD player (which is a form of computer) is that you have those digital files.

Supposing you downloaded 44.1khz lossless files and bought the CD, you would have the same digital files in the end. On the other had, if you buy the CD and 96khz lossless you end up with two different sets of files.

When talking about the actual music you hear, in the first example the end result both ways is exactly the same. But MB distinguishes between the two releases. In the second example, the music you hear from the 96khz download is different to the CD and the 44.1khz download, but MB won't recognise it as unique from the 44.1khz download, even though it says the CD and the 44.1khz download, which sound exactly the same, are both unique things.

That's not true, Digital File is still your medium, but the codec inside it is your music. Same logic applies to vinyls too, ie; every vinyl can be made of different chemical substance, still it's the same release, the audio material inside it is not changed, tho having such an info in annotation is nice.

Lixobix wrote:

That's the crux of the problem. Is makes no sense to say that two things that sound exactly the same are different but two things that sound different are exactly the same.

"sound different" is a really relative term.

Lixobix wrote:
ym wrote:

Actually I was doing same thing long ago for the CD releases to enter SPARS codes (like AAD etc.). These bitrates are the same logic IMO.

This is not the same at all. MB would accept a new release whenever the SPARS code is different because, presumably, each new SPARS code would mean a new release, whether with a different catalog, barcode or just date.

As I said above you will end up with different releases, but still you can't enter SPARSS code anywhere other than annotation.

Lixobix wrote:
pabouk wrote:

Annotation field is not structured and it does not enforce unified format of contained information thus it is not suitable for reliable search.

I think pabouk is saying there is not a consistent rule as to how thing are written in the annotation field, making searches inaccurate. For example, some releases will say 24/96, others 24bit 96khz, others 24 bit audio etc. So if somebody has phrased the information in a different way it won't show up in the search. And there are no guidelines saying how it should be written

You can have a style for this purpose and let everyone follow it. Besides, same problem will arise even if you had a text field. The only solution is to let people select from a combo-box like structure, but when I think about that combo-box I can see how pain it would be.

Re: Release medium specifics

ym wrote:
Lixobix wrote:
ym wrote:

If you think it needs a new release, it's another issue, but if you think there will be no need for a new release for small technical changes, then you can just create a fancy looking annotation that telling the technical details in different sources.

For the sake of argument, suppose the above release was available at amazon. You could add the release to MB and it would be exactly the same as the MP3 release, except it would have a different ASIN. Problem is that someone editing would see the two releases and think they are dupes, and they would be right under current schema. But in reality they are two distinct release with different prices. The fact that the price is different MUST mean the things are different. The seller knows that, the buyer knows that, so why does MB not know that?

Actually MB does this seperation by the Barcodes. Each of those sold items should have different barcodes which will result in different releases in MB. The only problem is that you cannot tell the technical difference unless adding it to annotation.

...no, because a digital release doesn't have a barcode, so how do you distinguish?

ym wrote:
Lixobix wrote:
ym wrote:

All in all they are still using a digital file for transporting the music. Bitrate or any other technical difference doesn't change how it is transported.

Digital files are not a mode of transportation, they ARE the music. CDs are a mode of transporting digital files. The end result, when you put the CD into your computer or CD player (which is a form of computer) is that you have those digital files.

Supposing you downloaded 44.1khz lossless files and bought the CD, you would have the same digital files in the end. On the other had, if you buy the CD and 96khz lossless you end up with two different sets of files.

When talking about the actual music you hear, in the first example the end result both ways is exactly the same. But MB distinguishes between the two releases. In the second example, the music you hear from the 96khz download is different to the CD and the 44.1khz download, but MB won't recognise it as unique from the 44.1khz download, even though it says the CD and the 44.1khz download, which sound exactly the same, are both unique things.

That's not true, Digital File is still your medium, but the codec inside it is your music.

ALL digital music, whether on CD or in files, is encoded with a codec. I think it's WAV for CDs. The CD was just a convenient way of getting those files to you, ordered and ready to play. It is a container for the files. A container you don't need if you just download the files.

My point is you can download 44.1k WAV files directly or you can copy them to your computer/CD player from a CD and you will still end up with a bunch of 44.1k WAV files. But if you download 96k files you have something different.

ym wrote:

Same logic applies to vinyls too, ie; every vinyl can be made of different chemical substance, still it's the same release, the audio material inside it is not changed, tho having such an info in annotation is nice.

The weight of vinyl affects the sound. So the material is different.

ym wrote:
Lixobix wrote:

That's the crux of the problem. Is makes no sense to say that two things that sound exactly the same are different but two things that sound different are exactly the same.

"sound different" is a really relative term.

This is not a matter of subjective perceptions, a 96k file contains more audio information than a 44.1k file.

ym wrote:
Lixobix wrote:
ym wrote:

Actually I was doing same thing long ago for the CD releases to enter SPARS codes (like AAD etc.). These bitrates are the same logic IMO.

This is not the same at all. MB would accept a new release whenever the SPARS code is different because, presumably, each new SPARS code would mean a new release, whether with a different catalog, barcode or just date.

As I said above you will end up with different releases, but still you can't enter SPARSS code anywhere other than annotation.

Possibly another improvement that could be made. But SPARSS codes aren't around anymore, to my knowledge, whilst his-res releases are current and growing in popularity.

ym wrote:
Lixobix wrote:
pabouk wrote:

Annotation field is not structured and it does not enforce unified format of contained information thus it is not suitable for reliable search.

I think pabouk is saying there is not a consistent rule as to how thing are written in the annotation field, making searches inaccurate. For example, some releases will say 24/96, others 24bit 96khz, others 24 bit audio etc. So if somebody has phrased the information in a different way it won't show up in the search. And there are no guidelines saying how it should be written

You can have a style for this purpose and let everyone follow it. Besides, same problem will arise even if you had a text field. The only solution is to let people select from a combo-box like structure, but when I think about that combo-box I can see how pain it would be.

Where would you put the guidelines explaining how to add the correct annotation in relation to hi-res releases? I think style guidlines for annotations would be very difficult to enforce. I don't see how a selecting box could be complicated. Even if there were 20 or so options, it's not hard to select the appropriate one.