Matt Carlson
Forum Replies Created
-
More memory will not help much with your setup as far as preview rendering. The bottleneck for most modern PC builds is not hard drive speed (although that does play a part in uncompressed video.) The main factor in preview rendering with Sony Vegas is CPU (now assisted by GPU) and with some effects and some codecs there is not a consumer computer made that can give perfect frame rate playback inside an editing framework. Professional dedicated effects hardware is truly the only thing that does that on a rock solid basis.
I have 12 GB in my machine and the reason I find it useful with Vegas is opening multiple instances and not having to shut Vegas down if I need to open another intensive editing program (Photoshop, Illustrator) as well. Being a Windows program you will find that Vegas actually does not go grabbing for memory so continually adding more has little effect. If Vegas actually can solve it’s GPU issues then “perfect” playback (as always consistent dedicated hardware gives) may become a Vegas reality because the GPU becomes that dedicated hardware. Memory is cheap right now but unfortunately it is not the answer to a better running Vegas. It would be nice if fifty dollars of memory solved preview issues. The answer is two-hundred dollars for a good graphics card (at least) or six to eight cpu cores at 4.0+ ghz.
-
Isn’t this the second instance in the last two weeks of a solid i7 setup showing massive rendering times? I think the other thread had a GTX 560 Ti as well. Have you tried disabling GPU acceleration to see if the 2600k takes 30+ hours all by itself? Are you editing in Vegas on the same rig that recorded the game footage? If so what else do you have in your PCI slots?
-
There are only two ways that I know of to get an effect to do what you want. Like you I hope one day to find a “proper” check box or parameter somewhere in Vegas to allow effect tails to continue.
Style 1: Render out your audio clip with enough dead space at the end to keep the effect going to your desired result. Replace it in the project.
Style 2: Create a new track for your clip (or if your audio is just a single source all the way through) and use the track effects plugin chain instead of the single clip chain. Track effects will run until it hits the end of the “loop region” so if you need to have reverb trail off at the end of the project you need to render the entirety as a loop region and extend the region passed the project end for your desired result.
Hopefully someone here knows some command that is a little more quick and elegant.
-
Certain plugins (like Neat Video because of its resource hogging “no lag mode” especially in a Best(full) preview) can start to mess with the audio outpu on a random basis having to do with the basic happiness of windows at the time. Your problem may reappear. Since I have had Vegas for a while (since before it was video) I still use Waves audio plugins and disabling the audio track buffer kills real time playback completely for some of them and stutters erupt for others. Depending on how much audio processing you have going on (in the future) continuing on without the audio buffer may not always be a viable option.
The one thing that struck me as odd though is that your problem transferred to rendering as well. All the audio stutters and pops I have encountered during playback never appeared in the render. This points to a much bigger problem than just internal resources becoming scarce for certain operations.
-
This is just a shot in the dark without knowing the full description of “not opening.” Sometimes when working with shared plugins if you add a new one, update them, or possibly have a crash in 10 because of one them, the “state” at which it exists (yes this is vague) is not liked by 11 and the executable does not even show the splash screen. You click on it and nothing. I can’t remember 100% if there is an instance in task manager still running but I think there is not. The instance of 11 just shuts down before showing any noticeable feedback. You said you have not done anything out of the ordinary so just file this possibility under things to check. A re-installation of 11, in my experience, is the only way to solve that particular problem.
-
My advice to neophyte programmers switching languages is to take a Zen approach to what you are doing. Don’t think of your programming as “now I have to learn C#.” Object oriented languages have their quirks but they are all the same in concept. The same with interpreted languages (php, old BASIC, SQL) You still wan’t to do the same things and if you have any programming experience it is just a matter of keeping syntax straight in your head (or better yet have an internet connection and google always handy.) The jump from Java to C# is not that big.
-
Rendering output that is “transparent” requires a codec that can produce an alpha channel. The uncompressed avi output from Vegas has an alpha channel checkmark box in the output settings window. Other codecs have alpha channels as well I just do not remember them off hand. When re-importing back in to Vegas you will need to check the clip properties and change the alpha channel (for your purposes “straight matte”.)
Unfortunately I think only the uncompressed codecs can do alpha channels which means huge files for you to import in to your other project. This begs the question whether you absolutely NEED to render the file first. Vegas projects can be nested, copy and pasted between instances, full of layers etc. Are there circumstances that make it impossible to work with your clips natively in the second project?
-
To have complete control on how and when your flight paths are drawn you need to use the “Mask” key framing in the event pan/crop section on your flight path clip. It will take a lot longer to hand key frame (maybe hours depending on how complex your flight paths are) versus finding a way to use a transition as a mask, however. You do have the added bonus of complete control with key framing though. If you are unfamiliar with mask key framing then learning the ins and outs will also take some time. It is worth it if you ever plan on doing more composite work. Masking is one of the most important tools in such work.
-
Mid level software like Vegas tends to have a sweet spot that once you find it problems become less intrusive to your work. Unfortunately for some (like you) it might not ever get there and you will move on. The reason some of us continue down the path to find that spot is that the “pro” editing software suites that have become industry standard were written by people who’s last priority was a clean interface. I started using Vegas before it was even a video editor because of the clean and efficient audio workflow and I continue to use Vegas for video editing now. That same interface efficiency is why people cling to hope that Sony will finally make it STABLE.
The problem is that Sony is outside the current political ring of the NLE “industry.” I know that seems strange considering how big Sony actually is but third party development is more about politics than manpower and third party development is a big boost to the success of a product. Vegas is the ugly stepchild because (this is only my own personal conclusion) that if Sony actually did it right they would have the economic and industry power to squeeze out the competition so others are quick to call Vegas a toy. Unfortunately for us Sony is accepting Vegas as the ugly stepchild and not fixing it’s problems. Their great interface designers are not backed up by equal system level programming greatness.