Thanks for that, I'll go through it tomorrow. Moog is all set up as per instructions, had it for years and it's never done this. This was happening before though, with the M-Track and not with USB connected synths, with midi ones through the M-Track. They're working fine now through Focusrite. And the Moog wasn't in the set up.

 

Tell me, can you describe the error a bit more and in more detail.

When does it occur, always at the same time, when you switch it on, when you play a lot, etc.! Do you perhaps have the feeling that it's more likely to happen when you send a lot of data, for example from volume pedals, mod and pitch wheels, from faders?

How to solve the infamous Windows 10 MIDI device renaming issue
https://medium.com/@stickgrinder/ho...ws-10-midi-device-renaming-issue-9aa793fa9f0a

KORG - MIDI Device is not recognized on Windows
https://support.korguser.net/hc/en-us/articles/115004269166-MIDI-Device-is-not-recognized-on-Windows

Resolving MIDI Device Issues on PC and Mac
www.sweetwater.com/sweetcare/articles/resolving-midi-device-issues-on-pc-and-mac/

 

Last edited: Jan 16, 2025 at 10:33 PM

Try uninstalling greyed out ghost devices in device manager. Change the view to show hidden device, then expand the universal serial bus controllers and uninstall the greyed out ghost devices, then try connecting again.

If no change, then experiment with different USB ports.

 

Didn't go through the thread, I guess others might already said so: Most definitely a power thing. I guess it would not happen with a powered USB hub. Why it worked before: You might have had the power hungry machine on one of the first ports. Now the thing with let's say 7 port hubs is: There is no such thing as a >4 port USB hub. The 7 port hob uses one port of a 4 port hub and attaches another 4 port hub. These upper 4 ports that already hang on an USB hub themselves act a little more sensitive. So it does make a difference in what order you plug your syths in.

 

It's just the Moog Subsequent 37 with the issue. The first thing I would do, would be to disconnect any other synths which are connected via USB; and then I would cable *only* the Sub37 to the computer directly. I would go on the Moog website and probably update the firmware for the Sub37; even if it is the same version it already has. Many times, you cannot update your synths' firmware when connected via a hub. Powered or not.

Some manufacturers will explicitly state in their manuals to never use them with a hub or you will get unintended results like this. Most of the time it is really just for the initial setup and connection, and then you can move the connection to a powered hub if you want and it will work ok. Connecting it directly to the computer will be the very first thing tech support will tell you to do, even if it is obviously not the source of your problem.

 

Well, if it's your Moog Subsequent 37 that's not working you can give it to me to free up the space in your room to get a different one that does.

 

Thanks for all the suggestions. None of the synths run through USB hub, all are straight into the computer. And I've tried everything suggested and it's still happening.

Here's what's happening. On 1st photo the Moog is connected via USB to Live (and it's sending and receiving midi). Then I switch on another piece of USB connected (not powered) hardware (doesn't happen with midi hardware) and Moog disconnects (photo 2) and I have to re-connect from the drop down menu. Only happens with the Moog and only ever when I switch kit on, never when I play or Live is running tracks etc.

 

Last edited: Jan 17, 2025 at 9:41 AM

Thanks for the generous offer. The Moog is working or you could pick it up today (it's the Sub 37 Tribute anyway, you probably don't want one of those....)

 

Could you try the same thing in another DAW to reproduce the error so that we know if the error is in Ableton, Windows or the Moog Sub 37.

 

Good idea but I only have Ableton.

 

Reaper can be downloaded from official site for free

 

I think we should focus on Ableton, does this happen even if you've turned off all FX/effects beforehand?
Help me out, what is the "kit" or in other words, does Ableton shut down due to overload or malfunction?

When you had problems with your old audio interface, was it the same problem as now?
And why is it happening now? Have you updated Ableton? Is it a different Ableton than it was back then?

Maybe the Ableton Crash report will shed some light?
Reading Live Crash Reports: https://help.ableton.com/hc/en-us/articles/5301568366354-Reading-Live-Crash-Reports

What to do if there are no crash reports?

In some cases, there may be no report. In this case, please send the following log file to our customer support.
Windows: \Benutzer\[Benutzername]\AppData\Roaming\Ableton\Live x.x.x\Preferences\Log.txt

Note: The log file also contains the date and time, maybe take a look and post it here.

 

Ok. When I had the M-Track it was midi synths that disconnected and midi was sent from the M-Track. I run two synths using midi and they would both disconnect. Set up the Focusrite and all was fine, no issues. Then I added the Moog 3 days ago and the same issue started but now it's a USB synth, not midi. If I switch the Moog to midi cable it's fine. When I say 'kit' I'm talking about hardware kit in my set up so sequencers, synths, midi keyboard. Any bit of kit I switch on (or off) will cause the Moog to disconnect. But not if it's one of the 'midi' synths.

Ableton isn't crashing but I am wondering if there's a bug somewhere. It's the most up-to-date version.

 

I've just disconnected the only USB device that's not connected to Ableton (external hard-drive) and it caused no issues. Not sure what that means but it does mean something.

 

Power Source

• USB-powered drives: Consume up to 4.5 watts, which is within the USB 3.0/3.1 power delivery limit (5 volts, 900 mA).

It does not mean much towards solving you problem. but it is good to rule out anyway.

 

Then it's more a matter of Windows.
Read my post about USB again --> #Reply2 --> https://audiosex.pro/threads/synths-disconnecting.78722/

How to Open Disk Management From Command Prompt
Execute DISKMGMT.MSC for quick access
https://www.lifewire.com/how-to-open-disk-management-from-command-prompt-2626097

Use the System File Checker tool to repair missing or corrupted system files
https://support.microsoft.com/en-us...em-files-79aa86cb-ca52-166a-92a3-966e85d4094e

 

Last edited: Jan 17, 2025 at 1:06 PM

This is exactly what I would do. Rule out your Ableton and every setting in it, by using a second stock daw.

 

Thanks, I'm very grateful for your time and thoughts here, but it's getting beyond me now, I'm not sure how to use some of these tools. I've done system file checker and it said it repaired corrupt files ( but still no different). I'm not sure what I'm supposed to do with Disk Management once it's opened? I have read your earlier posts and done what I can but some of it is way beyond me - USB tree etc. No ideas what I'm supposed to do there. The midi driver repair suggestion (you tube video) would not work, said this version of windows doesn't run it, or it's no longer used.

 

Did I understand you correctly, the problem no longer occurs?

Well, with the Ableton log file, you could use Ableton Support.

What to do if there are no crash reports?
In some cases, there may be no report. In this case, please send the following log file to our customer support.

Hidden Folder: C:\Users\YourName \AppData\Roaming\Ableton\Live 12.1.1\Preferences

How to Show Hidden Files on Windows 11 the Easy Way
www.howtogeek.com/743079/how-to-show-hidden-files-on-windows-11/


Example Ableton Log:
2024-11-29T22:10:32.257156: info: WaveIn: 1. device: Analogue 1/2 (Audient iD14)
2024-11-29T22:10:32.257250: info: WaveIn: 2. device: ADAT 7/8 (Audient iD14)
2024-11-29T22:10:32.257339: info: WaveIn: 3. device: SPDIF/ADAT 1/2 (Audient iD

Sfc / SCANNOW is always good for repairing errors in general, the goal is to have as stable a system as possible.

You can check and repair the external and internal hard drives for errors with this tool:

Run CHKDSK in Windows 11 and Windows 10.

Using the Command-Line Interface

1. CHKDSK can also run using the command line (DOS) prompt.
2. Click Start and then click Run.
3. Open the command prompt and type cmd in the search box.
4. Click OK.
5. Right-click cmd.exe in the search results and then select Run as Administrator.
6. Type CHKDSK /f and press Enter.

How To Run Chkdsk Scan In Windows 11 [Tutorial]

 

Last edited: Jan 17, 2025 at 3:01 PM

Ok, managed to get this working and it's not disconnecting so it's looking like it's to do with Ableton.