Live 5.02 and Presonus Firepod, on XP
Posted: Thu Dec 01, 2005 4:54 pm
Anyone using this setup?
I've just begun to use both Live and the Firepod and I think I'm still confused a little about the way latency/buffer size is set using these drivers/hardware. Buffer size is locked down/automatically calculated and defers to the Presonus CP in XP (linked via "hardware setup" button in Ableton audio CP) If I set the sample rate to 44.1 and the latency to 2.0ms, the buffer size gets calculated to 88, which doesn't seem like a friendly multiplier. And sure enough, mucho pops and clicks on test tone. If I then change the sample rate to 48 in the Firepod CP, I get a more familiar buffer size of 96, which seems to just barely hold a steady test tone at 80% CPU in Live control panel, overall latency of 2.54 + 2.54 + 0 = 5.08ms. I guess that's not that bad? But normally I'd like to be able to record at 44.1. Is there some process I'm not aware of to unlock these numbers and adjust them more finely so that I can get a correctly divisible buffer size? I've always had direct control over the actual buffer size which would then result in latency amounts, instead this Presonus/Live process seems to be the other way around. . .also Live seems to seomtimes lose touch with the Presonus ASIO driver so that when I return to Ableton CP I have to re-select the Presonus ASIO driver. Anyone else have experience with these issues? Thanks much in advance.
I've just begun to use both Live and the Firepod and I think I'm still confused a little about the way latency/buffer size is set using these drivers/hardware. Buffer size is locked down/automatically calculated and defers to the Presonus CP in XP (linked via "hardware setup" button in Ableton audio CP) If I set the sample rate to 44.1 and the latency to 2.0ms, the buffer size gets calculated to 88, which doesn't seem like a friendly multiplier. And sure enough, mucho pops and clicks on test tone. If I then change the sample rate to 48 in the Firepod CP, I get a more familiar buffer size of 96, which seems to just barely hold a steady test tone at 80% CPU in Live control panel, overall latency of 2.54 + 2.54 + 0 = 5.08ms. I guess that's not that bad? But normally I'd like to be able to record at 44.1. Is there some process I'm not aware of to unlock these numbers and adjust them more finely so that I can get a correctly divisible buffer size? I've always had direct control over the actual buffer size which would then result in latency amounts, instead this Presonus/Live process seems to be the other way around. . .also Live seems to seomtimes lose touch with the Presonus ASIO driver so that when I return to Ableton CP I have to re-select the Presonus ASIO driver. Anyone else have experience with these issues? Thanks much in advance.