Audacity/Peak and USBPre
Posted: Wed Jan 23, 2008 5:19 pm
Hi folks,
I've been using Bias Peak for a while now with a USBPre on my MacMini and 10.4.11. Recently (details deleted for now) I started to see problems in Peak after applying the DC Offset removal. The meters would stop working correctly in the playback. USBPre support suggested I use Audacity for recording.
I did an experiment, opening up a file in Audacity that was problematic in Peak. I removed the DC Offset and saved. Peak was happy with the change. Very strange. Now I'm thinking about recording with the stable version of Audacity instead of using Peak.
The USBPre only supports 24-bit, not 32. In Peak I can select 24-bit 44.1 AIFF, but when I try anything like that in Audacity, it crashes when I try to record. I notice that when I save a 24-bit file in Peak and open it in Cool Edit on Windows or Audacity on OX they are identified as 32-bit or 32-bit float. What's with that?
I wondered if I should go ahead an use 32-bit in Audacity, but I don't want a bunch of zero padding in the resulting file. If I record a 32-bit AIFF in Audacity and open it in Peak, Peak thinks it is a 32-bit raw AIFF. Doesn't seem right, given that 24 bit files are read as 32 in the other apps.
As far as DC Offset goes, maybe i can sill record in Peak and just do the DC Offset in another app (Audacity or Cool Edit - I use the latter for removing clicks anyway).
-gritingrooves
I've been using Bias Peak for a while now with a USBPre on my MacMini and 10.4.11. Recently (details deleted for now) I started to see problems in Peak after applying the DC Offset removal. The meters would stop working correctly in the playback. USBPre support suggested I use Audacity for recording.
I did an experiment, opening up a file in Audacity that was problematic in Peak. I removed the DC Offset and saved. Peak was happy with the change. Very strange. Now I'm thinking about recording with the stable version of Audacity instead of using Peak.
The USBPre only supports 24-bit, not 32. In Peak I can select 24-bit 44.1 AIFF, but when I try anything like that in Audacity, it crashes when I try to record. I notice that when I save a 24-bit file in Peak and open it in Cool Edit on Windows or Audacity on OX they are identified as 32-bit or 32-bit float. What's with that?
I wondered if I should go ahead an use 32-bit in Audacity, but I don't want a bunch of zero padding in the resulting file. If I record a 32-bit AIFF in Audacity and open it in Peak, Peak thinks it is a 32-bit raw AIFF. Doesn't seem right, given that 24 bit files are read as 32 in the other apps.
As far as DC Offset goes, maybe i can sill record in Peak and just do the DC Offset in another app (Audacity or Cool Edit - I use the latter for removing clicks anyway).
-gritingrooves