• SONAR
  • My Snap and Click Problem
2016/02/08 13:17:16
BbAltered
Hello.  I am using Sonar Plat. Lexington 64 bit with Win 7 64 bit.  My audio interface is a Mackie 1604 mixer with installed firewire A/D/A interface (this is not the Onyx-i series, but an earlier version); I am using the latest available driver version for this interface.
 
I have been having a snap/click/pop problem since getting Sonar Platinum.  I get brief (0.5 sec) white noise burst when a) arming or un-arming a track; b) doing a bounce to track or bounce to clip; c) when I hit the Apply button after making any change in the Edit/Preferences menu; d) adding an audio track to a project; e) perhaps couple of other circumstances I do not remember right now.  The noise burst occurs very consistently when I do these actions in Sonar.
 
The noise burst is clearly audible thru my speakers, is not affected by using Mute or Solo buttons in Sonar, and there is no corresponding bounce in the Sonar meters when the noise burst occurs.  The noise burst is not affected by changing settings for the audio buffers. 
 
I have not had problems with pops and clicks when playing back projects (but so far, none of my projects are big enough to tax my computer processor).
 
Any suggestions on removing these noise bursts is appreciated.  Thanks
2016/02/08 13:46:00
Zargg
Hi. What driver type do you use, and which drivers are available? What latency settings do you use? Have you tried a different FW cable? 
Best of luck.
2016/02/08 14:01:31
microapp
+1 to the firewire cable. Use a cable that is as short as possible. I use 3 ft.
I have read that the Mackie firewire interfaces (even Onyx) are sensitive to the firewire chipset issue. My old Tascam FW-1884 definitely suffers from this. So did my friend's Onyx.
Many firewire devices (audio AND video) work reliably only with PC firewire interfaces using a TI-chipset and then only using the firewire LEGACY driver.
However, since you report this with Platinum only, who knows? My TASCAM needed TI-chipset and Legacy drivers all the way back to Sonar 7.
If you can, try with other mode drivers. If it happens with ASIO, try WDM or vice-versa.
2016/02/08 14:44:50
BbAltered
Hello. Thanks for the thoughtful responses.
 
1) The Mackie driver is an AISO driver; Sonar is set to use AISO drivers.
2) I use the smallest buffers I can while getting solid audio playback.  Changing the buffer size has not affected the noise bursts one way or another.
3) The firewire cable I am using is (I think) 10 feet long.  I will try another cable and see what happens.
4) I am using a SIIG firewire card that includes a TI chipset.  This is the firewire interface card recommended by super-users at this forum.
 
 
 
 
2016/02/08 14:57:04
Zargg
Just out of curiosity. Have you tried to press "E" (bypasses all fx) before pressing the "R" button? Does that make a difference?
All the best.
2016/02/08 14:57:47
microapp
Try WDM driver and see if that helps.
Are you using higher sample rate like 96K ?
If so, try 48K or 44.1K.
Also, small buffer sizes only matter when recording(for low latency)
For mixing/playback, have you tried a really large one 1024/2048 ? 
If installed, uninstall ASIO4ALL.
If your video card has audio drivers, disable them.
Disable the internal sound card in your PC.
If you have a WIFI, disable it.
Temporarily disable antivirus.
These are all pretty standard things to try.
 
2016/02/08 16:40:39
BbAltered
Hello.  I don't get any noise burst when beginning recording or stopping recording - but I do get a noise burst when I arm or un-arm an audio track for recording.
 
I am running Sonar using 44.1 kHz sampling rate.  I am not using ASIO4ALL.  I do not have anti-virus on my audio computer (it is not online).  I do not have WIFI on the audio computer.  The MOBO audio device is de-activated.
 
Again, changing the buffer sizes has not had any effect on this problem.  I have tried both small and very large buffer sizes and everything in between. 
2016/02/08 16:54:45
microapp
Have you tried ( if not already using) the 1394 legacy driver ?
Device manager | IEEE 1394 Host controller
Select the card
Properties | Driver
Should have LEGACY in the driver name.
If that does not help, I am out of material.
 
2016/02/08 17:09:41
Zargg
I agree with microapp (Michael) 's latest advice in trying the legacy drivers. It is worth a try...
All the best.
2016/02/08 17:31:49
BbAltered
Hello.  I have not tried the FW legacy drivers.  I will try it and report back.
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account