Still attempting to edit on my new PC and getting all my amvapp shit re installed ect, ect.
While I tried applying a script to my footage and hit F5 I got an error message dirrecting me to my resize.
I opened it up as "directshowsource" and the file is a .mkv
I would appreciate any help if anyone can give it.
virtualdubmod scripting issue
- mirkosp
- The Absolute Mudman
- Joined: Mon Apr 24, 2006 6:24 am
- Status: (」・ワ・)」(⊃・ワ・)⊃
- Location: Gallarate (VA), Italy
- Contact:
Re: virtualdubmod scripting issue
The error there is that you shouldn't use the x but the comma. I have other suggestions though:
1) Don't use directshowsource, but ffvideosource. Look around in the section for more info about it.
2) The converttoyv12() is useless since your input is already yv12.
3) That filename tells me way more than enough to know that your input is progressive already. You do NOT want to use tfm and tdecimate.
4) Don't use lanczosresize, use spline36resize instead. Just for the sake of clarity: spline36resize(1280,720)
5) Why assumefps(24)? Some particular reason to edit at that instead of 23.976? But oh well, that's a non-issue, really, you're actually free on this.
6) MOST IMPORTANT OF ALL, DON'T USE VDUBMOD! Use the latest stable vdub instead! virtualdub.org is the homepage, moving from there is easy, and you'll have to choose between 1.9.11 stable and 1.10.0 experimental. I personally use 1.10.0, but feel free to use 1.9.11 if you want to be safer.
7) If the reason for using vdubmod was the avs editor, avspmod is a much better replacement: http://forum.doom9.org/showthread.php?t=153248
1) Don't use directshowsource, but ffvideosource. Look around in the section for more info about it.
2) The converttoyv12() is useless since your input is already yv12.
3) That filename tells me way more than enough to know that your input is progressive already. You do NOT want to use tfm and tdecimate.
4) Don't use lanczosresize, use spline36resize instead. Just for the sake of clarity: spline36resize(1280,720)
5) Why assumefps(24)? Some particular reason to edit at that instead of 23.976? But oh well, that's a non-issue, really, you're actually free on this.
6) MOST IMPORTANT OF ALL, DON'T USE VDUBMOD! Use the latest stable vdub instead! virtualdub.org is the homepage, moving from there is easy, and you'll have to choose between 1.9.11 stable and 1.10.0 experimental. I personally use 1.10.0, but feel free to use 1.9.11 if you want to be safer.
7) If the reason for using vdubmod was the avs editor, avspmod is a much better replacement: http://forum.doom9.org/showthread.php?t=153248
- ExSphere
- Joined: Sat Feb 03, 2007 9:43 pm
Re: virtualdubmod scripting issue
and another question mirk?
when I go to video < compression, what would be the best choice for editing? lagarith, uncompressed RGB, if so use multi threading, mode YV12?
dont wanna mess up my quality by messing around with color space is all.
when I go to video < compression, what would be the best choice for editing? lagarith, uncompressed RGB, if so use multi threading, mode YV12?
dont wanna mess up my quality by messing around with color space is all.
- mirkosp
- The Absolute Mudman
- Joined: Mon Apr 24, 2006 6:24 am
- Status: (」・ワ・)」(⊃・ワ・)⊃
- Location: Gallarate (VA), Italy
- Contact:
Re: virtualdubmod scripting issue
Use UTVideo in YV12 (it's the ULY0 one of the four that you find in the list). Also, be sure to use fast recompress to avoid any colourspace conversion. You can get utvideo 32bit here, if you don't already have it (an older version comes with the newest amvapp, so actually you prolly have to update anyway): http://umezawa.dyndns.info/archive/utvi ... .0-x86.msi
-
- Joined: Tue Dec 25, 2007 8:26 am
- Status: better than you
- Contact:
Re: virtualdubmod scripting issue
Also your source is terrible. The rules here IIRC say not to use pirated material, but if you insist on it, at least use something ripped by a competent pirate. THORA corrupt most of their stuff and might actually have decoding issues, even with ffms2. Caused by forcibly removing the SEI headers instead of just patching x264, if anyone cares.