Tip for less width in the bitrate field (Also V0 V2 talk)

[greenday1987]

Displaying V0 or V2 or whatever would be much better imho.

This

[lnminente]

Now we have the $Right function, we can see 128~ instead of 128 VBR and still will be sortable using the following algorithm:
$Left(<Bitrate>,3)$If($Right(<Bitrate>,3)="VBR",~,)

[EnduringGuerila]

+1 for displaying v0, v2, etc.

[Thorbjorn]

+1 for displaying v0, v2 etc. if possible. I'm tagging it manually now, so would love it to be automatic. I don't think it's straight forward to show that though?

[greenday1987]

I doubt it's that difficult although I'm not a coder so I could easily be wrong :/

[HHM]

I'm -1 as for V0, V1... option, here's why:
I think only more advanced users will understand it. people who know this terminology will know that 207k means V1 (dunno if it's correct - just gave an example), but most casual users don't what what V1 stands for.

+ (i'm not fully sure about it) isn't it 100% accurate only with these files you've decoded yourself?

[Thorbjorn]

If they don't know what v0 is they probably don't know what VBR is either. Having it as a separate field or option would be good enough for me.
But yes accuracy is what I thought could be a problem too. I just remember using this program long ago that could detect the encoding parameters, but it was never completely accurate and would only work for mp3's encoded with LAME.
Anyway I just did a quick search and I see foobar can display this, so it's possible at least.

[greenday1987]

If they don't know what v0 is they probably don't know what VBR is either. Having it as a separate field or option would be good enough for me.
But yes accuracy is what I thought could be a problem too. I just remember using this program long ago that could detect the encoding parameters, but it was never completely accurate and would only work for mp3's encoded with LAME.
Anyway I just did a quick search and I see foobar can display this, so it's possible at least.

This is because they are Lame presets

[Thorbjorn]

This is because they are Lame presets

Obviously, I'm just saying it couldn't read any other encoders.

[Steven]

i'm replying to this topic now as its not easy to find. I have mostly done an implementation that reads the encoding quality from lame encoded files.
The field will be available as a separate "encoding quality" field (that field might already be in the version you are using but doesnt currently display anything).
Additionally via preference setting you can display it in place of bitrate where a value is available.
It will require you to rescan your files though, but i will make that automated when the preference setting is first ticked

[greenday1987]

Wow, that sounds epic Steven

[Steven]

this has the change:
http://musicbee.niblseed.com/V2_1/MusicBee_Exe_Patched.zip

- Encoding Quality field
- setting in Preferences/ Layout/ Fields/ tick "replace Bitrate with Encoding Quality" if you would rather see encoding quality (when available) instead of the bitrate
- encoding quality displays in the Now Playing panel properties line and in the tag editor Properties page

However for MB to get the data you will need to rescan your library files (quickest way is File/ Advanced/ Rescan All Files)

[beeing good]

Steven, does this change/write to the tags at all or it is just reading the data already in the tags?

[Steven]

it only reads

[beeing good]

Ok, thanks. This is wonderful, no more sending to foobar to check the preset for me!