VS 2021 Ultimate Crash (Again)

[cybernick]

Finally I pulled the trigger and bought the new version again. Hopping to be much more stable.
Unfortunately I was wrong. Attached you will find a smart package. It is a very simple project. Only one png with an fx in overlay.
When I preview again and again the project in the location the the png with FX starts, VS2021 crashes.
I also included a screen recording showing the crash.
Can you please test on your systems? Try to preview again and again using the mouse and spacebar.

[cybernick]

A note. I am using HW acceleration enabled in Intel mode.

[lata]

Thanks cybernick
I am not on my pc just a little late, but will test your project tomorrow.
Hopefully others will have a go before then

[Ken Berry]

I have played that small project several times in VS 2021 version 260 without any problem. I have Intel hardware acceleration enabled and using the spacebar instead of the mouse (which is what I usually use) made no difference. It played properly and there was no crash. Screenshot attached, not that it shows much except that I have played it.

I like the Turkish, by the way: "A long time ago, in a galaxy not far away..." or something like that, anyway! Çok teşekkür ederim!

[cybernick]

I have played that small project several times in VS 2021 version 260 without any problem. I have Intel hardware acceleration enabled and using the spacebar instead of the mouse (which is what I usually use) made no difference. It played properly and there was no crash. Screenshot attached, not that it shows much except that I have played it.

I like the Turkish, by the way: "A long time ago, in a galaxy not far away..." or something like that, anyway! Çok teşekkür ederim!

Good Turkish....

Thanks for the test. I played continuously again and again one portion.
Strange. What is wrong?

Check the attached video to see what's happening to me
I tried twice. Check the whole video please.

[Ken Berry]

That zip contained the png and vsp, though I assume it is somehow different from the first version. But opened in the same project, it still causes no crashes. Again I played it several times, using either mouse or spacebar to start it.

I love Turkey and have been there around 7 times. I've been all over the Western half from Istanbul, to Ankara, over to Boghaz Köy and its Hittite ruins, Capadokia, down (by bus) to Kusudasi, Antalya, Myra and a pile of other places. And I adore the food!

[Davidk]

Something worth noting here is whether or not that same project
- plays/renders Ok with hardware acceleration OFF.
- since you say you upgraded to 2021, have you tried to compose the same simple project in the prior version you used and gotten the same result, or did the hardware acceleration in that version (which one?) work?
- what Intel cpu, graphics set and driver do you use? and is the driver up-to-date?

I have some background/interest in this at my end. I used to run only VS (4 versions) on a desktop PC under windows7. Hardware acceleration was my normal practice, and I didn't get error messages. However, there is a consistent thread thru topics on this forum about hardware acceleration . . VS working when OFF, not working when ON (or occasionally vice versa). Clarifying further, after upgrading the hardware to windows 10 in mid-2020, I now have only two editors (Vs2021 and PD18) installed on that same hardware and both of them render OK when acceleration is OFF, and both give error messages when trying to render with acceleration is ON. Which leads to one of the following:
- the Intel on-chip video cpu has failed. This is the specialised item Intel asserts has been present on every processor chip they made since 2011: all the software has to do is use it.
- the applications are not using the graphics driver interfaces for that video cpu correctly
- the graphics driver that does the interfacing between the apps and the actual video cpu has related bugs in it.
Both of the last 2 may be relevant to windows 10 because this problem only surfaced after the OS upgrade, altho I have no idea why - win10 has been around for a while now.
I currently have a dialog with Intel that began with this outline and a request for an their (independent) test program for the video cpu - one cannot point fingers at software if the hardware is not working. There doesn't seem to be a test program, but this situation has apparently caught their attention and lab testing is in progress. Their request for details about drivers used in the past with win 7 suggest something has been found that they are trying to isolate.

[cybernick]

Something worth noting here is whether or not that same project
- plays/renders Ok with hardware acceleration OFF.
- since you say you upgraded to 2021, have you tried to compose the same simple project in the prior version you used and gotten the same result, or did the hardware acceleration in that version (which one?) work?
- what Intel cpu, graphics set and driver do you use? and is the driver up-to-date?

I have some background/interest in this at my end. I used to run only VS (4 versions) on a desktop PC under windows7. Hardware acceleration was my normal practice, and I didn't get error messages. However, there is a consistent thread thru topics on this forum about hardware acceleration . . VS working when OFF, not working when ON (or occasionally vice versa). Clarifying further, after upgrading the hardware to windows 10 in mid-2020, I now have only two editors (Vs2021 and PD18) installed on that same hardware and both of them render OK when acceleration is OFF, and both give error messages when trying to render with acceleration is ON. Which leads to one of the following:
- the Intel on-chip video cpu has failed. This is the specialised item Intel asserts has been present on every processor chip they made since 2011: all the software has to do is use it.
- the applications are not using the graphics driver interfaces for that video cpu correctly
- the graphics driver that does the interfacing between the apps and the actual video cpu has related bugs in it.
Both of the last 2 may be relevant to windows 10 because this problem only surfaced after the OS upgrade, altho I have no idea why - win10 has been around for a while now.
I currently have a dialog with Intel that began with this outline and a request for an their (independent) test program for the video cpu - one cannot point fingers at software if the hardware is not working. There doesn't seem to be a test program, but this situation has apparently caught their attention and lab testing is in progress. Their request for details about drivers used in the past with win 7 suggest something has been found that they are trying to isolate.

Let me provide some more information about my system.
Windows 10 64 Bit 20H2 19042.804 Windows Feature Experience Pack 120.2212.551.0 (Up to date)
Nvidia GTX 1060 3GB 461.72 (up to date)
Intel(R) Core(TM) i5-6400 CPU @ 2.70GHz 2.71 GHz
16GB RAM
1 TB NVME Drive (Primary disk)
510 GB SATA SSD (secondary disk)
Two monitors

That project is generated in VS2021. It does not open in VS2020.
I will try to compose the same in VS2020 and see..

[cybernick]

Ok everybody to isolate the issue. I made the following tests:

1- I compose the same project in VS2020. HW decode and encode were on and INTEL selected. No problem in VS2020 during preview. Then I opened the same file in VS2021. Again HW decode and encode were on and INTEL selected. VS2021 crushed (Video file attached:"Composed in VS2020 and opened in VS2021")
2- In VS2021 I disabled HW Decode but a left HW encode enabled in INTEL and tried again. It seems that there is no problem.(Video file attached: "VS2021 HW decoder off")


The outcome is that there is a problem with HW decoder in VS2021 or VS2021 did not like something in my system.
Hw decoder is important since it effects directly the editing speed. I hope I find a solution soon.




UPDATE: AFTER I POST THIS. IT CRASHED AGAIN IN VS2021 WITH DECODER OFF. I AM REALLY COMPLETELY DEMOTIVATED.

[cybernick]

I also initiated a support ticket to Corel . I assume it has to do with the FXs in overlays.

Meanwhile I am open to any suggestion.

[Ken Berry]

Just for the record, for all of the above experiments, I had HW decoder AND encoder enabled. No crashes.

[lata]

I have tried to crash the program using your VSP project files and like others am unable to do that, the program at the moment just does not fail

If you feel it is the FX then remove that to see it the crashes persist or not, if it were FX then surely we would have crash issues.

If it is related to your graphics and the acceleration options then I cannot really help as I use AMD.

Can you use other clips from the programs library, do you still get this crash issue.

It may be your computers environment,
Can you check that your graphics drivers, that they are upto date.

I really do not know what else to check, hopefully Corel Support will find a solution.

[cybernick]

I have tried to crash the program using your VSP project files and like others am unable to do that, the program at the moment just does not fail

If you feel it is the FX then remove that to see it the crashes persist or not, if it were FX then surely we would have crash issues.

If it is related to your graphics and the acceleration options then I cannot really help as I use AMD.

Can you use other clips from the programs library, do you still get this crash issue.

It may be your computers environment,
Can you check that your graphics drivers, that they are upto date.

I really do not know what else to check, hopefully Corel Support will find a solution.

I did everything. When I remove the fx it did not crash.

My OS and all of my drivers even K-Lite is up to date. I always keep like this.

I really have very low hopes for support team. Also google a bit about Corel VS crash hoping to find something. It seems like as of VS2019, Corel lost the game.

I will send you a PM link. Please share with Corel PR team if you have access. They need to do something now. They need to push management and tech team to come up with a good product.

[lata]

Can you double check the FX filters, try using a different filter.

As I mentioned if it were just the filters then others would have the same issues with the program crashing.

[cybernick]

Can you double check the FX filters, try using a different filter.

As I mentioned if it were just the filters then others would have the same issues with the program crashing.

It is random. So I can not reproduce every time. In some other filter I had no issue so far...

It is difficult to say . That's why Corel should have wide range of beta testers with different enviroments. Different GPUs (AMD, nVidia etc), CPU etc. But it seems that they have very limited variety of beta testers.