import .mov fails and crashes X9

[bitman]

When trying to import some .mov files I made via Vasco Da gamma motion studios sw (itinerary contend creator sw) I crash my VS X9.
(and the file is not imported due to the crash). Note that the files have no audio...
Also note that the files play in Windows and can be imported and edited in Sony Vegas.
I hope it is not yet again a quicktime issue.
Following info:

Windows 10 application crash log:
Faulting application name: vstudio.exe, version: 19.2.0.4, time stamp: 0x570e478d
Faulting module name: H264VDec.dll, version: 19.1.0.10, time stamp: 0x566ff328
Exception code: 0xc0000005
Fault offset: 0x0000000000112c3a
Faulting process id: 0x2af4
Faulting application start time: 0x01d1a7b933eac403
Faulting application path: C:\Program Files\Corel\Corel VideoStudio X9\vstudio.exe
Faulting module path: C:\Program Files\Corel\Corel VideoStudio X9\Common Files\MPEG\H264VDec.dll
Report Id: 1dc95734-e661-495f-a24a-8405383e334f
Faulting package full name:
Faulting package-relative application ID:

Note that not all .mov files crash my VS X9,
For instance this one with the info below (filmed with an old canon waterproof) does not crash when importing

[Ken Berry]

I can only imagine that X9 might be choking on that high 168 Mbps bitrate -- though I note that you say Vegas can deal with it. Mind you, if indeed you have the full Vegas, it is a professional end editing suite. Or do you mean Sony Movie Studio, which is a cut-down consumer end version of Vegas?

Is there any particular reason you used or need that high bitrate?

Some people who have had trouble with mov files have renamed the extension as .mkv, and found that that often works. You might want to try that.

[bitman]

Thanks Ken,
your suggestion to change the file extension to .mkv solved the import crash issue.
I can import and put it on the timeline.
It can even play the in "clip" mode in VSX9, but as soon as I press pause or try to play in project mode it crashes VSX9 again.
I guess you are right about the bitrate, it is extremely high. I must have selected a way to high or professional output quality (in the Vasco sw render options). Halas I cannot remember as this was done some time ago during last winter!
I certainly do not need these high bitrates.
Probably VSX9 (or quicktime) just chokes on it. WMP or VLC can play it however.

The Sony Vegas I have is the full version 13.
You may wonder why I want to use VS instead of Sony Vegas, I wanted to invest in learning Sony Vegas, but it seems the future of Vegas looks bleak with no new version for almost 2 years and none announced for the future. Many loyal Vegas fans are jumping ship to the (free version) of black magic resolve.
I tried all sorts of NLE's over the years, some with trials, including pinnacle, cyberlink, Edius, and more recently black magic resolve, but I keep going back to VS (I upgrade every year) which I find most pleasant to work with thanks to its uncluttered interface and nice features if you go deeper.

[asik1]

Bitman, so just convert it to a more userable format.

[bitman]

to asik1, yep, indeed.

[bitman]

To follow up on the .mov file I changed in .mkv, as it now imports but crashes later on when trying to play the clip and pause, here is the windows app log event. It seems it crashes in a 32 bit dll, strange as VSx9 is clamed to be 64 bit (and installation path is in win64 program folder), I see a lot of 32 bit dll's down there, maybe VSX9 is not so full 64 bit as they claim?
and the reason for the crash with the insane bitrates?

[Ken Berry]

I can't explain any of that, though agree it seems strange to have dll's containing '32' in what is a 64 bit folder under 64 bit Program Files...

However, to get back to asik's suggestion, have you actually tried using a third party conversion program to convert the file to, say, mkv instead of just changing the extension (which I acknowledge was my suggestion)?

[aljimenez]

I can't imagine 32-bit dll's in the 64-bit installation. You may have an installation problem. I suggest re-installing; perhaps list here the dll's that are 32-bit, so we can check our 64-bit installations to compare it to yours.

[canuck]

Capture3.JPG

To follow up on the .mov file I changed in .mkv, as it now imports but crashes later on when trying to play the clip and pause, here is the windows app log event. It seems it crashes in a 32 bit dll, strange as VSx9 is clamed to be 64 bit (and installation path is in win64 program folder), I see a lot of 32 bit dll's down there, maybe VSX9 is not so full 64 bit as they claim?
and the reason for the crash with the insane bitrates?

That u32video.dll is a 64 bit dll despite the 32 in its title

[bitman]

I can't explain any of that, though agree it seems strange to have dll's containing '32' in what is a 64 bit folder under 64 bit Program Files...

However, to get back to asik's suggestion, have you actually tried using a third party conversion program to convert the file to, say, mkv instead of just changing the extension (which I acknowledge was my suggestion)?

I have not converted the file yet apart from renaming the extension, anyway I will (when I have some time) rerender the original file with vasco da gamma sw to a more "normal" bitrate and see if VSX9 swallows it then.

[bitman]

Capture3.JPG

To follow up on the .mov file I changed in .mkv, as it now imports but crashes later on when trying to play the clip and pause, here is the windows app log event. It seems it crashes in a 32 bit dll, strange as VSx9 is clamed to be 64 bit (and installation path is in win64 program folder), I see a lot of 32 bit dll's down there, maybe VSX9 is not so full 64 bit as they claim?
and the reason for the crash with the insane bitrates?

That u32video.dll is a 64 bit dll despite the 32 in its title

I can very well be, nevertheless this is very sloppy programming practices. I personally, when I program, go to great lengths to name my variables, files, objects etc... them proper names.

[bitman]

I can't imagine 32-bit dll's in the 64-bit installation. You may have an installation problem. I suggest re-installing; perhaps list here the dll's that are 32-bit, so we can check our 64-bit installations to compare it to yours.

I am not going re-install, VSx9 64 bit works fine, except for th1e issue here, maybe due to the extreem bitrates of the source file.
It is not because those files are named 32 bla bla bla that they are 32 bit, they could be 64 bit.
I can only imagine it went like so: we have the sourcecode and used these files for ages in 32 bit (hence the name), lets run it through the compiler for 64 bit,
shall we rename them? No to much extra work/complications and name dependancies in other files to deal with.
But that is just speculation.
Anywhay,
Did you check your 64 bit folder if it has a bunch of 32xxx.dll named files in them?

[lata]

Hi bitman

Are you able to provide a sample of the problem file.
You will have to upload to a sharing site, Google Drive, DropBox, Microsoft One Drive and provide a sharing link
Then we can test your video on other computers, I cannot test Windows 10 but others can.

I would not worry about the names of the files, yes Corel may be a little lazy in creating the correctly named files,
They still have Ulead files and folders, that’s nearly 10 years after taking over from Ulead.
And the next version will be a hybrid of X9 still containing the older structure.

[bitman]

Hi bitman

Are you able to provide a sample of the problem file.
You will have to upload to a sharing site, Google Drive, DropBox, Microsoft One Drive and provide a sharing link
Then we can test your video on other computers, I cannot test Windows 10 but others can.

I will try to setup some sharing one of these days, at 2.8 GB it is just a tad bit to large to fit in my current shares.

[Ken Berry]

It doesn't have to be the entire file -- just a (much) smaller sub-set of it.