Stuttering during Playback of Movie. 0

[StiffUpperNailTypo 5]

Hey, i am having an issue with playback of this file. 

Attached videos show what im seeing, and the load on the servers network card. 

The file works fine, i can direct play the video without issue (via Windows Share and using VLC). I cannot however force transcoding because 1080 is limited to a minimum of 4Mbps. 

Ive narrowed it down to an issue with Chrome (Version 110.0.5481.78 (Official Build) (64-bit) ) as the issue does not exist in Firefox (v109.0.1 (64-bit)).

 

Is there a  setting i can adjust here to correct this?

2023-02-12 20-08-19.mkv 2023-02-12 20-09-46.mkv

[Luke 38535]

Hi, I'm not able to watch that right now. Can you please describe the issue as well? Thanks.

[StiffUpperNailTypo 5]

30 minutes ago, Luke said:

Hi, I'm not able to watch that right now. Can you please describe the issue as well? Thanks.

its stuttering, like jumping back and forth every half second or so. makes it sort of look like the actors have parkinsons. like its having a problem going from frame to frame.

[Luke 38535]

And so you're looking to force transcoding to resolve this?

[visproduction 182]

Why is the file showing 60fps and playback at 23.976?  Is that expected?  It seems like the original file has issues. You need to find a better original file. If you go frame by frame, the video jumps around.  Does VLC figure it out and auto compensates?  

Edited February 13, 2023 by visproduction

[Happy2Play 9080]

2 hours ago, visproduction said:

Why is the file showing 60fps and playback at 23.976?  Is that expected?  It seems like the original file has issues. You need to find a better original file. If you go frame by frame, the video jumps around.  Does VLC figure it out and auto compensates?  

That is a recording of the issue not the media being played.

But direct playing HEVC in a browser can be problematic and there are thousands of topics on the internet with similar issues.  And every browser will have different results as you have noticed.  But your issues is specific to something Chrome does not like.

Also the quality selector is a bit deceiving as it is about bitrate not resolution so you would have to lower quality below 2Mbps to transcode this media.

@StiffUpperNailTypo

Edited February 14, 2023 by Happy2Play

[StiffUpperNailTypo 5]

21 hours ago, Luke said:

And so you're looking to force transcoding to resolve this?

not necessarily. but i have noticed a lot of playback errors i have encountered can be resolved by transcoding. I would rather not have to do anything to fix this, but ill take force transcoding if that fixes it.

[StiffUpperNailTypo 5]

16 hours ago, Happy2Play said:

That is a recording of the issue not the media being played.

But direct playing HEVC in a browser can be problematic and there are thousands of topics on the internet with similar issues.  And every browser will have different results as you have noticed.  But your issues is specific to something Chrome does not like.

Also the quality selector is a bit deceiving as it is about bitrate not resolution so you would have to lower quality below 2Mbps to transcode this media.

@StiffUpperNailTypo

yeah, i understand that with the bitrate. but to get below 2mbps i need to drop the **selected** resolution to 720p and then it just looks terrible. (attached).

 

i have seen some posts about chrome not likely B frames i think was the term, but im not really up to date on how all this actually works. 

Edited February 14, 2023 by StiffUpperNailTypo

[visproduction 182]

Could this issue have something to do with the CPU requirement to encode in HEVC is greater than x.264 due to adaptive quantization or the motion estimation methods in HEVC are more complex, like using the Uneven Multi-hex for image motion?  So when HEVC encoding runs into this, the encoding estimate time suddenly runs longer than expected and the maybe causes the encoder to drop down to another level of encoding, which results in the jumping around.

I notice the long period of time required to encode in HEVC with high quality settings compared to x.264.  Could it be that the transcoding just didn't estimate this extra time needed because estimate ran on some early example edit of the opening titles that was much easier to encode compared to panning across a detailed scene.  Does that make sense? 

Let me put it another way:  I think picking HEVC with high quality just does not get a correct time estimate and you run into needing something like 20 times the CPU effort, as expected in a complex camera movement or heavy detailed scene, and this trips other auto encoding changes to drop the image compression.  So the auto system works against itself and is essentially not correctly estimating the CPU demand to encode in HEVC.  Or does the encoding increase runs into the max bit rate setting to not be high enough to handle HEVC.  The max bit rate then forces a step down which causes a change in encoding and creates the glitching.

Whenever I manually encode to HEVC and get a very long encode time using highest quality, the end result after many hours, is a high quality video that does not jump around at all.  But that manual encoding speed at say 25 times the playback speed would never be allowed for transcoding.

My guess is you are running into this.  If you want the HEVC quality, you need really top hardware or more encoding time.

Comments? Ha!

Edited February 14, 2023 by visproduction

[Luke 38535]

Is this playback from a device on the same network as the server, or out of network?