Comments

Sylk wrote on 9/1/2019, 10:59 AM

 

Hi @Harry-Lamoen, need more informations.

- on which other previous version it works?

- the moment where it stops; at start? at middle?

- what format and settings you try to rendering?

Last changed by Sylk on 9/1/2019, 11:00 AM, changed a total of 1 times. 

Software:
[OS]  : Windows 10 Ent. x64 v1903 (18362.535)
[NLE] : Vegas Pro 17.0 (Build 321) // (Build 284 if posted before 9/24/19)
[DRV] : Studio 536.23 (Display, PhysX, HD Audio) // (Game Ready 436.15 if posted before 9/24/19)
Hardware:
[GPU] : Gainward RTX 4090 Phantom / GTX 1080 Phoenix GLH
[CPU] : Intel Core i7-2600K @3.4GHz OC@4.5GHz (HyperThreaded) | AirCooling: Noctua NH-D14
[RAM] : 16GB (4x 4GB GSkill Ripjaws X DDR3 1600MHz 9-9-9-24) @1333MHz
[SSD] : Samsung 860 Pro 1TB
[MOB] : Asus P8P67 Deluxe (Rev.1), No iGPU support
[SND] : Asus Xonar Essence STX
[PSU] : Corsair HX750
Devices:
[DSP1]: 30" DELL UltraSharp U3011 @2560x1600
[DSP2]: 28" Samsung U28D590 @3840x2160

[UPS] : Eaton 5PX 2200i RT

[CAM] : GoPro Hero8/4/3 Black. Apple iPhone 11Pro/6S.
[REC] : Zoom Handy Recorder H4.
Harry-Lamoen wrote on 9/1/2019, 11:10 AM

Vegas pro 16 worked
Halfway it stops
1920 - 1080
But i have the idea that Boris BCC that comes with Vegas has something to do with it.
When starting Vegas it comes with error

After i uninstalled BCC and reinstalled Vegas without Boris it still comes up with this error but if i click OK Vegas starts up. which is strange. Anyway rendering still stops.
Why does the Boris notice comes up while i didnt install this ?

Sylk wrote on 9/1/2019, 3:50 PM

@Harry-Lamoen if i'm not wrong, VP17 needs BCC 12 update.

Software:
[OS]  : Windows 10 Ent. x64 v1903 (18362.535)
[NLE] : Vegas Pro 17.0 (Build 321) // (Build 284 if posted before 9/24/19)
[DRV] : Studio 536.23 (Display, PhysX, HD Audio) // (Game Ready 436.15 if posted before 9/24/19)
Hardware:
[GPU] : Gainward RTX 4090 Phantom / GTX 1080 Phoenix GLH
[CPU] : Intel Core i7-2600K @3.4GHz OC@4.5GHz (HyperThreaded) | AirCooling: Noctua NH-D14
[RAM] : 16GB (4x 4GB GSkill Ripjaws X DDR3 1600MHz 9-9-9-24) @1333MHz
[SSD] : Samsung 860 Pro 1TB
[MOB] : Asus P8P67 Deluxe (Rev.1), No iGPU support
[SND] : Asus Xonar Essence STX
[PSU] : Corsair HX750
Devices:
[DSP1]: 30" DELL UltraSharp U3011 @2560x1600
[DSP2]: 28" Samsung U28D590 @3840x2160

[UPS] : Eaton 5PX 2200i RT

[CAM] : GoPro Hero8/4/3 Black. Apple iPhone 11Pro/6S.
[REC] : Zoom Handy Recorder H4.
Harry-Lamoen wrote on 9/2/2019, 6:27 AM

I have the idea that the windows energy screen saver plays a role in it.

Dr Zen wrote on 9/2/2019, 8:19 AM

Hi Harry_Lamoen

I will add my 2 cents worth.
After uninstalling 3rd party plugins, you need to delete/clean the temporary files cache for Vegas.
I suspect that's why that error window is popping up, even though you un-installed it.
I would recommend you actually do a full program reset of Vegas, just to be sure.

Reset instructions here:
https://www.moviestudiozen.com/doctor-zen-faq/573-how-to-reset-sony-software-to-default-settings

@Sylk is correct in what they have said.
Many older 3rd party plugins/FX will not work in VP17, because a major change was made to the way these FX are read/work in Vegas. All the big 3rd party FX makers were informed of this change and most of them have provided updates to make them compatible with Vegas Pro 17.

If you have added any 3rd party FX in your project and they have not been updated, you will need to remove them from your project or use an older version of Vegas to render with.

Final comment: When I'm rendering anything in Vegas, I make sure to turn OFF any screen saver that may be set to run after X amount of time. In the Windows search bar (lower left) type "screen" and select Turn Screen Saver on/off.

Regards
Derek

Harry-Lamoen wrote on 9/2/2019, 11:24 AM

Thanks a lot for professional help, i will have to contact Boris BCC