Pops, Clicks, and Delays with Tracktion 2/Firewire Solo
-
- KVRist
- 38 posts since 25 Apr, 2005
I am having severe problems using Tracktion 2 with the M Audio Firewire Solo interface when recording audio. Regardless of how I set my buffer, I get pops and clicks.
In addition, after recording more than two tracks, the audio is delayed on any subsequent track when I playback - you can see how far off the track is visually as well.
I am using an eMachines AMD Laptop with 1.25 GB of RAM hooked up through firewire to a 200 GB external hard drive. I have been successfully using this setup until this month.
I do not have any of these problems in Sonar 4 Producer Edition which makes me suspect it is a Tracktion problem. I love Tracktion and would prefer to keep using the program. However, I can't deal with the noise and delay. Can anyone offer any suggestions?
Thanks in advance.
Jeremy
In addition, after recording more than two tracks, the audio is delayed on any subsequent track when I playback - you can see how far off the track is visually as well.
I am using an eMachines AMD Laptop with 1.25 GB of RAM hooked up through firewire to a 200 GB external hard drive. I have been successfully using this setup until this month.
I do not have any of these problems in Sonar 4 Producer Edition which makes me suspect it is a Tracktion problem. I love Tracktion and would prefer to keep using the program. However, I can't deal with the noise and delay. Can anyone offer any suggestions?
Thanks in advance.
Jeremy
-
- KVRAF
- 12977 posts since 29 Sep, 2003 from Ottawa, Canada
I'm afraid I don't have enough expertise with a setup like yours to be of much help, but a bit more info that might be handy for someone who'd be better able to help:
- are you using the same driver in Sonar that you are in Tracktion? (ie. WDM in Sonar, WDM in Tracktion; or are you WDM in Sonar and ASIO in Tracktion, etc.)
- I know you've tried different buffer settings, but what are they currently at? (as a starting point for someone to tell you to try lower or higher)
- Are you adjusting buffer from within Tracktion or within your Firewire device? Not all devices can be manipulated from within Tracktion, so even if it 'looks' like changes are made, when you close the window, they're right back to what they were before
I'm sure someone will be a long who's a better help than me for your kind of setup and your specific hardware.

Greg
- are you using the same driver in Sonar that you are in Tracktion? (ie. WDM in Sonar, WDM in Tracktion; or are you WDM in Sonar and ASIO in Tracktion, etc.)
- I know you've tried different buffer settings, but what are they currently at? (as a starting point for someone to tell you to try lower or higher)
- Are you adjusting buffer from within Tracktion or within your Firewire device? Not all devices can be manipulated from within Tracktion, so even if it 'looks' like changes are made, when you close the window, they're right back to what they were before
I'm sure someone will be a long who's a better help than me for your kind of setup and your specific hardware.
Greg
-
- KVRist
- Topic Starter
- 38 posts since 25 Apr, 2005
Greg:
Thanks for asking the right questions.
- I am using WDM in Sonar and ASIO in Tracktion - I don't see how to select WDM in Tracktion. Perhaps this is the issue.
I am currently at 44/16 in Tracktion at 256 samples. I have tried raising the samples as high as they go and restarting the device each time. I still get the clicks and pops. I have also tried ASIO4all and I have the same problem.
Thanks for asking the right questions.
- I am using WDM in Sonar and ASIO in Tracktion - I don't see how to select WDM in Tracktion. Perhaps this is the issue.
I am currently at 44/16 in Tracktion at 256 samples. I have tried raising the samples as high as they go and restarting the device each time. I still get the clicks and pops. I have also tried ASIO4all and I have the same problem.
-
- KVRAF
- 12977 posts since 29 Sep, 2003 from Ottawa, Canada
Amyjer,
I'm still not much help, but if I keep bumping, maybe someone will come along.
As long as the WDM drivers are installed, I believe Tracktion will recognize them! Strange that they don't appear in the "Settings-->Audio Devices" page in the pull-down for selecting device. Or maybe it's not! I've never used WDM drivers, and maybe Tracktion itself doesn't support them. Hopefully someone can confirm.
256 Samples is pretty doable as long as your computer's not TOO old. I personally run at 512 Samples, which is a bit much for some people but is working great for me.
Close Tracktion, set your buffer from within the Firewire Solo's control panel, and then start Tracktion up again. That might help.
Another thing to do: in one of the settings pages (can't remember which one) there's an option for "ASIO Direct Mode". Toggle this to whichever option it's not currently set to. And though I'm not sure what difference it should make, also turn OFF the option for "Realtime Priority Mode" when you find it. I've never heard of that option EVER being a benefit, but it's sometimes a detriment. Even though I don't think it'll clear up this particular issue, it'll save you a headache in the future if you turn it off now.
Hope someone else comes along with better help soon!
Greg
I'm still not much help, but if I keep bumping, maybe someone will come along.
As long as the WDM drivers are installed, I believe Tracktion will recognize them! Strange that they don't appear in the "Settings-->Audio Devices" page in the pull-down for selecting device. Or maybe it's not! I've never used WDM drivers, and maybe Tracktion itself doesn't support them. Hopefully someone can confirm.
256 Samples is pretty doable as long as your computer's not TOO old. I personally run at 512 Samples, which is a bit much for some people but is working great for me.
Close Tracktion, set your buffer from within the Firewire Solo's control panel, and then start Tracktion up again. That might help.
Another thing to do: in one of the settings pages (can't remember which one) there's an option for "ASIO Direct Mode". Toggle this to whichever option it's not currently set to. And though I'm not sure what difference it should make, also turn OFF the option for "Realtime Priority Mode" when you find it. I've never heard of that option EVER being a benefit, but it's sometimes a detriment. Even though I don't think it'll clear up this particular issue, it'll save you a headache in the future if you turn it off now.
Hope someone else comes along with better help soon!
Greg
-
- KVRist
- Topic Starter
- 38 posts since 25 Apr, 2005
Greg:
Thanks for the suggestions. I tried them all. I found that turning off ASIO Direct Mode and Real Time Priority Mode combined with upping the recording frequency to 48 eliminated 95% of the popping and clicking. I have no idea why this "worked" and would still love to remove the 5% popping and clicking. I now have the samples set to 256. Sonar 4 still gives me no problem but is a more difficult program to use.
Thanks for the suggestions. I tried them all. I found that turning off ASIO Direct Mode and Real Time Priority Mode combined with upping the recording frequency to 48 eliminated 95% of the popping and clicking. I have no idea why this "worked" and would still love to remove the 5% popping and clicking. I now have the samples set to 256. Sonar 4 still gives me no problem but is a more difficult program to use.
-
- KVRAF
- 12977 posts since 29 Sep, 2003 from Ottawa, Canada
Glad to hear it helped a little. A few more thoughts:
- When I first open T and play an edit, it crackles 'n' stuff. What happens is that Windows' memory manager doesn't offload stuff until another application needs that memory. So, the initial few seconds are Tracktion firing up and telling Windows, "Hey, I need that memory now." Not sure if it's related.
- In addition to driver issues, Rice Krispies can also be caused by spikes in CPU, memory, and HDD usage. Although it might not be convenient, I find that freezing tracks I'm not using ALWAYS eliminates any remaining snaps, crackles, and pops that I'm getting.
Hope that helps,
Greg
- When I first open T and play an edit, it crackles 'n' stuff. What happens is that Windows' memory manager doesn't offload stuff until another application needs that memory. So, the initial few seconds are Tracktion firing up and telling Windows, "Hey, I need that memory now." Not sure if it's related.
- In addition to driver issues, Rice Krispies can also be caused by spikes in CPU, memory, and HDD usage. Although it might not be convenient, I find that freezing tracks I'm not using ALWAYS eliminates any remaining snaps, crackles, and pops that I'm getting.
Hope that helps,
Greg
-
- KVRAF
- 6490 posts since 14 Jun, 2004 from Rochester, NY
weird my firepod (8 in/out) has zero crackle probs
EDIT EDIT EDIT
NO WONDER.
youre using the firewire on both modules. thats why.
if you read your manual it says not to hook in two firewire things such as an ext. hd.
maybe if you bought another firewire card or something it might work.
RonC
EDIT EDIT EDIT
NO WONDER.
youre using the firewire on both modules. thats why.
if you read your manual it says not to hook in two firewire things such as an ext. hd.
maybe if you bought another firewire card or something it might work.
RonC
-
- KVRAF
- 12977 posts since 29 Sep, 2003 from Ottawa, Canada
Nicely observed, Ron. It didn't even occur to me, but it makes sense. That's not to say that multiple firewire devices can't co-exist (Yamaha specifically designed such a daisy-chainable system, I recently read... mLan or whatever?), but if your Firepod manual advises against it....
Cheers for popping in, Ron.
Cheers for popping in, Ron.
-
- KVRist
- Topic Starter
- 38 posts since 25 Apr, 2005
Thanks for the observations and suggestions. I am daisy chaining the hard drive and M Audio Firewire Solo. However, this set up does not present a problem for Sonar 4 and I used to have no problem with Tracktion. I could hook up the hard drive through USB. I will try that arrangement and let you know if it solves the problem.
-
- KVRAF
- 12977 posts since 29 Sep, 2003 from Ottawa, Canada
-
- KVRist
- 51 posts since 5 Apr, 2002 from Glasgow, Scotland
Definitely try it with only your Firewire Solo connected - I have an AMD64 (Socket 754) and a Firewire Solo and get no problems using the ASIO in both Live and Tracktion.. however if I connect my iPod to the firewire bus the Solo often goes offline, requiring a reboot.. i know that's not the same issue but it does back up what M-Audio say, ie that chaining the devices is not recommended and you may well find your problems lie there. Good luckamyjer wrote:Thanks for the observations and suggestions. I am daisy chaining the hard drive and M Audio Firewire Solo.
-
- KVRAF
- 12977 posts since 29 Sep, 2003 from Ottawa, Canada

