An X7 file format bug

[lata]

Hi David

I have no problems in opening the projects in any version of Video Studio, I did create a copy of the VSP to open in each version so as to retain the X5 integrity.

I have played the video in clip and project playback mode and from the library with no problems.

I cannot render the project, the program freezes at 46% I think that’s the end of the first clip / beginning of the second.

However I did notice that the project properties do not match the video files properties. Although I do not think that should cause any problems other than a quality issue (Dropped Frames)

Your project is set to use Pal 720 x 576 x 25 fps the video is clearly NTSC at 29.97fps,

I will do more tests and reply back…………….

[Davidk]

When I was first exploring what and why re these clips were malfunctioning in project mode - a major reason I've been doing testing with 2 clips is to get it to operate in that mode. Because that's the mode it failed in. Playing the clips one by one in clip mode worked even tho the imagery got stuttery half way thru. Again, issues only in X7. I tried to render the project to a video file, and it failed at the point you described. Right about then, I thought it was best to fix one problem before taking on another . . . .

Davidk

[Davidk]

The camera the test clips were recorded on is a Nikon S8100 - a compact still and video camera.

[lata]

Hi David

The problem seems to be associated with the first clip DSCN0413.mov.
Maybe just unlucky 13.

When playing in Project Playback the program crashes at 7 seconds 09 frames with your project and at approx 12 sec 08 frames with the project set to Ntsc.
Seems to do that every time.

On occasions I also saw an error message “ The instruction at 0x15bc5f0…….. referenced memory could not be read.”

OK
If I insert “0417” then “0413” to the timeline I do not get crashes. Hmmm
I was able to render this setup without crashes.

The question is how many clips are causing this problem.
So if you create projects without the DSCN0413.mov clip do you still have crashes?

Its hard work trying to test when the program crashes every time, I spend more time rebooting……

[Davidk]

Hi Trevor,

Without being as precise (x seconds y frames) as you have been, that's what happened to me. The error boxes did not display all that often. And the crashes were just for X7 - I could use other software and re-start any version of VS without having to re-boot either machine - laptop or the desktop.

I've tried transposing the 1st and 2nd clips - both in the original take from X3 via smart package, which had about 12 clips - and the smaller version with 2 clips which is the one I sent to you. Both varieties suffered the same fate: stuttering of the first image in a project sequence to play (and audio to suit) and then program failure. Having determined that at least the first 2 clips performed the same way, I thereafter I just focussed the first 2, in the sequence they were recorded in. In part, because project mode doesn't seem to run with just 1 clip in the storyboard but also because I expected you or someone would ask for an upload, and 2 clips was the smallest for that purpose.

Something else I have noticed (2 items) may be other aspects of this problem. Both these items show data with no projects or clips loaded - just the starting UI.
Item 1 - The clips show properties of NTSC, but my default project properties are PAL (see the screenshot image associated with the next item), and the preferences are set to display the different property format message (1st tab). So, when loading this vsp, I should have seen that message box asking if I want to set the project properties to suit the clip, and I don't (see the message box).
Item 2 - the project properties default is showing an item I cannot remove.

In this image for the X7 project properties, there are 3 items. They are all DVD PAL, and the 2nd 2 have audio set for dolby, whereas the the 1st one has audio set to LPCM. The 1st item in the list called 'previous setting' cannot be deleted (delete box greyed out). If I change it to the 2nd one, I get a message box about possible change to the current project, OK then shut down X7 and re-start, and the project preferences are back to default previous setting. The 'previous setting' item is the one the malfunctioning clips played under in all my posts to date.

If I open the project in X7, change the properties to the 2nd in the list, Ok the message box and play the project, I get the same stuttery and fail effect in the 1st clip, but this time there's data on the failure, and the program listed is vstudio.exe. See this screenshot of the crash data

Bewildering isn't it? On both my machines the only consistent factor is that X7 fails on those clips, and X5 and X6 don't.

Davidk

[lata]

Hi David

Automatically changing the project properties ( via Show Messages option) does not work for Mov files, project properties cannot be set to use mov properties.
Project Properties can only be set to a certain type of video file, in the case of Mov we can manually change the project properties to use NTS 29.97 fps.
Mpeg4 types can be set for project properties, NTSC VSP below.

Mov ntsc test x7.zip

(1.12 KiB) Downloaded 139 times

OK

I mentioned that Mov and Mpeg4 are very similar, with some mov videos (I say some not all) it is possible to change the files extension from Mov to MP4.
Now your files will activate the Show Messages allowing you to modify the Project Properties.
The above details have no bearing on the crashes you are experiencing, in a way taking us off topic. The video files should play without crashes irrespective of the projects settings.
However it is best to set them correctly...................

You mention having a 12 clip project,

I had not bothered with audio quality but the first clip certainly shows some problems, I only have the one clip to compare with.

if you remove the first clip, DSCN0413.mov do you still have problems with crashes.?

[Davidk]

Trevor,

I only mentioned that NTSC vs PAL project properties thing because the cause of the main problem could be anything . . I know formats ought to play OK, and in X5 and X6 using these clips, they do. Something is getting at X7 playing the same clips.

So. Problems with crashes if 413 is removed.
I assembled the remainder of the clips - 18 of them, 258Mb in total - and created both X7 and an X6 project files of them all. This is a listing of the folder with them all in it, and the properties box for the 413 clip as displayed by explorer.

Note that it says the .mov filetype displayed is an MPEG-4 file

Then
1 - opened X7 and the X7 project file on the desktop (running the x86 program version) with them all in it. 413 was the first clip, 417 the second, 419 the 3rd et seq. Deleted 413. Then, played the whole project as it then was. 417 was the first clip, and it played thru. Audio and imagery very stuttery, but it didn't fail. Played on to clip 419, and same stuttery effect audio and image and it failed out right about halfway thru. A brief flash of an error box and the whole UI vanished, back to the windows desktop.
2. For comparison, opened X6 and then the X6 mov project file with all the clips (inc 413). Played the file in project mode from the start. No issues at all. Stopped it after the 7th clip because there seemed no point in continuing.

Davidk

[aljimenez]

Project also fails in my X7 Ultimate with SP1 plus the Hot Fix. Each of the two .MOV files play well in Windows Media Player. Each also plays well in Clip mode in my X7. In Project mode is where X7 has issues. It hangs or dialog pops up with abnormal termination and I click Close button.

Here is my conclusion after several attempts at changing the Project Properties to match the .MOV files as much as possible. X7 can't handle the creation of a video project with the properties of the .MOV file, so any Project properties cause some trans-coding of the .MOV files and X7 can't do that and this is a bug IMHO. I tried creating a project template from the .MOV files and X7 can't do that either. Thus you need to trans-code the .MOV files to work smoothly with X7.

This small project file should be submitted to Corel as it is clearly a bug in X7.

[lata]

Hi Al

Thanks for confirming this problem.

David I have passed the details to Corel, Uploading the zip file to my BT Cloud account.

hopefully they will reply

[Davidk]

I continue to have problems with .mov files from this camera. This camera in the sense that it's the only one of that brand I have any regular contact with.

More recently (today, 14 Jan 15), I was editing a student's project file - created originally in x3, with a successful 'work-in-progress' render to mpg, for a final touch-up using x7 - containing a number of clips from that source before rendering to an mpg file. During the x7 render process, the whole thing stalled at 75% on one of the .mov clip files, and VS according to task manager was not responding. Having saved it prior to rendering, after the x7 shut down and bearing mind this post series several months old, I created an x6.vsp version, opened X6 and then that x6 project file. It rendered Ok.

Now, why point this out when we have agreement that x7 has a bug managing mov clips? Well, Corel has never acknowleged that. Not that's been posted in this thread at least. One does hope for better results in the future X8 version, but it has 2 obvious (negative) issues for Corel as things stand now:
1. For a user with a prior version of VS and a camera generating mov files, there is absolutely no incentive to upgrade to a later version. And I have so advised that person - there's no point in spending money on a later version if it compares poorly on clips the early version handles with ease. And Corel misses out on any upgrade or new purchase income he and any person he talks to cares to spend.
2. For those of us with several versions either available or even installed, reversion to a prior edition is no big deal. But that's an implicit acknowledment of a serious prblem with the x7 version. If you are a user with just the x7 version, and thus don't have that capability, this combination - a modern camera creating mov files that play fine in other software, and an editor (even if that version is the only one with the issue, a user having just that version, eg on a trial basis) that cannot manage those clips without falling apart - will tar Corel with the reputation of an unworkable product.

So, it would be really good if a statement from Corel acknowledging the issue and about any effort they have made/are making to fix this can be posted here, including what any user can do to fix x7 so it does handle mov files correctly. Upgrading to a later version at a cost really doesn't cut the mustard in that respect. A free upgrade probably would.

Davidk