Transcode and play to chromecast audio stops after 30 to 60s

[stefaandr 0]

Hi,

 

I'm running Emby server 3.5.3.0 on a Raspberry Pi 2 with Ubuntu 18.04 armhf (using the emby .deb package).

Playing audio to my chromecast audio from a file (.mp3) that doesn't require transcoding seems to work. However, I have a selection of .ogg files, which do trigger transcoding, and those mostly just stop playing after 30 to 60s, on rare occasions with an audio hickup on the way. The dashboard then shows "Transcoding - 384 kbps ts aac", and the transcoding progress bar always reaches the end, however, the "track playing" progress bar halts just as the audio does.

 

The stopping of the audio (and as I believe, also the rare hickups) coincides exactly with messages such as these in logs/embyserver.txt:

2018-10-28 14:13:33.838 Info HttpServer: HTTP POST http://192.168.2.112:8096/emby/Sessions/Playing/Progress. UserAgent: Mozilla/5.0 (X11; Linux armv7l) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.86 Safari/537.36 CrKey/1.35.137090
2018-10-28 14:13:33.857 Info HttpServer: HTTP Response 204 to 192.168.2.119. Time: 19ms. http://192.168.2.112:8096/emby/Sessions/Playing/Progress
 

I've tried this mostly from my Android phone, using Emby version 3.0.21. However, I've done some testing on my laptop Linux Mint 18.2 (Ubuntu 16.04 derivative), running chromium-browser 70.0.3538.67-0ubuntu0.16.04.1. Connecting and playing to the same chromecast audio gives the exact same symptoms.

 

My server has been (re-)set up from scratch today, with default configuration values, except disabling all DLNA, blast, port mapping, and enabling debug logging.

 

I'm a bit at a loss here as to what is happening. Any help would be appreciated. I'm attaching the logs from my last test run.

 

Many thanks,

Stefaan

embyserver.txt

ffmpeg-transcode-e302fa3e-8ab0-412f-93c3-dfa085423db8.txt

[stefaandr 0]

Of course, I can confirm that non-transcoding tracks (mp3) play fine. It's just my .ogg files that give this problem.

 

I realize pinpointing the problem based on my info may be hard... any hints on how to produce more useful or extensive debug info would be appreciated.

Thanks

[Luke 37247]

Hi, this should be resolved for the next release of emby server, thanks.

[stefaandr 0]

Oh, splendid! Looking forward to that.

Does it make sense for me to try the beta / should it already be fixed in 3.6.0.57?

Many thanks, Emby is a great project!

[Luke 37247]

No, in the next beta. Thanks for the feedback.