Focusrite control no hardware connected что делать
Question: Q: Focusrite control. Hardware no connected
Hi. I have problems with my Scarlett 18i20, becasue when I launch Focusrite Control, it says “Hardware no connected”. I wrote to Focusrite support, but they didn’t give me the solution. My macbook (13” late 2011) detect the interface, and even more, it works with Garageband without problems, but with Focusrite Control doesn’t. At the first tiem I installed the software, High Sierra asked me to allow new hardware. After that I uninstalled the software and reinstalled, but High Sierra didn’t ask me again to allow. why? How can I uninstall and delete everything about this software? Anybody has or had the same problem? I‘m thinking in buying Logic Pro, but if it doesn’t work I’m going to buy another software in windows plarform where Focusrite Control works without problems. I hope not to do. I don’t like windows. Thanks in advance.
MacBook Pro, Mac OS X (10.7.2)
Posted on Mar 21, 2018 7:34 AM
All replies
Loading page content
Page content loaded
I use a Focusrite Pre thunderbolt interface with Logic Pro on a MacBook Pro (a 2017) and it works fine.
If you want to upgrade to Logic Pro from GarageBand I would suggest going ahead and purchase Logic, install it, then install the latest Focusrite software and drivers.
Make sure all your device settings are correctly set in Logic, and in the Focusrite control panel, if you’re not using an external clock source like a. MIDI controller (just recording audio directly into Logic), make sure Focusrite is set to “internal.”
If you’re using an external MIDI clock, then set Focusrite accordingly.
It should work fine.
Mar 21, 2018 8:47 AM
Thanks Satellite, I saw with the help of a windows PC that my 18i20 is configured with internal clock, but when I try to us Focusrite Control on my macbook pro, It doesn’t work. It continues to pop up «Hardware no connected». I don’t know what can I do. At less, I can configure my interface on windows, and then open Garageband and use my interface without problems. But it isn’t the best way to use my interface. With 2 laptops. If I were at least able to uninstall completely Focusrite Control and start from scratch. Thanks again Satellite77
Mar 22, 2018 11:13 AM
The application should be able to connect to your interface as long as the correct driver is installed.
It sounds like you are using the interface in class compliant mode instead of using the dedicated driver. This might be why you are seeing the interface in GarageBand.
I would install the driver again then after restart go to System Preferences > Security and Privacy > General, and Allow the driver manually. This is a new security measure in High Sierra.
Here’s a link to the procedure:
Mar 23, 2018 5:36 AM
Thanks Cuauhtemoc!! I did what you told me, but the problem didn’t solve. I don’t know why, when I reinstall the software, my Mac doesn’t ask me for developer software permission again. I think when I uninstall focusrite control, actually the software doesn’t uninstall completely. I still cannot use focusrite control in my Mac.
Mar 27, 2018 8:19 AM
Try deleting it manually.
You should be able to find the following files:
Delete all these files then reboot the computer.
Now try a new install, followed by a reboot, and once again followed by the Allow procedure.
Mar 27, 2018 12:25 PM
Thanks Cuauhtémoc, I did what you told me, but allow button didn’t appear. It will no doubt a nonsense, but I feel hopeless. I will keep on trying to solve the issue.
Question: Q: Focusrite control. Hardware no connected More Less
Focusrite Saffire (56 and others?) «no hardware connected» on windows 10
Spoiler: At least for my issue I found a solution, see my answer for that.
Recently I got back into recording and wanted to connect my Focusrite Liquid Saffire 56 to my Windows 10 machine. AFAIK the liquid and the pro editions are all connected via firewire so I also bought a PCI Express firewire card for my machine.
I grabbed the latest Saffire MixControl which is 3.7 for windows but at the end I kept the older 3.4 version, which should not matter for the issue.
My machine kept detecting the saffire and my DAW and OS told me that it is there but I was not able to record with it and got always generic errors during opening the audio device. Furthermore the saffire mix control kept saying «no hardware connected»
I checked the firewire cable and socket, albeit a bit wobbly they are ok since the PC detects the interface properly.
6 Answers 6
Focusrite discontinued the support for the Saffire 56 from Windows 10 build 1903 due to device incompatibilities in the firewire interface and says «it will not work on versions >= 1903″. That’s not a good start for that.
Regardless of this fact my audio interface seems to work very stable and reliable on my windows 10 machine now.
My PC had no firewire inputs on the board so I bought a delock PCI firewire card. The brand is not important, important was the fact that Focusrite supports only VIA and Texas Instruments chipsets on the firewire interface. I was lucky because I had the Texas Instruments chipset and also the card was rated for 400 mbps, just like my saffire needed.
Beside that I could not work with the Saffire Mix Control nor record anything. The device appeared to be there but only as a non working zombie. I knew from the past that the interface was working on Windows 7 and cannot remember whether it did on 10.
After testing all of those focusrite articles and some threads on various forums I found an issue with microsofts driver selection in the device manager for my firewire card.
Looking at the device manager for the firewire card I noticed something strange:
Seems to work and looking good but then I said «wait, wasn’t my firewire chipset’s brand Texas Instruments and not VIA?»
Windows insisted it was a generic VIA chipset so I right clicked onto it, went to settings/properties, picked the «driver» tab, selected «Update driver» then selected the «locate driver on my machine», then clicked «pick one from a list» and got basically two different options:
I selected the non VIA version, installed it and that fixed my problem. The Saffire Mix Control was then able to detect the saffire without any issues and I was able to record instantly.
Firewire is quite old and I guess since windows already provides the drivers for firewire, the PCI card manufacturer relied on windows for matching it’s chipset signature to the necessary driver. Either the PCI card manufacturer or microsoft botched things up picking a driver that only «seemed» to work.
If you have the same issue I hope it will help my fellow friends in the firewire hell 🙂
Small disclaimer: The process of selecting another driver might use a different wording, I recommend searching for a guide on how to do this if you are stuck or not sure. My windows machine uses a non English language so the guide above might be not entirely accurate on the wording you might find on your machine.