Audio transcoding not working

[oneuser 0]

Hello,

I am trying to make Emby transcode ogg files (mp3 files play OK) to my Pioneer amplifier, but really cannot make it work. When I try to play ogg file, on the Pioneer only Connecting is displayed. 

Probably I have not configured profile correctly, but there is no documentation, and posts about the lack of it go back to 2015.

I attach log.

My profile settings are Container:mp3, Codec:mp3 for Direct Play and Container:ogg and Codec:ogg (tried also mp3) for Transcoding (all for Audio)

excerpt.txt

Edited December 31, 2020 by oneuser

[oneuser 0]

So I set DirectPlay to mp3/mp3 for Container/Codec and the same values for Transcoding - this should be OK. This is my only profile.

Still, when I try to play ogg files with VLC, it shows that the stream is ogg (and the amplifier still doesn't play them, obviously)

 

[Luke 42077]

Hi, what exactly did you do?

[oneuser 0]

Hi,

Below you can see my current setup.

I try to play a file by operating in amplifier/VLC UI. MP3 files behave as expected. 

Attempt to play ogg via the amplifier results in the exchange starting with (then GET/200 sequence is repeated):

2020-12-30 22:56:09.387 Info Dlna: DLNA Session created for Pioneer VSX-S520 F03FC6 - VSX-S520
2020-12-30 22:56:14.160 Info Server: http/1.1 GET http://192.168.0.175:8096/audio/2237/stream.ogg?DeviceId=7d8097d9802f1303815704d46f7681f8&MediaSourceId=5dda6d659422d24a2ecb75843e1d583f&Static=true&PlaySessionId=6e4895136013533efa24e47daf92f6f4. UserAgent: GStreamer souphttpsrc libsoup/2.48.1
2020-12-30 22:56:15.910 Info Server: http/1.1 Response 200 to 192.168.0.125. Time: 1762ms. http://192.168.0.175:8096/audio/2237/stream.ogg?DeviceId=7d8097d9802f1303815704d46f7681f8&MediaSourceId=5dda6d659422d24a2ecb75843e1d583f&Static=true&PlaySessionId=6e4895136013533efa24e47daf92f6f4
 

Here is an mp3 that plays correctly on the amplifier:

2020-12-30 23:03:54.281 Info Server: http/1.1 GET http://192.168.0.175:8096/audio/830/stream.mp3?DeviceId=7d8097d9802f1303815704d46f7681f8&MediaSourceId=1e555f69aea58f549975a7da55395395&Static=true&PlaySessionId=348ac02c3718b4e61ffdd9aa919b412b. UserAgent: GStreamer souphttpsrc libsoup/2.48.1
2020-12-30 23:04:08.422 Info Server: http/1.1 Response 200 to 192.168.0.125. Time: 14142ms. http://192.168.0.175:8096/audio/830/stream.mp3?DeviceId=7d8097d9802f1303815704d46f7681f8&MediaSourceId=1e555f69aea58f549975a7da55395395&Static=true&PlaySessionId=348ac02c3718b4e61ffdd9aa919b412b

I don't see any trace of selecting profile or (attempt of) transcoding information in emybserver.txt log (with DLNA debug logging enabled).

Also added full log for interaction via VLC. I would expect ogg file played to be transcoded, but in VLC stream shows as ogg.
 

embyserver (7).txt

Edited December 31, 2020 by oneuser

[Luke 42077]

Did you add identification criteria to ensure that your profile is being used?

[oneuser 0]

I tried "Pioneer" for manufacturer and "Pioneer VSX-S520" for other items. How can I trace the profile matching process/get values to put there. I would think that empty identification matches all???

Edited December 31, 2020 by oneuser

[Luke 42077]

You can't force it. You have to put something there that will work. There's two methods of identification and both need to be filled out. You could try manufacturer Pioneer. and then for http headers user agent pioneer.

[oneuser 0]

Not working, see device descriptor below and profile identification settings. Is there anything wrong about it?

		<friendlyName>Pioneer VSX-S520 F03FC6</friendlyName>
        <manufacturer>Onkyo &amp; Pioneer Corporation</manufacturer>
        <manufacturerURL>http://www.pioneer-audiovisual.eu</manufacturerURL>
        <modelName>VSX-S520</modelName>
        <modelNumber>Digital Media Client</modelNumber>

 

[Luke 42077]

You need to also add one http header. If you're playing from the device, that will use the http headers. If you're remote controlling from Emby, then that will go by the identification manufacturer/friendly name that you already filled out.

That's what I meant by both detection methods. Also just pick one between friendly name and manufacturer. Adding two fields will just make it more specific and less likely to match.

[oneuser 0]

Still no luck.

I used Friendly name "VSX" because of:

"Info Dlna: DLNA Session created for Pioneer VSX-S520 F03FC6 - VSX-S520" and "<friendlyName>Pioneer VSX-S520 F03FC6</friendlyName>"

and header "souphttpsrc" because of:

"Info Server: http/1.1 GET http://192.168.0.175:8096/audio/5545/stream.ogg?DeviceId=7d8097d9802f1303815704d46f7681f8&MediaSourceId=392c61d213f295613c361d5353bf51f0&Static=true&PlaySessionId=8ebd9c9fc96d2f80d38d1b8e6123f28a. UserAgent: GStreamer souphttpsrc libsoup/2.48.1"

[oneuser 0]

FWIW, I noted significant differences comparing to my Panasonic TV (for which a predefined profile works correctly - transcoding is triggered):

Info Server: http/1.1 GET http://192.168.0.175:8096/audio/5545/stream.mp3?DeviceProfileId=c6e18eb28eba37b7c818b1eb775a226c&DeviceId=055888377b2a34a46e7810caa3971351&MediaSourceId=392c61d213f295613c361d5353bf51f0&PlaySessionId=da16874499ca2c807c3e0bbc85f5bf77&AudioCodec=mp3&AudioBitrate=192000&TranscodeReasons=ContainerNotSupported. UserAgent: 

Note - it requests .mp3 file, while it's actually an .ogg file, it has more parameters and empty User-Agent (however for other requests the header is "UserAgent: Panasonic MIL DLNA CP UPnP/1.0 DLNADOC/1.50")

[oneuser 0]

So, problem solved.

I went to Emby source and found the place where profile matching is done. There I noticed debug messages that were never shown in Emby log despite enabling DLNA debug logging. So I enabled debug logging on the debug page as well and then got actual debug logging. From there I could determine actual headers used by "uPnP" part of client-server conversation (dLeyna/0.5.0 GUPnP/0.20.13 DLNADOC/1.50 in my case) and set up working HTTP header parameter.

There are so many bad parts in Emby for this experience, especially for a freemium project...

- Help button for DLNA configuration leads to empty wiki page which leads to knowledge base with NO items on DLAN whatsoever.

- When enabling DLNA debug logs there is no notification that global debugging needs to be turned on as well.

- When enabling DLNA server there is no information that a correct profile needs to be set up.

- Complete lack of configuration information/parameter validation in the web UI.

Amateurish and sloppy .

 

 

[Luke 42077]

Hi, yes we need to improve the user experience for dlna configuration but the reality is that it will always be a place that will mostly target advanced users. That limited audience is the main reason it keeps getting leapfrogged in priority by other development. But we will get there. Thanks for the feedback.