More > JRiver Media Center 26 for Linux
MC26 DLNA functionality has changed
berniel99:
Hi Bob,
Thanks for looking this up for me. The issue only came to my attention when I upgraded from MC24 to MC26. (not MC25) Yes I have a huge music library with over 25,000 songs. Yes the Synology NAS has updated its functionality many times over the years, but not recently and certainly not a the time that I upgraded the JRiver client. I have since experimented with different DMA profiles in the Synology for the JRiver client and found another one that appears to work slightly better. The one marked "Roku" does not have the error message and appears to work fine. (This is a manual override settings)
I am guessing that since the NAS is able to report details about the client software that connects to the media server, that there is something identifying that you send to the server. It reports the client as "JRiver Inc. <machine name>". If Synology know the exact client that is connecting, perhaps, one can be custom built in the NAS to better match the requests that you send. (I don't know how to do this).
I know that you have no control over Synology software but it is one of the big players in the market and it would be great to have this functionality working again (i.e. automatically). Any help would be appreciated. At the moment I am having to manually change the profile in the NAS every time I want to listen to music. This is not a good experience when you have to do it every day.
Cheers,
Bernie.
bob:
--- Quote from: berniel99 on August 14, 2020, 06:46:02 pm ---Hi Bob,
Thanks for looking this up for me. The issue only came to my attention when I upgraded from MC24 to MC26. (not MC25) Yes I have a huge music library with over 25,000 songs. Yes the Synology NAS has updated its functionality many times over the years, but not recently and certainly not a the time that I upgraded the JRiver client. I have since experimented with different DMA profiles in the Synology for the JRiver client and found another one that appears to work slightly better. The one marked "Roku" does not have the error message and appears to work fine. (This is a manual override settings)
I am guessing that since the NAS is able to report details about the client software that connects to the media server, that there is something identifying that you send to the server. It reports the client as "JRiver Inc. <machine name>". If Synology know the exact client that is connecting, perhaps, one can be custom built in the NAS to better match the requests that you send. (I don't know how to do this).
I know that you have no control over Synology software but it is one of the big players in the market and it would be great to have this functionality working again (i.e. automatically). Any help would be appreciated. At the moment I am having to manually change the profile in the NAS every time I want to listen to music. This is not a good experience when you have to do it every day.
Cheers,
Bernie.
--- End quote ---
This is the user agent for MC26 (when running on a Mac):
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_2) AppleWebKit/601.3.9 (KHTML, like Gecko) Chrome/75.0.3770.100 Safari/601.3.9 JRiver_Internet_Reader/2.0 UPnP/1.0
Here is the user agent for MC24
User-Agent: OSX Darwin, UPnP/1.1, JRiver Internet Reader/2.0 (compatible; Windows-Media-Player/10)
There were a few changes in MC26 because we are trying to conform to a more browser friendly user agent for streaming media playback.
The key really is likely to be JRiver_Internet_Reader/2.0 instead of JRiver Internet Reader/2.0
From what I understand the spaces were not standard in the string (versions prior to MC26).
berniel99:
Interesting. Do you think that the Synology NAS takes the "compatible; Windows-Media-Player/10" text from JRiver and uses a "DMA = Windows Media Center" in it's media server automatically, and responds more appropriately to JRiver when it makes the library request of the first 1000 titles? That may explain why it "just worked" out of the box and now no longer works.
I cannot tell you what is right or wrong since it is not my product to develop, however, it would be good if you could come up with a User-Agent header that worked with both the Synology NAS and MACs.
Here's hoping. Again, I appreciate your research, bob.
Bernie.
berniel99:
I noticed another change today in the DLNA functionality. I normally operate my media server by remote control using the JRemote app on my iPhone. When I was playing a song that was originally 96kHz/24bit, the JRemote app reported the file to be 96kHz/16bit. So I chased around today to try to see where this conversion was taking place.
1. I loaded the song directly into MC on the local file system and it was correctly reported on the JRemote app. (Hence we can surmise that JRemote is reporting accurately and the issue is within MC)
2. I then opened up the Options dialogue and MC reports the media source as 96kHz/24bit. Furthermore, I have no options set to do any conversions or set any DSP options.
3. I then loaded up VLC player and played via DLNA and it reports the media as being 96kHz/32bit.
It would be good to get an explanation of what is going on here, given that the system that I have is supposed to be bit perfect.
berniel99:
I installed MC24 today to see whether the bitdepth issue was a change in functionality, or was always wrong. I can confirm that MC24 also had this issue. Should this be submitted as a bug then? The steps are as follows:
1. Fresh install of MC26 (or MC24)
2. Select the audio device that is direct to HW. In my case it is "hw:CARD=HDMI,DEV=3,[ALSA] HDA Intel HDMI,HDMI 0,Direct hardware device without any conversions"
3. Select a DLNA media source (In my case it is the Synology Media Server)
4. Select a 96kHz/24bit source file
5. Confirm that the Options panel shows the file "source as 96kHz/24bit"
6. Connect JRemote as a control device. Play the song. Note the info bar on the bottom shows 96kHz/16bit.
Without being able to record the output of the HDMI cable, I cannot tell you, by measurement, whether the actual output is still 24bit, which would mean that what is reported by MC to the control point is incorrect,
or, whether MC is actually truncating the bits to 16.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version