More > JRiver Media Center 22 for Windows
Feature Requests
imugli:
--- Quote from: mattkhan on May 14, 2016, 03:34:28 pm ---Is the intention to create a new theatre view, with a cross platform implementation, or to port the existing theatre view to linux/mac?
it would be nice to enable a single library to be used across platforms too btw (that path problem whereby a library contains platform specific paths rather than some logical path name that has platform specific implementations depending on which platform you run on).
--- End quote ---
I can play my Linux library on my windows PC no problem. Can't remember if it works the other way, TBH, but happy to check and get back to you. I had to mount the folder / drive, then mount that to a samba share folder, then import from that (at least I think that's what I'm doing - I'll double check and get back to you). My problem with this is that the Linux library won't import file formats that cannot be played on Linux, so for instance I can't serve my ifo files from the Linux library.
mwillems:
--- Quote from: imugli on May 15, 2016, 09:57:45 am ---I can play my Linux library on my windows PC no problem. Can't remember if it works the other way, TBH, but happy to check and get back to you. I had to mount the folder / drive, then mount that to a samba share folder, then import from that (at least I think that's what I'm doing - I'll double check and get back to you). My problem with this is that the Linux library won't import file formats that cannot be played on Linux, so for instance I can't serve my ifo files from the Linux library.
--- End quote ---
The issue isn't that client/server doesn't work at all cross platform. It's that the filepaths are necessarily different so the clients don't have direct access to the files which has a performance penalty and breaks playback for certain file formats (i.e. prevents .ifo playback even if you could import them on Linux).
It's a tough issue with a couple possible solutions. I've been demoing a few other home media server solutions for research related to the competitive disadvantages thread, and I think the way emby addresses this exact issue is clever. They just have a "path substitution" setting that let's you specify an alternate "front" of the path and then reverses the slashes if needed. The emby server also tells you in real time when clients are "direct playing" the files or getting served by the server. So for example, if your linux audio is at /home/user/data/Audio, and your windows clients have the samba share mounted at X:\Audio, you can just enter "/home/user/data/" and "x:\" as the substitution. I have an emby server running on a Linux box, and my windows emby clients can easily direct play the files. It's an elegant solution (and I think one of the several that's been suggested over here as a fix); not sure how much work it was to implement and test for emby, but I can say it works well (at least in my setup).
daveman:
These are features I have requested for several previous versions...
1 - GIZMO - When using gizmo on my computer or phone, the biggest limitations is the inability to see the entire track name below the cover art. Is there a way to display the full Name either by having 2 lines of text or having the name scroll horizontally, or if move cursor over the image there is a popup? Also, if I make changes to the code, it always gets written over when one does an update to JRiver.
2 - GIZMO - I would like to see a Gizmo option for "visitors" that is, they ONLY get the This Location option. Can this be included in an upcoming version
3 - MC and WDTV - Documented Problem that needs resolution - as per https://yabb.jriver.com/interact/index.php?topic=93277.msg644242#msg644242 Whenever I add new media, MC automatically imports it. That works fine On the WDTV, when i go into the video listings, the media shows up under the RECENT tab. However, when I navigate through folders the folders do not get updated unless I actually turn off [close] MC (Media Server) and then turn it back on.
4 - As per a past post http://yabb.jriver.com/interact/index.php?topic=78510.msg533889#msg533889 - In the OVERVIEW, one can see all media servers that are connected to JRiver.
However, it does not seem to show info regarding connected devices using webgizmo or other ipad/android apps. Is there a way to see this info on the host computer? This is an important priece of missing info. I am not sure what would be required to include this info. I understand that one can look at the activity under Services & Plug-ins/Media Network (then select [ServerName] (Library Server) but this does not provide any other details about the device. Anyways, I would prefer to see this info in an overview listing rather than have to search for it. Please add this in so that we can have full information regarding how MC is serving information. Playing Now should show all files being served by MC and not just those in specific zones.
Thanks
Dave
imugli:
--- Quote from: mwillems on May 15, 2016, 10:10:46 am ---The issue isn't that client/server doesn't work at all cross platform. It's that the filepaths are necessarily different so the clients don't have direct access to the files which has a performance penalty and breaks playback for certain file formats (i.e. prevents .ifo playback even if you could import them on Linux).
It's a tough issue with a couple possible solutions. I've been demoing a few other home media server solutions for research related to the competitive disadvantages thread, and I think the way emby addresses this exact issue is clever. They just have a "path substitution" setting that let's you specify an alternate "front" of the path and then reverses the slashes if needed. The emby server also tells you in real time when clients are "direct playing" the files or getting served by the server. So for example, if your linux audio is at /home/user/data/Audio, and your windows clients have the samba share mounted at X:\Audio, you can just enter "/home/user/data/" and "x:\" as the substitution. I have an emby server running on a Linux box, and my windows emby clients can easily direct play the files. It's an elegant solution (and I think one of the several that's been suggested over here as a fix); not sure how much work it was to implement and test for emby, but I can say it works well (at least in my setup).
--- End quote ---
So by direct playing, do you mean playing from a mapped drive? OK, I get it now. Sorry, I was a bit slow on the uptake with that one...
mwillems:
--- Quote from: imugli on May 15, 2016, 10:28:06 am ---So by direct playing, do you mean playing from a mapped drive? OK, I get it now. Sorry, I was a bit slow on the uptake with that one...
--- End quote ---
Yes exactly; direct file access allows clients to just go grab the files via the operating system instead of having to receive them in pieces from the server.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version