video artifacts

[drorem99 0]

26-may

Hi,

I recently started seeing video artifacts when using the Roku app and watching liveTV (see attached photo of TV). I sent a debug log this morning (26-may 10:43AM EDT) which was generated while watching ch 2.2 (WBBM Chicago). I'm using an HDHomerun connect (2 tuner model) as the liveTV source and have Emby running on a linux server w/ Ubuntu 20.04.1 LTS w/ emby version 4.6.1.0. I also see the artifacts while using a web browser to port 8096 on the server (see attached screenshot). Curiously, I do *not* see the artifacts when using an Amazon Fire device with the Emby fire app.  I'm unsure when exactly the problem started - I did upgrade to emby v 4.6 recently - I've verified that the Roku Emby app is up to date. I also don't see artifacts when looking at the channels via the HDhomerun windows app. Does anyone have any ideas as to what might be wrong?

thanks.

[Carlo 4561]

Hi, do you have hardware transcoding currently turned on in the server?

Is so as a test can you turn that off to use only software transcoding to see if you still have the same problem?

Thanks,
Carlo

[Luke 42079]

Hi, yes can we please look at an example?

 

Thanks !

[drorem99 0]

Carlo,

I did find HW transcoding was enabled on the server - I turned it off and I'm not seeing the artifacts. I don't recall turning it on explicitly and (as I mentioned) I didn't see this behavior in the past with the Roku app. Did the HW transcoding flag get enabled by default with the recent 4.6 server upgrade? Also - I'm curious why I don't see the artifacts when using the Amazon Fire device and associated app? (wouldn't it have seen the same transcoded video from the server?)

Luke - I'm unsure what you want re: an example? I can certainly turn on HW transcoding again and send whatever would be helpful to diagnose the problem. FYI.. I did turn on debugging on the Roku app and sent a debug log (yesterday 26-may at 10:43AM EDT).

regards,

Doug

[Happy2Play 9781]

Ideally the server log and the ffmpeg log for the specific playback session having issues.

[Carlo 4561]

@drorem99 can you reproduce and send what Happy2Play mentioned above?

[drorem99 0]

Hi,

 

I re-enabled HW transcoding and tuned to ch 2.1 (WBBM Chicago) on the Roku device

around 9:22AM (CDT) this morning (and observed the video problem). I put the files

from the emby server here:

embyserver.txt:

https://docs.google.com/document/d/1FmgiJIIZClcC0VdEfj5VxX8WW6ZNDqVf7s-PjVrXrEg/edit?usp=sharing

ffmpeg-transcode-xxxx.txt:

https://docs.google.com/document/d/1Dxlebd87JPGawaA32NFmDamYN8_y5G3HaKH_OFBgtVA/edit?usp=sharing

thanks,

Doug

 

[Carlo 4561]

Hi, can you just attach them here?

[drorem99 0]

here they are..

embyserver.txt ffmpeg-transcode-05407ff9-84e0-4d81-a23b-0430ec6ef651_1.txt

[Carlo 4561]

Hi, your ffmpeg log file is incomplete.  Can you try this again please?

[drorem99 0]

Carlo,

Here's the files from another try ~13:15CDT. Interestingly, the first live TV station I tuned to - 2.1 WBBM Chicago had good video. Then I tuned to ch 2.2 and it exhibited the artifacts.

Regards,

Doug

embyserver.txt ffmpeg-transcode-a838a10f-cc1e-42e8-a1e4-ec01e5108f0f_1.txt

[Carlo 4561]

Thank you. Nothing looks wrong that I can see.  I can't help but think it's a VAAPI Radeon related issue.

@softworkz do you have any ideas on this?

[softworkz 5068]

2 hours ago, cayars said:

Thank you. Nothing looks wrong that I can see.  I can't help but think it's a VAAPI Radeon related issue.

@softworkz do you have any ideas on this?

Yes - he just needs to follow our HWA setup instructions for AMD 

Edited May 28, 2021 by softworkz

[softworkz 5068]

As a simple rule to keep in mind:   "Mesa Gallium" =>> WRONG

[Carlo 4561]

https://support.emby.media/support/solutions/articles/44001160148-hardware-acceleration-overview

[Luke 42079]

@drorem99 please let us know if this helps. thanks !

[softworkz 5068]

4 hours ago, softworkz said:

As a simple rule to keep in mind:   "Mesa Gallium" =>> WRONG

@drorem99 - Sorry for any possible confusion. That message was targeted at @cayars and  @Happy2Play - I forgot to mention that.