Hello everyone. Spot's latest Render Test probably resulted in a lot of people scratching their heads, including me. Also, with the numerous complaints of Vegas 6 being "slow", I wanted to find out the most efficient way I can perform a final render and obtain best performance during editing.
My detailed test page is HERE
No fancy grahpics or flash. Just info. I'll get there. I didn't want to post a huge message here.
From the link:
Obvious problem with the Vegas 6 with 16MB and 64MB Dynamic RAM settings!
(My) Conclusions:
"Dynamic RAM Preview Max" affects final rendering, not just "video preview"
Rendering if Dynamic RAM = 0 or >= 128
- Vegas 5 is very consistent
- Vegas 6 is very consistent
- Vegas 6 is ~10% faster than Vegas 5
- Maximum number of rendering threads > 1 makes little difference on Hyperthreaded/Dual CPU machines for final rendering when doing no other processing on the PC
Rendering if Dynamic RAM is > 0 and < 128:
- Vegas 5 is very consistent
- Vegas 6 has a problem if Dynamic RAM is > 0 and < 128; Much longer render times
- The Dynamic RAM problem is exacerbated if your number of threads is > 1
- This problem is not related to MainConcept MPEG-2 or Cineform AVI Intermediary
- I would assume this problem is in Vegas or a called module (i.e. not a Sony .dll): an "if" statement or loop ("for...next", "do...while", etc.) contains faulty logic
Final Conclusions:
- I will close Preview Window for final rendering.
- For Cineform avi Intermediate and Final MEPG-2 rendering: I will set V6 at 1 Thread, 0 Dynamic RAM, and leave the machine alone. Nothing is faster, as long as you do nothing else on the computer. ~10% time savings.
- For HDV detailed editing: I am setting my V6 at 512 Dynamic RAM and 4 Threads (512 allows smaller selections of HDV mpg/generated media/effects clips to preview at 29.97fps)
- I hope Forum Admin will forward this to developers to review, although I hope they have been looking into this already. Consider "fixing" this (or at least clarifying) for my wish list for Vegas 7.
- I wish Sony would choose an option name other than "Threads" and how it relates to "# of cpus". In another post, I noted that WinXP was processing 300+ "Windows threads" during a render I was doing. "Threads" does not equal "cpus".
I am going to have a good Holiday and get a life now! Hope this helps someone else. Happy Holidays everyone!
Dave
My detailed test page is HERE
No fancy grahpics or flash. Just info. I'll get there. I didn't want to post a huge message here.
From the link:
Obvious problem with the Vegas 6 with 16MB and 64MB Dynamic RAM settings!
(My) Conclusions:
"Dynamic RAM Preview Max" affects final rendering, not just "video preview"
Rendering if Dynamic RAM = 0 or >= 128
- Vegas 5 is very consistent
- Vegas 6 is very consistent
- Vegas 6 is ~10% faster than Vegas 5
- Maximum number of rendering threads > 1 makes little difference on Hyperthreaded/Dual CPU machines for final rendering when doing no other processing on the PC
Rendering if Dynamic RAM is > 0 and < 128:
- Vegas 5 is very consistent
- Vegas 6 has a problem if Dynamic RAM is > 0 and < 128; Much longer render times
- The Dynamic RAM problem is exacerbated if your number of threads is > 1
- This problem is not related to MainConcept MPEG-2 or Cineform AVI Intermediary
- I would assume this problem is in Vegas or a called module (i.e. not a Sony .dll): an "if" statement or loop ("for...next", "do...while", etc.) contains faulty logic
Final Conclusions:
- I will close Preview Window for final rendering.
- For Cineform avi Intermediate and Final MEPG-2 rendering: I will set V6 at 1 Thread, 0 Dynamic RAM, and leave the machine alone. Nothing is faster, as long as you do nothing else on the computer. ~10% time savings.
- For HDV detailed editing: I am setting my V6 at 512 Dynamic RAM and 4 Threads (512 allows smaller selections of HDV mpg/generated media/effects clips to preview at 29.97fps)
- I hope Forum Admin will forward this to developers to review, although I hope they have been looking into this already. Consider "fixing" this (or at least clarifying) for my wish list for Vegas 7.
- I wish Sony would choose an option name other than "Threads" and how it relates to "# of cpus". In another post, I noted that WinXP was processing 300+ "Windows threads" during a render I was doing. "Threads" does not equal "cpus".
I am going to have a good Holiday and get a life now! Hope this helps someone else. Happy Holidays everyone!
Dave