Virtualdub Workflow test

F

frear

Member
I've tried the VD workflow suggested by James, doing the following:

- shot: 720p50 auto everything, lumix 14-140 dynamic film mode
- VD: import clip, export lossless YUY 4:2:2 no corrections
- VD: added grading curves filter for bleach bypass test
- VD: added grading curves filter for contrast boost
- VD: export lossless YUY 4:2:2
- AviSynth: scripted "layer" filter, for "add" method overlay
- VD: imported script (WOW it worked!) as 25fps for slowmo
- VD: added grading curves filter for more contrast
- VD: exported as MJPEG

Total time: 10 minutes, maybe a couple more (for opening the vimeo account..).
Not bad for a first test!


AviSynth seems really a huge program.. buttons are better, but scripting is sooooo freak.... ;)
 
Hi Uncle, well, to tell you the truth I'm just moving first steps with this tool, it's fun but it's not so easy as an install&run workflow.

However, I'm following the suggestions I got from JamesRitson on a specific thread and could make it work.

First of all... you must install quite an amount of software to get the whole environment ready. I read a list somewhere but found it's outdated: it's easier today and google doesn't help, really.

This is what I got:
1. AviSynth
1.1 Decomb filter
2. FFMPEGSOURCE
3. FFDSHOW (don't know if really needed)
3. MatroskaSplitter (required to open .MTS via DirectShowInput command)
4. VirtualDub (I got latest)
4.1 Grading Curves Filter
4.2 Deshaker Filter
4.3 DirectShowinput plugin (don't know if really needed)
5. VideoPad (or your editor of choice)

And some codex
5. Lagarith (lossless)
6. Utvideo (lossless, awesome but I found it not so portable)
7. StaxRip (cool conversion sw that includes the x267 codec)

n.7 includes lots of stuff (i.e. old versions of some the above mentioned programs, that it batch uses). Even if there must be a way to slim it down, the HD is so big that I just don't mind.

I might have forgot to mention something, but once you got everything up and running, there you are. Write a simple script in AviSynth language, open VD, forget all the tutorials you might have read on internet, file-open your script and there it is: your .mts is served in VD.

I don't think either the mts itself or the served file can be called "raw" (since AviSynth serves it via another program called DirectSource).. but that's what worked for me. :)

Cheers.
 
You must log in or register to reply here.
Back
Top