Terje A. bergesen
Forum Replies Created
-
I have heard people run on Vista, but I don’t think it is a good idea to move to Vista yet, considering it is essentially 1.0 software, with all of the problems that will give you. Just my not so humble opinion.
—
Terje A. Bergesen -
Just for the record, the (or at least my) generated media box, when working with text, has a key-framer at the bottom. I can change text size, color and font during the duration of the text event. Font size etc changes are instant from one key-frame to the next (it jumps from 72 to 16 on the key frame) but color changes are gradual.
—
Terje A. Bergesen -
Burn at 1x or 2x
—
Terje A. Bergesen -
The number is the max number of operating system threads Vegas will start to render your video. Threads are difficult beasts, but they can significantly speed up any application. Even on a single CPU, no dual core, no hyperthreading, multiple threads can have a significantly positive effect on application performance. The reason for this is that most applications spend most of their time waiting for something, not doing any processing. Splitting the app into multiple threads will create better utilization of the CPU, even on a single CPU system.
How about rendering software? Well, rendering is mainly a CPU-bound process. Data is moved in and out of memory and a small (compared to the overall work) amount of disk reading and writing is taking place. Rendering therefore sees a far better improvement in speed on multiple CPUs than the typical application.
This may also actually mean that having too many threads doing CPU-bound rendering running on a single CPU may actually negatively impact performance. The reason is simple. THe process of scheduling threads, moving data in and out of memory for them, etc, takes some of the CPU cycles. If there are too many threads, the scheduling of threads (as opposed to actually running them) may consume most of your CPU cycles. This is not going to happen with only 4 threads, though.
So, I would say that there is a good chance your observations are accurate, having 4 threads may slow down your rendering. There is only one way to find out, and it isn’t really that hard. Create a project, save it. Reboot your computer. Start Vegas. Start rendering. Time it. Change the thread parameter. Reboot your computer. Start Vegas. Start Rendering. Time it. Repeat a few times for accuracy.
The reboot of your PC is so that each render starts with the same parameters. If you do this test after running 1 or 2 apps or doing other stuff, you will not get good data.
—
Terje A. Bergesen -
A 32 bit application in Windows can only allocate 2G of memory (Windows limitation). I assume the 1G max for pre-render comes from this. Since Vegas can never use more than 2G of RAM, setting aside some for it self, any codecs it will need to run etc, isn’t unreasonable.
—
Terje A. Bergesen -
It did for me.
—
Terje A. Bergesen -
Vegas will use as much RAM as it needs up to the limits imposed upon it by Windows. The memory setting for dynamic RAM pre-view is used for one specific feature of Vegas, namely dynamic RAM pre-view, not for Vegas as such. Do you have any particular reason for needing more than 1G of RAM for dynamic RAM pre-view?
Note that under windows, the maximum memory available to any one application is 2G.
—
Terje A. Bergesen -
Very happy with it. Can’t compare it to SS since I haven’t tried that one. Use it for most of my projects.
—
Terje A. Bergesen -
I have the 6800 card, and an on-board Soundblaster (can’t remember which, and won’t be in front of my PC for a while). When you are running Vegas, what amount of CPU is it using? Check the Task Manager, also check how much memory it is using.
If Vegas is using 100% CPU while doing this, then there is something wrong, more likely it is not, which would indicate it is waiting for something to happen, something that takes a long time. Hard to diagnose without sitting in front of the PC.
-
MPEG-2 or MPEG-4 at HD resolutions would be the thing, so 1920×1080 is fine, i or p.