• Hi and welcome to the Studio One User Forum!

    Please note that this is an independent, user-driven forum and is not endorsed by, affiliated with, or maintained by PreSonus. Learn more in the Welcome thread!

Yesterday Using Studio One, I noticed that still when I disconnect USB Devices it Freezes

That should actually have been fixed. What device in particular are we talking about?
 
It's not an issue for everyone. I add/remove USB devices all the time with S1 running (Faderport 16, USB sticks, etc).

However, I do have my monitor on an HDMI switch, and if I flip the monitor to the other computer, S1 crashes.
 
Yeah, I'd think it would come down to what devices are we talking about (as asked). An audio and/or MIDI interface is going to have more of a drastic affect than some USB control surface that isn't sending to a track, and so on. More information is needed.

I have no such crashes when changing out USB devices.
 
Last edited:
To the OP - What version of Studio One?
 
It happens on my Windows box but not my Mac. But I have to ask, why would you need to do that?
 
JohnnyG said:
It happens on my Windows box but not my Mac. But I have to ask, why would you need to do that?
Click to expand...

This is my question too. What is so important to have to yank any USB cable in the middle of a S1 session?

Can't it wait until you are finished and S1 closed?

This sounds like a problem that simply does not need to occur for obvious reasons.

VP
 
Well, in S1 if a USB keyboard or controller isn't recognized, in the External Devices panel, you are instructed to unplug the device and plug it back in...
 
Was this a 7.0 thing?

Never gotten this behavior on 6.6.4
 
Windows. It probably wouldn't happen on an Apple they seem to deal differently with disconnecting things. However it happens, sometimes a device isn't working. It can also happen when plugging something in to the computer or turning something off and on that wasn't connected. Any time a change in USB comes along, there can be a crash of the S1 and freeze. As I said, age old problem S1 3 thru 6. Always been a problem. For instance the other day my Roland System 1m (USB Audio) was throwing some issues in the VoiceMeeter and not coming in audio, so I needed to restart it. When I did I first forgot it has a switch (since this rarely ever happens) and just pulled the USB, taking care to first close my session in S1, (but not the program). The program crashed. I turned off the Roland and on again eventually also because the USB pull out and put back in didn't solve the issues. Only turning it off and back on (because it stayed on when I pulled the USB because it's got power from a plug).
 
Vocalpoint said:
This is my question too. What is so important to have to yank any USB cable in the middle of a S1 session?

Can't it wait until you are finished and S1 closed?

This sounds like a problem that simply does not need to occur for obvious reasons.

VP
Click to expand...
It's likely a matter of one's own needs, for sure. For example in my case, my main computer is a laptop, so I may relocate from the house to the yard, or another room. Potentially swapping out a controller like an Atom SQ, or a keyboard controller, or nothing. So in my case it happens quite a lot that I change a USB connection while running Studio One. That said, I've never had a single crash. Nadda, nyet, nunca.

So, I'm guessing it would have to be something awfully impacting like having an audio Interface connected, while in playback or record, or such a drastic change which would make no sense doing. Scratch that. I just tried this on two of my laptops. I only receive a notice that the audio device is not found. I merely re connect, or change my audio interface right in Studio One and all is fine. I didn't try while playing back because....well, ..... that could be dreadful. Lol.

So it must be some USB device, hub, or something that is crashing the OP's computer. That, or some USB device conflict.

Just noting, that changing a USB device can happen. It's more likely on a portable PC, though in a mobile situation.
 
OP is using VoiceMeeter for loopback audio streaming with a lot of gear.. I personally think VoiceMeeter is a different animal entirely. I don't think this can be pinned on Studio One (IMO). I've never had an issue either.
 
It's not just this situation in which it happens, It has been happening all along. Studio One 3 thru 6. I can't believe there is not others with this happening. Could be a MIDI controller, or a synth or whatever. Turned on or off. Any time a USB device is disconnected/turned off. No it is something with studio one for sure. Not saying that Pro Tools wouldn't do it I really haven't used Pro Tools in this decade. Reaper? Maybe don't use it much. But occasionally if you even turn on a device it will usually cause S1 to freeze. It freezes because of any device on or off or disconnect or connect. Windows of course always. iPad or Apple computers not probably the same at all.
 
The only way you can say "no it's Studio One for sure" (when other users aren't having the problem) would be to see if when you run a stripped session on your system (no VoiceMeeter for starters) and maybe start with a limited number of devices, you then see how it behaves. While nowhere near as complex, I use OBS to stream S1 sessions with friends, using an in-interface loop back driver for streaming audio with 4 midi controllers (3 USB, 1 DIN), multiple tracks, (no external synths though), and I don't have this problem. Like Lokeyfly, if I disconnect eg, a keyboard, I get a notification - I reconnect and all is well.
 
AAV said:
The only way you can say "no it's Studio One for sure" (when other users aren't having the problem) would be to see if when you run a stripped session on your system (no VoiceMeeter for starters) and maybe start with a limited number of devices, you then see how it behaves. While nowhere near as complex, I use OBS to stream S1 sessions with friends, using an in-interface loop back driver for streaming audio with 4 midi controllers (3 USB, 1 DIN), multiple tracks, (no external synths though), and I don't have this problem. Like Lokeyfly, if I disconnect eg, a keyboard, I get a notification - I reconnect and all is well.
Click to expand...
I am tired of repeating myself. Age old problem. Never going to change. Did not have voicemeeter in 2018 2019 and it was happening. Age old problem with Studio One.

Voicemeeter never crashed from that. nore did OBS.
 
NoTimeForThoughts said:
I am tired of repeating myself. Age old problem. Never going to change. Did not have voicemeeter in 2018 2019 and it was happening. Age old problem with Studio One.

Voicemeeter never crashed from that. nore did OBS.
Click to expand...

USB connectivity is 100% controlled by the OS. Doubt there is any DAW software that would not be effected.

Then again - others in this thread are clearly stating that they have no issues. Appears this is environmental to your hardware.

VP
 
Last edited:
  • Like
Reactions: AAV
NoTimeForThoughts said:
I am tired of repeating myself. Age old problem. Never going to change. Did not have voicemeeter in 2018 2019 and it was happening. Age old problem with Studio One.

Voicemeeter never crashed from that. nore did OBS.
Click to expand...
Troubleshooting is asking questions, and you needn't be tired of repeating yourself. These things usually require providing all the direct information one can from the start. From what you provided, it sounds like this happens in your PC with numerous devices on or off (as we don't know which ones). Consider, many here, but I can't say all, have no issue disconnecting a USB device and having it crash with Studio One. So it's my suggestion you remove all devices, cold reboot, and start weeding out what may be the culprit device. That's about the gist of isolating the problem. It's also not just hardware as you'll have to see what USB drivers are involved, and updating any such devices. For example, some years back I had a similar issue when using Pro Tools. Lone behold, I remembered using a new mouse with out of date (older OS) driver. Updated that and problem solved.

So just be a little patient. The ball is in your court. We can only make suggestions, and your feedback will help. That's not guessing it might be fine on a Mac, but more along you letting us know any specifics by trying to isolate things on your system. Thanks 👍
 
Last edited:
You must log in or register to reply here.
Back
Top