VP 17 + Red Giant (Magic Bullet Suite 13.0.11 or Universe 3.0.2) plugin causes VP to crush when trying to import RED's R3Ds.
Deleting FFCache_x64_1033 file, found in C - users - name - appdata - local - vegaspro - 17.0, before VP start, solves the problem til the next VP start.
Uninstalling Red Giant ehm "solves" it completely.
Can someone repro this?
I don't' know if this will be of any help to any body, but just in case:
I just installed VP17 buld 321 in a new Dell SPX 8930 i7 9700, with a Geforce RTX 2060.
Frustratingly, Vegas was still crashing after a few minutes of work, just as VP16 and VP15 had done.But I'd ordered the machine with just 8GB RAM, thinking I could get RAM cheaper than Dell wanted (I was right, and 32 more GB are on their way) and I thought RAM was the problem. But I read somewhere that if you're not gaming, but cutting video, Nvidia GPU drivers should be "Studio" drivers and not "Game" drivers.
I went to Nvidia.com and while I was ordering, using their text boxes to specifying my card, including choice of Studio or Game,I also saw a choice between "Standard" and "DCU." (or some such abbreviation) Their help feature told me to use Device Manager to see which of those my GPU was. I did all that, found I was a "Standard," and DL'ed and installed the right driver.
By surprise, Vegas has stopped crashing at all, even without the added RAM. I'm taking it slowly--no stress tests yet. Just enjoying not having to save with every edit and eventually losing something anyway.
But I'd recommend this process in any case..
Yes, I have the 2060 and a comparable machine (but I've got 64 G ECC RAM) and since I'm not going to be using Win 10 anytime soon, I can't use the "Studio" Nvidia Driver, they make if, as of now, for Win 10 only. I have a crash here and there, I'm actually running two Nvidia Cards - one Quadro, and I have a Black Magic card for when I want 10 bit output, and for Resolve.
It took a while to get them all to play nice together, and I usually disable the BM, It's pretty good, though while running vegas I don't get much of employment of either Nvidia card resources, the swing betwen 5% and 20%, with sometimes a quick spike. I noticed that one 3rd party fx actually really hit the card hard, which is a good thing, otherwise, they are not really being used all that much, talking about real time. I haven't tested rendering use.
To get your card to do certain specific tasks, you sometimes have to go to the Nvidia Control panel, specifically the 3d settings and there is the global, and there is a tab for each individual program on your computer, under that select VP 17 and you can select certain functionalities. You might not need it, but that is where you can make some adjustments if need be.
You can look at various videos on Youtube re: preferred settings.
My feedback:
1. This build (321) instantly crashes when Playback cursor reaches any Warp Flow transition on a timeline with GPU acceleration enabled on AMD card (Radeon HD 7850 2GB Pitcairn). With GPU acceleration disabled everything is ok.
Crashreport message:
Problem Description Application Name: VEGAS Pro Application Version: Version 17.0 (Build 321) Problem: Unmanaged Exception (0xc0000005) Fault Module: C:\Program Files\VEGAS\Vegas Pro 17.0\OFX Video Plug-Ins\MagixCVFx.ofx.bundle\Contents\Win64\MagixCVFx.ofx Fault Address: 0x000007FEC00D7260 Fault Offset: 0x0000000000357260 Fault Process Details Process Path: C:\Program Files\VEGAS\Vegas Pro 17.0\vegas170.exe Process Version: Version 17.0 (Build 321) Process Description: VEGAS Pro Process Image Date: 2019-09-23 (Mon Sep 23) 10:14:14
Tested on Win10 Pro/Win7 Ultimate with the same results.
2. Something is wrong with Event Pan/Crop scaling anti-aliasing methods of high-resolution PNG24-files with Alpha Channel (actually, this applies to any resolution PNG24+Alpha it's just more noticeable with 3840x2160) in comparison with Vegas 13 (at least). Here are some rendering examples with a noticeable difference between VP13 and VP17:
Vegas 13 render
Vegas 17 render
Project Settings
ZIP-archive (263kb) with .veg project files (for both 13 and 17 versions) and PNG24 sample file: https://files.catbox.moe/nl6hfv.zip
@AnotherOne Regarding those 2 issues:
1. I also see the same crash. I've made a separate post about it, as there may be extensive discussion about it, and to make it easier to find in search: https://www.vegascreativesoftware.info/us/forum/bug-vp17-warp-flow-transition-crash-with-gpu-acceleration--117349/
2. I'm also seeing the same. The rendered edges from VP17 are too soft. From VP13 they are much crisper. It seems to only affect video rendering. If I use "Save snapshot to video file..." to grab PNGs from your projects (in VP13 & VP17 respectively), I don't really see a difference. I think there might be even more discussion about that issue, and IMO lots of other formats and settings and Vegas versions need to be tested to establish the extent of it. Could you possibly make a new post on the forum just about that issue? I could add zoomed-in screengrabs (without zoom-anti-aliasing) to it to demonstrate the problem.
I think AC-3 Studio encoder cannot be modified... that's why 'Render Options' is grayed out.
The options include render loop region only which certainly can be modified and has been in the past in Vegas.
The options include render loop region only which certainly can be modified and has been in the past in Vegas.
That certainly could be modified still in VEGAS Pro 15 in the past as seen in the screenshot above. As for VPro 16 (and 17), please see below.
Does anyone know if they're working on a fix for dual card systems and HDR preview and render not working when hardware acceleration is enabled? I have 2 bug report threads on this for VP17.
Works fine with a 1 card system with same setup/settings exactly.
@Teagan Unlikely they're working on something specifically for that as their hands are already full and it's rare that SLI comes up as an issue on the forums. I don't think a great proportion of Vegas users use SLI. As previously advised, your best chance to get the issue into the developers' backlog is to submit a support request, including as much information about the issue as you can.
If they fix it for multi GPU I may be able to get it to work in single card mode in the NVidia control panel.
Could you possibly make a new post on the forum just about that issue?
@NickHope Done.
Unexpected behaviour. Not all my 3rd Party Licences Settings were immediately recognised. Updating required a PC Reboot to reactivate my BORIS MOCHAPRO19 License.
Vegas Pro crashes too often. The Boris licenses seem to appear and then disappear. Great features. But if it does not work correctly, makes it difficult to use. Software should be stable and sure footed.
Any solution to being able to update with W7 as OS? I understood (post escapes me) someone had stated that because of the 'terminate and stay resident' behaviour of the program that updating was problematical. Was a solution to the issue (outside of updating to W10) forthcoming or offered? Thanks.
I, too, suffered this problem. The offered advice that worked for me was to go into your Magix Account and download the VegasPro 17 from there. Once dowloaded, just launch the file and it will install the latest version.
@ Ralf ....
The minimum specs for VP17 state:
Operating system: Microsoft® Windows 10 (64-bit)
As good as it was, Windows 7 is now a part of MS history. Even MS is ceasing security updates from 14 January next year:
https://support.microsoft.com/en-us/help/13853/windows-lifecycle-fact-sheet
Mainstream support ended nearly 4 years ago. It would therefore not be expected that MAGIX (or any other softtware company for that matter) would support an OS that the OS owner no longer supports.
If you are getting VP17 to run successfully under W7, then that is great. But understandably it is extremely doubtful that MAGIX is going to address tech issues with W7 because MS won't be addressing any issues either.
The reality is if not wanting to update an older OS, then stick with the software that was designed to work successfully with that software back in it's day. Support must stop one day - it has for XP, ME and back to 3.1 and earlier.
@ Ralf ....
The minimum specs for VP17 state:
Operating system: Microsoft® Windows 10 (64-bit)
As good as it was, Windows 7 is now a part of MS history. Even MS is ceasing security updates from 14 January next year:
https://support.microsoft.com/en-us/help/13853/windows-lifecycle-fact-sheet
Mainstream support ended nearly 4 years ago. It would therefore not be expected that MAGIX (or any other softtware company for that matter) would support an OS that the OS owner no longer supports.
If you are getting VP17 to run successfully under W7, then that is great. But understandably it is extremely doubtful that MAGIX is going to address tech issues with W7 because MS won't be addressing any issues either.
The reality is if not wanting to update an older OS, then stick with the software that was designed to work successfully with that software back in it's day. Support must stop one day - it has for XP, ME and back to 3.1 and earlier.
I don't need the facile reminder of EOL for W7, thanks. We're all fully cognizant of that. I merely asked for a solution. If I were Magix, then focusing on why their software doesn't properly terminate would be a good investment of time. Regardless, W7 still commands nearly 35% market share across all desktop operating systems so please, I paid a large sum of money and I expect it to work at least reasonably enough -- which it does, protestation aside that we're unimportant now that Jan 20th is approaching.
facile reminder
That is just rude.
We're all fully cognizant of that
And who are "we"?
You are completely ignoring the FACT that VP17 does not support Windows 7.
we're unimportant now that Jan 20th is approaching.
That would be 14 Jan 20 actually. But that is Microsoft's decision, not MAGIX's - and relates to security updates only, not operational issues which ended some 4 years ago.
facile reminder
That is just rude.
We're all fully cognizant of that
And who are "we"?
You are completely ignoring the FACT that VP17 does not support Windows 7.
we're unimportant now that Jan 20th is approaching.
That would be 14 Jan 20 actually. But that is Microsoft's decision, not MAGIX's - and relates to security updates only, not operational issues which ended some 4 years ago.
Again, I asked for a solution not facile reminders of EOL. Thanks. I wasn't rude. You were by assuming I wasn't aware of the status of my operating system. But thanks. I'll file your posts where they need to go.
Have a nice day.
What a guy!
What a guy!
Thanks! You too! 😜👏👅👄🗣😸😹😹😹😹😹
LOL. Very classy. The end.
LOL. Very classy. The end.
Right back at you, Mr "last word".