[David Pendry]

Hmm… possibly, Dave.
The resolution was something like 1920 x 1440(?)
(the editing PC is having a little rest at the moment, having been switched off and on so many times this morning!).
I’ve not had anything to do with 4k (yet), so I’m not up to speed with it.
The strange thing is, is that the drone clip immediately before the problem one is absolutely fine!
I’m going to try sliding the text along to that clip and see if I can purposely ‘crash’ Vegas.
Here goes…..

It’s the drone clip!

So – the moral of the story is, children – don’t use footage from a drone!!
(perhaps I’m being punished because of where they filmed it? – even with permission granted!)

DP

[David Pendry]

Hi, John.
(Do you EVER sleep?!)

Well, it’s definitely that drone clip.
I’ve even run it through some conversion software to bring the res. down to 1280 x 729 (729?!), but it STILL locks up as soon as that image begins to fade in – and this is when it’s just PLAYING, not even rendering anymore!!
I’ve shifted the thing right to the end of the timeline to play it on its own – and, sure enough, it gets about 2 seconds in and simply crashes Vegas.
I did wonder if it was the two lines of text I have ‘sliding’ in from each side, but I moved those out of the way (leaving the reduced-resolution drone clip in place) and it still crashed.

Should I further reduce the resolution of the drone clip?
It’s a pity, because it’s the closing shot of the whole thing and is really beautiful! (up and over one of the larger, and most famous cemeteries, here in Belgium)

I’ve had to re-boot the PC so many times this morning that it’s now become a challenge to see if I can get to the end!

Cheers.

DP

[David Pendry]

John.
At the “88%” point on the timeline, where it keeps stopping, I have just discovered that the resolution on that particular (TINY!) clip (taken from a drone and supplied to me by the client) is MUCH higher than the previous drone clip, which was taken by the same camera on the same day.
Now, these clips were emailed to me, but I have no idea how or why the res. should be so different.
It would appear that as soon as this clip comes into play, Vegas 13 has a little panic and simply seizes up.
The odd thing is, however – it actually worked on Vegas 11, but it would explain why I kept being told the ‘system is low on memory’.

More news as it happens!

DP

[David Pendry]

Okay, John 🙂

I’ll collate the relevant info and let you have it.

There’s practically no FX, just some floating texts.
It has just failed another three times.
1. Stopped at 87%
2. Video and no sound (yes, the settings were correct according to the screen)
3. Stopped at 47% (causing total melt-down yet again.)

Have just rebooted for the n’th time today.
I’ll get the figures to you asap.

Cheers,

David.

[David Pendry]

Yep!
That was it, John!
Things have moved around since Vegas 11, and this new computer has had to be ‘explored’, too!
I can now get resolution levels akin to a Mac, which is good, when you consider how much this PC cost! 🙂

Good to hear from you after such a long time!

Regards,

David.