Split + Delete (While Playing) Causing Huge Hangs

Comments

pierre-k wrote on 8/15/2020, 2:17 AM

The team is now full of worries about VP18. Lots of crashes and for some non-functional AI FX. They now have other priorities. Still, I hope for a miracle.

Marco. wrote on 8/15/2020, 5:16 AM

@Phil_P
That little communication came through me and fr0sty. We were in communication with the developers, reached all the information we could gather and they approved they work on the issue. My guess still is this is a very hard and complex one.

Phil_P wrote on 8/15/2020, 1:17 PM

Marco and Frosty thanks much appreciation and credit to you.

However, with all due respect and as I mentioned numerous times, I work in QA testing myself. I have a history of over 12,000+ (valid) reports with just one of the software companies I work with.

Because of the above I am also well used to the fact that when an "outsider" reports an issue, it sometimes takes time for that info to be taken seriously and given credibility.

My info has been succinct and detailed including videos and screen shots and as much info as was available at the time.

Yet still, nobody has communicated directly with me

I have seen comments on these forums on much smaller and less "significant" posts, from "Vegas" people but none on at all on this thread.

I spent a lot of time and effort tracing this issue and pushing this thread. When I first posted it, it was pretty much ignored. Until I kept adding more info. I have been patient and polite.

A simple message from one of the official Vegas guys and/or a reply from support would have gone a long way.

Even if that message was to simply say "We are aware thank you and you can help is further by doing x y z".

Just because someone has an issue and is persistent about it and maybe expects a little interaction with the developers does not make them an idiot.

Remember, my first reply from support weeks ago, said the problem was my GPU. So I went and bought a new GPU. I then paid for V18 only 5 weeks after paying for V17 as support told me I had basically missed the time window.

None of this instils confidence. I have never been one to rant or even moan on forums etc. but this all makes me kind of understand why some folks here do it.

And finally, of course all the above is intended with the best possible intention that someone reading will realise that a customer has genuine reason to be a little upset.

Thanks again, P.

 

pierre-k wrote on 8/15/2020, 3:02 PM

a little upset? that's a lot to put it mildly.

I draw attention to this problem from VP12. Tips like - buy a new card or processor and don't complain, they're really crazy. If you buy everything and still have problems, some of them will advise you to turn off the gpu, including turning off So4.

They don't understand why you're upset and take it as an attack on the team.

However, if the official advice of the team with the purchase of new hardware does not solve your problems, then Magix should bear the consequences and reimburse you for unnecessary costs.

The team does not pay attention to old mistakes at all. Problems with Dram, number of threads, various flickering errors in the image during rendering, occasional problem with wav or mp3 editing. If an individual has a problem then they are ignored. But the team does not realize that not everyone will write here.

There are users who delete Vegas at the first problem and try other software. They have no time and boundless patience like us.

Marco. wrote on 8/15/2020, 3:04 PM

None of what you say about the VCS team is true.

pierre-k wrote on 8/15/2020, 3:16 PM

Before the release of Vp14, the team had to do the first thing - to address all users to report all the various bugs and try to fix them. And only then start releasing more versions. As I say start with a clean table. But that did not happen.

New features inexplicably affect other older ones, and more and more bugs arise. Without devoted fans, many of them will remain hidden.

That is all. This topic made me unnecessarily tired again.

j-v wrote on 8/15/2020, 3:21 PM

This topic made me unnecessarily tired again.


    Nobody obliges you to come here (to complain only)

 

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 17,18 and VMS PL 16,17 are installed, all latest builds
Both Nvidia GPU's have driver version 456.38 Studio Driver.
TV      :LG 4K 55EG960V

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

pierre-k wrote on 8/15/2020, 3:24 PM

If what I wrote is not true, then I am honestly happy. This means that all the errors mentioned are being worked on intensively.

fr0sty wrote on 8/15/2020, 6:27 PM

Marco and Frosty thanks much appreciation and credit to you.

However, with all due respect and as I mentioned numerous times, I work in QA testing myself. I have a history of over 12,000+ (valid) reports with just one of the software companies I work with.

Because of the above I am also well used to the fact that when an "outsider" reports an issue, it sometimes takes time for that info to be taken seriously and given credibility.

My info has been succinct and detailed including videos and screen shots and as much info as was available at the time.

Yet still, nobody has communicated directly with me

I have seen comments on these forums on much smaller and less "significant" posts, from "Vegas" people but none on at all on this thread.

I spent a lot of time and effort tracing this issue and pushing this thread. When I first posted it, it was pretty much ignored. Until I kept adding more info. I have been patient and polite.

A simple message from one of the official Vegas guys and/or a reply from support would have gone a long way.

Even if that message was to simply say "We are aware thank you and you can help is further by doing x y z".

Just because someone has an issue and is persistent about it and maybe expects a little interaction with the developers does not make them an idiot.

Remember, my first reply from support weeks ago, said the problem was my GPU. So I went and bought a new GPU. I then paid for V18 only 5 weeks after paying for V17 as support told me I had basically missed the time window.

None of this instils confidence. I have never been one to rant or even moan on forums etc. but this all makes me kind of understand why some folks here do it.

And finally, of course all the above is intended with the best possible intention that someone reading will realise that a customer has genuine reason to be a little upset.

Thanks again, P.

 

Your frustration is understandable, however there may be valid reasons they have not yet contacted you. Perhaps they're onto the source of the bug, but have not yet worked out a fix... perhaps they just haven't had time to get to responding to every thread because they're well on the way to having an update out soon that fixes numerous bugs, and aren't checking the forums as frequently as a result. Maybe your thread wasn't near the top when they did have time to respond to some of those others. It's a small team working during a pandemic, they're doing their best.

I do know we've found a way to reproduce this bug on another system using scripts that imitate the behavior described in your post, and I know it's been reported in a place where I know the team will see it, so there's that.

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Radeon VII

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

Phil_P wrote on 8/16/2020, 12:34 AM

a little upset? that's a lot to put it mildly.

I'm British

Your frustration is understandable

Yup thank you.

All I can say is that any QA/developer (including me - I also develop small software some of which require support, although I only have a few thousand users) knows that user forums, although sometimes tough and abrasive, will usually give a good idea of issues and complaints. It's not difficult to keep up with new threads daily, using "New Posts" as an entry point to the forum. I do it with many forums, (including this one now), it goes along with the morning email check.

And I have seen posts from Vegas people in the last few days I am not imagining that. Here is one, vey nice chap it seems:

https://www.vegascreativesoftware.info/us/forum/vegas-pro-18-internal-preferences-menu-gone--122757/

Anyhow, thanks again for the positive and calm responses. I certainly don't wan to turn fully in to that guy who moans and complains.

I have made all my points and I guess now will leave it at that.

Cheers and thanks again everyone.

cyro wrote on 8/16/2020, 4:07 PM

Just wanted to say: THANKS Phil_P. I recently ran into the same issue in VP18 and VP17 and it is definitely impacting my workflow and project times while cleaning up audio (de-umming etc.).

Thanks for staying on this and getting it through the initial layer of indifference/non-prioritization, let's hope this gets fixed soon!

VEGAS_EricD wrote on 8/28/2020, 4:13 PM

This is being looked into, and is listed in our issue tracker.

As far as paying attention to old issues - one of the first things we did 4 years ago when VEGAS became a MAGIX IP was to aggregate the old feedback that has been provided on the SCS forums (much of which is archived here) as well as set up an internal escalation path for reporting newly discovered issues through support.

Phil_P wrote on 8/28/2020, 4:53 PM

This is being looked into, and is listed in our issue tracker.

As far as paying attention to old issues - one of the first things we did 4 years ago when VEGAS became a MAGIX IP was to aggregate the old feedback that has been provided on the SCS forums (much of which is archived here) as well as set up an internal escalation path for reporting newly discovered issues through support.

Hi Eric,

Thanks for the message. That is great to hear. If I can help (further) in any way please let me know. :-)

cyro wrote on 9/22/2020, 6:50 PM

Just FYI - This issue is still happening in the latest Build 334, 100% repro after the update.

Phil_P wrote on 9/23/2020, 12:18 AM

Just FYI - This issue is still happening in the latest Build 334, 100% repro after the update.

Thanks for the heads-up. Was just downloading and will check today.