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. |
11th December 2018, 16:21 | #21 | Link |
Join Date: Mar 2006
Location: Barcelona
Posts: 5,034
|
Why? It does exactly what it says on the tin - setting a key frame every xxx frames.
__________________
Groucho's Avisynth Stuff |
11th December 2018, 17:22 | #22 | Link |
Registered User
Join Date: Dec 2013
Location: France
Posts: 64
|
FILM9 is already working in 2 steps with a Lagarith intermediate file.
The encoding is, of course, in the 2nd step. As has been said, everything works fine except with H264/FullHD encoding. And only with some clips. Probably those who have hectic images that forces the GOP to work more. Therefore, the impact of the GOP should be reduced to limit the memory bug. For the problem of versions W10 : leave aside for the moment. Not everything is for the last 1809. |
11th December 2018, 19:03 | #23 | Link | |
Registered User
Join Date: Mar 2011
Posts: 4,823
|
Quote:
For "force keyframes every" to work exactly as the option name suggests, it'd have to also set --no-scenecut or --scenecut 0, but it doesn't. |
|
11th December 2018, 19:12 | #24 | Link | |
Registered User
Join Date: Mar 2011
Posts: 4,823
|
Quote:
To me though, that makes the problem more odd, given all you're doing at the x264 stage is re-encoding a lossless file. I run XP, so I only have 4GB RAM, with only 3.5GB being usable (due to the video card RAM) and I don't have a problem encoding 1080p, even with a bit of slow Avisynth filtering included in the process. If that's what you're doing, do you need to use FILM9 for the x264 encoding? You could open the lossless file with most GUIs to re-encode it. |
|
11th December 2018, 19:31 | #25 | Link | |||
Join Date: Mar 2006
Location: Barcelona
Posts: 5,034
|
Quote:
Clip encoded with VD2/H.264 8 bit using "Force keyframes every 39 frames": Quote:
Quote:
__________________
Groucho's Avisynth Stuff |
|||
11th December 2018, 19:34 | #26 | Link |
Registered User
Join Date: Mar 2011
Posts: 4,823
|
GillesH,
Is it only VD2 running during the x264 encoding part of the process? I just opened a video with VD2 via an Avisynth script and resized it to 1920x1080 as a quick test. It encoded with x264 fine (I only encoded 1000 frames). It converted to huffyuv in an AVI container without problems and also to huffyuv in an MKV (using VD2). Both lossless files encoded with x264's default settings without an error (using VD2). Last edited by hello_hello; 11th December 2018 at 19:54. |
11th December 2018, 19:50 | #27 | Link |
Registered User
Join Date: Mar 2011
Posts: 4,823
|
The irony there is quite funny.
Even if you're not clever enough to understand, I haven't denied the "force keyframes every" option sets --keyint for x264. Although due to the option name I didn't realise that's what it did originally, which is why I said it could possible use a rename, but --keyint doesn't necessarily force keyframes to be an exact distance apart. Without disabling scene detection, --keyint only sets the maximum distance between keyframes. You might end up with the same result much of the time for low keyint values, as the maximum distance will often be reached before a scene change, but you only have to encode with x264 once or twice to realise --keyint 250 doesn't give you keyframes exactly 250 frames apart. I just opened a video I encoded yesterday with --keyint 250, picked a random keyframe and then looked at the distance to the next one. They were 135 frames apart. How would the VD2 option have forced them to be 250 frames apart instead? Last edited by hello_hello; 11th December 2018 at 23:44. |
13th December 2018, 14:16 | #28 | Link | |
Registered User
Join Date: Mar 2015
Posts: 775
|
Quote:
Honestly I did not put much thinking in it. For me linking this option to "--keyint" sounds reasonable. I needed to do something with the option (either disable it or make it do something), and implementing any behavior other than --keyint is just more effort and maybe unnecessary confusion. As I understand, forcing keys at fixed frames is only good for precise cutting afterwards.
__________________
VirtualDub2 |
|
13th December 2018, 14:21 | #29 | Link |
Registered User
Join Date: Mar 2015
Posts: 775
|
GillesH,
It seems you pass message about crashes from somebody else (rather than yours own). If the person who encounters crash can isolate reproducible case, he/she should report it directly and prepare files, crash reports, logs. This way I may find out what the problem really is and whether it is possible to improve something.
__________________
VirtualDub2 |
13th December 2018, 17:35 | #30 | Link | |
Registered User
Join Date: Mar 2011
Posts: 4,823
|
Quote:
It might work that way for other formats, but now I know it sets the maximum keyframe distance without disabling scene change detection for x264, I know what to expect. Only setting --keyint probably makes more sense most of the time. As I mentioned previously, if the option also set "--scenecut 0" for x264, it'd work as the name seems to imply, but that's probably not too important. Although for x264 at least, you could possibly have the best of both worlds without too much work. The current option for specifying --keyint and automatically enforcing "--scenecut 0", with an additional option to enable x264's scene detection. Or the other way around. If something like that involves too much work, I'd probably leave it as it is (or maybe have the option's name change when appropriate to indicate it sets --keyint instead). Edit: Currently the option is greyed out when selecting a codec for which it doesn't apply, so maybe you could duplicate the option and call it --keyint, and grey out the appropriate option(s) as it'd apply to the selected codec. Just some thoughts.... Last edited by hello_hello; 13th December 2018 at 17:57. |
|
13th December 2018, 18:46 | #31 | Link | ||
Join Date: Mar 2006
Location: Barcelona
Posts: 5,034
|
Quote:
Quote:
__________________
Groucho's Avisynth Stuff |
||
13th December 2018, 20:47 | #32 | Link | |||
Registered User
Join Date: Mar 2011
Posts: 4,823
|
You're beginning to look silly by continuing with this, but here's what I said including the part you left out.
Quote:
Quote:
Ever since then you've been claiming that setting a --keyint and "forcing keyframes every xxx frames" are the same. The option might set --keyint, but as I've said several times, setting --keyint doesn't force keyframes every xxx frames as the VD2 option suggests, it just sets the maximum distance between them. Have you used x264 before? Quote:
Here's the question you ignored. I can only assume you're so intent on proving me wrong you were blinded to it, but I'll try again. Last edited by hello_hello; 14th December 2018 at 00:39. |
|||
13th December 2018, 22:30 | #33 | Link |
HeartlessS Usurer
Join Date: Dec 2009
Location: Over the rainbow
Posts: 10,980
|
Stop squabbling girls, nuff is e-nuff
__________________
I sometimes post sober. StainlessS@MediaFire ::: AND/OR ::: StainlessS@SendSpace "Some infinities are bigger than other infinities", but how many of them are infinitely bigger ??? |
13th December 2018, 23:05 | #34 | Link |
Join Date: Mar 2006
Location: Barcelona
Posts: 5,034
|
Agreed.
@hello*2 Time is too precious to argue with you. Your tendency to mis-quote and deflect is annoying and pathetic.
__________________
Groucho's Avisynth Stuff |
14th December 2018, 00:02 | #35 | Link |
Registered User
Join Date: Mar 2011
Posts: 4,823
|
And yet two days after your last post you returned specifically to spend your time arguing again (and parrot what I said about mis-quoting). Before you leave while pretending not to notice my question for a second time, would you please give me an example of where I mis-quoted you to show you're not blatantly lying.
Last edited by hello_hello; 14th December 2018 at 00:23. |
17th December 2018, 12:26 | #36 | Link |
Registered User
Join Date: Dec 2013
Location: France
Posts: 64
|
Code:
It seems you pass message about crashes from somebody else (rather than yours own). If the person who encounters crash can isolate reproducible case, he/she should report it directly and prepare files, crash reports, logs. This way I may find out what the problem really is and whether it is possible to improve something. Yes, about FILM9, we have user feedback on some issues. But the analysis of these problems is not always easy to identify. Also, in general, these users do not attend Doom9. That said, I confirm that the setting of the "keyint" has improved the x264 encoding for formats FullHD (1920x1080) which is very greedy in memory. The crash has disappeared. This setting in the "Force keyframes every" window is convenient. This makes it possible to enter the value in the line "VirtualDub.video.SetCompression" without difficulty. Thanks for your advices. |
17th December 2018, 13:15 | #37 | Link |
Join Date: Mar 2006
Location: Barcelona
Posts: 5,034
|
I never wrote that you mis-quoted me. Try to read my post again before accusing me of lying.
__________________
Groucho's Avisynth Stuff Last edited by Groucho2004; 17th December 2018 at 22:04. |
18th December 2018, 17:18 | #38 | Link | |
Registered User
Join Date: Mar 2011
Posts: 4,823
|
Quote:
Whoops.... it's been so long since you contributed to discussing the actual topic I almost forget to ask again.... Last edited by hello_hello; 18th December 2018 at 17:57. |
|
18th December 2018, 18:24 | #39 | Link |
HeartlessS Usurer
Join Date: Dec 2009
Location: Over the rainbow
Posts: 10,980
|
Come on girls, stop it, tis getting a tad tedious.
__________________
I sometimes post sober. StainlessS@MediaFire ::: AND/OR ::: StainlessS@SendSpace "Some infinities are bigger than other infinities", but how many of them are infinitely bigger ??? |
19th December 2018, 01:40 | #40 | Link |
Registered User
Join Date: Mar 2011
Posts: 4,823
|
StainlessS,
I count six posts over eight days not on the topic of GillesH's problem or VD2's "force keyframes every" option (related). Two posts from Groucho2004, two replies from me, and two from the armchair moderator. You must have a very low threshold for tedium. |
Thread Tools | Search this Thread |
Display Modes | |
|
|