Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Goatshade]

The title is pretty self-explanatory. See here for a use case.

Can confirm via my own conversions that this is a viable solution to high-resolution mobile streaming and bottlenecking.

[Goatshade]

Anybody?

[Goatshade]

Hello?

I've found another use case: My TV is DLNA-compliant but doesn't support PCM; however, it does support FLAC. I know. It's weird.

[AndrewFG]

PCM L16 is in fact the only format that must be supported in order to comply with DLNA certification rules.

So if your renderer does not support L16 then it is in fact NOT compliant with DLNA..

[bob]

Also, I looked at the flac conversion issue a long time ago.
From what I remember, you cannot do a seek on flac during a streaming conversion unless it's in an ogg container and I don't know of anything that will play that.

[Goatshade]

PCM L16 is in fact the only format that must be supported in order to comply with DLNA certification rules.

So if your renderer does not support L16 then it is in fact NOT compliant with DLNA..

Interesting. Maybe I'll tinker with it further and see if there was something wrong with my conversion options.

[Goatshade]

Interesting. Maybe I'll tinker with it further and see if there was something wrong with my conversion options.

I figured out the issue:

It would appear that my TV doesn't support bit depths above 16-bit, sample rates above 48,000 kHz, or PCM with headers. Changing the output format to PCM L16 No Header and the Output Format options to down-sample anything above 48,000 kHz down to that level enables play-back.

I appreciate the insight!

...I would still use FLAC as a DLNA conversion option for mobile, though, even without seeking.

[Goatshade]

Sorry, additional question: What does it mean when a given DLNA renderer does not advance to the next track upon reaching the end of the previous in a playlist and just stops instead? Is there any way to get around this?

My TV is doing this when content is pushed to it. The forwards and backwards buttons work as expected; it just won't advance automatically.

EDIT: Oh, wait. It just worked. How odd. Further testing required.

[bob]

Sorry, additional question: What does it mean when a given DLNA renderer does not advance to the next track upon reaching the end of the previous in a playlist and just stops instead? Is there any way to get around this?

My TV is doing this when content is pushed to it. The forwards and backwards buttons work as expected; it just won't advance automatically.

EDIT: Oh, wait. It just worked. How odd. Further testing required.

You can check that the button for repeat option for the zone is not set to stop after each track.

Also, some renderers have issues with the setNextAVTransportURI command used to send the next track gaplessly. If MC detects an issue with the it will disable it. You can see that in the DLNA controller options gotten at by right-clicking on the DLNA renderer zone.

[Goatshade]

I figured out the issue there: Interacting with MC at the server in some ways clears Playing Now—for example, closing MC (while leaving Media Network open). If I leave it alone during play-back, it won't do this.