INTERACT FORUM
More => Old Versions => JRiver Media Center 21 for Linux => Topic started by: kstuart on June 02, 2016, 03:47:47 pm
-
Are there any MC21 for Windows functions that are not currently supported in MC21 for Linux ?
I ask because I remember that - at first - there were major swaths of MC21 for Windows that were not (yet) supported in the stable Mac releases.
(This is as opposed to bugs, of course.)
-
There are a few -
No remote control support.
No TV support
No Theater View support
Video Playback support not as complete
There may be others, but they're the main ones I think.
-
Video support not as complete examples being no MadVR or any Directshow filters, for example.
-
By the way, everything above, other than the video support, is included in the "Plans for MC22" list.
-
That's correct, but bear in mind that doesn't mean "Plan to be there when 22 is released". I believe they are more v22 lifecycle plans.
-
Other things currently missing (or less robust) on Linux:
1) Cannot open files in an external program.
2) No integrated web browser
3) No loopback or line in of any kind.
4) No cross platform filepaths, which has implications for client/server setups (e.g. so you won't be able to play DVDs in .ifo format on a client).
5) Very limited Data file support (works for server, not for client)
6) No native DSD playback (only DoP) (this is a limitation of the OS not MC, Linux has no equivalent to ASIO which is required for native DSD playback)
*7) Start on boot checkboxes do not work (you'll need to script auto start if you want it).
*8 ) Related to incomplete video support, the on screen display for video is currently broken. Playback works, but it can be hard to use the OSD controls to pause, skip ahead, or stop playback. Keyboard shortcuts work fine.
There are more, I'm just trying to recall them all (I'll add them as I think of them with a star to indicate later additions).
Also, let me know if you plan on using MC for Linux as a server in a mixed windows and Linux environment. There are some "tricks" you can do. For example, MC for Linux doesn't support theater view, so won't let you edit views for theater view in its interfaces. But if you backup a windows library and import it on a Linux server, the theater view customizations you made on the windows library "come through" and the Linux instance will faithfull serve them to windows clients. Stuff like that.
-
2) No integrated web browser
In my experience with MC, that's a big improvement. :D
6) No native DSD playback (only DoP)
This area is a matter of personal viewpoint, but my elaborate investigation of DSD came to the conclusion that it is technically and sonically inferior to PCM (the latter a very subtle difference, confounded by the fact that the added low level noise makes it often subjectively "better"). After coming to this conclusion, I discovered that many other audiophiles have come to the same conclusion.
Also, roughly 90% (quoted from memory) of DSD recordings have had a PCM conversion in the middle of the recording or mastering process, so there is thereby no inherent advantage to "native DSD playback" for those 90%.
The only thing in the list that I may be using is "cross platform filepaths" if that includes UNC network paths.
-
In my experience with MC, that's a big improvement. :D
Sadly you can't currently launch things in an external browser either (see issue 1) ), so there's no way to access web content from the MC UI at all. It's less of an issue in the absence of theater view, but it pushes MC integration of things like netflix from "fiddly" to "literally impossible."
This area is a matter of personal viewpoint, but my elaborate investigation of DSD came to the conclusion that it is technically and sonically inferior to PCM (the latter a very subtle difference, confounded by the fact that the added low level noise makes it often subjectively "better"). After coming to this conclusion, I discovered that many other audiophiles have come to the same conclusion.
Also, roughly 90% (quoted from memory) of DSD recordings have had a PCM conversion in the middle of the recording or mastering process, so there is thereby no inherent advantage to "native DSD playback" for those 90%.
I also don't care particlarly about DSD; it's a fringe issue, but one that some people care a lot about. I aim for completeness ;D
The only thing in the list that I may be using is "cross platform filepaths" if that includes UNC network paths.
The issue is that Linux paths have slashes in place of backslashes and a different file root (e.g. no drive letters). UNC paths deal with the latter issue, but not the former. So if your server is windows hosted, your linux client will never be able to have "local" access to the files. This mostly doesn't matter as the server JRiver instance will just stream the audio or video across to the client, but this is 1) less efficient and so is more likely to expose a weak home network (i.e. more likely to get drop outs with a weak network connection) and 2) breaks playback of certain file types, most notably video discs ripped in .ifo structure and may also affect .ISOs (I can't test as I have no files in .ISO format).
-
Copy and paste is also hit-and-miss right now - it doesn't even work for me in my tests between a text editor (gedit) to MC and vice versa.
-
No cd ripping in linux mc.
Assets not supported in linux mc (that's pdf files etc, see http://yabb.jriver.com/interact/index.php?topic=92389.0)