@Keir , @Grzesiek

I have an open ticket with Focusrite and they are aware of the issue and working on a solution...

Meanwhile I went back to version 2.1.9 which is not available in their download section anymore. I have uploaded it for you guys on Zippy here : http://www111.zippyshare.com/v/NKMcamsn/file.html

This version works fine except it crashes when you exit the program so I leave it always open.

Focusrite said they had released version 2.3.3 to address this "crash on exit" issue, but created another buggy app instead. Focusrite produces great hardware but their softwares really sucks.

 

@safran5020

Thanks mate. Good of you to pass on this info. For the time being I can still use the gear without the extra features of Focusrite Control. So I'll sit tight and hopefully there'll be a working version available soon.

I agree that the hardware is brilliant.

 

Focusrite wrote to me today and sent me a link to their 2.3.4 driver. I have tested it and it works perfectly on my system (Windows 7 Pro 64-bit). The Focusrite Control mixer utility recognises my 18i20 immediately and behaves exactly like it should. I also had an opportunity this evening to do some test recordings using multiple audio tracks and MIDI and it's all working faultlessly.

I recommend that you ask Focusrite support directly for this driver if they haven't already pointed you to it. I don't know if it's a beta version, if it's about to be made available to everyone or what the story is but I'm sure they'd not want me to start distributing it on their behalf.

Anyway, it's solved the problem for me so shoot them off an email if you think it'll help you.

 

This 2.3.4 driver is the the official release, available on Focusrite's website, so no beta here (but it's still faulty to me). Although yesterday I have also received an email from Focusrite provided with this driver version. Now lets talk about how it performs. It does detect hardware like 2.3.1 so it's an improvement. What is still buggy - if I open Focusrite Control app, then close it and try to reopen it, the app will freeze and shutdown. Trying to relaunch it second time will usually bring Focusrtie Controll back to life, but it will happen every time when I close the app and try to reopen it. The same problem was present with 2.3.1 and 2.3.2 driver. Can't speak about 2.3.3 because it would not even detect hardware as we all know. Let me know about your experience with the new driver.

 

Last edited: Mar 21, 2018

Yes I get the same behaviour you are describing when you try to run the program a second time. It's weird but doesn't concern me too much as I either don't close it or, know that it will run properly if I load it again straight after it stalls.

 

Thanks guys

I will try the 2.3.4 even though it appears it still has an issue on exit (if it hangs on next startup it is because a process is still running behind while it shouldn't)

I will report back !

 

According to their web site, the official version is still 2.3.3 for windows
2.3.4 is for mac




Will ask support for a 2.3.4 beta and see.

Have you replied to Focusrite and report this new bug ? I think they will appreciate. The more we are reporting the better it helps the devs.

 

Last edited: Mar 22, 2018

Yes, I emailed them right away I found the problem. They have answered me yesterday, and they successfully reproduced this issue and they are working on the solution. Sorry about misleading you about the 2.3.4 driver availability. Officaly it's only available for Mac. I got mine from Focusrite tech support.

 

Hey guys, 2.3.4 is officially available for Windows, check Focusrite's website. For me no improvement unfortunately - Focusrite Controll still crashes after closing it and quick relaunching. Have to realunch it second time in order to bring it back to life. What a company...
Although Tech support have solution for that. Quote "this issue only occurs in the close Focusrite Control then re-open it within about 10-15 seconds. If you close Focusrite Control > leave it for 10-15 seconds (this allows all parts to close - Client and Server) then re-open it, you should no longer encounter the issue." Well yes, after waiting for 10-15 seconds it won't crash but isn't it ridiculous? Why am i have to wait 15 second in the XXI century in order to launch a damn simple program?

 

Last edited: Mar 31, 2018

Is it just me or do they never even say what they fixed, they just keep copy pasting the same changelog smh

 

We have the new Scarlett 1820 in one of our MIDI rooms courtesy of Focusrite and after experiencing the same problem and contacting Focusrite Support their response was:
---------------------------------------------------------------------------------------------------------------------------------------------------------------
We have seen a few reports of this on certain systems and whilst our developers haven't been able to re-produce this particular issue 'in -house', they have created a new build (build 2.3.4) which we believe will resolve this issue. If you would like to give this a go, please find Focusrite Control 2.3.4 attached to this email.

Please do let us know how you get on and we can take things from there.

Best Regards,
Ben Dandy // Focusrite Tech Support"

---------------------------------------------------------------------------------------------------------------------------------------------------------------
Of course we are going to let them know...! We are shipping the unit back to them on Monday.

EDIT: I would like to point out to the members who have purchased the Focusrite hardware and are having the same problems that Focusrite Control 2.3.4 DOES FIX it. Our decision to return the hardware is based on their terrible tech support and the time it takes them to solve problems.

 

Last edited by a moderator: Mar 31, 2018

Curious, what kind of problems did 2.3.4 fix for you in the end?

 

48 h after my help request they send me the same message, and indeed, now the unit is reconized by the software...

 

Besides the Focusrite Controll app, did you experience any other problems with the 18i20 2gen? I am struggling with major playback issues, like stutter/glitch audio playback if buffer size in ASIO Control Panel is set to different value than 512 samples. I alos got problems with metronom plugin keeping all clicks and accents in check inside Pro Tools 2018.3 if buffer size is different than 512 samples. If it's different the metronom would skip clicks or double them. I mean WTF and FML rly... I am runing high performance power mode with disabled USB energy savers so it should be all good.

 

It was able to recognize the hardware. And it closes without crashing. Indeed, it is the only version of the software that seemed to have corrected those problems at least on our configuration. I know that others continue to have one or the other.

 

The message is the same they use for everyone. Mine was addressed to "Mark". We have no "Mark" on our staff. Welcome to the copy and paste era.

 

I confirm, version 2.3.4 solved both issues:
- Crash on exit
- No hardware connected

At last...

@Grzesiek
For the 10-15 seconds delay it is not a big deal and I think it is actually normal since the application also rely on a service (Focusrite Control Server) and it is current to have a certain delay upon starting/stopping a service.

After all, why would we want to reopen an application instantly after we just closed it ?