19 will not start

Glen-Stork wrote on 6/24/2022, 11:23 AM

Just installed 19. when the splash screen comes up it gets to ASIO driver legasy 2016 then just stops. Nothing at all. I have rebooted several times and still the same. what is worse is that when I try to start up 18 it now does the exact same thing. I have no editing suite now. Just a bit of panic setting in. Win10 64bit Vegas pro 19.

Comments

diverG wrote on 6/24/2022, 11:30 AM

Assuming 18 functioned before installing 19 I would suggest rolling back to the system image you took before adding new software. Some info on your computer would help.

Sys 1 Gig Z-890-UD, i9 285K @ 3.7 Ghz 64gb ram, 250gb SSD system, Plus 2x2Tb m2,  GTX 4060 ti, BMIP4k video out. Vegas 19 & 122(194), Edius 8.3WG and DVResolve19 Studio. Win 11 Pro. Latest graphic drivers.

Sys 2 Laptop 'Clevo' i7 6700K @ 3.0ghz, 16gb ram, 250gb SSd + 2Tb hdd,   nvidia 940 M graphics. VP17, Plus Edius 8WG Win 10 Pro (22H2) Resolve18

 

Glen-Stork wrote on 6/24/2022, 12:33 PM

This is a windows 10 64bit system 32mb ram  NVIDIA GeForce RTX 2070 SUPER

Glen-Stork wrote on 6/24/2022, 2:30 PM

I did a restore and then the program worked then after reinstalling the program and all the add ons it has gone back to the same thing. I will remove all of the add ons and try again

Glen-Stork wrote on 6/24/2022, 2:31 PM

I think the restore was to before the microsoft visual c++ 2013 was intalled.

Glen-Stork wrote on 6/24/2022, 2:34 PM

removed sound forge and it went all the way to creating window then it crashes. I'll reboot now and see if that clears up

Glen-Stork wrote on 6/24/2022, 2:40 PM

Extra Information
   File:                C:\Users\Duane Stork Photo\AppData\Local\VEGAS Pro\19.0\fileio_x64.log
   File:                C:\Users\Duane Stork Photo\AppData\Local\VEGAS Pro\19.0\persist.prefs
   File:                C:\Users\Duane Stork Photo\AppData\Local\MAGIX\FileIO\1.0\So4HardwareDetectionError.log
   File:                C:\Users\Duane Stork Photo\AppData\Local\MAGIX\FileIO\1.0\So4HardwareDetectionOutput.xml
   File:                C:\Users\Duane Stork Photo\AppData\Local\VEGAS Pro\19.0\dx_video_grovel_x64.log
   File:                C:\Users\Duane Stork Photo\AppData\Local\VEGAS Pro\19.0\svfx_video_grovel_x64.log
   File:                C:\Users\Duane Stork Photo\AppData\Local\VEGAS Pro\19.0\ocio_x64.log
   File:                C:\Users\Duane Stork Photo\AppData\Local\VEGAS Pro\19.0\dx_grovel_x64.log
   File:                C:\Users\Duane Stork Photo\AppData\Local\VEGAS Pro\19.0\vegas_script_x64.log
   File:                C:\Users\Duane Stork Photo\AppData\Local\VEGAS Pro\19.0\gpu_video_x64.log

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 19.0 (Build 643)
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        C:\Program Files\Common Files\OFX\Plugins\BCC_DFT\BCC+.ofx.bundle\Contents\Win64\BCC+.ofx
   Fault Address:       0x0000000043D50969
   Fault Offset:        0x00000000001B0969

Fault Process Details
   Process Path:        C:\Program Files\VEGAS\VEGAS Pro 19.0\vegas190.exe
   Process Version:     Version 19.0 (Build 643)
   Process Description: VEGAS Pro
   Process Image Date:  2022-06-14 (Tue Jun 14) 23:43:46

Glen-Stork wrote on 6/24/2022, 2:46 PM

Deleting the OFX file fixed it. But why wont it load with it? Why cant I use that plug in

jetdv wrote on 6/24/2022, 2:58 PM

You might try reinstalling Boris now that it's starting.

diverG wrote on 6/24/2022, 4:25 PM

Searching the forum reveals references to some problems experienced with asio drivers and soundforge. No similar problems at my end, 636 & 643 loaded without problems.

Sys 1 Gig Z-890-UD, i9 285K @ 3.7 Ghz 64gb ram, 250gb SSD system, Plus 2x2Tb m2,  GTX 4060 ti, BMIP4k video out. Vegas 19 & 122(194), Edius 8.3WG and DVResolve19 Studio. Win 11 Pro. Latest graphic drivers.

Sys 2 Laptop 'Clevo' i7 6700K @ 3.0ghz, 16gb ram, 250gb SSd + 2Tb hdd,   nvidia 940 M graphics. VP17, Plus Edius 8WG Win 10 Pro (22H2) Resolve18

 

RogerS wrote on 6/25/2022, 9:14 AM

Deleting the OFX file fixed it. But why wont it load with it? Why cant I use that plug in

Great question. I'd pose it to Boris and send them a link here and include the text of the error message.