More > JRiver Media Center 26 for Linux

MC26 DLNA functionality has changed

<< < (3/3)

bob:

--- Quote from: berniel99 on August 19, 2020, 07:45:33 pm ---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.

--- End quote ---
Let's try to narrow this down a bit to see where the change is taking place.
If you are in MC and you do a file list and choose to show the BitDepth field in MC, what do you see for the files that are supposed to be 24 bit?

When you are playing the file from JRemote, what is your output device? The Player zone in MC? Some other zone in MC? The device zone in JRemote?

berniel99:
OK.

1. In MC, in the file list it the files shows up as 16bit.
2. The Zone is set to "Player" which is the default. (I have never used the Zone functionality)

JRemote is therefore showing what MC is reporting. (good, then its not JRemote)

I am using JRemote, simply as a control point and media is still being output to the Linux client which is just denoted "Player".

bob:

--- Quote from: berniel99 on August 20, 2020, 08:31:45 pm ---OK.

1. In MC, in the file list it the files shows up as 16bit.
2. The Zone is set to "Player" which is the default. (I have never used the Zone functionality)

JRemote is therefore showing what MC is reporting. (good, then its not JRemote)

I am using JRemote, simply as a control point and media is still being output to the Linux client which is just denoted "Player".

--- End quote ---
So what that says to me is that the DLNA server is showing you the content directory as it will be when the DLNA server transcoded the content.
We basically do the same thing when you configure our DLNA server to transcode content.

You should check to see if your DLNA server settings can be tailored to MC better, in other words it really should never have to transcode content. MC can basically play anything.

berniel99:
What you say may be right, but the Synology documentation does not say that that will occur if you leave "transcode" unselected (as shown in the attached screenshot).  The only two "profile overrides" that work with MC26 are "Windows Media Center" and "Roku", shown in the second screenshot, both have the same effect on MC26.

The behaviour shown by the Synology DLNA to other applications, eg. VLC and Foobar 2000, suggest that no transcoding is taking place.

Navigation

[0] Message Index

[*] Previous page

Go to full version