Hi Nick

This isn't crashing Vegas, it's just rendering with a glitch that shouldn't be there. To be frank I don't care where these effects have originated from, to me the customer, it's a Vegas FX that I've paid for as part of Vegas Pro and expect to it to work.

Apologies if I've mis-understood you, but to me it seems you are saying that Magix isn't responsible and the problem is something we should just put up with because these are third party effects and so not bugs with Vegas? We might as well say all bugs are nothing to do with Magix as they bought Vegas from Sony!

I upgraded to 15 because I wanted to benefit from hardware acceleration that I didn't have in 13, now needed more than ever as I'm now 4K. This acceleration is something advertised as a reason to upgrade by Magix.

But...

1) I have to disable GPU accelerated processing because I can't trust the FXs to be rendered correctly. This option seems to disappear completely anyway if using Intel's latest graphics driver.

2) Intel HEVC 10 bit doesn't work at all.

3) Rendering using Intel QuickSync doesn't populate the meta-data correctly.

4) Dolby Pro has gone.

And these are just bugs and problems found in the first few hours of using 15, I've not done anything serious with it yet at all so goodness knows what else I'm going to fall over.

So I've hardly any benefit if any at all over and above version 13. Like I joked elsewhere, I'd be happier if Magix just stole my credit card details and took the upgrade fee without my permission, at least then I'd know I was robbed of the money, rather than just feeling I have been. Can we get refunds?

Regards

Phil

Can we get refunds?

These links below should apply for VPro as well

https://www.vegascreativesoftware.info/us/forum/is-there-a-30-day-money-back-policy--109022/#ca671997

Next time try before you buy as Nick recommends. And yes, you misunderstood Nick's history lesson.

Hi

Many thanks. Yes I did try it before I purchased but a) Some things just don't show up that quickly when having a play b) It was sometime ago on an older version and my trial had expired so I couldn't use the latest one, and c) I already use Vegas, and I never thought that 2 versions away from what I had could be so much worse, or broken enough that all the advertised upgrades I was interested in essentially do not work.

Regards

Phil

Hi

I didn't have the option to use GPU acceleration with my PC on 13 so never came across it. Ironically it was a quick go at re-rendering a project from Vegas 13 that had me wondering why the bottom of the frame had an odd artefact which I felt sure I'd never seen before, and it was easy to compare with a finished rendered version that had come out of Vegas 13 that indeed it was a new problem, at least for me.

Yes stupid for thinking posting a bug report might see it fixed given the bug has been around all that time! I've seen a lot of mentions of bugs that have been around for years.

Regards

Phil

Cornico, I believe you are out of line by calling someone stupid and possible violation of forum terms.

Cornico, I believe you are out of line by calling someone stupid and possible violation of forum terms.

Maybe but I'm not offended, I've been called worse and perhaps my remarks about being robbed were emotional rather than objective. 😀 Overall I'm just frustrated by bugs and issues that really shouldn't be, certainly not across 2 or more versions, and certainly not related to new functionality Magix have used to advertise the upgrade making me part with my cash!

Regards

Phil

Yes, but forums have terms that users agree to abide by.

"Insults, coarse language, and harassment of any kind toward other community members is forbidden."

Hi Nick

This isn't crashing Vegas, it's just rendering with a glitch that shouldn't be there. To be frank I don't care where these effects have originated from, to me the customer, it's a Vegas FX that I've paid for as part of Vegas Pro and expect to it to work.

Apologies if I've mis-understood you, but to me it seems you are saying that Magix isn't responsible and the problem is something we should just put up with because these are third party effects and so not bugs with Vegas? We might as well say all bugs are nothing to do with Magix as they bought Vegas from Sony!...

You misunderstood me. I'm actually cursed with an extreme, pathological hatred of Vegas bugs, no matter what their origin. Hence this. I was merely giving some background information to help anyone interested in this issue to understand it. That might even one day include someone who has the power to actually fix it.

You can report a bug by submitting a support request at https://support2.magix.com/customer/en/vegas/form , including as much detailed information about the problem as you can. That's the best way to draw the developers' attention to bugs and get them into their backlog. Even if you believe an issue has already been reported, further reports might push issues up the to-do list.

Thanks for the response.

Hi Nick

This isn't crashing Vegas, it's just rendering with a glitch that shouldn't be there. To be frank I don't care where these effects have originated from, to me the customer, it's a Vegas FX that I've paid for as part of Vegas Pro and expect to it to work.

Apologies if I've mis-understood you, but to me it seems you are saying that Magix isn't responsible and the problem is something we should just put up with because these are third party effects and so not bugs with Vegas? We might as well say all bugs are nothing to do with Magix as they bought Vegas from Sony!...

You misunderstood me. I'm actually cursed with an extreme, pathological hatred of Vegas bugs, no matter what their origin. Hence this. I was merely giving some background information to help anyone interested in this issue to understand it. That might even one day include someone who has the power to actually fix it.

You can report a bug by submitting a support request at https://support2.magix.com/customer/en/vegas/form , including as much detailed information about the problem as you can. That's the best way to draw the developers' attention to bugs and get them into their backlog. Even if you believe an issue has already been reported, further reports might push issues up the to-do list.

Many thanks, I have reported it, confidence level of it being fixed unfortunately are not high if it's been around since at least Version 13. I use that FX quite a bit to give a false shallow depth of field (blur top and bottom portions of the frame and used carefully on tripod steady shots it is quite convincing), is there another effect in Vegas doing a similar thing I could use in order to keep the acceleration enabled?

Regards

Phil