Can I deinterlace an individual clip in Sony Vegas 12?

[CursedLemon]

I'm trying to import a DV video into a 60FPS project, and deinterlace just that clip, while the rest of the project remains progressive scan.

Any tips on how to do this? There don't seem to be any filters I can add that have anything to do with deinterlacing, only things that can be set in the project properties.

[poisondeathray]

That's how it works. If the project properties are set to progressive, and the export settings are progressive, all progressive assets will remain progressive, all interlaced assets will be deinterlaced according to the project settings (e.g. if you have it set to "blend" it will blend deinterlace, if set to "interpolate" it will interpolate deinterlace. The latter is usually the preferred mode in vegas) . DV will normally automatically be interpreted as interlaced, so it should work the way you have it set

[CursedLemon]

Well, in that case...can anyone tell me why it doesn't work? lol

Vegas gets the PAR correct but refuses to render the fields correctly.

[poisondeathray]

Well, in that case...can anyone tell me why it doesn't work? lol

Vegas gets the PAR correct but refuses to render the fields correctly.

What does "refuses to render the fields correctly" mean ?


Check to see if
1) your DV clip is interpreted correctly (is field order correct, bff or tff)
2) your project settings are correct
3) export settings are correct

Is your DV clip truly interlaced NTSC DV ? or is it a 24p or 24pA variant ?

[Cornucopia]

Agreed (to post #2). But if you aren't satisfied with Vegas' forms of deinterlacing, it would probably make sense to deinterlace (in AVISynth or ffmpeg, etc) and convert to Lossless DI prior to importing into Vegas.
There are many more & smarter options to deinterlacing available this way. But there are obviously extra steps.

Scott

[CursedLemon]

Ah, I figured out the problem, Vegas just doesn't want to let you know that it's going to deinterlace the clip on export. I was expecting to see the results in the preview, but I guess I have to wait until it's rendered.

[poisondeathray]

But the preview should be deinterlaced (you shouldn't see "combing" or "horizontal lines") .

Just render out a short loop region to test it

[CursedLemon]

Agreed (to post #2). But if you aren't satisfied with Vegas' forms of deinterlacing, it would probably make sense to deinterlace (in AVISynth or ffmpeg, etc) and convert to Lossless DI prior to importing into Vegas.
There are many more & smarter options to deinterlacing available this way. But there are obviously extra steps.

Scott

Only reason I'm trying to import raw DV video is that DV seems to be one of those formats that Vegas actually enjoys using. As opposed to H264, XviD, etc. which stutter constantly.

[CursedLemon]

But the preview should be deinterlaced (you shouldn't see combing)

Just render out a short loop region to test it

Apparently Vegas will only show proper deinterlacing in the preview window when you've got the preview render set on "Good", at least. Mine's always left on "Draft" (it's BS that I have to do that with a GTX960 and an i7-6700K). You also, obviously, have to set "Apply Deinterlacing Filter" in the preview device preferences.

[poisondeathray]

You shouldn't have problems with an i7-6700k and GTX960 . There shouldn't be any stuttering on h264 unless it's UHD/4K or in an AVI container. You shouldn't have to put preview on "draft" with that hardware unless you're dealing with >HD resolutions or have many layers or multiple slow effects

[CursedLemon]

You shouldn't have problems with an i7-6700k and GTX960 . There shouldn't be any stuttering on h264 unless it's UHD/4K or in an AVI container. You shouldn't have to put preview on "draft" with that hardware.

That's what I keep hearing. lol Yet issues abound. That's a problem for another thread though!

Guess I just need to ask people before I start tweaking the right knobs and figure out the problem myself. There's gotta be a name for that phenomenon.

[_Al_]

I theory it should work but if exporting to High definition , adn therefore resizing as well you'd get artifacts. If you keep same resolution, it should be ok.

Not sure what you do, but you just could use proxy. Where you edit DVavi, just before exporting you replace them back with original H.264 etc. clips.

[creakndale]

CursedLemon,
Vegas 12 ( 32-bit or 64-bit)?

Back when I started editing h246, I was using Sony Movie Studio 11 Platinum (32-bit) and my PC (Windows XP) was 1/8 the speed of your machine. Scrubbing the timeline was a nightmare.

I upgraded the PC, effectively doubling its speed, went to Windows 7 64-bit and tried the same Sony Movie Studio 11 Platinum (32-bit). Timeline Scrubbing improved but it was still not good enough.

Upgraded to Sony Movie Studio 13 Platinum (64-bit) and Timeline Scrubbing improved again but still too much lag, especially when scrubbing in reverse. I resigned to let Movie Studio make proxy clips for me which takes a long time but at least it's a feature built into the program.

I've always wondered if doubling my PC speed again, to the processor/video card you are using, would solve the h264 stuttering timeline scrubbing saga once and for all. From your experience, it appears that I would continue to be disappointed. So I guess I'll stick with what I have and continue using proxies.

I'm glad to have read your post as it's saving me the aggravation of upgrading only to still be lacking the necessary processing power for native h264 editing. Very helpful info. Thanks.

creakndale

[CursedLemon]

CursedLemon,
Vegas 12 ( 32-bit or 64-bit)?

Back when I started editing h246, I was using Sony Movie Studio 11 Platinum (32-bit) and my PC (Windows XP) was 1/8 the speed of your machine. Scrubbing the timeline was a nightmare.

I upgraded the PC, effectively doubling its speed, went to Windows 7 64-bit and tried the same Sony Movie Studio 11 Platinum (32-bit). Timeline Scrubbing improved but it was still not good enough.

Upgraded to Sony Movie Studio 13 Platinum (64-bit) and Timeline Scrubbing improved again but still too much lag, especially when scrubbing in reverse. I resigned to let Movie Studio make proxy clips for me which takes a long time but at least it's a feature built into the program.

I've always wondered if doubling my PC speed again, to the processor/video card you are using, would solve the h264 stuttering timeline scrubbing saga once and for all. From your experience, it appears that I would continue to be disappointed. So I guess I'll stick with what I have and continue using proxies.

I'm glad to have read your post as it's saving me the aggravation of upgrading only to still be lacking the necessary processing power for native h264 editing. Very helpful info. Thanks.

creakndale

64-bit for me. I will say that it more or less works when it wants to. For example, I happened to notice at one point that H264 videos coded with NVENC were a complete nightmare to work with in Vegas, but for some reason if I coded them using my CPU (not QuickSync, just normal CPU usage) they would behave relatively okay. Then, a few weeks later, that no longer proved to be consistently true either.

Same with with XviD. For a while, whenever I'd have two XviD clips playing at the same time (track-motioned to different parts of the video frame), the preview playback would stutter like crazy and I couldn't get anything down with reliable timing. Then that spontaneously resolved itself for a while, before new problems started cropping up like artifact hiccups sneaking into the final render.

Freakin' Sony, man.

[aedipuss]

you don't have to complain about sony anymore, vegas is owned by magix now if the end product is going to be 60p why not take the 30i DV and bob deinerlace it to 60p? then use that on the timeline.

[CursedLemon]

I just wanted to do it in Vegas to save time, normally I would take the DV footage and use Yadif in VirtualDub then bounce it as a full-quality XviD file as an intermediary. This was before I learned just how unbelievably fickle Vegas is with what formats it chooses to work with.

[poisondeathray]

xvid problems are fairly common - it's an issue with b-frames in AVI . Not just vegas, this problem occurs in many programs

artifacts hiccups are commonly from GPU acceleration in vegas. Disable it => GPU acceleration is the most common cause of problems in vegas

NVEnc can drop frames, depending on how it's encoded. There is a higher chance when you use GPU decoding and encoding without indexing. If you index the decoding (e.g. with avisynth) , there are fewer problems, or if you use CPU decoding to feed GPU (but then CPU can sometimes be bottleneck)

[CursedLemon]

Yeah, I've been discovering the whole alpha-frames shtick and how it's a death spell for the editing process. I also learned very quickly that Vegas absolutely does not want to work with your graphics card at all, in any capacity, so that's been turned off for a while.

I've been experimenting with trying to capture/render video as lossless x264, which from my understanding uses nothing but i-frames and would likely be Vegas-friendly. I've had poor luck getting the settings correct, though.

[_Al_]

lossless H264 does not encode every frame as I-frame unless you specify keyint, .... , talking about Standard resolution, just to set GOP's as one second intervals might be ok, 25 or 30 or something:

x264.exe --qp 0 --keyint 30 --profile high444 --output out.264 input_yuv.avs

[CursedLemon]

Hmmm alrighty, I'll give that a shot!

[budwzr]

You may be throwing too much in the hopper. Hard Drive may be the bottleneck. Even 7200 is slow nowadays. Try to prerender occasionally.

TIP: In Vegas, you can loop a selection area from timeline events, and the preview will build up to realtime in a couple loops usually.

Another tip is to use twin SSD drives. One as the main drive, the other a USB3 portable. Another good idea is to convert to Mpeg2. In Vegas, Mpeg2 can be smart rendered.

Regarding Magix, I doubt Vegas will remain a Windows Native application which uses the Microsoft Database Engine. Magix other products are built like Adobe, they use a clickmap interface that runs custom code that may or may not be optimized for Windows. This is called a Shell. Running in a Shell makes the program easier to port to other OS's, but may slow down throughput.

The use of MS Database was the hallmark of why Vegas can run well on older computers.

[CursedLemon]

My video sources are usually very light on the bitrate side, I can't imagine that I'd be pulling 65+ MB/s.

[budwzr]

My video sources are usually very light on the bitrate side, I can't imagine that I'd be pulling 65+ MB/s.

I wouldn't rule out a complete uninstall, including all related shared folders, and start brand new. Saved Projects and media will not be touched. You can download at Sony.

[aedipuss]

for Vegas i use 4 hard drives. programs are installed on one, the programs temp directory on a separate one, input/source on a third and output files on the fourth. in addition long term storage is moved to nas boxes.

it helps prevent bottlenecks at the i/o level where a single drive is trying to read/write at the same time.