Having some issue with Vegas Pro 15 That I cant work out -

Comments

Pursuit-Perfect-System wrote on 4/29/2018, 1:55 PM

The error 59 was fixed with a new installation of the software.

However the registration process didnt seem to work and I had to keep doing it every time I started Vegas again

Another installation of Vegas fixed that issue.

I did try third time lucky and installed Vegas again but not joy on the gpu rendering problem

Pursuit-Perfect-System wrote on 4/30/2018, 11:58 AM

I thought things mere miraculously fixed - I changed a HD for a larger one - 3TB to 8TB - I used the 8TB as the source for the media and another 4TB as the drive to render to.

The video got to 74% before it crashed same as usual - talk about a tease.

So then I tried a render with GPU disabled and the pc seemed to be acting strange there was nearly the full 32GB of ram being used.

A restart - the same project rendering now using 11GB of ram. That's how much the software is messing around for me

OldSmoke wrote on 4/30/2018, 1:18 PM

@Pursuit-Perfect-System sorry if that has already been covered, but can you share what kind FX and Plugins you are using in that project? Are all native to Vegas?

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: Intel DX79SR
Ram: G.Skill 8x4GB DDR3 2133 (running at 1600 and lower latency)
CPU: 3930K @ 4.3GHz (custom water cooling system)
GPU: 1x ASUS Fury-X
Hard drives: 4x 2GB WD Red in RAID 5 (with Hot Spare), 2x Crucial 256GB SSD in RAID 0 (mulitcam project drive), 1x Samsung 850 Pro 256GB SSD (System), 1x Crucial 64GB SSD (temp files and swap file), 1x 3.5" Hotswap Bay, 1x LG BluRay Burner
PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM, 1x Sony HDTV 32" preview monitor

Pursuit-Perfect-System wrote on 4/30/2018, 1:24 PM

only some basic ones - native brightness contrast, Luts and Sharpness - nothing external.

That is my concern 4-5 hours for a render like this cpu only will be 20 once I start using Denoise or Mercalli or the one that stops led light flicker - forget the name now

OldSmoke wrote on 4/30/2018, 1:46 PM

VP15's build in LUTS FX or VisionColor? And you mentioned this is a 8bit project? Did you monitor disk activity too?

Last changed by OldSmoke on 4/30/2018, 1:48 PM, changed a total of 2 times.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: Intel DX79SR
Ram: G.Skill 8x4GB DDR3 2133 (running at 1600 and lower latency)
CPU: 3930K @ 4.3GHz (custom water cooling system)
GPU: 1x ASUS Fury-X
Hard drives: 4x 2GB WD Red in RAID 5 (with Hot Spare), 2x Crucial 256GB SSD in RAID 0 (mulitcam project drive), 1x Samsung 850 Pro 256GB SSD (System), 1x Crucial 64GB SSD (temp files and swap file), 1x 3.5" Hotswap Bay, 1x LG BluRay Burner
PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM, 1x Sony HDTV 32" preview monitor

Pursuit-Perfect-System wrote on 4/30/2018, 1:58 PM

I was using Vison colour but realised recently they make renders slow as hell so moved over to the native Luts option in VP15 and rendering times reduced by about 10x.

I havent monitored drive activity no - however I can run a test now rendering to my OS SSD from my new 8TB Barracuda Pro to rule out the Other HD which is a WD Black I think

Could it be too slow now its 85% full? Surely it would slow the project down not cause it to crash.

It renders fine to that drive using CPU Only GPU disabled

Thanks for trying to help

 

OldSmoke wrote on 4/30/2018, 2:11 PM

85% is rather full and if the drive is fragmented, it can cause problems.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: Intel DX79SR
Ram: G.Skill 8x4GB DDR3 2133 (running at 1600 and lower latency)
CPU: 3930K @ 4.3GHz (custom water cooling system)
GPU: 1x ASUS Fury-X
Hard drives: 4x 2GB WD Red in RAID 5 (with Hot Spare), 2x Crucial 256GB SSD in RAID 0 (mulitcam project drive), 1x Samsung 850 Pro 256GB SSD (System), 1x Crucial 64GB SSD (temp files and swap file), 1x 3.5" Hotswap Bay, 1x LG BluRay Burner
PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM, 1x Sony HDTV 32" preview monitor

Pursuit-Perfect-System wrote on 4/30/2018, 2:25 PM

I will run the test as mentioned - if thats a fix then happy days.

Pursuit-Perfect-System wrote on 5/31/2018, 11:51 AM

I thought I would update this thread - Magix support had me trying all sorts and nothing fixed my problem.

 

I posted today in the new 361 Build thread and one of the developers contacted me personally try a fix.

This is the fix

If you hold down the shift button can going into the preferences dialog, there is a tab called "Internal". Go to that tab. In the bottom of the dialog there is a text box. Type "Enable OpenCL/GL Interop". Set the value of this setting to "FALSE" and restart VEGAS. Then do your render again

I actually dont believe it - my problem is fixed at last - with a really simple settings change - I knew it had to be something.

 

There is a slight trade off - the cpu is working harder than normal but only about 80% with gpu working a little less at approx 10%

However an approx 8 hour render on CPU only is down to 3 hours like this so I am not complaining and am happy to be not leaving a render running all night every night.

Thanks very much to the Magix Developer for contacting me personally with this fix I am extremely grateful to you. So grateful in fact!!! Thank you

karma17 wrote on 6/1/2018, 10:08 PM

That's cool you got help after all that. Just for my own info, what does OpenCL/GL Interop do exactly? Why was that the culprit?