Menu
▾
▴
#853 Indexing with ffms2 and cropping or resizing
I appreciate this is a known problem but has there ever been a bug report submitted regarding the issue?
If not, here it is, because it drives me insane.
When indexing with ffms2, cropping or resizing too quickly in the Script Creator (and "too quickly" means not cropping painfully slowly) causes MeGUI to crash.
I don't know why it makes a difference but if I create a script that opens a video with ffms2 and save it, then import that video into the Script Creator as the source video, the problem goes away. That's my current workaround, although it's not ideal for anamorphic video as the source display aspect ratio is lost.
Thanks.
Does this happen also with FFMS 2.23?
Unfortunately it does, but for some reason I don't think it's quite as bad. I can click the copping or resizing arrows a little more furiously before the "object reference not set to an instance of an object" error message appears.
Does lsmash have an option to not index the audio yet? Not that it'd help me as newer versions don't work on XP, but most of the time my motivation for using ffms2 is it indexes faster than lsmash and I'm pretty sure that's because MeGUI can tell it to only index the video. Larger files, especially those with multiple audio streams, seem to take a lot longer to index with lsmash.
I'm fairly sure the ffms2 issue is worse when using one type of Avisynth (installed Avisynth vs MeGUI's portable version) and I think it's worse for the portable verion. I'm currently using the installed Avisynth (2.6) but I can't restart MeGUI to check at the moment as it's in the middle a long encode.
It does not seem that lsmash can nowadays only index the video.
There is not much what I can do about this error here. The crash happens in the unmanged code (either the wrapper or the ffm2 plugin itself). I can try to implement workarounds like a "speed limit" about those changes in cropping/resizing.
To work around the problem is it possible to change MeGUI so it never opens a video with ffms2 directly, or would it be too much hassle?
If implimented, you'd index with MeGUI and ffms2 as usual but MeGUI would create a script that does nothing but open the video, then it could import that script as the video input for the script creator. Doing it that way, you can crop and resize to your heart's content without any danger of it causing a crash.
Not that I'd know, but I assume that wouldn't be too hard to impliment as MeGUI currently does something similar when it can't extract the audio from the source file. MeGUI would still have to take the input display aspect ratio from the source file though, in case it's anamorphic, rather than the imported script.
That's sometimes what I do now, only it'd be easier if MeGUI could do it automatically.
Cheers.
PS I originally posted this in the wrong "thread" so I deleted it and posted again here. Sorry.
Last edit: hello_hello 2016-11-07
I have implemented in 2708 a fix which may help.
Wow! First couple of quick tests seems to indicate the problem has gone. Could I ask what was causing it?
On the subject of ffms2, I think removing the frame rate conversion MeGUI adds to each script would be a good idea and probably should be a priority, and ffms2 could also be re-instated as an indexing option for AVI.
Nothing to do with the cropping/resizing problem, but it relates to this:
https://sourceforge.net/p/megui/feature-requests/591/
Thank you very much!
The update of the preview will be delayed (or even cancelled) so that continuous pressing the mouse button will not cause continuous refreshes which have seemed to cause these issues.
Fixed