Choppy audio and pixelating video across multiple clients

[rfischman 1]

I'm seeing pixelating video and getting choppy audio across multiple clients to include:

Samsung Galaxy S8

Web Client on Chrome

iPad Mini 4 with iOS 12

 

The server version in the logs will show 3.6 beta, however I saw the same choppiness in 3.5.3.  For comparisons, I shutdown emby and fired up plex on the exact same hardware and played the same live TV station with no choppiness.  I did see several errors in the ffmpeg log files.  Choppiness occurs with hardware acceleration on and with it off under the transcoding options

 

ffmpeg and server logs are attached

 

embyserver-63673411232.txt

ffmpeg-transcode-0c36ee09-f2cb-4c7c-85bf-6b94a56d207c_1.txt

embyserver-63673412567.txt

[Luke 42083]

Can you provide an ffmpeg log with qsv off? thanks.

[rfischman 1]

Sure thing.  Here's the ffmpeg log with qsv turned off.  Choppiness is still there but not quite as severe.  The video pixelation wasn't as bad, and instead of skipping it would pause playback and then resume periodically.  Noticed it occuring more on the web client to chrome then on the iPad or the Galaxy S8.  Had all three going at the same time on the same live stream

 

 

ffmpeg-transcode-a1c3482f-3c5d-4b7d-8f82-0829621b2d1a_1.txt

[Luke 42083]

thanks.

[rfischman 1]

@@Luke, are there updates in the new beta that address any of the transcoding errors?  interested in giving it a try if there was something changed.

Thanks!

[Luke 42083]

You could try it yes.

[rfischman 1]

Cool. Have it running will report back. Also just added any android TV and noticed it does direct stream where the other clients I was using would transcode

[rfischman 1]

Unfortunately, it doesn't seem to have made much of a difference.   Still seeing errors in the ffmpeg logs on the decoding.  Whats really interesting is now I'm seeing freezes on direct stream channels such as the HDHomerun Premium channels.   Those channels will start and stream for a few seconds and then they freeze up.  but I don't see any errors in the logs.

 

Directstream and transcode ffmpeg logs are attached for a few different channels.

 

ffmpeg-transcode-cd32cbc7-cd48-4e94-9090-63787f978815_1.txt

ffmpeg-transcode-92e98a48-721e-4a94-8f9c-5a2a0d6fbc83_1.txt

ffmpeg-directstream-5a75b1ee-ab5e-4aaa-b89e-1f3f9e6cc844_1.txt

ffmpeg-directstream-b2d1ca60-0f2f-4045-995e-60807185d878_1.txt

embyserver.txt

[Luke 42083]

I would try dropping the in-app quality setting and see if that helps. Thanks.

[rfischman 1]

Will do.  Also removing McAfee from the server and seeing if that helps at all..  Not seeing an impact on processor utilization but want to take as many external influencers out of hte mix.

 

@@Luke, any suggestions for settings to use?  I've got the web browser (Chrome) set to auto for home network quality and chromecast quality.  Sitting on a gigabit network connection to the server, happens to be on neighboring switch ports.

Edited September 26, 2018 by rfischman

[rfischman 1]

Another data point for this issue....  I just tried playback on the emby theater application on Windows 10 and the web client in chrome browser simultaneously pulling from the same stream (HD Homerun's USA channel).  Both players were set to auto for the playback quality.

 

The Emby Theater app played back with no problems at all, while the web player in chrome froze up playback after about 15 seconds.  I was able to exit the player, go back to the guide and restart playback with the exact same result...  Meanwhile the theater app played back no problem.

 

Tried the same thing with a broadcast channel (local channel 10.1 off the antenna) and similar result - the theater app chugged along with no issue while the web player sputtered occasionally.

[Luke 42083]

Thanks for the info. I would still suggest dropping the in-app quality setting. Thanks.