[Rick Anvican]

John, can you clarify three things for me please:

1) Nested projects would be used like if you want to apply like a single transition on a composited shot (e.g. made by multiple layers on different compositing modes), right? Kind of like an After Effects composition…

2) Has Vegas 12 resolved the green tinted bar that affects GPU rendered output on Mainconcept AVC 480p templates? I know this had something to do with width (854) not being divisible by 16 and would be fixed by using width divisible by 16. Any known reasons why it occurred?

3) I tend to think that giving Sony Vegas source video with non-standard resolution dimensions (e.g. 1258×544) would exhibit problems like garbled renders, would it be better to convert it into resolutions with one commonly used dimension (e.g. 720×310 or 1280×554)?

Thanks.

(Ever had the situation where you have HD AVC/MOV footage where the video won’t show up in the preview window on preview qualities Draft/Preview(any mode) but would show up with Good/Best(any mode)?)

[Rick Anvican]

Hey guys, thanks for all the suggestions, I will have a go at them soon. Initially, I had the 23.976p footage slowed down using velocity envelopes where duplicate frames are distributed evenly, but I switched to time remapping where smooth motion is required and duplicate frames are not wanted at all.

Twixtor has shown unwanted warping (e.g. straight edge becomes curvy) on a few frames even with keyframed adjustment, considering the footage had quick panning and distinct edges, so I’ll see if the alternatives suggested give better results, again, thanks for the help.

John, nesting would work just requiring a bit of recalculating speed values but would take more time to render, especially with projects having many event FX/transitions and layer compositing, pre-rendering the “twixtored” footage would cut down rendering time I suppose.

[Rick Anvican]

Hi Matt,

Thanks for sharing your experience, my current workaround is that I would speed up the 23.976p footage to 29.97p and since I’m doing some processing in Virtualdub for the 23.976p footage, might as well do that there, render it back out in lossless and re-import that version into vegas, then “twixtoring” it. This would probably give me the best workflow. Anyway, thanks again for your suggestion.

[Rick Anvican]

Oh yes, I forgot about “Selectively Prerender Video“, I remember using it for prerendering finished parts of projects, especially for parts where I used FX/transitions that caused problems when whole project was rendered (e.g. black screen, partial glitch).
Don’t worry, left the internal prefs as is, but there’s a setting where you can change when the preview updates while rendering – default is every 5 frames.

Funny, never realised that bug in vegas pro 10.0…
The message dialog I mentioned in a previous post about different color depth… that never showed up again in the same unchanged project after a cold restart, I think it was a one-timer.

Something I’m sure that a lot of Vegas have experienced before – MainConcept 480p Internet Widescreen template with GPU render gives vertical green-tinted bar to the right, I’ve heard it’s fixed in Vegas 12, could you please confirm? Thanks for the previous info.

[Rick Anvican]

Other NLEs I’ve tried like Adobe’s Priemere can adjust RAM usage but eats it up quick.
By the way, do you use dynamic RAM preview? How much RAM would you allocate? Currently I’m on 600MB, it would be pretty useful if you can save the DRAM preview for later viewing.

(In Preferences–>Internal, what do the 2 RAM preview limits(MB) do? Haven’t touched them yet, non-64-bit is at 1024MB, 64-bit is at 32768MB)

I’m not sure if this problem affects a lot of Vegas users but I’ve found when I sometimes close Vegas after around an hour or so of editing any project, process “vegas110.exe” stays in memory with 600-1500MB occupied at times with CPU usage at 0% or 13-25%, usually I leave the process for 10 minutes to see if it closes by itself along with “FileIOSurrogate.exe” and “sfvstserver.exe”, if it doesn’t then “End Process” it is, occasional “Sony Vegas has stopped working” message pops up.

[Rick Anvican]

I’ll just leave GPU to do accelerated rendering in cinema4d then, the Quadro 4000 is really out of my budget.

On Vegas, the max write speed I’ve seen was 3 MB/s, back when I used FRAPS, I’ve seen write speeds of 35 MB/s (1920×1080@60). Once I had a new Hitachi HDD that became unusable but I couldn’t determine whether the cause was sustained 35MB/s writes or was it just plain faulty, replaced it with a Seagate. I don’t think Vegas will ever reach that speed because like what you said about the CPU bottleneck.

Guess defrag’s a thing of the past too, I’ve seen Vegas used up to 2.5GB of out of my 8GB physical RAM, how much would it use on your 16GB RAM?

Like I mentioned before, my current cpu is i7 2600k running max 3.7ghz (not overclocked), I find rendering speeds very reasonable considering that my projects use a lot of effects, which CPUs would be good Vegas now?

[Rick Anvican]

Despite transcoding media sources from delivery to editing formats, most projects I’ve done needed the GPUA off because the preview window gets messed up often, going to have a look at the CPU parking technique to try speed rendering up.
I rarely play video games, not really play but emulate the old platforms like PS1 to study on their game engines, so I don’t want to go upgrade my GPU for some features that I don’t use and if it doesn’t improve Vegas’ performance.

HDDs or SSDs for Vegas use? Will it improve performance? I’m still reluctant on how SSDs have limited read/write like USB flash, Windows OS already reads/writes a lot to storage. My 2 HDDs have been running well for 8 years, considering that they have done large amounts of large file transfers.

[Rick Anvican]

Hey John, have you ever came across this error message in Vegas?
==============================================
Title bar: Different depth or BPP
Description: Warning
Button: “OK”
==============================================
During rendering on one project (settings @ 8-bit for pixel format), this message
popped up several times when rendering segments where source media of color depth
24-bit(bob-deinterlaced from Avisynth) and 12-bit(original source footage) overlapped
(e.g. crossfade transition), the crossfade in the render output was glitched. The
only filters I used in AVIsynth were SeparateFields and “bob-field“,
compressed with Lagarith codec, I assume lagarith is the one saving at 24-bit
color, any way to use video source media with 2 different color depths in a single
project?

[Rick Anvican]

Other than personal recordings, I have some VHS tapes that were purchased from a rental store during their closedown, which are not available anymore. My VCR didn’t have AGC and would be able to record tapes with Macrovision’s analogue protection, possible with the cards that you mentioned?

Edit: forgot to ask about GPU – planning to upgrade to nvidia gtx 700 series but heard that sony doesn’t support nvidia’s new architecture which is making lots of problems for gpu acceleration in vegas, using gpu GTX550Ti and cpu Intel i7 2600k @ 3.4Ghz, would GPU acceleration matter? With 2 working projects, I noticed both had decreases of around 2-3 minutes with GPUA on.

[Rick Anvican]

Interesting, what capture card are you using/did you use? I have many old VHS tapes with rare recordings that I would like to archive. Of course, being VHS you can’t really “upscale” or enhance its image quality in the capture, so I just want to get the best out of the original, want to do this before my 20-year old VHS recorder gives up its soul.

Do you know anybody else on the forum here or another forum that might have worked with analog broadcast equipment?