Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
|
|
Thread Tools | Search this Thread | Display Modes |
27th January 2022, 08:20 | #21 | Link | |
Lost my old account :(
Join Date: Jul 2017
Posts: 326
|
Quote:
Topic/thread starter 😀 |
|
28th January 2022, 02:11 | #22 | Link |
Registered User
Join Date: Dec 2003
Posts: 485
|
OK so conversion done. So changing the keyint=24 made it track real fast audio and video, but when I'm jumping quickly thru the footage still had the issue where when I took my hand off the jump forward button the playback was jumpy. Even stopping the video and playing still did it. Going back 10 seconds or so played thru that area fine then. Ugh. Oh and the footage even though the call was:
ffmpeg.exe -i <input>.mkv -c:v libx265 -x265-params level=51:high-tier=1:repeat-headers=1:colorprim=bt709:transfer=bt709:colormatrix=bt709:crf=13:chromaloc=0:no-sao=1:info=0:range=limited:vbv-maxrate=17500:vbv-bufsize=17500:keyint=24 -vf crop=1920:816:0:2 -preset slower -pix_fmt yuv420p -sn -an <output>.hevc The footage itself was 1920*816 (2.35:1), at 23.976 (24000/1001) FPS, HEVC (Main@L5.1@Main) With the DTS Master audio - stutters With the DTS Core extracted - Fine now with the keyint Converted to AC3 audio - Fine Guess I either leave the audio I guess and don't fast forward, switch to DTS Core or get the Emby folks to look into issues with their player and DTS XLL audio. Think the core sounds quieter than the master audio but may be me. Last edited by jriker1; 28th January 2022 at 03:33. |
28th January 2022, 23:09 | #25 | Link | |
Lost my old account :(
Join Date: Jul 2017
Posts: 326
|
Quote:
From the information you har given us it seems to be audio relatated, but i’ve seen x265 to have some vbv issues in the past. What happens if you use: ffmpeg.exe -i <input>.mkv -c:v libx265 -x265-params level=41:vbv-maxrate=20000:vbv-bufsize=20000:repeat-headers=1:colorprim=bt709:transfer=bt709:colormatrix=bt709:crf=18:chromaloc=0:no-sao=1:info=0:range=limited:keyint=96 -vf crop=1920:816:0:2 -preset slower -pix_fmt yuv420p -sn -an <output>.hevc If the issue persist that at least should rule out bitrate/vbv/level/tier issues. Last edited by excellentswordfight; 28th January 2022 at 23:17. |
|
29th January 2022, 14:39 | #26 | Link |
Registered User
Join Date: Dec 2003
Posts: 485
|
Is that limited for 1080p? When I used to create my videos thru Premiere Pro and a difference here, was using NeatVideo to get rid of some of the noise, I was using 8,000 for a CBR and 10,000 for shows I liked a lot. I was trying to reproduce CBR with ffmpeg but it's my understanding those settings set thte upper limit to how high a bitrate the encoder can use. This would be a lot higher than what I used to do. I think. And picture seems very clean.
|
29th January 2022, 23:08 | #27 | Link |
Registered User
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,407
|
Don't use VBV to try to get CBR, it isn't meant for that and it isn't good at it.
Do you really need to cap the max rate? Pick a higher crf without VBV (or the normal VBV for the level) for better quality at the same size. If you want to always get the same size use 2-pass and target a bitrate. If you want a flatter bitrate distribution for some reason use qComp. VBV is designed to avoid buffering issues when streaming over a network or off of slow storage. It is not designed to cutoff the bitrate of all the high motion scenes. The rate control works better if you let it fluctuate as it desires, with VBV only stepping in rarely to keep extreme bitrate spikes within the limits of the hardware.
__________________
madVR options explained |
1st February 2022, 23:57 | #28 | Link | |
Moderator
Join Date: Jan 2006
Location: Portland, OR
Posts: 4,771
|
Quote:
For stuff that'll be played of a drive, VBR (either 2-pass VBR or using CRF) will be flat-out better most of the time. |
|
2nd February 2022, 00:01 | #29 | Link | |
Moderator
Join Date: Jan 2006
Location: Portland, OR
Posts: 4,771
|
Quote:
x265 generally picks a sane default level based on the input, and then constrains VBV appropriately for that, so setting VBV isn't needed in a lot of cases. But we want VBV to be used by the encoder in almost all cases. Also, if you know you have a better decoder available, setting that and VBV can improve quality. For example, encoding 2160p24 would default to Level 5 and thus a 25 Mbps max VBV. But if targeting a Level 5.1 decoder, max VBV can be raised to 40 Mbps, which can help quality with high complexity or grain. |
|
2nd February 2022, 13:13 | #30 | Link | |||
Lost my old account :(
Join Date: Jul 2017
Posts: 326
|
Quote:
It's also in the docs Quote:
Quote:
Last edited by excellentswordfight; 2nd February 2022 at 15:41. |
|||
2nd February 2022, 18:05 | #31 | Link | |
Moderator
Join Date: Jan 2006
Location: Portland, OR
Posts: 4,771
|
Quote:
|
|
Tags |
ffmpeg, h.265 |
|
|