Export Selected Tracks - digital noises after import?
Using Soundtrack Pro 1.1
G5 2.7DP/OS 10.5.7
After being away from STP for quite a while, I revisited this app this week, and I used my favorite function: "Export Selected Tracks" -- to then import a bunch of stereo files into protools.
Unfortunately, the exported files on the RIGHT channel only, have digital "madness" -- making the files unuseable.
I tried all different sample rates, bit-depths, interleaved or mono, etc.. no matter how I "export selected tracks" the RIGHT channel is always a mess. Sounds like a bad sci-fi movie (unfortunately, I'm not working on a bad sci-fi movie)
I have tested with many different sources -- aif, wav and at various sample rates, etc...
I always have protools running, and I clock using an external wordclock source...
I can't upgrade to the latest version (intel only) - and 1.1 has served me well and has all the features I need... and I am still on a PPC G5 that runs great...
But this is a VERY annoying bug/feature. Could this be an OS 10.5.x incompatibility? Anyone experience anything like this?
Thanks for any ideas or workarounds.
Jeremy
G5 2.7DP/OS 10.5.7
After being away from STP for quite a while, I revisited this app this week, and I used my favorite function: "Export Selected Tracks" -- to then import a bunch of stereo files into protools.
Unfortunately, the exported files on the RIGHT channel only, have digital "madness" -- making the files unuseable.
I tried all different sample rates, bit-depths, interleaved or mono, etc.. no matter how I "export selected tracks" the RIGHT channel is always a mess. Sounds like a bad sci-fi movie (unfortunately, I'm not working on a bad sci-fi movie)
I have tested with many different sources -- aif, wav and at various sample rates, etc...
I always have protools running, and I clock using an external wordclock source...
I can't upgrade to the latest version (intel only) - and 1.1 has served me well and has all the features I need... and I am still on a PPC G5 that runs great...
But this is a VERY annoying bug/feature. Could this be an OS 10.5.x incompatibility? Anyone experience anything like this?
Thanks for any ideas or workarounds.
Jeremy
Mac OS X (10.5.7)