[BUG] VP17 Warp Flow transition crash with GPU acceleration

NickHope wrote on 10/2/2019, 12:22 PM

Further to @AnotherOne's comment here, regarding the Warp Flow transition causing a crash when GPU acceleration is ON (Radeon HD 7850 2GB Pitcairn), I also get the same crash when my Sapphire AMD Radeon HD6970 (Catalyst driver 15.7.1) is ON, whether it's manually adding a Warp Flow transition, or attempting to play a Warp Flow transition created by the Smart Split feature.

Do others with more recent AMD GPUs experience the same crash?

Do others with NVIDIA GPUs experience the same crash?

Comments

j-v wrote on 10/2/2019, 12:41 PM

Not with me on desktop if I understand the problem well Nvidia acceleration on, look

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W10 home version 2004 build 19041.264, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti.
Laptop  :Asus ROG GL753VD, W10 home version 2004 build 19041.264, CPU i7 7700HQ, 8 GB RAM, GeF. GTX 1050 (2 GB) + Int. HD Graphics 630(2GB).VP 16,17 and VMS PL 16,17 are installed, all latest builds
Both Nvidia GPU's have driver version 451.48 Studio Driver, desktop the Studio DHC driver
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEMCELL DONOR !!!

matthias-krutz wrote on 10/2/2019, 2:14 PM

Wrap Flow transition has not caused a crash on my desktop so far. AMD R9 380 4GB driver 19.9.2.

Desktop: Ryzen R7 2700, RAM 2 x Ballistix DIMM 16 GB DDR4-2666, X470 Aorus Ultra Gaming, Radeon R9 380 4GB, Win10

Laptop: T420, W7 SP1, i5-2520M 4GB, SSD, HD Graphics 3000

VEGAS Pro 14-17, Movie Studio 12 Platinum, Vegasaur, HitfilmPro

Sylk wrote on 10/2/2019, 2:21 PM

No crash on my NVidia system.

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 431.86 (Display, PhysX, HD Audio) // (Game Ready 436.15 if posted before 9/24/19)
Hardware:
[GPU] : Gainward GeForce 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
[PSU] : Corsair HX750
Devices:
[DSP1]: 30" DELL UltraSharp U3011 @2560x1600
[DSP2]: 26" iiyama ProLite E2607WS @1920x1200

[UPS] : Eaton 5PX 2200i RT

[CAM] : GoPro Hero8/4/3 Black. Apple iPhone 6S.

 

jrb101 wrote on 10/2/2019, 3:22 PM

Seems fine on my Radeon RX570 system too with GPU enabled.

Perhaps it's specific to Radeon HD series cards?

Jon Baker - Experienced in music creation, still a newbie at the video game 😉

(YouTube and Instagram - "Jon's Musical Musings")

PC: AMD Ryzen 3 2200G Desktop w/16GB DDR4 and Radeon RX570 (4GB) , ~5TB of storage across various HDDs, Focusrite Scarlett 6i6 audio interface, Mackie CR5BT studio monitors, 24" 1080p monitor (not anything special!)

For capture: Olympus PEN E-PL6 camera (1080p30) with external mic input adaptor and Olympus ME51S electret lavalier and Takstar SGC-598 shotgun mic and a Samsung Galaxy S10e (4K30 or 4K60) with Filmic Pro or stock video apps and external mic adaptor.

frmax wrote on 10/2/2019, 5:56 PM

No crash, Nvidia 2080RTX

monoparadox wrote on 10/2/2019, 7:21 PM

No problem with Radeon RX590

Grazie wrote on 10/2/2019, 9:54 PM

NVIDIA GPU: Straightforward Warp Transition can't repro.

However . . .

STRESS TESTED employing a Transition Progress Envelope and was able to crash everything!:

I have the ERROR Dump to send off, if that assists?

 

NickHope wrote on 10/3/2019, 1:24 AM

Thanks for the feedback. So it looks like the basic bug might only affect Radeon HD GPUs. I have submitted a support request (unfortunately the Support email "system" appears to have lumped it in with [Ticket#2019100217002991], which was for another issue).

@Grazie Can't do any harm to submit your report. Does the problem description look like AnotherOne's in this comment (which is the same as mine)?

Grazie wrote on 10/3/2019, 1:40 AM

How do I send the Report once I've got out of that "Send Email" thing?

NickHope wrote on 10/3/2019, 2:13 AM

How do I send the Report once I've got out of that "Send Email" thing?

@Grazie Assuming your crash generates a "Problem Report" window:

  1. Force the crash
  2. Check both boxes on the Problem Report window
  3. Write a brief description of what you were doing in the "Optional..." box
  4. Include your name and email address in the "Optional..." box
  5. Click Send

The PRS system works properly these days.

Grazie wrote on 10/3/2019, 2:22 AM

Nick what is your @ callout?

And now I can't repro!!! - Anyway, the email links dont fireup my Gmail account. It wants me to go via M$. So, is there another way to get this to the Hobbits?

NickHope wrote on 10/3/2019, 7:44 AM

Nick what is your @ callout?

If you type @Hope then my name should appear in the list of people you can tag. There are too many "Nick***" usernames and unfortunately the tagging system can't deal with spaces in user names.

And now I can't repro!!! - Anyway, the email links dont fireup my Gmail account. It wants me to go via M$. So, is there another way to get this to the Hobbits?

I'm not sure what email links you are referring to. The Problem Reporting Service (i.e. the "Problem Report" window that you get after a crash) doesn't use email; it just sends the report. And you don't get an email receipt for that.

The other way to get info to Support is to file your own Support Request, then reply to the acknowledgement email, attaching further info as you do so. But you no longer need to mess about zipping up problem reports and attaching them to emails, because the Problem Reporting Service now works correctly.

Having said all that, if you can't now repeat that crash, maybe best not to bother at the moment, as they no doubt have their hands full with clear cut issues.

Grazie wrote on 10/3/2019, 11:10 AM

I'm not sure what email links you are referring to. The Problem Reporting Service (i.e. the "Problem Report" window that you get after a crash) doesn't use email; it just sends the report.
 

@Hope - Well, when I go SEND I get an EMAIL option. That’s what I mean.

And you don't get an email receipt for that.

@NickHope - Never said I did. And to repeat, I get an Email option to send. What can I say?

NickHope wrote on 10/3/2019, 11:48 AM

I'm not sure what email links you are referring to. The Problem Reporting Service (i.e. the "Problem Report" window that you get after a crash) doesn't use email; it just sends the report.
 

@Hope - Well, when I go SEND I get an EMAIL option. That’s what I mean.

And you don't get an email receipt for that.

@NickHope - Never said I did. And to repeat, I get an Email option to send. What can I say?

@Grazie I don't think that is typical or intended behaviour. This video shows what happens when I submit a Problem Report. I don't remember ever seeing an "email option", or having to set this up in any way:

Might be worth a Support Request for that issue in its own right.

Grazie wrote on 10/3/2019, 12:11 PM

@NickHope - Ahah! Thanks for that, when I go SEND I get an Auto Menu fired-up at me asking me to use an EMAIL account! Previously I have had exactly what you’ve shown in your video.

NickHope wrote on 10/3/2019, 12:57 PM

@Grazie I guess it must be something about your Windows/router/network/firewall connection that is giving you that menu. Not my strong point I'm afraid. Someone here might know.

This also explains the "uh??" response on your thread here. There might be the best place to follow this up, probably best with screenshots or recordings of what you're seeing.

Grazie wrote on 10/3/2019, 1:19 PM

@NickHope - Indeed. You were knowing one thing, but I was seeing another! The NEXT time I get that Message Error Send thingie, I’ll hit SEND and try and remember to do a Grabski!

NickHope wrote on 10/4/2019, 12:46 PM

Support's answer about the Warp Flow crash:

"I can see that this card is no longer updated and the driver version was released in 2015 as it is a much older card. As such it does not meet our system requirements that can be found on our site here https://www.vegascreativesoftware.com/us/vegas-pro/specifications/#productMenu
Because of this it appears that the card may not be fully compatible with VEGAS Pro 17 and crashes may be experienced when using certain function."

Fair enough, I suppose, especially as it's a new transition only introduced in VP17. I will leave it in the Known Issues list in case it helps someone else troubleshoot, but I will insert the word "unsupported".

@AnotherOne