INTERACT FORUM
More => Old Versions => JRiver Media Center 27 for Windows => Topic started by: JimH on August 23, 2020, 11:57:38 am
-
Please also see New in MC27 (https://yabb.jriver.com/interact/index.php/topic,126718.0.html) for what's already been done.
Here are our thoughts for MC27. Because conditions can change quickly, we may not do all of these. We will also do others not listed.
My goals are the following.
Completion of Missing Features
Example: TV on Mac and Linux
Extension of Cloudplay and improved GUI
More progress toward feature parity among OS's and Remotes
Tighter integration
Sharing of data between installs
Single Log-in for licensing and forum and others JRiver services
For Remotes (where possible), Cloudplay, Chromecast, and Airplay
Other
Windows Defender defense
Improved install guides
Export and Import Settings
or
Download settings from a server. Point and Clone
-
I've locked this for now because we can't handle more discussions about where MC is going. There are other threads where you can express an opinion or suggestion. We will consider or implement many of the ideas posted on this board.
-
Tighter integration with HDHomeRun devices.
-
Hi, quick question so I can use the MC27 update without searching further - is the WDM driver still labelled MC25 please?
I need to introduce Qobuz to MC27; the copy of MC25 was removed a while back but Qobuz finds it and I see it being utterly confused by having 3 named versions :D
I occasionally have to correct its choice of player to get any sound through, don't know if its because of the driver being named MC25.
Thank you
-
Album scanning and tagging must be improved. Trying to import albums with subpar tagging and informational sources even though they maybe free is just becoming archaic and frustrating. A lot of effort needs to go into GUI and album curation and scraping/lookup functions. These are very old and generally hit or miss.
Further, Media Center needs to refine their audio sampling and filtering algorithms to render sound and this has not happened for some time too-- or is not up front and center like providing users willing to put in the time with additional sampling/filtering algorithms to try out. I presume the engine is fixed for convenience but it precludes incorporating newer approaches to rendering digital audio.
Without too much technical speak, I hope the general idea gets across.
-
Please add support for decoding TV channels encoded using Common Interface (CI) / Conditional Access Modules (CAM).
P.S. I am *not* a recent member. I have been following JRiver MC for over 13 years, as you can see by searching for my posts.
I don't (yet) use JRiver MC because this feature is missing.
-
MQA unfolding?
-
MQA unfolding?
Do a search of the forums, official support for MQA is likely not going to happen.
MC can unofficially passthrough MQA to a MQA-capable DAC if you use no DSP and set volume to 100%.
-
TY
-
It would be interesting to understand where JRiver is going in terms of the strategy for the future..
For instance will JRiver seek to be available on platforms like Android TV , Apple TV , Roku etc as perhaps a paid app? In other words continue work on the stream server/client. To me it seems that focus has been more on the TV than on the streaming.
Or will JRiver continue to develop as a tool, for a more specialized group of users
For me personally a combination would be to prefer. If available on the popular platforms of today my family would start using it which they do not today. The reason for this is the use requires the use of a PC instead of just starting a app present on the entertainment systems in the house..
I have been an enthusiastic JRiver user for 22 years.
-
It would be interesting to understand where JRiver is going in terms of the strategy for the future..
For instance will JRiver seek to be available on platforms like Android TV , Apple TV , Roku etc as perhaps a paid app? In other words continue work on the stream server/client. To me it seems that focus has been more on the TV than on the streaming.
Or will JRiver continue to develop as a tool, for a more specialized group of users
For me personally a combination would be to prefer. If available on the popular platforms of today my family would start using it which they do not today. The reason for this is the use requires the use of a PC instead of just starting a app present on the entertainment systems in the house..
I have been an enthusiastic JRiver user for 22 years.
Please use this thread:
https://yabb.jriver.com/interact/index.php/topic,128299.0.html