The only issue with this workflow is that you have to keep track of the 0-255 to 16-235 mapping. Using the frameserver, if Vegas can open it, I can get the video into AVISynth. It takes less than one minute to download and install. I don't like to deal with all of this mess, so when I use AVISynth I put the video into Vegas, do all my editing, and then use the Debugmode frameserver to serve the video into an AVISynth script. The "dvsd" codec is indeed a DV codec, but unless you are editing DV video, this isn't what you need.Īlso, AVISynth can only open certain video files directly and can only open other types of videos - like MPEG-2 or AVCHD - by using other "helper" apps. To know what you need to install, can you either post a small, unedited clip of the video you are trying to process, or at least put it into MediaInfo (free utility) so it can report exactly what codec it is using. There are dozens of posts in this forum warning against installing codec packs. ![]() Can anyone say what might be safe to install? Are there other codecs that will be required for decoding other file formats? I am afraid to install a codec that could clobber one of the Vegas-supplied codecs. That's it! Justĭon't forget that when using Cedocida to compress widescreen DV, you must go to the codecĬonfiguration dialog and set "Aspect Ratio" to 16:9. ![]() At the bottom you'll be able to download version 0.2.2, which isĮxtract the files to a convenient location, right click the. Donald Graft hasĬompiled a Windows version, which can be found by heading to andĬhecking the "Hosted" section. Myself, and I'm quite happy with the results of both decoding and encoding. Windows architecture, and in order for it to decode DV, a VfW codec for the format must beįor DV, a very common recommendation is Cedocida, by Andreas Dittrich. Avisynth's AVISource, however, uses the Video for Most NLE packages, large and small, have internal decoders for the DV25 format,Īnd can play the footage without issue. This error is an old standard, and is the result of not having a system-wide DV codec I found the following post on another forum, indicating I need a system-wide VFW codec:Įrror message: "AVISource: couldn't locate a decompressor for fourcc dvsd" However, I am now stumbling on an error:Ĭouldn't locate a decompressor for fourcc UYVY I am trying to run one of John Meyer's denoiser scripts. John Meyer and others' excellent posts have gotten me farther than I ever expected to get. I have spent the better part of today learning to run AVISynth. I’ve run the 32-bit codec.bat file with AACACM, but I’m unsure that the codec has installed.I do not want to mess up my SVP 12 install. I’ve already installed Quicktime, I’ve installed the ffdshow codec pack and I’ve tried installing the AACACM 32-bit codec (I’m running a 64-bit system, but I’ve been advised to use the x86 version of Virtual Dub as it has more plugins). (source format tag: 00ff)" error in Virtual Dub. Unfortunately, having decided to start all over again with the jello removed via VirtualDub, I’m getting a 'No audio decompressor could be found to decompress the source audio format. Have learnt to identify from the Movie Clip Editor that I get red in the MCE timeline when I don’t have overlapping markers (also, the blue line of the solution in the graph editor completely cuts out). ![]() How can I convince Blender that it’s looking at a fairly broad street, not a tiny, thin path?ĭove into the video last night and was getting a fairly stable track (until the very end) with about 77 markers (with a solution of 1.1829). I’ve set the floor, the origin, the x axis, the scale - all to only minor adjustments. Huzzah!Įxcept when I Setup Tracking Scene - the presented solution shows the camera and the markers in an almost completely straight line, or has the camera stretched out to a ridiculous distance, covering the markers (which are in an almost completely straight line). I wiped my progress and started again with my crappy iPhone 4 footage and managed to get a solid 0.7159 solve error (using the phone preset w/k1+k2+focal length) with just 21 markers (including my new Favourite Thing, perspective markers). Like, I’ll set 90+ markers, but often I see great tracks made with 20-40 markers. So! I’ve done some more research into Camera Tracking - and one of the things I’ve discovered is that I tend to set wayyy more markers for footage than most compositing Blenderheads need for good tracks and end results.
0 Comments
Leave a Reply. |