Trevor,
Yes!!! renaming to .mkv works, no errors using the individual file, or when that file is added to the project file.
hosannas, many of.
(Read/actioned this after my latest email).
updating the bugzilla post now.
Davidk
project file assertion error
Moderator: Ken Berry
- Davidk
- Posts: 2090
- Joined: Wed Nov 26, 2008 12:08 pm
- System_Drive: C
- 32bit or 64bit: 64 Bit
- motherboard: ASUS Prime B660M-K D4
- processor: Intel core i3-12100 3_3ghz quad core processor
- ram: 16Gb
- Video Card: on-motherboard Intel UHD 730 graphics chipset
- Hard_Drive_Capacity: 6Tb
- Monitor/Display Make & Model: HP E240c video conferencing monitor
- Corel programs: VideoStudio: 2022, 2023
- Location: Brisbane Australia
- Davidk
- Posts: 2090
- Joined: Wed Nov 26, 2008 12:08 pm
- System_Drive: C
- 32bit or 64bit: 64 Bit
- motherboard: ASUS Prime B660M-K D4
- processor: Intel core i3-12100 3_3ghz quad core processor
- ram: 16Gb
- Video Card: on-motherboard Intel UHD 730 graphics chipset
- Hard_Drive_Capacity: 6Tb
- Monitor/Display Make & Model: HP E240c video conferencing monitor
- Corel programs: VideoStudio: 2022, 2023
- Location: Brisbane Australia
Re: project file assertion error
In previous posts, there has been a clear suggestion that more than one hotfix2 version was/is available to correct the launch failure of X8 induced by 2 of the MS Feb 16 security updates. Mike asked me to test a version to make sure we both used the same fix, and supplied a weblink to a google drive for it.
I downloaded that google drive version of hotfix2 (I'll call it hotfix2_2.exe to distinguish it from the 1st hotfix2.exe I downloaded in the week following 9feb). Today I uninstalled X8 and re-installed (main, content, bonus, 3 service packs and 2 hotfixes, including the 2nd hotfix2_2). The resulting X8 v18.6.0.6 installation
- launched OK (always a good sign lately), and had the usual long delay between the splash screen and the workspace on the 1st start.
- did NOT generate an assertion error with the problem .mov file, or the project file incorporating it, when either of them was loaded.
So, issue fixed. There was more than one hotfix2 version published - I got version 1, and subsequently, version 2 got a distribution audience that I missed. Bugzilla for bug1262 updated. Including suggestions to:
- create and use a file naming policy which indicates the versions of this sort of update, eg 2nd version of hotfix2.exe named as hotfix2_2.exe
- more widely distribute the information that revised versions of updates are available, especially in the user forum.
Davidk
I downloaded that google drive version of hotfix2 (I'll call it hotfix2_2.exe to distinguish it from the 1st hotfix2.exe I downloaded in the week following 9feb). Today I uninstalled X8 and re-installed (main, content, bonus, 3 service packs and 2 hotfixes, including the 2nd hotfix2_2). The resulting X8 v18.6.0.6 installation
- launched OK (always a good sign lately), and had the usual long delay between the splash screen and the workspace on the 1st start.
- did NOT generate an assertion error with the problem .mov file, or the project file incorporating it, when either of them was loaded.
So, issue fixed. There was more than one hotfix2 version published - I got version 1, and subsequently, version 2 got a distribution audience that I missed. Bugzilla for bug1262 updated. Including suggestions to:
- create and use a file naming policy which indicates the versions of this sort of update, eg 2nd version of hotfix2.exe named as hotfix2_2.exe
- more widely distribute the information that revised versions of updates are available, especially in the user forum.
Davidk
-
Alexeiev
- Posts: 2
- Joined: Sat May 14, 2016 3:19 am
- System_Drive: C
- 32bit or 64bit: 64 Bit
- Corel programs: Videostudio x8
Re: project file assertion error
Microsoft has released an update in February that damaged VideoStudio x8. Corel released the first VSX8_HotFix_2.exe (with 4,772 kb). In April Microsoft released new update that caused this message when importing .mov files, then Corel released a second update (VSX8_HotFix_2.exe with 4.883kb) that solved the problem. The confusion was that the two Corel hotfixes has the same name but are different. At the moment only has the current hotfix modified, with the same name and date of release in February. Now Videostudio x8 works seamlessly with QuickTime files (.mov). Sorry for the language, I am Brazilian and I do not write well in English.
- Attachments
-
- sem título1.jpg (37.32 KiB) Viewed 3275 times
-
Alexeiev
- Posts: 2
- Joined: Sat May 14, 2016 3:19 am
- System_Drive: C
- 32bit or 64bit: 64 Bit
- Corel programs: Videostudio x8
Re: project file assertion error
Davidk, thanks for your explanation, it solved the problem.
-
Revup67
- Posts: 18
- Joined: Sat Feb 13, 2016 7:50 am
- System_Drive: C
- 32bit or 64bit: 64 Bit
- motherboard: gigabyte
- processor: i7 920
- ram: 6gb
- Video Card: Nvidia GTX 260
- sound_card: built in
- Hard_Drive_Capacity: 4tb
- Monitor/Display Make & Model: 55 inch plasma samsung
- Corel programs: Paint Shop Pro 2020 Ultimate
Re: project file assertion error
I can speak for this renaming solution, this did work. Clean without any errors or uninstalls / installs.
-
Revup67
- Posts: 18
- Joined: Sat Feb 13, 2016 7:50 am
- System_Drive: C
- 32bit or 64bit: 64 Bit
- motherboard: gigabyte
- processor: i7 920
- ram: 6gb
- Video Card: Nvidia GTX 260
- sound_card: built in
- Hard_Drive_Capacity: 4tb
- Monitor/Display Make & Model: 55 inch plasma samsung
- Corel programs: Paint Shop Pro 2020 Ultimate
Re: project file assertion error
Anyone know where this hotfix can be found VSX8_HotFix_2.exe with 4.883kb ? It is not on the Corel site http://www.videostudiopro.com/en/suppor ... sion-tab=1
Update; though the Corel site shows the date being in February 2, 2016, once you download the file you'll see its the 4.883KB file. perhaps Corel can do a better job of file naming conventions - why not simply call this Hot Fix 3 with a newer date especially since quite a few of us already had the previous update. In addition, at least correct the date listed in the support section.
In all renaming to MKV is no longer necessary with this fix.
Update; though the Corel site shows the date being in February 2, 2016, once you download the file you'll see its the 4.883KB file. perhaps Corel can do a better job of file naming conventions - why not simply call this Hot Fix 3 with a newer date especially since quite a few of us already had the previous update. In addition, at least correct the date listed in the support section.
In all renaming to MKV is no longer necessary with this fix.
