rendering problem

sidewaysup wrote on 9/9/2006, 2:15 PM
Hello, I have just started using movie studio, I was using Pinnacle, and was looking forward to something better.

Movie Studio, so far seems to work well. I mostly just make movies with still images, slideshows with music, and movie menus to select specific parts of the show.

My first project includes approx 500 jpeg's, each around 4megs in size.

At first I started with making one movie of all the pictures, however rendering would not complete.

So I broke it up into 2 parts, the 1st rendered fine, the second would not complete, so I have broken the 2nd into 2 parts.

Now the 2nd part rendered fine, but the 3rd will not render. It consists of 3 songs and 205 images.

Each time the rendering stalls/hangs between 73-98%.

My computer is a 2.8ghz, 1.5meg ram.

I really would rather not break the 3rd part into 2 pieces.

Any suggestions, or possible causes?

Thank you

Comments

Terry Esslinger wrote on 9/9/2006, 2:51 PM
Need more information. Is it hanging in the rendereing from time line to AVI or to MPEG2? In Vegas or in Archetect?
But gerally sounds like a corrupt scene.
sidewaysup wrote on 9/9/2006, 9:49 PM
The problem is in Movie studio, when using "render as" to convert to avi.

I split section 3 in half, and it rendered fine.
Any ideas why it would not render to avi before splitting it?

Would I be better of rendering as mpeg?

Thanks.
rustier wrote on 9/10/2006, 8:51 PM
I would bet it is stalling on a particularly large photo. Check your sizes and reduce the larger ones. If you do a search in this forum with keywords photo rendering you will find a number of strings on the subject. For some reason VMS gets "indigestion" when you give it too big a picture and will hang. Remember your typical size is 600x800, 720x480, something like that.(pixel size).
ritsmer wrote on 9/11/2006, 8:59 AM
As to the possible "indigestion" with big pictures: I just made a video with some 50 still photos in jpg format sized 2816x2112 and beeing up to 2,2 MB each - and VMS made everything - editing and rendering - very well and without any problems - as usual :-)

Probably the only way forward is to continue to spilt in halves until you can identify precisely the media that causes the problem. Remember that the problem also can be in the codec that VMS uses to deal with the media - a codec possibly not supplied by VMS itself.

On many of our machines there can be a multitude of more or less well working codecs - some coming from halfheartedly deleted trials of other products.
Chienworks wrote on 9/11/2006, 7:59 PM
I believe if you right-mouse-button click on the preview window an option menu pops up and one of the options is to display details. This will add a couple of status lines beneath the window showing things like preview frame size, project frame size, frames per second, and frame number. If you have this display on while rendering you can see which frame number it's gotten to when the problem hits. Stop the render (or restart Vegas and load your project if it crashed) and move to that frame number. You'll now be able to see precisely which pictures Vegas had gotten to when it had the problem.