X9 crashes using clip trimming handle

[Davidk]

I'm using X9 64 bit ultimate, v 19.5.0.35, and there are no applicable updates (according to the updates check). The PC OS is win7sp1.

I am experiencing regular and immediate VS crashes during editing when I attempt to use the RH trim handle to adjust a clip in a project. I've captured the essence of it in this image

The clip affected is highlighted in orange, the progress arrow in the window is where I will move the RH trim handle to, and it crashes (message box saying VS has stopped working). The properties of the clip are in the captured image.

This isn't the only clip this condition occurs - there are others, they all come from the same camcorder, it's just taken me a while to a) get irritated enough to report it, and b) figure out just what I was doing when it happened. There is a work-around that works - instead of trimming the clip, cut it and delete the unwanted part. But that avoids the issue of why? it should not be happening.

Anyone else have this issue?
Is there a known cause or fix?

Davidk

[Ken Berry]

I don't have any .mod files but have DVD-compatible mpeg-2 with properties almost identical to your clip. However, nothing I do can induce my own X9 19.5.0.35 to crash. So I am wondering if there might be some specific tag associated with .mod which could be causing the problem -- even if, as we know, .mod is just one camera company's take on mpeg-2...

Is it only that one clip or all clips from the camera? Can you upload that clip to a service like Dropbox so we can try it at our end?

[Davidk]

Hi ken,
It's certainly feasible - that whole original clip is only 17.6Mb long. The clips from this camera have worked fine in Vs for years, so I don't really think it was a single failure of the clip. But first, I thought a bit more looking might suggest something, specifically whether there was a program ie vsp influence here. So I did some comparisons between project files with clips from the same camera on successive days.
So, day 1, this image of a clip from an undeveloped (ie, barely started) vsp on a llama farm near Yucay Peru

Apart from the duration, there's no difference between properties of this file and the one below. But this file allows trimming from both ends without crashing. I noted here that there was only one other item (music) in the timeline tracks at this point, so i went back to the failing one to check that point

And day 2, this file from the Inca fort at Ollantaytambo (previously posted with only part of the timeline showing - this one has it all)

And this clip (shown here in it's cut state) continues to fail when using trim handles. And more detail on that is:
- when the "VS has stopped working" message appears, 'print screen' doesn't work (meaning that I can press that key, open paint and paste the clipboard to it, but it's not the image of the screen with the failed message on it. And it's right - nothing in the VS workspace works, but clearly the print screen function has also stopped working, or perhaps it would be better to say it captures nothing.)
- the trim handle failure occurs from both ends - trimming the start of the clip as well as the end of the clip.
- I can use the trim handle to trim the clip, and as long as I have the left mouse button held down, the program stays alive. 2 seconds after releasing the left mouse button after moving the trim handle, that stopped working message appears.

Trying to trim other clips in the particular project file has the same effect, so I'm thinking that the trim handle crash has something to do with the vsp itself, but what it is beyond me. I tried attaching the Inca Fort vsp, but that filetype is not allowed. Is there a way to do that, and would it be helpful?

Davidk

[lata]

Hi David

We have to zip the vsp file to be allowed to attach to the post, even so that won’t be of any use without the clips used in the project.

You could create a Smart Package, zip that and upload to a sharing site as Ken mentioned, DropBox, Google Drive , Microsoft OneDrive etc.

File Extension, if that is the problem have you tried renaming the files to use MPG instead of Mod.
Sometimes that works?

Taking a snapshot of the error message, click the message window to make that the active window, PrtSc + Alt should copy that window, and only that window.

[Davidk]

Hi Trevor,

The zipped package of project files (The Inca Fort) including vsp is here on my public folder https://onedrive.live.com/?id=F258AB298 ... 2984C226A1
260Mb of it, took about 80 minutes to upload.

Davidk

[asik1]

Hi Trevor,

The zipped package of project files (The Inca Fort) including vsp is here on my public folder https://onedrive.live.com/?id=F258AB298 ... 2984C226A1
260Mb of it, took about 80 minutes to upload.

Davidk

3.5 min to download...
Now lets see whats going on.....
Nothing, the vsp will not load on my 19.2, see the "info" is inactive

*** So I loaded few mod's to the timeline, I have no problem at all trimming them from the head. No VS pouse , I can trim as fast as I want any clip. I will continue the test.

[lata]

Hi Asik

I assume the project was made using CVSX9.5
attached is a resaved version for X7, you should be able to open that project.

The Inca Fort_x7.zip

(14.39 KiB) Downloaded 141 times

[lata]

Hi David

Well I managed to crash the program by changing the length of clip MOV057 Inca Fort3.mod

Can I ask, the image you first attached shows the video appearing to be in full, as indicated by the white bar below the preview screen, however this may be misleading if FX is still active/selected, and your properties panel covers that detail. I see the clip as being 00:00:07:16 in length the original full size as 00:00:15:08

You mention dragging the RH side of the clip yet the image shows the left side? Oh maybe in au you have things upside down?

I will continue to test this, but was wondering if the Mercalli being applied to adjacent clips has some impact? Post updated Upps not mercalli?

As an aside, some of your long text lines run past the safe area and you may lose characters from the ends when viewed on TV.

Trimming that clip, at least a workround.
You could use the F3 / F4 to remove those frames rather than Cut and Delete.

[asik1]

Hi Asik

I assume the project was made using CVSX9.5
attached is a resaved version for X7, you should be able to open that project.

The Inca Fort_x7.zip

If 19.2 is not opening 19.5 vsp's I consider this a major bug.
** I open the vsp in X7 and relinked the clip.
No clips head trim as the ripple lock is set. once opened head clips are trim able.

[lata]

Hi Asik

I agree but Corel seem to treat CVSX9 and CVSX9.5 as different versions.
We did raise a similar issue when first testing CVSX9.5 before being released to the public.
Corel will only advise you to run the latest version and if you don’t do that I cannot see how you expect then to fix.

[RobertOZ]

Didn't Yvonne state some time ago that projects created with VSX9.5 could not be opened with VSX9 due to coding changes

[Ken Berry]

Extracting the individual clips, I have no trouble at all with any of the .mod files, clipping them from either end. The first time I opened the entire project, however, I chose 7.mod at random. When I moved the right end handle and went to play with the left hand one, I got a crash message and had to use Task Manager to close the program. It would not close by itself despite the crash message.

However, on reopening the program and reinstating the project, I then chose your problem 3.mod. Nothing at all happened when I played with the handles at either end. I then used Ctrl+Z to restore the original length. I then moved on to 6.mod, and after moving the right handle and moving to do the same to the left handle, again the program gave an error message, and this time crashed and closed by itself.

I have no idea why it is doing so since all the individual clips play by themselves without problems, and allow adjustments without problem.

I have to add that personally I simply don't try to adjust the length of clips with the handles once clips are actually included in a project, though I suppose that is a valid thing to do. Instead, I go through all my individual clips and adjust the length before including them in a project. Once in the project, I don't use the trim handles to change the length (which I only do very rarely in any case). And when I do, I tend to use the scissors instead. So I have not noticed in the past whether these sorts of crashes occur when associated with changes via the handles.

On a totally personal note, I am very happy to see Ollantaytambo once again. I visited it twice, once in the mid-80s when I was visiting from Brazil, where I was then stationed, and then ten or so years later when I was Australian Ambassador to Peru! But all of those places are just marvellous... and great to see again!!

[Davidk]

I do see Ken and Trevor having the same type of problem - using trim and crashing.

Trevor mentioned influence of Mercalli - which is applied to sections of 1 cut/sectioned early clip, so I created a test vsp (save as) and started by cutting out the mercalli filter, and then the frames I'd never used before. But none of that had any effect - after each deletion, VS kept crashing when I used the trim handles on a video clip.

So I tried the another approach - a new project, imported only the video clips used in the original project from the data folder, organised them in the same time sequence, no voiceover, effects music or text, and then tried trimming several of these. No issues at all here - they allowed it and VS carried on . . . .

Ken mentioned his approach to trimming clips - basically, each one individually. Which does seem like extra work, and I've never been motivated to even try that - trimming a clip in project file (where you can see the result in context of adjacent clips) has always worked for me over 7 major version releases.

A corrupted project file? Apart from this trim thing, it does not look like it. But clearly this particular project file is giving VS serious indigestion. Baffling just doesn't describe it.

David

[asik1]

David have you tried that vsp in X7?

[Davidk]

Hi Asik, Trevor, Ken

Until asik suggested it, no. Don't have X7 installed now. BUT do have X8. So I saved the X9 vsp (that has the problem) as an X7 vsp, and then ran that file under X8: and wonders, no crashes when I trim video clips. several of them.

Then I downloaded the X7 vsp that Trevor linked in one of the posts here, and - after I'd unzipped it and I'd re-linked all the various bits in it to my source files - saved that as an X7 vsp (unique filename) also, and then ran that file under X8. And again, no crashes when trimming video clips.

So, next step was to run one or both of those X7 vsp's in X9 and immediately the trim and crash issue appeared. I didn't try the second (downloaded) X7 vsp

So it seems that
- X9 has the issue, whatever it is.
- X8 doesn't have it: 2 X7 formatted vsp's with the same content (different only in how I got them as X7 files) running under X8 do not have the trim and crash problem
and I therefore think there's several factors here: 1) something in X9 release 19.5 and 2) that something is tripped by this specific vsp in an X9 format which causes the crash after the grab handle is released after trimming.

All the source files are up 'there', so maybe Corel could trip over them and do some analysis/fix work?

Davidk