-
An anomaly I have been ignoring until now
I have noticed this behavior on more than one of my HP z800s running Vegas 9e…
I render multiple .wmvs daily at these specs: 320×240, CBR 480k, 30fps, 120 seconds per keyframe.
I have noticed that the very first .wmv I render after opening Vegas will render very quickly, about 13 seconds of render time per 1 minute of video. EVERY .wmv after that renders at about 26 seconds per 1 minute of video. I have even tested this by rendering the same exact project multiple times.
All of my videos are a single event on the timeline with fades at the head and tail, no effects what so ever. The raw files are .mpg2.
Any thoughts? Turnaround time is paramount in my department. Cutting it in 1/2 would be like money in the bank.
-
2 Replies
-
I don’t have an answer for your 13 seconds difference. But if these 13 seconds are so important for your department and you only fade head and tail on one single event followed by rendering, could you not save many more seconds by using Assistant Pro?
Just start Assistant Pro when you leave the building and when you come back next morning, all the work for the rest of the week is already done. Sounds perfect to me….Theo
-
This is a live broadcast environment where we are continuously pulling clips directly off air and editing them for the web. We post clips to our site 24 hours a day. The idea is to get each clip up to the site as soon as possible after they air on television, which is completely dictated by render time. So this isn’t the type of work that can be batched overnight.
13 seconds vs. 26 seconds per minute of video is 1/2 the time. That’s a lot, especially when your clips get up to 40 minutes in length.
Among other reasons, we don’t use Assistant Pro because it doesn’t support network rendering, another integral part of our workflow.
I hope that explains why this is a legitimate issue for me. I am still hoping someone could explain this!
Reply to this Discussion! Login or Sign Up