Well, I just learned a hard lesson on Vegas temporary
files. I thought I was originally doing myself a favor when
I built my own system and made the decision to Partition my
main program Drive into 2 partitions. My program drive is
10gigs and I partitioned it so that Drive C: is just under
650Meg with Drive D: handling the other part of the 10gig.
My reasoning behind this is because I install all my
programs to Drive D: and then Drive C: only contains windows
and the drivers that my programs put there. With this said
after I installed all my software drive C: had about 200Meg
left on it. I then burn a CD image of my Drive C:, in that
case if anything ever goes wrong with my system I just put
that CD image in my CDrom and restore everything back to a
working state in about 10 Minutes. Well I did my first
music production track last night(I usually just do
commercial advertisement which stays under 8 Tracks) using
Acid, the song was approximately 20 Tracks with mabe 10
simultaneous tracks playing back at one time. I opened the
individual tracks in Vegas to do a mix down and alls it did
was spit and sputter at me. I though this was very odd for
20 tracks running on a 700Mhz Athlon,128Meg ram, with a
Seagate SCSI Cheetah Drive, from that is only used for my
audio. I then trimmed all the events so that they would
only play when audio was present, so it should be doing the
Same as Acid had just previously done. 10 Simultaneous
Tracks no plugins added. Still spit and sputter. From what
I figured out is that Vegas uses the WIN386.SWP file when
playing back. The more tracks you have playing the larger
this file becomes. Well this file had gotten over 180Meg in
size and my drive C: was running out of space so Vegas could
not play back. By the way yes, my Temporary audio
folder,Preferred recording and Video folder where not stored
on my drive C:. So now it looks like I will be repartioning
my hard drive and reinstalling all my hardware and software
for the next couple of days, I won't be using partition
magic either, I've had problems with that in the past also.
It just seems really odd that Acid Pro wouldn't have this
same problem. Maybe instead of saying in the manual that
you need at least 40meg of free hard drvie space that, you
need at least a gig on drive C: if you decide on doing any
real work?
files. I thought I was originally doing myself a favor when
I built my own system and made the decision to Partition my
main program Drive into 2 partitions. My program drive is
10gigs and I partitioned it so that Drive C: is just under
650Meg with Drive D: handling the other part of the 10gig.
My reasoning behind this is because I install all my
programs to Drive D: and then Drive C: only contains windows
and the drivers that my programs put there. With this said
after I installed all my software drive C: had about 200Meg
left on it. I then burn a CD image of my Drive C:, in that
case if anything ever goes wrong with my system I just put
that CD image in my CDrom and restore everything back to a
working state in about 10 Minutes. Well I did my first
music production track last night(I usually just do
commercial advertisement which stays under 8 Tracks) using
Acid, the song was approximately 20 Tracks with mabe 10
simultaneous tracks playing back at one time. I opened the
individual tracks in Vegas to do a mix down and alls it did
was spit and sputter at me. I though this was very odd for
20 tracks running on a 700Mhz Athlon,128Meg ram, with a
Seagate SCSI Cheetah Drive, from that is only used for my
audio. I then trimmed all the events so that they would
only play when audio was present, so it should be doing the
Same as Acid had just previously done. 10 Simultaneous
Tracks no plugins added. Still spit and sputter. From what
I figured out is that Vegas uses the WIN386.SWP file when
playing back. The more tracks you have playing the larger
this file becomes. Well this file had gotten over 180Meg in
size and my drive C: was running out of space so Vegas could
not play back. By the way yes, my Temporary audio
folder,Preferred recording and Video folder where not stored
on my drive C:. So now it looks like I will be repartioning
my hard drive and reinstalling all my hardware and software
for the next couple of days, I won't be using partition
magic either, I've had problems with that in the past also.
It just seems really odd that Acid Pro wouldn't have this
same problem. Maybe instead of saying in the manual that
you need at least 40meg of free hard drvie space that, you
need at least a gig on drive C: if you decide on doing any
real work?