ViritualDubMod issues

[Magnus]

Hi,
I'm not all that sure that this would be the most suitable place for this post.
But what ever.

I have for some time now, had a certain problem with "vdubmod", when I try to preview'
frames and such in the software (trying to select sections of .d2v files to render out/compress).
Now. It's not as a I press play that I cannot preview, but rather as I use my arrows to skim
through frame-by-frame that it won't load the frame that I am located at, unless I hit the play button.
And as I hit the play button, it will preview the frame, but will continously "preview" but the video won't
show, it freezes on the frame it was located at as I hit play.

Please the Org, any suggestios of how to fix this?
I'm asking for any way that might fix it, before I turn to reinstallment.

Thanks in advance,
H. Magnus "ZetZu" Kylliäinen.

[Mister Hatt]

Sounds like a hell slow script if anything. Use VirtualDub latest version instead of mod, it was updated this decade.

[Mister Hatt]

Paste your script please.

[Magnus]

It's not because of any script.
Never had any problems with it before, just once I re-installed it all after a format.

Code: Select all

mpeg2source("K:\End of Evangelion\VIDEO_TS\End of Evangelion.d2v",cpu=6)
ConvertToYV12(interlaced=true) 
Telecide(order=1)

and my 2nd alternative. a simple directshowsource script...

Code: Select all

#ASYNTHER DirectShowSource
DirectShowSource("D:\Evangelion 1.11\Evangelion_1.11_You_Are_(Not)_Alone_(2009)_[720p,BluRay,x264,DTS-ES]_-_THORA\Evangelion_1.11_You_Are_(Not)_Alone_(2009)_[720p,BluRay,x264,DTS-ES]_-_THORA.mkv")

[Mister Hatt]

>Using DSS on MKV
>Using Telecine() on anything
>Using CPU argument in DGDecode

These aren't particularly slow, but they are certainly almost the worst way to do both things. Going by your scripts it sounds like VDM is the issue and not avisynth. Upgrade to the latest vdub, it came out in January IIRC. VDM hasn't been fixed or updated since 2005, it's no wonder it's not working so great.

[Magnus]

>Using DSS on MKV
>Using Telecine() on anything
>Using CPU argument in DGDecode

These aren't particularly slow, but they are certainly almost the worst way to do both things. Going by your scripts it sounds like VDM is the issue and not avisynth. Upgrade to the latest vdub, it came out in January IIRC. VDM hasn't been fixed or updated since 2005, it's no wonder it's not working so great.

Well, I had NO problem what so ever, with any of these scripts before.
Results were also great, so yeah. I also got the newest Vdub, didn't work there either.

Although, I got it to work in AvsP, so I'll probably just write out a script to select the frames I want taken out.


Thanks for the help anyways!

[Mister Hatt]

Could be vdub rendering like ass, but I don't know that much about vdub. Dump your shiz to lossless or something. Also don't use THORA for sources, their video is horrible, and breaks a lot of things which could actually be causing this although I doubt it. They remove the SEI header from their videos, which actually corrupts h264 quite heavily.

[mirkosp]

If you absolutely need to use a THORA encode, then what you should do is use DSS2 to load it and set windows' directshow to use coreavc instead of ffdshow. That way it'll render properly (as Hatt explained, THORA encodes break compatibility and thus make the video fail on pretty much anything that isn't CoreAVC 2.0) and be frame accurate (or at the very least MUCH more than the plain directshowsource is).

[Mister Hatt]

Don't use DDS2 on MKV. Just, don't. Using CoreAVC in avs is a bad idea. You never need to use a THORA encode. Ever. There is ALWAYS an alternative.