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. |
31st March 2003, 18:13 | #1 | Link |
Retired AviSynth Dev ;)
Join Date: Nov 2001
Location: Dark Side of the Moon
Posts: 3,480
|
Using ffvfw to create AviSynth AVI files
Apparently milan has been doing his wizardry again, and this time he has come up with an experimental AVI wrapper for AviSynth.
It is included in his "ffvfw" codec, and enables YV12 data to be passed to any application accepting AVI files. I found some links to binaries: [Removed - see below] Milan says it is at an experimental stage so far, but so far it has worked fine for me. You create a script - open the "makeAVIS" utility that is a part of ffvfw - open the script here and save the new AVI file. Now you should be able to open this AVI anywhere. So far I have only tested YV12 colorspace, which milan suggests you to use. You might also have to force ffvfw to use RGB32 or RGB24 for programs like AfterEffects, etc. Open the codec configuration, select this in the "Decoding" tab. Edit: It does however seem to be hard to get other than YV12 output working. A thread in the XviD forum discussing ffvfw (although no AviSynth specific stuff).
__________________
Regards, sh0dan // VoxPod Last edited by sh0dan; 26th April 2003 at 18:03. |
31st March 2003, 21:08 | #2 | Link |
Retired, but still around
Join Date: Oct 2001
Location: Lone Star
Posts: 3,058
|
Sh0dan, thanks for mentioning this. I did a few preliminary tests with Vegas and unfortunately it has problems. With force input colorspace unchecked in the decoder tab it will load but Vegas doesn't grok YV12 so video is whacked. WIth RGB24 forced, it refuses to load at all, which surprised me.
Of all things, Windows Movie Maker 2 will load these fake files just fine. I don't have AfterEffects installed at the moment so I could not check there. Anybody got Premier installed and can check? |
31st March 2003, 21:39 | #4 | Link |
Retired, but still around
Join Date: Oct 2001
Location: Lone Star
Posts: 3,058
|
VFAPI will serve to AfterEffects so maybe a comparison of the outputs might provide some useful info? I put some current links in the NLE forum that might save you some time if you want to try and don't already have it set up.
|
31st March 2003, 21:48 | #5 | Link |
Retired AviSynth Dev ;)
Join Date: Nov 2001
Location: Dark Side of the Moon
Posts: 3,480
|
Seems like AfterEffects will only properly decode RGB data, even though it claims to be able to open it. ffvfw still outputs YUV data - so I guess it doesn't force the output colorspace.
Probably quickly fixed by milan.
__________________
Regards, sh0dan // VoxPod |
31st March 2003, 21:56 | #6 | Link |
Retired, but still around
Join Date: Oct 2001
Location: Lone Star
Posts: 3,058
|
Sh0dan, well that is why I am a bit confused. I used avisource ("fake.avi").info to open the fake.avi. Showed rgb24 when I checked force input color as RGB24 and showed YV12 when I unchecked it. So, the force input color space IS doing something, don't you think?
-------------------------------- @Milan, again thanks for this work! When I loaded the fake.avi into CCE 2.5 it complained it could not find a handler for AVIS. Just goofing around I added vidc.avis=ffvfw.dll in registry. CCE then encoded although output was half duck doody green and sort of looked like the video in Vegas when it tried to open the fake.avi in YV12. Perhaps this is useless info, but we see this a lot with CCE and new codecs/handlers. For instance with avisynth 2.5, CCE complained about not being able to find a handler for YV12. Although it turned out to be better to use a ConvertToYUV2 statement in the script, setting vidc.YV12=Divx.dll allowed CCE to encode a Avisynth 2.50 script outputting YV12. Anyway, just some CCE background for you as I do not know if you use it or not. Last edited by DDogg; 31st March 2003 at 23:09. |
1st April 2003, 12:46 | #7 | Link |
Registered User
Join Date: Apr 2002
Location: Slovakia
Posts: 220
|
Thank you for testing makeAVIS.
I'm just downloading Adobe After Effects tryout and hopefully I'll able to make ffvfw compatible with it soon. I'll look for some Vegas demo version too. @DDogg I might modify ffvfw installer to add vidc.avis=ffvfw.dll to registry. AVIS would be fine, because AFAIK no other software uses this FOURCC (please correct me if I'm wrong, it's still time to change it). I'll check the forcing of output colorspace too. BTW there are still crashes when closing some players if ffvfw was used for decoding. I'm investigating this.
__________________
ffdshow homepage: http://ffdshow.sourceforge.net/tikiwiki/ ffdshow download: http://sourceforge.net/projects/ffdshow/ |
1st April 2003, 18:12 | #8 | Link |
Retired, but still around
Join Date: Oct 2001
Location: Lone Star
Posts: 3,058
|
milan, some folks (like me) would only use the filter for frameserving. Would it be possible for MAKEAVIS to allow the choice of initial colorspace? In effect, could it automatically do the reg change equivalent of config>decoding tab>force input color space>colorspace choice, and if possible, reflect the registry setting active when it is opened and in use? This would allow the frameserving tool to be more transparent to people not needing the full power of the filter. I hope you might consider this.
|
2nd April 2003, 06:46 | #9 | Link |
Registered User
Join Date: Apr 2002
Location: Slovakia
Posts: 220
|
I think it's a good idea. It would require a change in fake AVIs header structure, but this shouldn't be a problem. I'll do this today. Perhaps I should try to work with link2 more to see which of its features would be useful in ffvfw too (except for sound support).
__________________
ffdshow homepage: http://ffdshow.sourceforge.net/tikiwiki/ ffdshow download: http://sourceforge.net/projects/ffdshow/ |
2nd April 2003, 09:49 | #11 | Link |
Registered User
Join Date: Apr 2002
Location: Slovakia
Posts: 220
|
It may look strange, but I've never developed any application which would work with ACM in Windows, only the video. Maybe it's not difficult, but I'd have to start to learn it from the beginning.
__________________
ffdshow homepage: http://ffdshow.sourceforge.net/tikiwiki/ ffdshow download: http://sourceforge.net/projects/ffdshow/ |
9th April 2003, 11:24 | #12 | Link | |
Moderator
Join Date: Nov 2001
Location: Netherlands
Posts: 6,364
|
Quote:
Now I don't know whether Premiere requires RGB24 or RGB32, but I haven't tried RGB24 yet. I also noted there are two options in makeavis (forgot the names), what's the difference? |
|
9th April 2003, 15:25 | #13 | Link | |
Retired, but still around
Join Date: Oct 2001
Location: Lone Star
Posts: 3,058
|
As an update, I did some testing for Milan on a private build he did. That build worked in most of the colorspaces but was having trouble with YUV2. He said he is very busy at work doing a project for his company, but replied:
Quote:
|
|
10th April 2003, 17:26 | #16 | Link |
Retired AviSynth Dev ;)
Join Date: Nov 2001
Location: Dark Side of the Moon
Posts: 3,480
|
After battling ffvfw for almost an hour before getting it to compile, I can say the results are very promising. I got AviSynth video directly into After Effects, so I guess most other apps will also work now.
I'll ask in the XviD forum for a compile for you all to test.
__________________
Regards, sh0dan // VoxPod |
10th April 2003, 19:25 | #17 | Link |
Retired, but still around
Join Date: Oct 2001
Location: Lone Star
Posts: 3,058
|
Did you use the source from his test build (or newer) or the one from above? I ask because the newer has the force colorspace built in to MakeAvi.
Last edited by DDogg; 10th April 2003 at 19:36. |
23rd April 2003, 08:17 | #20 | Link |
Registered User
Join Date: Apr 2002
Location: Slovakia
Posts: 220
|
During last weekend I was experimenting with sound support in ffvfw. Now makeAVIS can store the audio stream in the "fake" AVI. This stream contains only sample numbers and ffvfw acts as ACM decoder and provides the actual audio data to the application. I've tested two clips with simple Avisynth scripts and they worked. Even when I extracted the audio stream to a separate wav file I was able to load it into the Cool Edit Pro 2.1.
Few questions to anyone who knows the ACM: 1. For format tag I've chosen the 0x3313 value. It's not used in MMReg.h file I've got. Is there some more up-to-date database of format tags? 2. ACMDRIVERDETAILS structure contains fields wMid and wPid. Now both are set to zero. Do I really have to obtain IDs from Microsoft before distributing the codec? Thanks for help. And as usual this is just experimental. This time _very_ experimental: not all ACM messages are handled nor all message flags.
__________________
ffdshow homepage: http://ffdshow.sourceforge.net/tikiwiki/ ffdshow download: http://sourceforge.net/projects/ffdshow/ |
Thread Tools | Search this Thread |
Display Modes | |
|
|