Log in
Log in

or

Thread LIquid Saffire 56 ASIO Troubles!

  • 1 comment
  • 1 participant
  • 4,421 views
  • 1 follower
ThomasKu

ThomasKu

2 posts
New AFfiliate
First post
1 Posted on 02/11/2012 at 09:29:35
Dear forum!

I'm new here and from Austria, so please be patient with my not totally perfect English...

First, my system description:

MixControl v2.4
Liquid Saffire 56
Win 7 x64
Cubase 5 and Reason 4
Core i7 920
ASUS Rampage II Extreme (WITHOUT internal sound card!)
12GB of DDR3 RAM

So, I've bought a few days ago the Liquid Saffire 56 on Thomann. Before I had a quite cheap Creative sound card, which I used with the Asio full duplex driver at 96kHz in Cubase and 32 float bit. This configuration ran at about 10ms - 20ms latency. When it came to clicking (usually with some VSTi), I had to increase the buffer size, so it was just about 30ms latency, but then everything worked!
Then, a few months ago I had the opportunity to buy an M-Audio Fast Track about my school and use it for about half a year at my home. I was then on the M-Audio Fast Track driver (no ASIO driver!) and all run very well. I had about 7 ms latency input / output and NEVER had to change this setting, no matter what I've done and no matter what VSTi plug-in I used.
This time, however, I used to save money for a "great, good and strong" audio interface. My choice was clear early on, namely the Liquid Saffire 56. Today I finally got it and I've set it up the first time. Then I installed the included drivers, connected the interface and turned on. I was about to start in Cubase (of course I started before even the MixControl and placed in Cubase the ASIO drivers from Saffire), but I could not believe my eyes, because the DSP indicator flashed almost solid red! (And this at 48kHz, 32 bit float, 480-bit buffer size and latency of around 30-40ms!). When I've tried to play the, with the M-Audio already begun project, I could not hear any sound except noise and popping with some breaks.

So then I went on the trouble-shooting for my own, but the error was not found until now!
Here's what I've already tried, with a enormous variety of combinations:

Sample rate of 44.1 kHz up to 96 kHz Adjustments => no difference.

Adjustments of Bis from 16bit-32 bit float => no difference.

ASIO buffer size changes of 128-3072 => slightest change, it was at 44.1 kHz + 3072 bit buffer size about 3 seconds till pops emerged the first time, but more begun in very short intervals. What I noticed is that the DSP indicator of Cubase was at the beginning "only" filled to about one-quarter and when I pressed play it increased about a quarter / sec (maybe the buffer does not get cleaned, only filled, till it is full?!). After just about 3 seconds it crackled back through, although I had a latency of >70ms which is absolutely unacceptable (! See M-Audio Fast Track with 7ms !).

FireWire Driver adjustments from short to very long in MixControl => no change except that the lower buffer sizes were no longer eligible.

I have tried in Cubase both other available ASIO Drivers, the ASIO4All and ASIO Full Duplex (Maybe incompatibility with ASIO4All if ASIO Saffire is installed?!) => It got Worse.

I also tried the legacy driver and the other proposed improvements on http://www.focusrite.com/answerbase/en/article.php?id=1071. =>
Unfortunately, very little or no improvements...

In Reason 4 is the whole not quite so bad, but also not bearable. But that would probably be only Reason, because the old Creative problem was in Reason also not so persistent.

Overall, it seems to me, like my problem is very similar to the one, that I had with the Creative in use with the ASIO Full duplex driver, but now in MUCH more extreme form. Apparently, the fault must lie on ASIO, since the M-Audio with the included M-Audio Fast Track driver (NO ASIO driver) was functioning normally ..

I hope that I oversee any possible problems and get a good and soon reply ..

The same was already sent to the Focusrite support!

Best regards
Thomas
ThomasKu

ThomasKu

2 posts
New AFfiliate
2 Posted on 02/13/2012 at 09:40:43
Close Thread.

Everything is woriking now.
I've had to optimize my whole system like
http://www.timos-welt.de/win7/Windows_7_PC_als_DAW_optimieren.pdf
and everything is ok.

So Thanks.
Thomas
cookies
We are using cookies!

Yes, Audiofanzine is using cookies. Since the last thing that we want is disturbing your diet with too much fat or too much sugar, you'll be glad to learn that we made them ourselves with fresh, organic and fair ingredients, and with a perfect nutritional balance. What this means is that the data we store in them is used to enhance your use of our website as well as improve your user experience on our pages and show you personalised ads (learn more). To configure your cookie preferences, click here.

We did not wait for a law to make us respect our members and visitors' privacy. The cookies that we use are only meant to improve your experience on our website.

Our cookies
Cookies not subject to consent
These are cookies that guarantee the proper functioning of Audiofanzine and allow its optimization. The website cannot function properly without these cookies. Example: cookies that help you stay logged in from page to page or that help customizing your usage of the website (dark mode or filters).
Audience analysis (Google Analytics)
We are using Google Analytics in order to better understand the use that our visitors make of our website in an attempt to improve it.
Advertising (Google Ads)
This information allows us to show you personalized advertisements thanks to which Audiofanzine is financed. By unchecking this box you will still have advertisements but they may be less interesting :) We are using Google Ad Manager to display part of our ads, or tools integrated to our own CMS for the rest. We are likely to display advertisements from our own platform, from Google Advertising Products or from Adform.
Marketing (Meta Pixel)

On our websites, we use the Meta Pixel. The Meta Pixel is a remarketing pixel implemented on our websites that allows us to target you directly via the Meta Network by serving ads to visitors of our websites when they visit the social networks Facebook and Instagram. The meta pixel are code snippets which are able to identify your browser type via the browser ID - the individual fingerprint of your browser - and to recognise that you have visited our websites and what exactly you have looked at on our websites. When you visit our websites, the pixel establishes a direct connection to Meta's servers. Meta is able to identify you by your browser ID, as this is linked to other data about you stored by Meta on your Facebook or Instagram user account. Meta then delivers individualised ads from us on Facebook or on Instagram that are tailored to your needs.

We ourselves are not in a position to identify you personally via the meta pixel, as apart from your browser ID no other data is stored with us via the pixel.

For more information about the Meta Pixel, the details of data processing via this service and Meta's privacy policy, please visit Meta Privacy Policy - How Meta collects and uses user data for Facebook and Meta Privacy Policy - How Meta collects and uses user data for Instagram.

Meta Platforms Ireland Ltd. is a subsidiary of Meta Platforms, Inc. based in the USA. It cannot be ruled out that your data collected by Facebook will also be transmitted to the USA.


We did not wait for a law to make us respect our members and visitors' privacy. The cookies that we use are only meant to improve your experience on our website.

Our cookies
Cookies not subject to consent

These are cookies that guarantee the proper functioning of Audiofanzine. The website cannot function properly without these cookies. Examples: cookies that help you stay logged in from page to page or that help customizing your usage of the website (dark mode or filters).

Audience analysis (Google Analytics)

We are using Google Analytics in order to better understand the use that our visitors make of our website in an attempt to improve it. When this parameter is activated, no personal information is sent to Google and the IP addresses are anonymized.

Advertising (Google Ads)

This information allows us to show you personalized advertisements thanks to which Audiofanzine is financed. By unchecking this box you will still have advertisements but they may be less interesting :) We are using Google Ad Manager to display part of our ads, or tools integrated to our own CMS for the rest. We are likely to display advertisements from our own platform, from Google Advertising Products or from Adform.

Marketing (Meta Pixel)

On our websites, we use the Meta Pixel. The Meta Pixel is a remarketing pixel implemented on our websites that allows us to target you directly via the Meta Network by serving ads to visitors of our websites when they visit the social networks Facebook and Instagram. The meta pixel are code snippets which are able to identify your browser type via the browser ID - the individual fingerprint of your browser - and to recognise that you have visited our websites and what exactly you have looked at on our websites. When you visit our websites, the pixel establishes a direct connection to Meta's servers. Meta is able to identify you by your browser ID, as this is linked to other data about you stored by Meta on your Facebook or Instagram user account. Meta then delivers individualised ads from us on Facebook or on Instagram that are tailored to your needs.

We ourselves are not in a position to identify you personally via the meta pixel, as apart from your browser ID no other data is stored with us via the pixel.

For more information about the Meta Pixel, the details of data processing via this service and Meta's privacy policy, please visit Meta Privacy Policy - How Meta collects and uses user data for Facebook and Meta Privacy Policy - How Meta collects and uses user data for Instagram.

Meta Platforms Ireland Ltd. is a subsidiary of Meta Platforms, Inc. based in the USA. It cannot be ruled out that your data collected by Facebook will also be transmitted to the USA.


You can find more details on data protection in our privacy policy.
You can also find information about how Google uses personal data by following this link.