I'd love to see the addition of a bitrate node or view (ie, to view only mp3s with a bitrate of 192, 160, 128, VBR, etc.)
It would also be cool if we could relate the "Quality" classification to the bitrate.
Bitrate View
Moderator: Gurus
some help
Bitrate node
The problem with bitrate node would be VBR (which has many different bitrate possibilties) and other standards. A solution to this could be to only include the standard MP3 CBR values and a other subnode for everything else. I myself don't need this feature.
A current solution
To see only tracks from one bitrate ie 128k you can use the search, you'll need to see if this field is searchable in the standard search, but if not you'll need to use the advanced search (Gold version only). Here you can add a condition with bitrate = 128k, or also higher than 128k or even in between two bitrates. This actually results in a couple steps more then a bitrate node, but it works.
Relate quality to bitrate
This could be achieved by a script (program addon) and you can either write it yourself or request it in the developers forum (scripts are only available for Gold users). Using another program that does this is of course an option too.
My question is why would you want the same thing stored twice. If bitrate 192k is always good quality this seems to be redundant information. I'm not sure but the MP3 standard might create a bigger file the more fields you use to store information and with thousands (don't know how many you have) of MP3's this could take up some space.
I personally think the field quality pertains to the quality of the song ie. no errors like gaps and noises, and it generally sounds good or not.
I hope this helps you
The problem with bitrate node would be VBR (which has many different bitrate possibilties) and other standards. A solution to this could be to only include the standard MP3 CBR values and a other subnode for everything else. I myself don't need this feature.
A current solution
To see only tracks from one bitrate ie 128k you can use the search, you'll need to see if this field is searchable in the standard search, but if not you'll need to use the advanced search (Gold version only). Here you can add a condition with bitrate = 128k, or also higher than 128k or even in between two bitrates. This actually results in a couple steps more then a bitrate node, but it works.
Relate quality to bitrate
This could be achieved by a script (program addon) and you can either write it yourself or request it in the developers forum (scripts are only available for Gold users). Using another program that does this is of course an option too.
My question is why would you want the same thing stored twice. If bitrate 192k is always good quality this seems to be redundant information. I'm not sure but the MP3 standard might create a bigger file the more fields you use to store information and with thousands (don't know how many you have) of MP3's this could take up some space.
I personally think the field quality pertains to the quality of the song ie. no errors like gaps and noises, and it generally sounds good or not.
I hope this helps you
Download MediaMonkey ♪ License ♪ Knowledge Base ♪ MediaMonkey for Windows 2024 Help ♪ MediaMonkey for Android Help
Lowlander (MediaMonkey user since 2003)
Lowlander (MediaMonkey user since 2003)