VideoStudio 2021 (Ultimate) Constant Random Crashing

[lata]

Jpeg properties, does the encoding show as Baseline or Progressive

Attach images to posts, info here
https://forum.corel.com/viewtopic.php?t=57659

[dalessad]

Hi All,
I've continued with struggling with random crashing and have been saving regularly in case of crashes.
What I've experienced now is that the saved file is corrupt. I'm getting a "Failed to open document." message when I try to open the saved file. This is after restarting the Video Studio application AND restarting the OS.
I've spent upwards of 30 hours making a reel and now the file is corrupt and if this file cannot be opened, I've lost this work. I want to use a bunch of expletives directed at the Corel people that build this horrendously unstable software. I've struggled to m

COREL: What the F--k is wrong with your software? The support person I've chatted with asked for a full system dump of every application, device ID, user path, installed program, etc. which is ridiculously insecure to be sending especially over email. Then I'm told someone would get back to me with a fix once one is determined? How is that possible? Either there's a solution already for the problem I'm having, in which case give me the details on the fix; or there is no idea what the problem is and the tech is just pacifying me hoping I'll go away.

Either way the support is piss-poor, the Video Studio software is aggravatingly unstable and has now torched hours of my effort and possibly sunk my project.

Does anyone from Corel read these message? Can someone please reach out to me to provide some type of support from Corel. The people here have been great but the developers or product people at Corel need to see this and do something.

This has been total BS for the past 3 year with this wretched software. God dammit!

Adam

[dalessad]

ah got it. You were referring to properties in Video Studio.
The images I've spot checked have all been "Base line" for encoding.
File attached.

[dalessad]

More continued crashing after leaving the system and VS 2021 running for the evening. Perhaps some type of application garbage collection messes something up.
As soon as I interacted with the application it vanished and crashed.
Also on the restart of VS2021, when reloading the applicaiton more "insufficient memory" errors. I noticed this happens if the Edit tab is not selected before opening or if the Edit tab is open to a bunch of pictures I imported into the library. (folder has about 150 pics although I've split them into multiple years). Project has about 2000 photos in various folders.

If I select the standard Background --> Images folder and open the project then VS memory seems stable at ~300MB. But if I have the Edit tab selected with my photo folder or just the Home tab then the memory progresses towards 1500MB and crashes.

See attachment.

[Davidk]

A lamentable tale . . but there is one sleeper re the QT file discussed early in the thread, with specific reference to the registry.
Your original post indicated a windows re-install had been tried, without effect. Can you clarify that? Specifically, was it just a re-install, or was it a clean install? The former does re-install windows but keeps the registry file and the apps, whereas a clean install is just that - nothing is carried over and you get a new windows install with a new registry, and you have to re-install everything you want to use: a real pain and a major incentive not to do it.
However, registry entries are rarely fully expunged when software is un-installed: vendors are careful to make entries for the app during install, but rarely take the same care when it's uninstalled. As an example, on my old system I found using a registry search program that I had residual entries (880+) from beta and release versions of CVS from X8 onwards, even tho those versions had long been uninstalled. That had frustrating consequences for newer versions: share did not work with any version first installed under win7 after a win10 upgrade, and MyDVD did not appear for any new versions I installed. All of that got fixed when my m/b failed (7+ years old) last August and I had to replace it, RAM, cpu and SSD. Essentially, a new PC, a clean win10 install and specifically a new registry: the old irritations just "went away".
My point here is that the apparent QT issue may be a result of entries in the registry, even if "programs and features" says it's not installed. If you have not already done it, I'd suggest a clean windows install, updated, then a progressive install of software you really want to run. This gets you a new registry with no leftovers to ##### things up. And then confirm whether the original issues are still extant.

[lata]

I was browsing the previous replies, we recommended deselecting the Acceleration options, you indicated NOT doing that.
Have you since tried using the program without Acceleration?

[dalessad]

I was browsing the previous replies, we recommended deselecting the Acceleration options, you indicated NOT doing that.
Have you since tried using the program without Acceleration?

I turned off the acceleration features during the crashing with the "qtbridge.exe" issue, which didn't' seem to have any effect as crashing was regular. I have not tried it after the VS2021 uninstall, cleanup tool and progressive install where I am now getting the vstudio.exe crashes as seen in logs or the crash with no log entry at all. Will turn it off now and see how that goes.

Thanks again for all the suggestions and to the other helpful forum members. It really shouldn't be this hard. It's like a Rube Goldberg process.

[dalessad]

A lamentable tale . . but there is one sleeper re the QT file discussed early in the thread, with specific reference to the registry.
Your original post indicated a windows re-install had been tried, without effect. Can you clarify that? Specifically, was it just a re-install, or was it a clean install? The former does re-install windows but keeps the registry file and the apps, whereas a clean install is just that - nothing is carried over and you get a new windows install with a new registry, and you have to re-install everything you want to use: a real pain and a major incentive not to do it.
However, registry entries are rarely fully expunged when software is un-installed: vendors are careful to make entries for the app during install, but rarely take the same care when it's uninstalled. As an example, on my old system I found using a registry search program that I had residual entries (880+) from beta and release versions of CVS from X8 onwards, even tho those versions had long been uninstalled. That had frustrating consequences for newer versions: share did not work with any version first installed under win7 after a win10 upgrade, and MyDVD did not appear for any new versions I installed. All of that got fixed when my m/b failed (7+ years old) last August and I had to replace it, RAM, cpu and SSD. Essentially, a new PC, a clean win10 install and specifically a new registry: the old irritations just "went away".
My point here is that the apparent QT issue may be a result of entries in the registry, even if "programs and features" says it's not installed. If you have not already done it, I'd suggest a clean windows install, updated, then a progressive install of software you really want to run. This gets you a new registry with no leftovers to ##### things up. And then confirm whether the original issues are still extant.

Hi David,
Regarding the clean Windows install.. it was a completely fresh as in repartitioned by HD. I've also only selectively installed purchased or validated software so no spammy toolbars or crap like that floating around my system. I've had same issues with VS2020 on the previous install including uninstall, cleanup tool, etc.
With this latest OS install and upgrade to VS2021 the issues seem pretty much the same despite a fresh OS install and a fresh VS2021 install using the cleanup tool.
So, I've only has VS2020 & VS2021 on the previous system and not only VS2021 on this fresh install. All hardware checks out on the BIOS hardware scan... memory, CPU, HD, fans, etc. all green and all solid as per Lenovo hardware scan so I think it's safe to rule out anything to do with hardware considering nothing else ever crashes or hangs.

So from all my experience, all signs point to VS2020 and VS2021 being completely flakey and poorly coded OR there is something wrong with my system that hasn't been picked up by any Lenovo hardware scan AND that has not affected any other software stability on my system including other image editing software, Digital Asset Management, Office, browsers, video players, etc.

Adam