Focusrite Saffire Pro 24 Problem (Clicks - Pops)  

Page 1 of 2 12 LastLast

  1. Posts : 15
    Windows 7 Professional 64-bit
       #1

    Focusrite Saffire Pro 24 Problem (Clicks - Pops)


    I have a Focusrite Saffire Pro 24 sound card that has been tested on Windows XP (with a relatively old system : Intel Core 2 Duo, 2GB RAM etc) and it works perfectly fine.

    I bought a new PC a few weeks ago (Intel i5 -750 @ 2.66 GHz, 4GB RAM) and I have installed Windows 7 Professional 32-bit on it. The sound card works with FireWire (6-pin, no AC power needed). I have installed the latest update for Windows 7, for the drivers of the sound card. It has been recognized and everything about it's connectivity is -almost- fine, but when I play a simple youtube video or a song on Windows Media Player, it's highly possible that the sound will click or pop.
    I e-mailed the company and for now they think it's a resource/conflict issue and they suggest that I optimize my OS, such as enabling DMA access to all IDE channels, minimizing the use of CPU for visual enhancement (such as Aero etc) and even shutting down my antivirus software and the Windows Firewall. Also they asked from me to run a test for latency and send them back the results.
    Does this have to do anything with resources, since my system is brand new? Any opinion expressed is highly appreciated. Thank you.
      My Computer


  2. Posts : 2
    WIN 7 64bit
       #2

    Hi Lefteror,
    Hope you are still active in this forum.
    I read your issue with WIN 7 and Pro24.
    Well I am having the same problems, but I have a PRO14.

    My new laptop is exactly as yours: Intel i5 -750 @ 2.66 GHz, 4GB RAM

    I installed everything well on the PC, FW connection is OK for starting up, but after a while I have a drop out.

    Focusrite requested a lot to set on the PC, like you said:
    "optimize my OS, such as enabling DMA access to all IDE channels, minimizing the use of CPU for visual enhancement (such as Aero etc) and even shutting down my antivirus software and the Windows Firewall. Also they asked from me to run a test for latency and send them back the results. "

    Yesterday I sent DPC test results to focusrite.

    If you would help me out what was the solution in your case, I might save some time, and could get on quick with the PRO14.

    I even installed 2.4b2 beta version....

    In my DELL PC I have Ricoh FW on the motherboard. Do you think I need to buy an Express Card - FW card - that uses TI chipset?
    Is that a solution, or can it be solved with a talented IT guy.

    Thanks.
      My Computer


  3. Posts : 15
    Windows 7 Professional 64-bit
    Thread Starter
       #3

    Hey szupeter,

    I have to tell you, I did virtually nothing about it. I'm really annoyed by the suggestions of Focusrite like turning off Aero and stuff so I didn't change anything. Nevertheless, the problem seemed to fade out gradually. For some time now I have no problems with my PRO 24. Maybe it's the new Mix Control version, I really don't know...

    Best of luck!
      My Computer


  4. Posts : 2
    WIN 7 64bit
       #4

    HI Lefteror,

    Thanks for your feedback.
    I am still trying and trying.... look to be solved my drop out issue yesterday... but this morning my AC adaptor pissed - I smellt electonic burning???
    As I have no 6pin FW possibility on my laptop I can't proceed.
    I really need luck....
      My Computer


  5. Posts : 8
    Windows 7 Professional 64 SP1
       #5

    It definitely sounds like an issue with your FW chipset.

    in the meantime have you tried this.....
    (taken from Focusrite website under downloads for Pro 24


    "PC Users

    This release requires the use of the Windows Legacy FireWire Driver on Windows 7 64-bit. Windows 7 32-bit users should however use the default Windows 7 FireWire driver."

    instructions can be found here.
    Are Focusrite's FireWire Products Compatible With Windows 7? .: Focusrite Answerbase

    To be honest, I just found THIS post having done a search for Saffire Pro 24 issues.
    I am not having any issues, but as one of those "Talented IT guys" mentioned earlier in the thread, I was just preemptively searching for known issues, in the rare event that I experience one, to know about it before hand.
    That said, I saw your problem, and having previous experience with it in particular, I signed up here to answer you.

    Let me know how you make out.
    xXx


    EDIT: p.s. if you have not seen this yet, I suggest you check it out.
    http://www.focusrite.com/answerbase/...patibility.pdf
      My Computer


  6. Posts : 8,135
    Windows 10 64 bit
       #6

    I have a Focusrite Saffire Pro 40. It too is Firewire and like most Firewire devices uses a "DICE" Firewire chipset in the device. Basically you need a T.I. chipset in the PC. There is one other that will work but from discussions on the Sonar forum and gearslutz forum if you don't have a T.I. chipset it's iffy if it will work or work correctly.

    Focusrite, as noted, says you must use the Legacy Firewire driver for Win 7. I've tried it with the native driver and did get dropouts. I now have the Legacy driver installed and no more dropout problems. I am using my Saffire Pro 40 with Sonar X1b.

    Popping and clicking can be caused by many problems. We see many posts about this in the audio section here, and on other PC forums such as the Dell users forum. The device driver is one issue, WI-fi is a major contributor to popping and clicking. Video drivers are another possibility. And others. It's not a "one fix for all".
      My Computer


  7. Posts : 8
    Windows 7 Professional 64 SP1
       #7

    Nice response Fireberd.

    As most now know, DPC latency checker is a great way to see which devices may be causing system hiccups. (w/ WIFI, Video, throttling, etc.) And ironically, all my experience with that is from having dealt with my own sound card issues (where M Audio's drivers are concerned for the entire Delta series)... which prompted me to switch interfaces after a couple YEARS of intermittent issues. As a result, like I said I was preemptively searching for issue with my new device, the Pro 24, JUST TO MAKE SURE I wouldnt have issues.

    That said, despite the DICEII chipset these interfaces seem to be rock solid, drivers and all, provided you use a T.I. FW controller, and follow Focusrite's published technical advice. HOWEVER, to my knowledge, NOT EVERY win7 pc MUST switch to the Legacy FW driver. It's my understanding that you only need to use the Legacy driver in the event that the Standard one is being employed and resulting in problems i.e., pops&clicks, etc.

    On my system I am using the Standard Driver, not the legacy, and have no issues. And yes my FW chipset is T.i.
      My Computer


  8. Posts : 8,135
    Windows 10 64 bit
       #8

    Triplexbeatz, When I was using Vista 64 bit, I was using the legacy firewire driver. When I installed Win 7 (on a new hard drive) I forgot and didn't change the firewire driver. I used the default firewire driver in my Win 7 64 bit system for quite a while without problems (I have an Intel M/B with the T.I. chipset). I ran into a problem one day, and unfortunately during a recording session, with dropouts. I thought I had set the driver to the legacy but didn't. I changed it to legacy and the problem was fixed and I finished the recording session with minimal interruption.

    I also have an MAudio Fastrack Ultra 8R USB interface recording unit. But it is relegated to "backup" as the preamps in the Ultra 8R are not near the quality of the preamps in the Saffire Pro 40. The preamps in the Pro 40 are what I would call transparent as what is input is what is recorded. With the Ultra 8R, it changes the tone slightly to a brighter (more treble) tone. I had recorded a steel guitar track (a clean guitar track no distortion) and had to fix a spot on the track. Between the original track recording and when I went to fix it (about a month) the Saffire Pro 40 developed a problem (the power on/off switch) so I used the Ultra 8R to fix the spot and there was an obvious difference in the "fixed" spot. Fortunately Focusrite sent me a new switch and I got the Saffire Pro 40 working again and fixed it with the Pro 40 and the tone was just like the original.
      My Computer


  9. Posts : 8
    Windows 7 Professional 64 SP1
       #9

    gotchya. Makes sense. I know the Pre quality and converters will obviously make a difference.. But I bet in the context of a single audio take, the use of two pre's could become pretty noticeable. cool way to compare actually.

    As for the driver thing, Ill have to keep that in mind. Im also using an Intel Board with a TI fw chip as well. Running 2.2 mixcontrol, set to short, at 256 buffer, and just did a Reason to Cubase rewire test with excellent results. So I am pleased.

    Since everything is working, I plan on leaving it alone. if i begin to experience any issues, the Driver type legacy/standard issue is the first thing I would try. Obviously best results are achieved with a TI chipset being used. That said, since not everyone is forced to use the legacy driver I wonder what the variables are between the device and the fw chipset(along with whatever other variables exist) that allow some users to get away with using the standard driver without problems, like myself.
      My Computer


  10. Posts : 8,135
    Windows 10 64 bit
       #10

    Like I said, mine worked OK for over a year with the default driver and never had a problem - until one day about 4 months ago. The only thing that I can think of that caused this could have been some Microsoft update. There wasn't any hardware changes.
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 00:45.
Find Us