If this is your first time here please read our FAQ and Rules pages. They have some useful information that will get us all off on the right foot. More details on our policies, especially our Own the Source rule are available here. If you do not understand any of these rules send a private message to one of our staff for further details.

Vegas Pro issues and crashes
#71
(03-17-2019, 11:40 AM)ThrowgnCpr Wrote:
(03-17-2019, 11:32 AM)wilhelm scream Wrote: I'm starting to be glad I never upgraded Vegas past movie studio HD Platinum 11.

There have been substantial upgrades since movie studio 11, especially when considering the move to Pro, so your point is rather silly.

In the last version or two, there have been some conflicts with hardware, but this is as much the fault with hardware/OS configurations as it is with Vegas.



To expand on Dig's questions, we need some more info. Do you have VST or external plugins installed? What plugins are you using in this particular project? When exactly does the crash occur, and can you provide screenshots of the crash message?

Screenshots of your Vegas Preferences (video tab), project settings, and render settings will all be informative for us to diagnose your problem.

Those substantial upgrades being?
Reply
#72
since 11? a ton. 11 came out in 2012, and a lot has changed in terms of digital formats since that time. I started using Sony Vegas Pro version 7, and have tested most versions since. The biggest jumps in features/workflow came between 7 and 9, and then maybe between 11 and 12. 15 and from the looks of it 16 are also big jumps from version 13. This also corresponds to the time that Magix took over development after Sony abandoned it.  Off the top of my head, here are just a few of the things that have been added in the last few versions:

# of available tracks in a project (studio is incredibly limited compared to Pro)
rendering options
added codec compatibility
added native plugins (many)
advancements in masking
added 3rd party plugin functionality
rendering speeds
GPU acceleration
4k workflows
HDR support
hover scrubbing

Vegas 16 is adding:

video stabilization
advanced motion tracking
media bins and tagging
storyboarding
backup options
lots of new shortcodes like gap closing



Google is your friend...
Reply
#73
(03-17-2019, 11:52 AM)The Scribbling Man Wrote: Do you use Boris fx? I used to have very regular crashes with Vegas - drove me insane. It was especially provoked by undoing any action that involved a clip with FX on. Once I got rid of BCC everything ran a million times better.

(03-17-2019, 12:22 PM)DigModiFicaTion Wrote: Slight segway, hitfilms plugins are directly accessible by Vegas and can be used in the program. I've not experienced a crash from using them, but  I thought I'd throw that out there since the Boris fx plugin was brought up.

I  use the BCC plugins that are already incorporated into Pro - i renamed the VST folders to old as mentioned in  Throwgncpr link and the plugins have disappeared from my Media Generators tab which i presume was the idea but I'm still getting the freeze when rendering. I haven't however done any work on my timelines yet, so i don't know if removing the plug ins stops the crashes.

(03-17-2019, 03:58 PM)TM2YC Wrote: Vegas has been mostly pretty good for me crash wise.

- Have you tried rendering to a different format? or with different settings?

- Have you tried copy & pasting everything from your timeline into a new project and saving. I've had that sort of thing work with other programs.

- Have you tried selecting everything in your timeline and then rendering using the "render looped region only". I've weirdly had this work in the past.

I have done all of the above - i am happy to say that i did manage to render an AVC file which i muxed in TS Muxer with the audio AC3 file , however the render did take five hours. I usually render to M2V file for Bluray. 

(03-17-2019, 04:58 PM)DigModiFicaTion Wrote: How much space is left on your hard drives. When I have low space, my Vegas acts up.

plenty of space on the hard drive

(03-17-2019, 05:03 PM)Captain Khajiit Wrote: Try disabling GPU rendering in both Options-->Preferences-->Video-->GPU acceleration of video processing and Options-->Preferences-->General-->Allow legacy GPU rendering.

TM2YC is right. You should try to render to lossless AVI.

Why is your source YUV?  Decode it properly, convert it to RGB, render a lossless AVI, and then edit that.

I tried both GPU & CPU rendering they both keep freezing.

I'll try converting to lossless AVI - i havent converted to this format before and i never had problem with TS files in the past. I always had succesful renders.

I think i will do a fresh install and see what happens. Once again thanks for all your help - i'll keep you posted.
In the Works - Age of Adaline - Miss Larson edit
Reply
#74
(03-19-2019, 06:07 PM)ThrowgnCpr Wrote: since 11? a ton. 11 came out in 2012, and a lot has changed in terms of digital formats since that time. I started using Sony Vegas Pro version 7, and have tested most versions since. The biggest jumps in features/workflow came between 7 and 9, and then maybe between 11 and 12. 15 and from the looks of it 16 are also big jumps from version 13. This also corresponds to the time that Magix took over development after Sony abandoned it.  Off the top of my head, here are just a few of the things that have been added in the last few versions:

# of available tracks in a project (studio is incredibly limited compared to Pro)
rendering options
added codec compatibility
added native plugins (many)
advancements in masking
added 3rd party plugin functionality
rendering speeds
GPU acceleration
4k workflows
HDR support
hover scrubbing

Vegas 16 is adding:

video stabilization
advanced motion tracking
media bins and tagging
storyboarding
backup options
lots of new shortcodes like gap closing



Google is your friend...

And are the HD file sizes any smaller (I just rendered about 40 minutes of HD video, it was over 200GB)?
Reply
#75
The version of Vegas has nothing to do with your output file size. Whatever you set as your render settings (dimensions, codec, bitrate, etc.) determines the file size, and that is not NLE-specific.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)