Kev, that suggests it's a software setting or hardware configuration, if previously ok renders are also looking strange.

Don't know which - just check everything ...

Thanks Peter

That was my thought too, I haven't changed anything that I can think of though ...

It's 9pm here now, gunna bug off to the pub.

See what tomorrow brings.

Cheers

couldn't it be that preview is set to 'best'? Is it still jerky at 'preview' of 'draft'?

Or is this really stupid.. works for me sometimes..

mark

Grrr

No answer as to why it was doing it, but I did a ctrl/shift restart and the problem has gone away.

I hate not knowing the cause :-)

Cheers

Arggghh!

It's back!

Been fine for half an hour then suddenly all prerenders are jerky again. Even the ones I rendered a little while ago that were playing fine, now don't.

Help please! Anyone got any idea what could be causing this?

I've changed no settings since the ctrl/shift restart ... (apart from things like "double click on media clip to trimmer" and the like).

This is getting silly ...

Cheers

Back again :-)

System lasted fine after another ctrl/shift restart, but about 90 minutes later the prerenders are again jerky.

As a test I rendered a section to a new track and that renders and plays fine. it is only prerenders that are dodgy.

At least I know it can be fixed but returning Vegas to defaults every couple of hours is painful to say the least.

Sony - any ideas?

Cheers

Just a thought - you could change the drive on which your pre-renders are being built, (File > Properties) to see if that's a factor ....

Thanks Peter

I have tried that.

What I can't understand is why only the prerendered files? They aren't any different to captured files or "render to new track" files. It doesn't make sense ...
Also - prerenders that _were_ OK don't play properly any more once this fault appears.

Cheers

You might try setting your dynamic ram preview setting to zero MB and see what happens. I'm thinking it is a bad/unseated memory stick. But why would that only affect prerenders Hmmmm
Check your system resources when the problem pops up and see how much memory you're using.

Craig H.

Tried that and no difference.

Resource use seems normal. And reboots don't fix the problem, it only goes away if I do ctrl/shift restart of Vegas...

I know logic isn't always the best tool, but if Ctrl/Shift restarts are a temporary solution, that logically suggests that the default Vegas settings work ok.

Now - you mentioned changing a double click to open in Trimmer setting - have you changed anything else, no matter how seemingly irrelevant? I suggest working for 90 mins+ without changing anything.

Just trying to pin it down - if default settings work, then the problem returns, SOMETHING must have changed ..... but what?

In case something strange is happening to the veg file, you could also try Saving as with a new name (if you haven't already!)

I have kept changes to a minimum for that reason but will try to work from minimal default for a while.

I don't think anything I have changed could really cause it as I make those few changes (ie trimmer and don't close media) when I first do the ctrl/shift start and it works fine for an hour or two and then suddenly the problem appears without me having changed anything for that hour or two.

I'll try the Save As now - although I doubt that will work as this error is showing in an older project that was fine before. But it can't hurt.

Thanks for nutting it over. I really am at a loss here. All I'm doing is editing and it just suddenly goes...

Cheers

Just a thought here, try moving the prerender files off the RAID 0 drives to say the system drive. I had problems with RAID 0 and gave it the flick. Also mobo type RAID 0 is rather processor intensive.

Hi Farss - how's sunny Syderney?

The system is on the Mobo Raid0

These files are on a PCI Promise Fastrak Raid0

There are two 400 Gig Raid0s (and an old 20 gig IDE which is not AV rated) on this machine. (Plus three 70 Gig SCSIs, but they are not accessible to the system as they drive a DPS Perception and are attached directly to it).

The fault shows up whether the prerenders are on either Raid. And if it was a drive problem then surely the captured files would show the error too?

Cheers

Interesting

Just did another ctrl/shift restart and the fault didn't go away.

The only things I did were the trimmer and close media option and define where prerender files were going plus define the 1394 output for the external monitor.

I think the next thing is to uninstall Vegas and reinstall.

If I do this should I update to 4.0e? Did I read somewhere that 4.0e was buggy?

I hate doing a reinstall as I really haven't solved the problem ... I'd rather know what causes it than just bug out.

Cheers

Sunny Sydney is very hot at the moment and not a drop of rain for ages so we're into water restrictions.
I guess if you've tried moving the preremder files to another drive that kind of clears the drives as being the problem. All I was thinking was that the prerender files are written later than the files that you're playing back from.
Don't know if you covered this earlier, I suppose the prerender files themselves playback OK if you bring them into a new Vegas project. Just to determine is this just something to do with their playback or when they were rendered, not that I imagine something could go wrong with the render. If you go through the prerenderd files frame by frame are they OK?

I'll be surprised though if a re-install fixes the problem for good. It really sounds like some subtle system problem.

Heard it was a tad warm up your way. Been relatively cold and windy here, no rain either though.

OK - good thought re new project.

Started a new project, brought the prerendered files in and they play fine.

Open current project. Files still jerky. Import prerendered files, place them on the timeline, they play fine. They only jitter when Vegas tries to play them when it creates the little green indicator bars at the top of the timeline.

Just don't make sense...

Cheers

Well I'm no guru in the internals of Vegas. My understanding is this, and this is only by reverse engineering if you get what I mean, at the point where you see those green bars it switches from playing back from where ever the T/L tells it to play to playing the prerendered file.

So from your latest experiment it's purely the playback of the prerendered file that is going wrong, the file itself is OK. Now what's even wierder is this only happens after some period of time running Vegas. It could be something like memory leakage chewing up RAM but I'd expect to see other things start to fall over as well and that isn't happening. Restoring defaults fixes it it seems, but I bet after a while after you do that it comes back again.

It would seem like a resource being consummed, something maybe that should get released when Vegas has finished with it but isn't so it runs low and performance suffers. I suppose you've tried looking with Sysmon to get some clues as well.

Must say I'm at about the limits of my knowledge. What would be good is if you can find a way to make it happen very quickly, oftenly that approach works better than trying to make it go away.

The resource thing doesn't really seem to make sense either though. System resouces aren't stretched by a long means. I've defragged the drives. There is plenty of spare RAM and a reboot doesn't fix the problem (which would free up system, resources).

I'm happy to throw another Gig of RAM at it but I really doubt that is going to fix it.

I'll do a reinstall tomorrow night unless anyone has any better suggestion before then (it's 9:45pm Sunday here).

What is the general consensus on 4.0e?

Cheers

As far as I know between 40.d and 4.0e the only change was the branding and which directories it installs into. Also I think you need to run some utility to migrate your licences or something like that.
I've stuck with 4.0d but my new SF7 is a Sony not SoFo product but they still managed to find one another.

Yeah - I'd sorta got the idea that 4.0e wasn't worth worrying about ....

Cheers

Bump