[Nigel O’neill]

It could be rolling shutter. Camera’s with CMOS sensors are susceptible to this phenomenon, which is most noticeable when panning across verticals or when you are following action. It shows up as a watery effect on verticals or strobing effect on fast movement.

You can do a Google search on rolling shutter and find plenty of discussion on it.

If your issue is indeed a rolling shutter problem, I have been unable to correct it on the timeline in POST. I have found turning off image stabilisation when the camera is mounted on a tripod seems to help a bit… . That probably is of no help to you for your current project… .

[Nigel O’neill]

You might want to try ‘Prepare’ first instead of ‘Burn’ to see if files are being created in the first place.

My first Blu-Ray project (2.5 hours of 1440x1080i HDV edited m2t’s) took 15 hours to prepare and about 1 hour to burn on a 2X RE disc.

Do you need to format your BD disc first? Some discs like the RE’s are rewritable.

[Nigel O’neill]

My workflow used to be Vegas Pro with m2t & AVCHD files rendered out to DVDA template (mainconcept mpeg2) as a single A/V stream. A one hour project from Vegas typically takes 2~2.5 hours to render as many tracks have effects and colour correction applied to them. I would then bring the files into DVDA and ‘make disc’. The ‘make disc process can take up to five hours! I noticed quality loss by this method, so I now render out from the timeline using the HDV 1440 x 1080i template and then bring that into DVDA. I don’t seem to get a ‘softening’ effect of the video like I was getting using the DVDA template in Vegas. Neither way seems to result in faster DVDA ‘make disc’. Is there an article on this forum outlining a workflow process from Vegas to DVDA?

[Nigel O’neill]

Jason

I don’t believe your problem lies in Vegas Pro 8.

Without further information about the blue screen message, there could be multiple causes:
– your system is overheating under load. You could test this by removing your case cover and blowing a fan on it. If your render works OK, note that this is only a temporary fix and you need to get a better cooling system.
– you have a buggy driver. I had massive NVIDIA driver issues (BSOD with nvata.sys errors) which I resolved by rolling back the drivers (video and RAID) to Microsoft drivers. This assumes your motherboard has NVIDIA video/RAID.
– you have faulty RAM or mismatched RAM to your motherboard. Check with the motherboard manufacturer.
– you have a faulty HDD (it does happen, even for new systems – I had a faulty Raptor installed once)

Hope this helps.

[Nigel O’neill]

I had this problem recently rendering out a 4 minute photo montage with audio in Vegas Pro 8a. Turns out one of my media assets (a m2t file) was corrupted. I discovered this accidentally when I loaded the project on my second machine (which coincidentally did not include the problem asset). When I did a render without it, I got past 0% and concluded that the asset (even though it was not on the timeline anymore) had somehow been preventing the render process. When I put it back in, the problem returned. I ended up removing it from the Project Media bin as it was not actually required and the render out was OK to 100%.

Hope this helps.