FredbobJackson
August 13th 04, 03:06 PM
A couple of behaviors that I consider odd are making me wonder
about Adobe Audition's limitations when dealing with larger
files:
I'm currently working on a 60-minute file, 44.1, 32-bit. When I
open it, it's like the .pk file isn't even present. It has to
read in the whole .wav, which takes 4-5 minutes. My options are
set properly to tell it to always look for the .pk file, that has
been set since I installed the thing, months ago.
Another "feature" I've noticed is that some operations (like
Noise Reduction) don't work for large blocks of data, eg, 90 or
100 minutes. The operation has to be done on smaller blocks of
the file. This isn't a severe inconvenience, but it still raises
the "Is this bogus software?" flag.
Anyone know of other limitations this piece of code has when
attempting to deal with larger files? Are there system-related
options that can be tweaked to allow Audition to perform better
when working with larger files?
fred
about Adobe Audition's limitations when dealing with larger
files:
I'm currently working on a 60-minute file, 44.1, 32-bit. When I
open it, it's like the .pk file isn't even present. It has to
read in the whole .wav, which takes 4-5 minutes. My options are
set properly to tell it to always look for the .pk file, that has
been set since I installed the thing, months ago.
Another "feature" I've noticed is that some operations (like
Noise Reduction) don't work for large blocks of data, eg, 90 or
100 minutes. The operation has to be done on smaller blocks of
the file. This isn't a severe inconvenience, but it still raises
the "Is this bogus software?" flag.
Anyone know of other limitations this piece of code has when
attempting to deal with larger files? Are there system-related
options that can be tweaked to allow Audition to perform better
when working with larger files?
fred