1. There is an option to Pre-render, I'm not in front of vegas right now but I think it's by using Shift+M and you can prerender a section (it actually renders it in a temp folder), and I think you can do live render too, maybe it's Shift+B.
I've always had lagg issues though and learned to live with it, sometimes playing a section a few times will probably add it to the cache somehow and then it's smoother. Prerender helped me in that way.
2. I never thought of correlating laggs with FPS from different sources, but I realise now it could have played a part. I personnaly put the clips/episodes/sources as they are in vegas and let vegas make the conversion so I don't work on the source themselves to make them the right framerates. But that might not be the clever way. I just never thought of doing something else.
Shift+M, and set the pre-render settings to match your project settings. I highlight a small loop section at a time (say 2-3 secs) and pre-render each section individually, because if you pre-render the whole timeline and then change one clip, the whole pre-render falls off. So pre-render small bits as you go, then you only need to re-pre-render a few seconds worth if you change one of the clips within that section.
The other good thing is if your whole timeline is made up of pre-rendered segments, however small, not only will your preview be smooth, but your export will be fast because it doesn't need to re-render.
Haha I didn't know about this either. This will help some of my timing issues, thanks!
O24, I've found Vegas to be extremely fragile when it comes to mpgs. (An issue since I use mumublemumblemumble's logo-less SPN source.)
I got most of the way through Above and Below before I found out that there seems to be an arbitrary limit on how many Vegas will allow in the timeline before crashing continuously. I use Vegas 8 Pro; perhaps they've fixed it in subsequent versions, but it's a known bug in my version.
Thank you, that's useful to know. I've been loading it up with some 30-odd VOBs and so far it seems to work fine, but I haven't tested it extensively with MPGs. Damn these crashy programs! *shakes fist*
I convert my source to make everything 29.97 FPS, using koyotesoft video converter.
When I did my first VVC vid a few years ago, I used source which was 25 FPS and then rendered it for con specifications and it was riddled with ghost frames simply because it went from 25 FPS to 29.97 FPS. It was a nightmare to fix - thence my habit of converting things before it gets to vegas.
I agree. I had the same problems when I used to have to change project framerates around in my old,old program (don't even ask), so I always have in the back of my mind that you can't just mix FPS and have everything turn out fine. What format do you convert it into to be dropped into Vegas?
Comments 9
I've always had lagg issues though and learned to live with it, sometimes playing a section a few times will probably add it to the cache somehow and then it's smoother. Prerender helped me in that way.
2. I never thought of correlating laggs with FPS from different sources, but I realise now it could have played a part. I personnaly put the clips/episodes/sources as they are in vegas and let vegas make the conversion so I don't work on the source themselves to make them the right framerates. But that might not be the clever way. I just never thought of doing something else.
Reply
Reply
The other good thing is if your whole timeline is made up of pre-rendered segments, however small, not only will your preview be smooth, but your export will be fast because it doesn't need to re-render.
Reply
Reply
Reply
O24, I've found Vegas to be extremely fragile when it comes to mpgs. (An issue since I use mumublemumblemumble's logo-less SPN source.)
I got most of the way through Above and Below before I found out that there seems to be an arbitrary limit on how many Vegas will allow in the timeline before crashing continuously. I use Vegas 8 Pro; perhaps they've fixed it in subsequent versions, but it's a known bug in my version.
Reply
Reply
When I did my first VVC vid a few years ago, I used source which was 25 FPS and then rendered it for con specifications and it was riddled with ghost frames simply because it went from 25 FPS to 29.97 FPS. It was a nightmare to fix - thence my habit of converting things before it gets to vegas.
Reply
Reply
Leave a comment