When I attempt to record from my Kurzweil keyboard via firewire m-audio 410 into my Mac ibook in Tracktion I get pops and clicks and crackle. I hear it as I record, and sure enough, when I play back the recording its there also. Here are my specs:
I have 1.25 Gb Ram, 1.0 mhz G4 Ibook, system 10.3.9. Nothing else is running in the background that I know of.
using m-audio firewire 410
input levels set well below clipping, recording at 44k, 16 bit, mono, recording as wave, cache 65 mb.
When I record into Sound Studio (the free audio recording program which comes on the MAC) the recording is clean.
If I open a new project in Tracktion and import a AiFF file recorded in Sound Studio, it comes in fine and plays back cleanly and I can manipulate it at will with filters, etc.
If I attempt to record a second track in Tracktion with my keyboard while the imported track is playing, I get the crackle sounds. Some of the sounds are spaced randomly but others seem related to when I press the keys on my keyboard. CPU meter indicates approx 1/8 being used
I've tried the full range of latency settings from close to 0 to a huge delay, with no lessoning of crackle.
All of the demo programs play cleanly with plenty of room to spare on the CPU meter
I've tried rebooting, replugging cables. Everything stays the same. I can record into Sound Studio but not Tracktion. There must be something I'm unaware of.
What else can I try? I'm dying to use this program to do some multi-tracking projects.
thanks for any help
Ryan
need advice, new T2 user has pops and crackle
-
- KVRAF
- 2009 posts since 9 Apr, 2003 from Cornwall, UK
try turning off real-time-priority-mode.
Make sure you press 'resart drivers' after changing latency settings.
Choose ASIO derivers from the drivers list.
Make sure you press 'resart drivers' after changing latency settings.
Choose ASIO derivers from the drivers list.
-
- KVRer
- Topic Starter
- 7 posts since 24 Jun, 2005 from New England
Thank you for the suggestions. I have a MAC, so I don't access to real-time-priority-mode settings. My manual says that it is for PCs. But there is a button next to the slider for setting latency, which is entitled "restart device," which I assume has a similar function as "restarting drivers" on the PC version. I used it but I'm still getting pops and clicks at any latency setting. I tried out my AT stereo mic this morning, with the same results as with my keyboard.
I use the mic regularly to record stereo into Sound Studio via the 410. I can record in Sound Studio and then import the aiff file into Tracktion. This works perfectly. Its only when I record live into tracktion that I have the audio artifacts. And they are loud and distracting.
I did another test this morning. Recorded into Tracktion using just the built in mic in my ibook laptop. It worked fine. I recorded multiple tracks, it still worked fine.
Might there be an incompatibility between my M-audio firewire 410 and Tracktion?
Any more ideas from anyone?
I use the mic regularly to record stereo into Sound Studio via the 410. I can record in Sound Studio and then import the aiff file into Tracktion. This works perfectly. Its only when I record live into tracktion that I have the audio artifacts. And they are loud and distracting.
I did another test this morning. Recorded into Tracktion using just the built in mic in my ibook laptop. It worked fine. I recorded multiple tracks, it still worked fine.
Might there be an incompatibility between my M-audio firewire 410 and Tracktion?
Any more ideas from anyone?
-
- KVRian
- 1272 posts since 11 Apr, 2002 from Nashville, TN
"Make sure you press 'resart drivers' after changing latency settings." was a good suggestion did you try that?
-
- KVRer
- Topic Starter
- 7 posts since 24 Jun, 2005 from New England
Thanks for you reply
Yes I did try it, a number of times, at a wide range of latencies. Although on my MAC version, the control is labeled "restart device" instead of "restarting driver." There is no change in the crackling sound between different latencies, although I can certainly hear the echo effect as the latencies get longer and longer.
Another thing that I didn't mention, Is that I can hear the crackling sounds merely while monitoring, and even before I begin recording. This happens both with my stereo mic, or with my keyboard plugged in via the 410.
Yes I did try it, a number of times, at a wide range of latencies. Although on my MAC version, the control is labeled "restart device" instead of "restarting driver." There is no change in the crackling sound between different latencies, although I can certainly hear the echo effect as the latencies get longer and longer.
Another thing that I didn't mention, Is that I can hear the crackling sounds merely while monitoring, and even before I begin recording. This happens both with my stereo mic, or with my keyboard plugged in via the 410.
-
- KVRAF
- 4644 posts since 28 Nov, 2002 from Chicago
can you monitor outiside of Tracktion to verify that the crackling isn't being introduced by your drivers (or even a dodgy connection somewhere)?
Someone shot the food. Remember: don't shoot food!
-
- KVRAF
- 2009 posts since 9 Apr, 2003 from Cornwall, UK
have you updated the latest drivers from the m-audio website?
-
- KVRer
- Topic Starter
- 7 posts since 24 Jun, 2005 from New England
Thanks,
Yes, I thought of that and downloaded the latest driver yesterday. In fact, both the latest driver and the earlier one I was using both work fine with the Sound Studio program, but I get the pops and clicks either way with Tracktion. I just talked with M-audio tech support, and the tech person suggested that there might be an incompatibility between my version of tracktion and my MAC 10.3.9 operating system. I purchased the box set version 2.0.1.2. I've been reading about a newer version that some people are using.
Ryan
Yes, I thought of that and downloaded the latest driver yesterday. In fact, both the latest driver and the earlier one I was using both work fine with the Sound Studio program, but I get the pops and clicks either way with Tracktion. I just talked with M-audio tech support, and the tech person suggested that there might be an incompatibility between my version of tracktion and my MAC 10.3.9 operating system. I purchased the box set version 2.0.1.2. I've been reading about a newer version that some people are using.
Ryan
-
- KVRer
- Topic Starter
- 7 posts since 24 Jun, 2005 from New England
thanks to Valley also,
I've got both Tracktion and Sound Studio loaded on my laptop, so I can switch between either with out altering the physical set up. In Sound Studio (just a two channel program), the recording is clean with either mic or keyboard. I only get the popping and clicks with Tracktion. So that probably rules out connections, and I can monitor from within Sound Studio, so that's monitoring outside of tracktion.
I called M-Audio tech support, and they suggested that the version of tracktion that I have is possibly incompatible with my MAC 10.3.9, especially since my 410 works fine with both the older driver and the latest driver with Sound Studio.
Ryan
I've got both Tracktion and Sound Studio loaded on my laptop, so I can switch between either with out altering the physical set up. In Sound Studio (just a two channel program), the recording is clean with either mic or keyboard. I only get the popping and clicks with Tracktion. So that probably rules out connections, and I can monitor from within Sound Studio, so that's monitoring outside of tracktion.
I called M-Audio tech support, and they suggested that the version of tracktion that I have is possibly incompatible with my MAC 10.3.9, especially since my 410 works fine with both the older driver and the latest driver with Sound Studio.
Ryan
-
- KVRAF
- 4644 posts since 28 Nov, 2002 from Chicago
Unfortunately I'm not much a of a Mac expert, so I can only offer generic advice at this point, but:
If you disable scrolling (the scroll button exists down by the CPU meter) in Tracktion, minimize any open VSTi windows, and avoid moving the mouse, do the pops go away? I'm wondering whether this is a generic Mac/Tracktion UI performance issue, or a driver conflict (which on the mac seems a little[1] less likely that on the PC).
[1] admittedly for rather small values of 'little'.
If you disable scrolling (the scroll button exists down by the CPU meter) in Tracktion, minimize any open VSTi windows, and avoid moving the mouse, do the pops go away? I'm wondering whether this is a generic Mac/Tracktion UI performance issue, or a driver conflict (which on the mac seems a little[1] less likely that on the PC).
[1] admittedly for rather small values of 'little'.
Someone shot the food. Remember: don't shoot food!
-
- KVRer
- Topic Starter
- 7 posts since 24 Jun, 2005 from New England
I just downloaded the newest April 29th T2 version. I started it up and found the same symptoms as the boxed version. I've spent so many hours working on this now though, that I can offer more info. When I have the Tracktion Window open, and while monitoring with headphones, audio from either my keyboard or stereo mic sounds fine. When I arm the input arrows, aiming them to the right towards a track, the popping and clicking starts as I test the keyboard. Then as I start recording, the popping and clicking stays exactly the same, no better or worse. When I stop recording and disarm the inputs, the popping goes away in my headphones.
I haven't discovered anything which makes it either better or worse, not mouse clicks, scrolling, changing latency, opening more windows, starting up other programs, running on battery power, changing input levels, etc.
Now, I also realize that the sounds often have a pattern. If I strike a key firmly on my keyboard and then release, the note starts out, sounds fine for about a second, then there is a pop, then as the note continues towards decay, there is often a second pop or click just before it becomes inaudible. When the first pop occurs, it sound much like when someone flips a switch (an A B test) between two different brands of speakers. Not only is there a pop, but the "quality" of the sound is slightly different following the pop. This is repeatable, although not all key presses result in pops, more like about 3 out of 4 times.
Using the mic, its harder to determine such a pattern, but sounds more like clicks or scratches. But then I'm just talking or singing into it. But, in both cases, with the microphone or keyboard, some clicks and pops also occur during "silences" in the absence of key presses or audible input.
Is anyone else out there using M-Audio interfaces with Tracktion?
Ryan
I haven't discovered anything which makes it either better or worse, not mouse clicks, scrolling, changing latency, opening more windows, starting up other programs, running on battery power, changing input levels, etc.
Now, I also realize that the sounds often have a pattern. If I strike a key firmly on my keyboard and then release, the note starts out, sounds fine for about a second, then there is a pop, then as the note continues towards decay, there is often a second pop or click just before it becomes inaudible. When the first pop occurs, it sound much like when someone flips a switch (an A B test) between two different brands of speakers. Not only is there a pop, but the "quality" of the sound is slightly different following the pop. This is repeatable, although not all key presses result in pops, more like about 3 out of 4 times.
Using the mic, its harder to determine such a pattern, but sounds more like clicks or scratches. But then I'm just talking or singing into it. But, in both cases, with the microphone or keyboard, some clicks and pops also occur during "silences" in the absence of key presses or audible input.
Is anyone else out there using M-Audio interfaces with Tracktion?
Ryan
-
- KVRAF
- 1615 posts since 28 Mar, 2005
I use T2 w 10.3.9 no problems so I think you can rule out system conflict.
Are you monitoring only through T? are youusing the keyboard to plkay a vsti or are you recorrding its audio output? where is the cpu meter during all this?
might there be a clock issue?
Are you monitoring only through T? are youusing the keyboard to plkay a vsti or are you recorrding its audio output? where is the cpu meter during all this?
might there be a clock issue?
-
- KVRer
- Topic Starter
- 7 posts since 24 Jun, 2005 from New England
I was sending analog sound out of my keyboard. The CPU meter never went higher than 1/4 of the way up, that I saw, and most of the time hardly even budged.
But, I've finally had success! Perhaps this will help out another beginner. Besides being new to Tracktion, I'm also new to using an iBook. Although I've been happily recording many hours of stereo for the past month into Sound Studio, evidently Tracktion requires a bit more processing power, even when recording merely in stereo. I discovered that I could get worse pops and clicks by reducing latency to zilch and maxing out the sample size, so I went on a search through my OS X system preferences for things sapping the power of my iBook.
Sure enough I found that my energy settings were set for "longest Battery Life" rather than "highest performance." This seemed to cause problems even when the laptop was running on the AC adaptor, something that I wouldn't have expected. Another thing that fooled me was the low reading on the CPU meter in Tracktion.
To its credit, I couldn't fool the M-Audio 410. Everytime I changed sample rate in Tracktion, the 410 detected the change and displayed it, keeping pace.
So now, I'm going to have some fun with Tracktion! Thanks to everyone who gave me advice.
But, I've finally had success! Perhaps this will help out another beginner. Besides being new to Tracktion, I'm also new to using an iBook. Although I've been happily recording many hours of stereo for the past month into Sound Studio, evidently Tracktion requires a bit more processing power, even when recording merely in stereo. I discovered that I could get worse pops and clicks by reducing latency to zilch and maxing out the sample size, so I went on a search through my OS X system preferences for things sapping the power of my iBook.
Sure enough I found that my energy settings were set for "longest Battery Life" rather than "highest performance." This seemed to cause problems even when the laptop was running on the AC adaptor, something that I wouldn't have expected. Another thing that fooled me was the low reading on the CPU meter in Tracktion.
To its credit, I couldn't fool the M-Audio 410. Everytime I changed sample rate in Tracktion, the 410 detected the change and displayed it, keeping pace.
So now, I'm going to have some fun with Tracktion! Thanks to everyone who gave me advice.
-
- KVRAF
- 4644 posts since 28 Nov, 2002 from Chicago
glad you got it working. 
Someone shot the food. Remember: don't shoot food!