[George Dean]

Hi John,

John Parks @ “In fact, even with increasing RAM for preview from 200 to 4000 doesn’t do anything.“. If you haven’t already, I would set the Dynamic RAM back to 200. In the test I made, going above 2000 started to slow down the render times. You might not see a huge difference in render time if set at 4000, but if you don’t need it that high for Dynamic RAM preview, it will only hurt render times setting it really high. It supposed does better than v13, but it is not perfect and still has limitations.

Have you tried to start a new project with a fresh source media, maybe a minute or two long and test the render times? There may be something in your project, or in the source media of your project which the render is tripping on. A fresh project and source should avoid this. Also, you may want to reset Vegas and delete the cache, just to make sure there isn’t something nasty stuck in there before making the fresh project test.

I’m not familiar with your laptop, does it have Intel Quick Sync Video? And, if so, is there an option for that in the Sony AVC render template? This might decrease render times.

Another option, which doesn’t shine any enlightenment to address you question, is to use the Vegas2Handbrake script, which will DebugMode FrameServe your project out and render in Handbrake. Handbrake usually will give you better quality, a faster render and smaller file size……just a suggestion. I use this process for anything that goes to YouTube or PC for playback.

Best Regards……George

[George Dean]

Hi Scott,

That’s pretty much what I think, although I haven’t been using Vegas as long as you, with Sony v13 or Magix v14, when I put a V-Log clip in and apply a lut, Vegas goes to a craw. I do the same in Resolve 12.5.2 and it doesn’t miss a beat. And, like you, I know Vegas better and like it better, but even with the learning curve of Resolve, my attraction to Vegas is Desolving!

Best Regards…..George

[George Dean]

Rick, I don’t think you interest in an update this soon after a release is unwarranted in this case.

David, good point, but I doubt Magix even thought of it that way, nor are they capable of pulling off a meaningful update in that short period. Despite having a team that has been with Vegas for a while, I now think they are way behind the curve. My faith in Magix Madison has been shattered, by the poor results they delivered.

Nigel, I agree…..it’s their program to license as they please, it’s my money to spend as I please. I please not to spend it with Magix.

Best Regards……George

[George Dean]

Hi Scott,

I haven’t moved completely to Resolve, but about 60% there. I will still be using Sony Vegas Pro 13 (build 453) for at least a while long. Resolve needs a few more update features, but by the time I fully understand it, most likely they will be the NLE of my choice. For sure I ill not be buying from Magix.

Best Regards…..George

[George Dean]

Hi Scott,

I’m only using the trial version of Magix Vegas pro 14 for testing, and then only using small projects. I have read many issues, some based on using mts type source media and others about large projects. All I have tested so far are some h.264, DNxHD, and ProRes source files and I have not expereinced any render issues. Can you provide more detail about your source, your project, and the render results?

Best Regards……George

[George Dean]

Hi Scott,

Sorry, my memory was a bit off….the program I thought of is actually used to load Vegas Pro into Movie Studio, it is called Movie Studio / Vegas Pro Faker, to assit in swapping projects between Vegas Pro and Movie Studio…..no help for your purpose!

Best Regards……George

[George Dean]

Hi Scott,

When I tried, it didn’t work. It was a simple project (2 minutes) for testing Magix Vegas Pro 14 ( build 161). When I tried to load the project into Sony Vegas Pro 13 (build 453), I got the message that the project was created in a newer version.

However, I read a while back about a developer that created, I think a script file, that will load various projects into various versions. I’ll try to run it down and get a link….

Best Regards……George

[George Dean]

Hi Robert,

Do a search for ‘Vegas Pro nested projects’. That should reveal some information that may be helpful.

Another quick and clean method is to open the intro project in Vegas, make any modification you like, then render it out to an intermediate file. This file then can be brought into any Vegas pro just like you normally add your clips to the timeline, because after rendering, that is exactly what they are, a video clip.

There are several ‘render as’ options that will provide visually loosless or uncompressed files which will look good in your project. CineForm is one that I use a lot, but not the only option. If you are not familiar, the CineForm codec comes when you install GoPro Studio and will appear as a codec option in the ‘Video for Windows’ Output Format. Choose any template, then change the options to match your project settings. The CineForm codec will appear in ‘Customize Template’ under ‘Video Format’ drop down options. The file extension (wrapper) will be AVI.

Best Regards…….George

[George Dean]

Hi Darcy,

Glad that helped and you are up and running.

Best Regards……George

[George Dean]

Hi Roger,

That is what I was thinking, but I had a home emergency and didn’t get back to post a link that would have helped, but you found the issue and glad you got it all fixed.

Best Regards……George