The beta.... well there you go.

Vegas is uses floating point for internal process. We "dither" to
floating point and from floating point. Not overly CPU intensive.

My point was that if you set your project sample rate to 48 but your
material is 44.1, then we must resample and this resample must be a
high quality resample. This _is_ expensive as far as CPU goes.

I don't even remember the beta any longer nor what its limitations
were. I believe that you can download the demo to try out. If you
have a problem, contact our sales dept and I am sure they will help
you out some way. I don't know what the actual policy on this is. (I
don't work in that dept..) Peter Brad Drozda wrote: >>Thanks for the fast response, I was running twelve tracks of 44.1/16 >>audio it was a session that was recorded on Cool Edit Pro at 44.1/32 >>and dithered down to 16 bits before I Imported it to Vegas. It was >>six tracks of real drums, kick,snare,toms,overheads,bass gtr,2 gtrs >>and a few vocal tracks. Are you saying that the internal processing of >>Vegas is 48/24 and it is easier on the system using higher resolution >>and bit rates to process the audio? The project settings did match my >>audio, and I was using only one stereo bus for all the tracks. And >>yes they were solid tracks. The disc indicator only would jump to >>16%. I only had the Beta version and it ran out before I had a chance >>to thoroughly test it, I want to give it another try, but I'm not sure >>If I can use the Beta twice or how that works. >>I had another problem my DSP/FX wouldn't fully load after I exited >>vegas, I had to redo the chain each time I fully exited Vegas, Is that >>a incompability issue or because it's just a Beta version of the >>program? >>Brad Drozda >> >>Peter Haller wrote: >>>>The track count will depend on the bit depth and sample rate of the >>>>media as well. If your project is 48/24 and your media - or some of >>>>it - is 44.1/16 Vegas has to dither and resample on the fly. This >>>>costs CPU cycles. >>>> >>>>If you have multiple busses going to different sound cards, then >>this >>>>also uses additional CPU. If you don't need multiple buses, then >>>>don't create them. Even if you are not assigning a track to a bus, >>>>the bus is still active. If you need the multiple busses, but don't >>>>need them assigned to different audio ports, then assign them to the >>>>same port. This will save CPU and prevent i/o bottle necks as well. >>>> >>>>Q: What does the disk indicator show when playing this project? >>>> >>>>It also depends on whether you are talking about 12 solid tracks of >>>>audio - i.e 12 files played from beginning to end - vs multiple >>>>tracks accessing many different files or events. Look at some of the >>>>demo songs that come with Vegas. Very few have solid audio tracks. >>>>These demos show the the power of non-linear multitracks DAWs. >>>>Silence is golden when it comes to a DAW. >>>> >>>>Typically additional memory will not help much with any project. >>More >>>>memory will permit more FX chains - both assignable FX and Bus >>>>inserts FX - as some FX can require significant buffering. >>>> >>>>I ran a simple test for you: This was under a Dual PII400 CPU NT >>box, >>>>so my milage is considerable. I could create a similar project to >>>>yours with out even breaking a sweat. I had 35 solid tracks of audio >>>>all at 48/24. The Vegas project settings matched my audio. I then >>>>switched the project to 44.1/16 and CPU overhead increased >>>>dramatically. Vegas didn't choke, but CPU usage was exteremly high. >>I >>>>started to add FX to see when it would die. Audio started to choke >>at >>>>around 10 Assignable FX. When I switched the project back to match >>>>the raw material, the problem went away. >>>> >>>>Under Win9x what you can get would be lower, along with the lesser >>>>CPU. >>>> >>>>My point is that there are a number of variables to consider. How >>you >>>>arrange the tracks events and what type of raw media you are using >>>>all play into things. >>>> >>>>It depends. 12 tracks of one type of media with specific project >>>>settings could cause a problem vs 12 tracks of matching media types >>>>that match the project settings would be fine. >>>> >>>>Hope this helps. >>>> >>>>Peter >>>> >>>> >>>>Brad Drozda wrote: >>>>>>Hi, I've got a P11 350,64RAM, how many 24 bit tracks should >>>>>>I be able to run with 2 track effects on each track and four >>>>>>or five fx sends. So far all I've been able to run is 12 >>>>>>tracks, plus compresser and eq on most of them, and 3 FX >>>>>>sends, any more FX and it stutters like mad. I tried another >>>>>>64 RAM but I think it was a bad stick because it made some >>>>>>of my other audio programs crash and burn. Any suggestions, >>>>>>please let me know. >>>>>>Thanks, >>>>>>Brad D. >>>>>>