Dave Lozinski
Forum Replies Created
-
Simple questions but need to be asked:
1) what are you trying to render to? GPU accelerated encoding is only for mp4/h.264 encoded files. Either the Main Concept or Sony codecs.
2) In the options menu under video, how much memory do you have set for the Dynamic Ram preview? If you have anything higher than 256MB, try reducing it to 128MB and see what happens.
3) Also for rendering options you should see a drop down on whether to use CPU, or GPU. What do you have set? You need to set this to GPU.
4) Lastly (I forgot where this is, but I think it’s under Options and then the Video Tab), you need to make sure your cards are selected from the dropdown menu. If the cards aren’t listed, then Vegas isn’t recognizing them. This could be because they don’t have the latest or supported driver version.
—————————————–
https://www.davelozinski.com
https://www.davelozinski.com/DemoReel/
—————————————– -
No worries.
Yeah, 511 has been going good for me.
Only word of caution (if you haven’t used VP11 yet) is once you save a file in Version 11 format, it can’t be used in a previous version of Vegas. So definitely make sure you create a backup copy first before saving it in Vegas 11.
Good luck! Let us know how you go.
—————————————–
https://www.davelozinski.com
https://www.davelozinski.com/DemoReel/
—————————————– -
Dave Lozinski
December 27, 2011 at 2:36 pm in reply to: Here is how dynamic ram preview is affecting rendering times[Jim Greene] “I’ve never tried using dynamic RAM as a logical drive. Maybe there is actually a bottleneck with Vegas dynamic RAM? Have you tried using a physical disk instead?”
Hi Jim:
I’m not using dynamic ram as a drive (if you’re referring to the dynamic ram setting in Vegas?). I’m using a RAM Disk, which is separate. I can’t tell from your post if that’s what you’re referring to or not.
To answer your other question, yes. The whole reason I’m using a RAM disk for this now is to eliminate and prove that it’s not a bottleneck on my physical drives from the rendering process.
See this thread:
https://forums.creativecow.net/thread/24/941540So by using a RAM Disk, no physical drives are involved at all. All the source files, Vegas temp drives, and rendered files are set to the RAM disk.
Yet, for some reason, when increasing the setting in the “Dynamic ram preview” > 256MB, Vegas rendering slows down, whether in the RAM disk or when using a Physical disk.
Also, my Ram disk I have set to a size of 2GB so there’s plenty of room to hold the source file and render to.
—————————————–
https://www.davelozinski.com
https://www.davelozinski.com/DemoReel/
—————————————– -
It has been working fine for me.
No bugs that I’ve noticed.
No crashes.
All my plugins work as they should.
Everything does. Albeit I am experiencing a curious issue with rendering when my dynamic ram preview is > 256MB.
Otherwise, Vegas is a dream to work with as always.
And much to my surprise and delight, it even works with Ram disks. Woohoo! No more drive lags!
—————————————–
https://www.davelozinski.com
https://www.davelozinski.com/DemoReel/
—————————————– -
Two obvious questions to be asked:
1) Are the audio tracks acc3 audio?
2) Are they muted?—————————————–
https://www.davelozinski.com
https://www.davelozinski.com/DemoReel/
—————————————– -
Dave Lozinski
December 27, 2011 at 11:46 am in reply to: Here is how dynamic ram preview is affecting rendering times[Mark Barton] “Looks like in your last screen shot that most of the disk usage is photoshop.exe, but you had it unchecked for the other screenshots, why?”
Two reasons:
1) for the first 3 captures where I have the Dynamic RAM set to 256MB, there’s a lot of other files listed, so I unchecked Adobe to save space in the listing2) I checked it in the last one to show everyone that it wasn’t affecting anything. If you notice, it’s writing to the D drive, which is the RAM drive (that’s where I have all the Photoshop scratch disks and temp folders set up). Look at how much data it’s reading/writing and the queue for the RAM Drive D isn’t even flinching.
I only had Photoshop open to do the screen captures.
—————————————–
https://www.davelozinski.com
https://www.davelozinski.com/DemoReel/
—————————————– -
Dave Lozinski
December 27, 2011 at 4:26 am in reply to: Amount set to dynamic-ram preview DOES affect rendering! :-/Dave and everyone:
Check out this thread I started:
https://forums.creativecow.net/thread/24/941866it has screen captures showing the disk activity and what’s happening when.
Dave Haynie: I even went back to the good old C= Amiga days and borrowed a concept from there: I installed a 2GB RAM Disk on my machine, running everything from there to eliminate the possibility of it being a drive bottleneck.
Hopefully you’re curious about the results too. 🙂
—————————————–
https://www.davelozinski.com
https://www.davelozinski.com/DemoReel/
—————————————– -
Dave Lozinski
December 21, 2011 at 2:22 pm in reply to: Amount set to dynamic-ram preview DOES affect rendering! :-/[Matt Carlson] “Obviously all of these things are not what you want to hear. It would be nice if some distinct parameter was just easily fudged and things would slide back in to place. What are the results if you choose to force CPU rendering on the different preview ram scenarios?”
Matt:
Thanks for the suggestion! I never thought to try that. So I did tonight. Here’s the interesting thing…
1) when I turned off GPU acceleration and had the dynamic ram preview setting at 9000MB, Vegas got up to about 40% before it started to slow down. It still slowed down though. 🙁
2) when I had the GPU acceleration turned off and set the dynamic ram preview to 128MB, this is where things got interesting! Not only did it zip through the video as it does with the GPU, but alas while watching task manager CPU usage was at a steady 50%! In scenario 1, the CPU usage hardly got above 15%!
So again it leaves me with a mystery as to why in this test lowering the dynamic ram preview increases CPU utilization.
When I have the dynamic ram preview set to 9000MB, the memory usage in the task manager and resource manager never gets above 4GB (and my machine has 16GB).
Any other theories to try?
—————————————–
https://www.davelozinski.com
https://www.davelozinski.com/DemoReel/
—————————————– -
Besides backing up to a hard drive, you might consider:
1) backing up to an SDHC card (they come in sizes up to 32GB now a days so should be able to hold quite a bit)
2) back up to blu-ray or a DVD.
Generally speaking, I keep everything backed up to an SDHC. When my project is delivered, I then back it up on DVD and put it some place where I’m tired of dusting. 🙂
—————————————–
https://www.davelozinski.com
https://www.davelozinski.com/DemoReel/
—————————————– -
HI John:
Unless anyone else has any suggestions, I suppose one thing to try is making up a quick video using some of the effects you have in your current project that’s causing issues.
If you experience the same memory problems, that would point to the effects you’re using.
If you don’t experience the problems, then that would point to the project causing issues with Vegas somehow.
Let us know.
-Dave
—————————————–
https://www.davelozinski.com
https://www.davelozinski.com/DemoReel/
—————————————–