Troubleshooting suggestions: https://www.vegascreativesoftware.info/us/forum/faq-vegas-pro-won-t-start-what-can-i-do--104784/
If those don't help, and you want help with diagnosing and solving this, please provide more information in accordance with this post: https://www.vegascreativesoftware.info/us/forum/important-information-required-to-help-you--110457/
Trust me, Premier and Final Cut are no better. It would be great if Magix gave you a little more guidance on cards tested and verified as it does seem card and drivers do make an impact on stability.
My old Nvidia GTX 560ti was horrible for stability but a Radeon R7 250x was solid as a rock. My new RTX 2060 is also solid, not a single crash yet but it is a freshly built system and ive not had years of monkeying with drivers to contend with.
Often its the drivers which are the problem. Make sure you do a clean install of them. For AMD the latest were horrible, seriously horrible for stability. The most stable I found for AMD were whql-win10-64bit-radeon-software-crimson-relive-17.7.2-july26
Its often down to how the vendors change their API's and then expect every bit of software to jump on board and make sure they are complient.
Yeah, more likely the case is shoddy code from AMD. I quit using their cards years ago because of how bad their drivers were.
I've also had crashing issues with Vegas Pro 15 and 16 using the NewBlueFX products included with Vegas Pro upgrades (you know, the ones used to entice you to upgrade Vegas Pro).
1). They never truly work without issues with Vegas Pro (not sure if Magix or NewBlueFX is to blame here) and
2). They never work past the Vegas Pro version you get them with, so I've quit using them as a reason to upgrade.
--------------------------------------------------
Per Nick's request...
VEGAS Version & Build: Vegas 16 (latest build)
Windows Edition & Version: Windows 10 Pro (all current updated applied)
Camera/App that created your footage: SONY PXW-Z90
Your Delivery Destination: JW Platform
Exact symptoms of your problem: Constant crashes, daily.
PS - I've visited these links multiple times. None of the suggested "fixes" work.
Troubleshooting suggestions: https://www.vegascreativesoftware.info/us/forum/faq-vegas-pro-won-t-start-what-can-i-do--104784/
If those don't help, and you want help with diagnosing and solving this, please provide more information in accordance with this post: https://www.vegascreativesoftware.info/us/forum/important-information-required-to-help-you--110457/
Yeah, more likely the case is shoddy code from AMD. I quit using their cards years ago because of how bad their drivers were.
I have been using AMD cards since 2014 when I switched from two GTX580 to two R9 290 and never had an issue. I currently have a Fury X in my system and it too works without any issue. AMD driver's are no worse then NVIDIA drivers, that is a thing of the past.
@Corkey Plenty missing from that info, including the crucial info about your media and which decoder Vegas is using to decode it. But looking at the specs of your cam, which shoots primarily XAVC, it's likely that so4compoungplug.dll is the decoding plug-in used, and therefore you have a good chance of improving stability by disabling it. It's not really something known to affect startup, which is why it's not in the startup-troubleshooting link I gave you earlier, but it certainly can help with "Constant, daily crashes" from your later comment.
I just recently purchased (Feb. 2019) a Sony FDR AX-53. It shoots XAVC-S, in mp4 at 100Mbps. I pull out that fast ProGrade SDXC card I purchased as well, put it into that fast ProGrade Dual SDXC card reader (memory card and card reader use UHS-II Standard), with card reader connected to back of computer via USB 3.1 Gen 2 Type-C port (bought an internal front panel, but the USB 3.1 Gen 2 cable too short to get to my motherboard connection). Put that downloaded content on a newly purchased Intel 660p PCI-e 3.0x4 NVMe drive, then open up Sony Catalyst Browse, and Transcode that/those files to MXF. Then I open that transcoded file in Vegas Pro Suite 15 (Build 416), and have no issues at all, either editing, timeline speed, etc. And that is using the camera's 4K24p recording. My rig is in my signature, no overclock. Crashes, usually due to something stupid I did.
Now, those AMD cards/drivers...well, I have had bad luck in the past, but waiting for that Tax Refund to get the new AMD Radeon VII, and give them another go. Heck, moved CPU over to AMD from Intel, I'll give them another shot at the GPU side of things. I know they work well (cards and drivers), though I always seemed to have an issue, most likely due to something I did.
If computer is always crashing, I would suspect that there are other "Hardware" problems within a machine, than what I seem to always see people complain about the software side of things. Undo overclocks, make sure you got air flow (clean case and fans), clean up the "less than ideal" cable management, etc. Oh, and from what a lot of Vegas Forum, Creative Cow, FX Home (HitFilm), Adobe, etc. - don't download and use "CODEC" packs. Best way to muck up your system! I know, I know, if it is said on YouTube, it must be the Truth!
you can try disabling iGPU in BIOS and see how you go after that..
you can try disabling iGPU in BIOS and see how you go after that..
No such option in my BIOS.
@Corkey Plenty missing from that info, including the crucial info about your media and which decoder Vegas is using to decode it. But looking at the specs of your cam, which shoots primarily XAVC, it's likely that so4compoungplug.dll is the decoding plug-in used, and therefore you have a good chance of improving stability by disabling it. It's not really something known to affect startup, which is why it's not in the startup-troubleshooting link I gave you earlier, but it certainly can help with "Constant, daily crashes" from your later comment.
The application won't even launch, so there is no way for me to disable so4compondgplug.dll
So besides the "JW Platform" being some place to upload videos for website applications, if I got that correct, their site "JW Platform" had no reference on what FORMAT a video should be. And no, will not do any "Trial" form something I will never use.
Additionally, you have yet to provide the needed information requested earlier, and "Windows Pro 10" does not suffice. Already went to the Sony site on your listed camera, and it captures videos in the same type of format as my Sony FDR AX-53, which I already gave you a suggestion to try. You have not provided any information on the "videos" (Nick's post would show you where to get and how to use "MediaInfo"), your render and project properties, etc., how can anyone assist you? Your video card you listed, AMD Radeon Pro WX7100 is essentially the "Pro Workstation" class of GPU, as the Vega 56/64 are consumer class, which are working for people in Vegas Pro and Vegas Movie Studio.
Yep, this is why I never got into any type of "Customer Service" job in the workplace, after I retired from Military Service. Don't have the patience, and one of my favorite sayings (of many I like or use): "I'm from Missouri, show me".
So besides the "JW Platform" being some place to upload videos for website applications, if I got that correct, their site "JW Platform" had no reference on what FORMAT a video should be. And no, will not do any "Trial" form something I will never use.
Additionally, you have yet to provide the needed information requested earlier, and "Windows Pro 10" does not suffice. Already went to the Sony site on your listed camera, and it captures videos in the same type of format as my Sony FDR AX-53, which I already gave you a suggestion to try. You have not provided any information on the "videos" (Nick's post would show you where to get and how to use "MediaInfo"), your render and project properties, etc., how can anyone assist you? Your video card you listed, AMD Radeon Pro WX7100 is essentially the "Pro Workstation" class of GPU, as the Vega 56/64 are consumer class, which are working for people in Vegas Pro and Vegas Movie Studio.
Yep, this is why I never got into any type of "Customer Service" job in the workplace, after I retired from Military Service. Don't have the patience, and one of my favorite sayings (of many I like or use): "I'm from Missouri, show me".
Not sure why this is important in regards to solving my problem, but a simple Google search produces...
https://support.jwplayer.com/articles/supported-video-and-audio-formats-reference
Since I am using a "Pro Workstation" class GPU, do I need to move to a more "Pro Workstation" class software?
To reiterate. The application won't even launch.
@Corkey In an earlier post you mentioned that you use 3rd party plug ins like NewBlue FX and others? Is your VP16 install mixed in with the VP14, VP15 and all the 3rd party plug in software? If so, that may well be the major issue of your crashes or Vegas not even able to launch.
I gave up on NB a long time ago. Their upgrade policies and installer is a nightmare. If you have a drive that you don’t use and are still willing to experiment, a clean Windows install and just Vegas 16 install without any 3party software might be worth a try. The WX7100 should in fact play very nicely with Vegas.
Does your motherboard have an onboard GPU? Are there HDMI, VGA, etc. ports on the motherboard itself? I know you looked for an option to disable integrated GPU in BIOS... just making sure there is no hardware there at all.
When you boot Vegas 15, and go into preferences, what is listed as your GPU acceleration device? Do you see your WX7100 listed? I'm curious here because, if there is indeed an integrated GPU involved, Vegas 14 and 16 could be crashing trying to initialize it, and maybe 15 is set to use the proper GPU... or perhaps 15 is set to not use GPU acceleration at all... and that is why it is able to boot...
Does anybody out there have the recommended configuration for magix vegas pro16. For example I am running win10 pro64bit/ 4th generation i7, 16 gigs ramm / a nvidea gtx 1050ti graphics and two internal drives and 1 external for a backup. I have my os and all apps on the C: and i use my D: drive(7200rpm)( as a media drive for my video and media files only. Now should the temp files folder be on c or d? Are there any other recommended tweaks I should do. I am having a lot of crashes and can't figure out why?
When you are having a crashing issue, you need to look at what media you are using (there is a program called mediainfo that will give you detailed reports about every aspect of the media being used, it helps us to identify problems people are having, so come prepared with a mediainfo report on all of your source media clips (or at least one per camera used). Then we're going to want to know your exact project settings as well. That will help us get started with diagnosing your issues. It's also best to put it into a new thread, so we can keep up with things easier when diagnosing your problem.
Your hardware is ok, I would personally recommend more RAM, and maybe solid state internal drive (especially a NVME internal drive), but your hardware isn't likely the cause of your issue. If so, it would be due to a hardware failure, as your rig is more than powerful enough to run Vegas in most cases.
Plugins. What do you have installed and are they upto date? Often we use older versions to save paying for updates
As per a discussion in another thread and my own experience: if you use an Nvidia card, stay away from the latest drivers. I'm using a GTX 1080 Ti with driver version 417.35 and things work fine.
you can try disabling iGPU in BIOS and see how you go after that..
No such option in my BIOS.
If you're using a laptop you might be out of luck. most of my issues have stopped once I disabled my iGPU.
Boris FX BCC Units causes Vegas Pro 16 to crash on launch!
OK. If you track my posts over the course of the last year or so, you will most likely read me complaining about the stability of Vegas 16. Turns out that the real culprit is Boris FX BCC Units 10.9.2279.0 (the one that installs with Vegas Pro 14 Suite). It causes Vegas Pro 16 to crash on launch. I've tested this on multiple computers with the same result. The only way to get Vegas Pro 16 to launch is to uninstall Boris FX BCC Units.
One thing this has taught me is to never use a plug-in as a reason to upgrade to a newer version of Vegas. Not only could the plug-in be a potential cause for instability issues, they also expire whenever you upgrade to newer version of the software. So, they essentially end up being worthless accept to use over the course of one software version and they never go with you when you update a project with a newer version of Vegas.
This time it is NewBlueFX...Titler Pro 7. No chance of having consistent (or matching) titles for my project series when I'm forced to use something else because this NewBlueFX plugin doesn't work consistently and/or without issues.
Again, I remind you, NEVER USE A PLUGIN AS A REASON TO UPGRADE! My experience has been nothing but headaches. Eventually they will stop working (either because you upgraded and loose access to the plugin or they just plain break and refuse to work).
That is all.
You are right, never use a plug-in as a basis to upgrade. Also since 2015 I have been using XAVCS 4K from Sony AX100 camera. Used it in VP13, 14, 15, 16 and now 17. I have NVIDIA card and VP cannot hardware decode as it is not recognised as standard H264 as it is inside the Sony wrapper. I compared VP17, Resolve and Power director for timeline GPU decoding performance and they were all the same at 11% GPU utilisation. I have disabled the So4compundplug as it just slows down everything by a factor of three. So far on my system (i5, 16GB ram, windows 10, GTX1080Ti ) I have has no VP17 crashes and thats editing and rendering to Blu-Ray three projects each of 1000 clips. I have used levels filter, stabilization and colour grading. The Newblue titler 5 works but is not nice to use - too cluncky and laggy.