#Starting with 0.7.4-e5ef8eaf-docker-vaapi all videos jitter

1 messages ยท Page 1 of 1 (latest)

nimble orchid
#

Current version: 0.7.4-f320d848-docker-vaapi
Player: Tivimate
FFmpeg Profile: h264, Vaapi, IHD

Since upgrading to 0.7.4-e5ef8eaf-docker-vaapi and newer I am seeing a jitter in every video I play. I'm not sure Jitter is the best way to describe it. Audio is fine but it appears maybe frames are dropping?

Every version AFTER 0.7.4-6db71f52-docker-vaapi does this. I have included the logs from each version playing the same file, although they look identical to me. NOTE: It does this on every channel and every video.

cyan folio
#

which gpu are you using and can you paste the output of vainfo (from inside the container)

nimble orchid
#

I have a Intel i5-8500 with UHD Graphics 630.

cyan folio
#

can you try qsv to see if it works any better?

nimble orchid
#

When using qsv the videos play without the jitter BUT the problem I experience with qsv is it encodes for a minute, stops encoding, then video pauses and transcoding starts again and video begins playing. It repeats this infinitely

cyan folio
#

can you paste the ffmpeg args there? that's odd behavior

nimble orchid
#

I'm not sure what happened there I meant to only paste the ffmpeg RGS

#

Watching the transcode folder once the GPU stops encoding then the transcode files delete and the video plays for a about 45 seconds and then starts transcoding again. In logs it show a new session transcoding starting after these warnings "Unable to locate session worker for channel 2.6"

cyan folio
#

ill have to test with tivimate to see if it changed its behavior. this should only happen when the client doesn't request the playlist for 60 seconds Information Terminating HLS process for channel 2.6

#

so etv thinks its no longer being watched and it terminates that worker, then tivimate finally requests it again, but it's no longer running so it starts up again. you could try increasing the idle timeout in etv's global settings in the meantime

nimble orchid
#

I will go back to the working version (0.7.4-6db71f52-docker-vaapi) for now. FYI qsv does the same thing in 0.7.4-6db71f52-docker-vaapi as well. I'm not sure how long this has been a problem for me since I only use vaapi.

#

Any ideas on the problem I am having with vaapi in the newer versions?

cyan folio
#

the intel media driver was updated to a pre-release version. hopefully it stabilizes for the final release. nonetheless, qsv usually performs better and it's more likely that we can address the timeout issue that is prematurely terminating the hls worker

nimble orchid
#

If you need me to try anything let me know. I am happy to use qsv if it works.

cyan folio
#

ill add some logging to try to figure out why it's terminating early

nimble orchid
#

I look forward to what you come up with

silk cove
#

can I add that I also have this issue?

cyan folio
#

which cpu?

silk cove
#

11900k

#

I believe that uses UHD 750

cyan folio
#

thanks for the data point. will test with some other intels i have

silk cove
#

this is while using vaapi setting, qsv seems to be even more broken (like shinedou said, there's no more jitter but there's a lot of artifcating/visual errors)

cyan folio
#

which format are you normalizing to in your ffmpeg profile?

silk cove
#

I use the normalize loudness function, but I'm not sure what you mean other than that

cyan folio
#

video format

#

in the ffmpeg profile editor in etv, it's the first drop down under "video"

silk cove
#

oh I have tried both h264 and hevc

#

hevc definitely is less jittery

cyan folio
#

ok, was checking that it wasn't mpeg2video as that is usually blocky

silk cove
#

I have also noticed if I increase the bitrate and buffer it SEEMS to be slightly less jittery, but not any appreciable amount (especially when there was no jitter before the update)

#

I reverted to the same tag mentioned (6db71f525d46c465706521e314c1fa4f3dbeae4e-vaapi) and I no longer have any jitter using any of the profiles (hevc or h264)

nimble orchid
#

Any updates on this issue? I'd really hate to lose the ability to update to new versions because of this.

cyan folio
#

latest develop uses ffmpeg 6, which might be better. i haven't been able to reproduce so you'll have to tell me when it gets better

nimble orchid
#

Ok I will try the newest version.

silk cove
#

I am currently on latest (to fix the scanning issue with multi episode titles) and there's no more jitter ๐Ÿ™‚

#

you fixed both my issues in like two days