![]() So I am now looking for an other editing problem which handles 18fps (and also 12 / 16 / 24 frames/sec) from import, timeline and export. But I don't like this because there are at not regular points images added and the result is not so smooth as the original 18fps. BUT Adobe Premiere can not export 18fps files. This program imports these AVI files without problems. noise reduction, sharpness, etc).Īfter this step I use today Adobe Premiere CC. I use virtualdub/avisynth to improve the captured super8 films (e.g. I need to work also, so please be a bit patient It can be also done with older AE over QT engine, but needs some knowledge and setting up.įfmpeg decoding is 10bit (actual over 16bit pixel format, but 6 bits are 0s), but there is no encoding at all. Outside Edius, Resolve is about only app which can encode HQX at 10bit as it has a native integration over codec SDK. Do the same for Cineform (not internal one, but VFW if you have it installed) and it will work, as Cineform is coded to support 10bit pixel format on input/output even over VFW. Vdub will show error when you try to export. This will force to push 10bit into codec. Go to Compression, choose GV HQX and set Pixel Format to v210. If you have codec installed you can use it (instead of internal engine) and then it will be also only 8bit. Vdub2 can uses ffmpeg for HQX, so decoding is at 10bit. Internally data can be normalised to 10bit, but it doesn't change fact it's only 8bit data which gets fed into codec. 10bit pixel formats are not supported on input/output of the codec when used with VFW/directhsow. ![]() You can't push 10bit data to codec over these technologies. It's 8bit over VFW or directshow (Vdub2 uses ffmpeg for decoding, so this is different). Thinking back, there was a similar issue importing Cineform.avi files encoded with 'old VDub' (using the GoPro VFW codec). I don't have the Grass Valley VFW codecs installed, but I passed your sample through VDub2 (as Direct Stream Copy again) saving as AVI and Resolve imported the AVI file. I'll bet you've been using 'VideoFred's (Freddy Van de Putte) AVISynth routines on your Super8 captures ?Įdit: Actually if you switch from 'old' VDub to VDub2 I think you might find that Resolve will import your GV HQX.avi encodes outright. It would give other 'Resolve-compatible' options besides GV HQX (8-bit only with the VFW codecs), including Cineform (native), ProRes. In fact if you plan on continuing to use VDub for encoding, I'd suggest switching to VirtualDub2 anyway. Just a matter of loading the file, setting 'Video' and 'Audio' for 'Direct Stream Copy' and Queue Batch Operation > Save As > Save as Type > QuickTime/MOV (.mov). Since you are familiar with VDub, I'd suggest using VirtualDub2 (formerly VirtualDub FilterMod): Good news though is that Resolve will import your sample after re-muxing to MOV container. Evidently the GV HQX.avi files you created with VirtualDub (with Grass Valley VFW codec pack installed) are such a case. Yeah, Resolve can be a bit picky when it comes to importing AVI files created with other programs.for the supported AVI codecs that is. The process of elimination is a long one, but accurate.Uli and Jean Claude beat me to it, but to add to their suggestions. So it's not, at all, how differently VD loads a script. So far, everyone has tried that script with VirtualDub 1.10 without errors. That "effect" is what people need to properly get an idea of what's going on (since we know nothing about the AVS version you are using and if you're using the 圆4 build of VD or etc etc). ![]() Probably the rest of the error message you left out and summed it up as "to that effect". VirtualDub should be giving more detailed information on the error. I'm going to guess even Avery's forum, you'll end up in the same dead-end with the reluctancy you have in providing information. There's plenty more variables with little to work with.
0 Comments
Leave a Reply. |