INTERACT FORUM
More => Old Versions => JRiver Media Center 26 for Windows => Topic started by: PhDSM on January 10, 2020, 10:11:41 am
-
Hello,
I using MC with server and files on a Windows 10 PC, playing either on HDMI or via 3 DLNA renderers ( Raspberries with upmpcli)
Since mid august (on MC25 first and then on MC26) when playing playlist or album on DNLA renderers it sometimes stops or pauses without any reason.
It took me quite long to investigate and understand what was going on (Is it the raspberry , the gizmo remote, the network...) to finally be able to reproduce it.
In fact MC stop playing music after 2 or 3 tracks when album is a SACD or High Res album. It never occurs with MP3 or basic Flac, only SACD or 96k records.
It seems that the conversion of format causing the trouble
Any ideas about that or things to investigate further ?
Regards
Phil
-
Hello,
I using MC with server and files on a Windows 10 PC, playing either on HDMI or via 3 DLNA renderers ( Raspberries with upmpcli)
Since mid august (on MC25 first and then on MC26) when playing playlist or album on DNLA renderers it sometimes stops or pauses without any reason.
It took me quite long to investigate and understand what was going on (Is it the raspberry , the gizmo remote, the network...) to finally be able to reproduce it.
In fact MC stop playing music after 2 or 3 tracks when album is a SACD or High Res album. It never occurs with MP3 or basic Flac, only SACD or 96k records.
It seems that the conversion of format causing the trouble
Any ideas about that or things to investigate further ?
Regards
Phil
I'd like to verify that you see this happen even when playing back on the Windows 10 PC over HDMI (not using DLNA at all)?
-
It doesnt happen when I play over DLNA. All format are correctly played.
Only when playing thru DLNA.
If the list contains Mp3 or flac 44k no problem.
If list contains SACD, FLAC 96, it stops in the middle of the 2nd track for SACD or further tracks for Flac96
If I convert SACD files to 44.1k format, it plays completely
Regards
-
It doesnt happen when I play over DLNA.
Only when playing thru DLNA.
Which is it? :)
-
OOps sorry
It doesnt happen when I play over HDMI. All formats are correctly played.
Only when playing thru DLNA.
-
OOps sorry
It doesnt happen when I play over HDMI. All formats are correctly played.
Only when playing thru DLNA.
What are the settings of your MC DLNA server?
What formats can your renderer play?
You can specify which formats should be converted in the advanced settings for the DLNA server in MC when you choose convert when necessary.
-
I have done more investigations :
the DLNA server I use, is configured as "specific out format"> MP3 High Bandwith
I use it with a Raspbeery Pi DLNA renderer.
If I play a SACD ISO it play well the 1rst track of the list and stop somewhere in the second track
If during the play of the track I do position changes manualy then the next one is played and it stops during the one after next. So If i do some position change every 2 tracks it plays the whole list.
I have another DNLA server configured as "specific out format" > PCM24-Bits
that I configured to play on Hifi device, and which works well
I noticed that If a use this DNLA server (24bits) on the RaspBerry Pi DNLA renderer the SACD plays well
So the problem seems to be linked with the "MP3 High Bandwith" DLNA server which stopped at the 2nd track of a SACD play list
Does that help
-
Try setting the server to convert to WAV or PCM.
-
I have done more investigations :
the DLNA server I use, is configured as "specific out format"> MP3 High Bandwith
I use it with a Raspbeery Pi DLNA renderer.
If I play a SACD ISO it play well the 1rst track of the list and stop somewhere in the second track
If during the play of the track I do position changes manualy then the next one is played and it stops during the one after next. So If i do some position change every 2 tracks it plays the whole list.
I have another DNLA server configured as "specific out format" > PCM24-Bits
that I configured to play on Hifi device, and which works well
I noticed that If a use this DNLA server (24bits) on the RaspBerry Pi DNLA renderer the SACD plays well
So the problem seems to be linked with the "MP3 High Bandwith" DLNA server which stopped at the 2nd track of a SACD play list
Does that help
Interesting.
You might also try under the server advanced options enabling the bitrate field.
-
If during the play of the track I do position changes manualy then the next one is played and it stops during the one after next. So If i do some position change every 2 tracks it plays the whole list.
That sounds to me like the DLNA Renderer is losing connection to the DLNA Server, but if the DLNA Controller talks to the Renderer, which it does when doing a position change, then the Renderer maintains its connection and keeps asking for files from the Server.
That sounds like an issue with upmpcli on the Raspberry Pi DLNA Renderer.
This would be further evidence:
If the list contains Mp3 or flac 44k no problem.
If list contains SACD, FLAC 96, it stops in the middle of the 2nd track for SACD or further tracks for Flac96
If I convert SACD files to 44.1k format, it plays completely
Maybe try changing the "DLNA Controller Options" for the DLNA Server you use with the Raspberry Pi DLNA Renderer.
-
Something else to try just to test, for the DLNA renderer zone in MC that you are playing to, right-click on the zone and under DLNA Controller Options, disable SetNext support.
You'll lose gapless playback (if you were using it) but the results could be informative.
-
Bob, the OP says he encounters the problem when pushing/converting an SACD ISO to hi-res MP3. I don’t know details of how an ISO looks, but isn’t this one where the whole album is in one file, and MC has to break it into individual track files to push/convert?
-
Bob, the OP says he encounters the problem when pushing/converting an SACD ISO to hi-res MP3. I don’t know details of how an ISO looks, but isn’t this one where the whole album is in one file, and MC has to break it into individual track files to push/convert?
Yes that's true.
I'm wondering though if the SetNext logic is causing an issue.
Transcoding/decoding to both mp3 and wav is done inline on each track without waiting for the transcode/decode to finish so the issue shouldn't be with that. It's suspicious that the wav works and the mp3 is an issue.
-
Yes that's true.
I'm wondering though if the SetNext logic is causing an issue.
Transcoding/decoding to both mp3 and wav is done inline on each track without waiting for the transcode/decode to finish so the issue shouldn't be with that. It's suspicious that the wav works and the mp3 is an issue.
Perhaps a timing issue between MCs transcoding to cache, and when MC is sending SetNext: What url is it pushing? Perhaps it’s a url of a transcoded track that’s not all there yet? Perhaps the renderer responds to the SetNext with a GET at a time when the MC transcoder thread is writing to, moving, or renaming from the cache file to the correct url?? Or something like that. (The Seek behaviour that the OP observed might be a clue to delaying such a clash..)
-
Perhaps a timing issue between MCs transcoding to cache, and when MC is sending SetNext: What url is it pushing? Perhaps it’s a url of a transcoded track that’s not all there yet? Perhaps the renderer responds to the SetNext with a GET at a time when the MC transcoder thread is writing to, moving, or renaming from the cache file to the correct url?? Or something like that. (The Seek behaviour that the OP observed might be a clue to delaying such a clash..)
It is a url of a file that's not all there yet but the content-length for what the file will be is correct.
When one seeks it restarts the conversion at that point and gives a new content length.
-
It is a url of a file that's not all there yet but the content-length for what the file will be is correct.
When one seeks it restarts the conversion at that point and gives a new content length.
A half random thought re Content-Length: when transcoding to L16 or WAV if you have a duration then you can exactly calculate a Content-Length, whereas with MP3 you can’t — unless you are using MP3 CBR in some form..
-
A half random thought re Content-Length: when transcoding to L16 or WAV if you have a duration then you can exactly calculate a Content-Length, whereas with MP3 you can’t — unless you are using MP3 CBR in some form..
It is using CBR :)
-
I did more tests.
In fact 96k/24 are ok, only SACD cause problem, wheteher they are in 1 ISO file or in seprarate .dsf files.
I tried to disable SetNext support but it doesn't change anything
If I use DNLA server converting to PCM24-Bits => every ok
If I use DNLA server converting to mp3 high => I get the problem
If I use DNLA server converting to PCM16-Bits => I get the problem
regards
-
I did more tests.
In fact 96k/24 are ok, only SACD cause problem, wheteher they are in 1 ISO file or in seprarate .dsf files.
I tried to disable SetNext support but it doesn't change anything
If I use DNLA server converting to PCM24-Bits => every ok
If I use DNLA server converting to mp3 high => I get the problem
If I use DNLA server converting to PCM16-Bits => I get the problem
regards
Is it possible the input file size is > 2gigs?
-
About the size I have also the problem with separate .dsf files which are below 500M
iIt seems linked with the DSD format