THE ISSUE IS WITH SAFFIRE MIX CONTROL 2.4   End of. (damn it why don't people read)   Oh and if you read the thread you would realise this is nothing to do with running transport Ifm.... > Just responding - not trying to help. Thank you for your contribution (in turning this into a debate rather than a diagnosis). ----------->  

apologies for instigating a hissy fit-we call it venting here-
the point I attempted to make was that i (mis)understood that Mix Control was universal across the Focusrite range-I`ve been using Version 2.1 since unpacking  on all 3 interfaces with none of the reported faults and was suggesting you roll back to a version that "works",unless the latest version is specific to your card and version of Sonar.


I get annoyed with the constant inferences of Focusrite`s "dodgy drivers" but admit they do more harm by releasing apparently buggy,rushed updates.
cheers

Just a Question on updates downgrades , etc............... Every time I try to update or downgrade Mix Control I receive the "please disconnect your FW device dialog, even though the device is off, the FW cable unplugged, ................ I have to pull my FW card out of the PCIe slot to perform the software up/down grades , only then will the installer continue.. I have even tried UN-installing the existing Mix Control , but havent fooled with registry entries... I know I shouldnt have to do this... .

Yup:
http://www.focusrite.com/answerbase/en/contact.php

Oh and I agree with Dappa1, you shouldn't never ever need to update any software... ever, whilst his system is fully working ... Amen.

What's actually going on Guitslinger I suspect is some sort of port delay. If a port is already opened and there is another instruction to open a port, then there's no delay... it's the same vice versa. However if a port is not open and there is an instruction to open it then there is a delay (and vice versa). Note if you wait a few seconds a port probably auto closes if already open (hence the effect you are experiencing).

If Cakewalk or other software requires ports to be opened/closed during playback then it's possible you will get latency during playback which you may or may not perceive. This is likely to be caused by the driver, it is also possible that the Cakewalk software is not closing ports properly as well, i.e. it is possible that Cakewalk is opening/closing ports at times that it does not have to do so (not optimal).... i.e. the Focusrite drivers and Cakewalk software is not HANDSHAKING together correctly....

Others will of course say that their non Focusrite card has no issues (or their 2.2 drivers work correctly).... this is quite valid, but that may be down to the fact these drivers open and close ports fast enough for them not to perceive any problem. Then again it may also be down to the fact that there is no issue with the Cakewalk software (right now we are judging Focusrite to be the sole cause, and it does seem that way, but all we see is the smoking gun in our eyes, we do not have access to the source code).. 
 
All we can do is act on evidence. The evidence right now shows us that 2.4 drivers suck., but there are also known knowns, and known unknowns.

The fact that this could happen and I've seen some other weird latency issues with 2.4 during playback which are hard to consistently reproduce (and admittedly some with 2.2, only it seems far less than 2.4) is the reason why I am taking Focusrite's advice and rolling back to a less buggy driver. There may be also things that Cakewalk can do here (which is the reason the problem has been reported to them as well).

Cheers.

Alex

Focusrite Liquid 56 Pro 

This was newer and came with 2.4. 

Is 2.2 posted somewhere?

I love the unit, but the button delay is annoying.

Does not do this on my Saffire firewire (desktop version)

Focusrite just released version 2.4.1 for the SP40 mix control:

http://beta.focusrite.com/

To which I can add that the latest Allen & Heath ZED-R16 drivers (3.5.6.11675) will cause exactly the same thing. Rolling back to previous version (3.5.5.10185) cures it. A & H are 'investigating'.

jtwinpcola


I had this issue as well. I just downloaded and installed the Saffire MixControl v2.4.1 beta. So far it looks good. I tested quite a few clicks and it now consistently takes about 1 second to arm a track.
 
:)

Same here...Pro24 with MC 2.4 originally.  I upgraded to MC 2.4.1 yesterday and it fixed the slow response of the track arm and metronome buttons.  On a side note, Focusrite recommended the 2.4 drivers to me originally (over the 2.2 version) as I was told that they were optimized for the 64-bit environment.

http://www.focusrite.com/...ffire_mix_control_2_2/

Has 2.4.1 been sucessful for you guys or should I still rollback to 2.2?

Has 2.4.1 been sucessful for you guys or should I still rollback to 2.2?

 
Some users have reported that the 2.4.1 driver is working consistently good for them.
 
It's worth a shot.

I was very pleased to find this web-site tera gold.I wanted to thanks for your time for this wonderful read!cheap swtor credit! I definitely enjoying every little bit of it and I have you bookmarked to check out new stuff you blog postbuy wow gold.

The new 2.4.1 Mix Control driver on my Saffire 24 DSP Pro is working fine. Cleared up that 2-3 second record/arm delay in X1E. (was using 2.4 driver previously) Been using it for a few days with no issues...so far.

arachnaut


Does 2.4.1 need the legacy Firewire drivers or standard drivers on Win 7 64-bit? EDIT: Currently I'm using ver. 2.2 and Windows Firewire driver 6.1.7600.16385 (win7_rtm.090713-1255)

focus rite suggests the use of legacy drivers. I have a TI based card driving a liquid Safire 56 and pro 24 dsp ,works better with legacy drivers, I had dropout issues n lockups trying the win drivers on Win 7 64 bit

me too