Log in
Log in

or

Thread Focusrite Pro 24 Not getting any input or output from Sonar Platinum

  • 3 replies
  • 3 participants
  • 1,053 views
  • 3 followers
Mosvalve

Mosvalve

5 posts
New AFfiliate
First post
1 Posted on 03/05/2016 at 15:12:18
on a new pc I just built.

specs: ASUS H170M System board

Intel(R) Core(TM) i5-6500 CPU @3.20GHz 16GB Ram

SIIG NN-E20012-S2 Firewire card TI chipset. I was using this card in my HP so I know it works and Assume it's compatible with this new system.

Here's what's going on and I want to note that this issue is not just with Sonar, Same with Studio One 3. I also unistalled Sonar and re-installed it.

See my interface in Sig.

If I plug in my guitar to the Focusrite (doesn't matter which input)I get an input signal on the interface and in Mixcontrol and can hear what I'm playing through my monitors.
When I open a blank project and insert a new track, arm it to record there is no signal, meter activity or sound in Sonar. Even if I use Sonar's input monitor instead of mixcontrols. Also There is a 4 or more second lag from when I click to arm the track.

If I open a new project, add a track and import a guitar track for example (wave file) when I press the space bar or click the play on the transport there is a 4 second delay then platback begins but there is no sound or meter activity. Sonar will also white out and I have to close it. When that happens I have to reboot because Sonar won't load again.

I hope you guys can help me figure this out. I'm in a boat without a paddle.
David_Focusrite

David_Focusrite

65 posts
AFfable Poster
2 Posted on 03/11/2016 at 16:23:38
Hi Mosvalve,

Sorry to hear of the issues, but hopefully we can help get you back up and running.

It will be ideal to review this article covering chipset compatibility : https://support.focusrite.com/hc/en-gb/articles/207546925

With the behavior possibly being related to a few different causes it may be best to submit a support request to us here: https://support.focusrite.com/hc/en-gb/requests/new

This will allow us to do more troubleshooting along with gather some information that will allow us to help you get up and running!

Best Regards,
David // Focusrite Technical Support
Mosvalve

Mosvalve

5 posts
New AFfiliate
3 Posted on 03/11/2016 at 18:43:34
Hi David, Thanks for the reply. I found that my firewire card just didn't like the motherboard. Most likely a chipset incompatibility issue like you mentioned. I put in a new card. This one has a VIA chipset and is working fine. So all is well now. I heard that there is an issue with firewire cards with VIA chipsets on Win 10 with your interfaces is this true? Thanks for your assistance.
Simon Focusrite

Simon Focusrite

207 posts
AFfinity Poster
4 Posted on 04/26/2016 at 02:15:13
Hi Mosvalve,

We have an article covering what you mention here:

https://support.focusrite.com/hc/en-gb/articles/207546925-How-can-I-tell-if-my-Firewire-chipset-is-compatible-with-my-interface-

I hope the above helps, please do let us know if you need anything else.

Simon // Focusrite Technical Support
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).
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
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.

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).

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

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.


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.