More > JRiver Media Center 28 for Windows
Feature request: more than 5 stars for rating.
MusicBringer:
Five stars is just right.
2 stars = fully satisfactory; 1 star is not.
The remaining ratings are scores for good, better, best.
I require nothing more.
😃
HPBEME:
Rutabaga, I requested a 10-star rating system myself in the MC27 thread earlier this year.
https://yabb.jriver.com/interact/index.php/topic,127672.0.html
And then expanded on that thread in another thread specifically with "Feature Request" as the subject (which others recommended I do):
https://yabb.jriver.com/interact/index.php/topic,127686.0.html
Bottom line is, you can use 10-stars right now with very little effort. And that "how to" video you desperately want... It already exists:
https://www.youtube.com/watch?v=0Fjrf5mTcWg
However, there is 1 big downside for me with using 10-stars: while you can edit the 10-star rating in detail lists and the tag window, you cannot edit the stars directly in the Player Bar (like you can with the default 5-star system), which is by far the most useful/convenient area to change it. When I am listening to music, I am either in full screen mode or doing other things in MC where I don't have the tag window open, or the main content area is showing something other than the Playing Now window. This forces me out of full screen mode, or stop whatever else I am doing, and open the tag window or playing now window just so I can edit the 10-star rating, which is highly annoying and inconvenient. In the 1st thread link above, Zybex even suggests a way it could be incorporated/coded by Matt.
I will take this opportunity to beg JRiver to add this functionality to the Player Bar please! I would like to think I might merit some extra consideration for implementing this request. After all, I invested 600+ hours of my personal time developing the very popular skin, Dream in Blue (with 7 different skin variations built-in no less!), which is JRiver's 1st brand new skin in nearly a decade! https://accessories.jriver.com/mediacenter/accessories.php. Also see: https://yabb.jriver.com/interact/index.php/topic,128460.0.html
I am not sure anyone from JRiver has acknowledged this massive (free) effort with even a thank you (though a number of users have, which I greatly appreciated). Yeah... I can't lie... I guess I am a little bitter about that. That said, I know there are a lot of MC users in this forum who have also donated lots of their time too. Perhaps JRiver should offer some kind of incentive for those who "volunteer" to make JRiver a better product. Who knows, it might entice folks to... I don't know... make more new skins!?
I humbly await, or not so humbly I guess, to see JRiver make the 10-star rating editable in the Player Bar.
JimH:
--- Quote from: HPBEME on September 03, 2021, 11:06:32 pm ---I am not sure anyone from JRiver has even acknowledged this massive (free) effort with even a thank you (though a number of users have, which I greatly appreciated).
--- End quote ---
Thank you! We're grateful for your work. i'm sorry we neglected to say that.
Bob was enthusiastic about it.
HPBEME:
Thanks Jim, much appreciated. As the saying goes... better late than never.
If you have not read my original post announcing the skin (https://yabb.jriver.com/interact/index.php/topic,128460.0.html) you may not be aware that, in addition to providing a configurable skin with 7 variations, I also made a "main+comments.xml" which has 300+ lines of comments.
These comments detail numerous aspects of how the skin handles various XML inputs/variables, such as: how and where every single hex color is applied in the skin (80+ places where a hexcode color must be specified!); how certain XML controls affect image position/size; how various inputs interact with each other; etc. Most importantly... it documents how numerous inputs change things that are unrelated to the input itself (unrelated because the area affected is "unrelated" to the input name and XML section it resides in).
This comments file alone is worth its weight in gold. I imagine there are many folks who have attempted to create a skin and gave up... as I almost did several times... because as you edit the XML, things change/blow-up in the skin where you would never expect it to, and it is a nightmare trying to diagnose why. But I persisted, hunted down every anomaly, and documented them... 1 by 1. It was pure torture and tedious as hell, but in the end I have given JRiver a roadmap of items they can/should clean up in the skin XML. If nothing else, it will be invaluable to anyone else who decides to take on the task of creating a new skin. By using my files as a starting point, I estimate the effort required to create an exotic skin (along the lines of DiB) would be reduced by 75% .
gulp:
Do you know why neither a custom 5 start or 10 star field can be used like this over JRemote (although it's generally possible, as the track rating in the play screen shows)?
The use of this field type would be most useful in JRemote, even more than in JRiver.
Navigation
[0] Message Index
[*] Previous page
Go to full version