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.
Live 5.02 and Presonus Firepod, on XP
-
nuperspective
- Posts: 1394
- Joined: Sun Oct 31, 2004 3:45 pm
- Location: was: accrington [england]. now: melbourne [australia]
i have a firepod. however, its on a boat being shipped out to australia. i'm hoping theres no bug with 5.02 coz i upgraded my laptop after i arrived here. all my hardware apart from the laptop has been shipped.
there are new drivers for the firepod out on the presonus website, that might be worth a try. i never noticed a problem with my original set up, but i can run a test until my stuff arrives in january.
there are new drivers for the firepod out on the presonus website, that might be worth a try. i never noticed a problem with my original set up, but i can run a test until my stuff arrives in january.
mixes & tracks here:
http://soundcloud.com/thenarcoticcreatures
http://soundcloud.com/thenarcoticcreatures
-
donnydonny
- Posts: 305
- Joined: Sat Jul 23, 2005 9:36 am
- Location: San Francisco, USA
- Contact:
Try a latency of 3.0ms for a 128 buffer. That's what I have on my FW410 and my Delta 1010 is something like 3.06ms in and out.
That's really weird that the Firebox adjusts the latency time as opposed to the buffer size. If my FW410 ever craps out on me (which I'm expecting), I was planning on get the Firebox.
Hope that helps!
That's really weird that the Firebox adjusts the latency time as opposed to the buffer size. If my FW410 ever craps out on me (which I'm expecting), I was planning on get the Firebox.
Hope that helps!
Macbook Pro 2.16GHz, 3GB, OS X 10.6.2, Live 7.0.18 (Triceratopz), Torq 1.5.2, M-Audio Xponent, Access Virus TI Polar, Trigger Finger
It's actually the firepod and I'm really not positive it's the only way you can do it since I've only had it a short time. I'll post if I find any more information on it.donnydonny wrote:Try a latency of 3.0ms for a 128 buffer. That's what I have on my FW410 and my Delta 1010 is something like 3.06ms in and out.
That's really weird that the Firebox adjusts the latency time as opposed to the buffer size. If my FW410 ever craps out on me (which I'm expecting), I was planning on get the Firebox.
Hope that helps!