Anderton

soens

Anderton

AdamGrossmanLG
probably just poor coding as usual with Cakewalk.

 
Actually it's almost certain that it isn't, given that no one else is chiming in to say they've experienced this problem.

Not everyone reads every post. I've had USB issues like this since... ever. We'll see if my issues are fixed by these setting changes.

I know not everyone reads every post, but I do monitor posts. Although there are quite a few posts about various issues with USB, particularly audio, I don't recall seeing any that were solved specifically by reboots (of course, I don't read every post either but I do try to keep on top of problems). Most fixes have involved techniques that have already been mentioned, along with quirks like certain interfaces being "wedded" to certain ports so if you unplug them and plug into a different port, the driver doesn't register (and this adds another port to the ongoing list Windows keeps).
 
There have also been threads that have gone on forever where people have offered a zillion different suggestions, only to find out that something was going through an unpowered hub that had multiple peripherals plugged into it, and plugging directly into the motherboard's USB port or a dedicated USB card solved the problem.
 
Because I haven't seen this issue appearing with regularity, if it was indeed "poor coding" then it should be fairly prevalent because the problem would relate to SONAR, as opposed to an interaction within the system. It really helps to isolate the issue as much as possible. A lot of people assume that if SONAR acts up, it's a SONAR problem so they re-install SONAR to no avail...or if Windows acts up, they re-install Windows and it doesn't make a difference because the problem may actually be a piece of hardware or driver.
 
If the problem is solved by exiting and opening SONAR, then that might point to some whacked SONAR preference. If the problem is solved by rebooting the computer, then it sounds like something computer-related. But I can't say for sure because I never needed to come up with a solution past "turn on the peripherals before turning on the computer." BUT that's not universally applicable advice, either 

Well, then can you explain how when the MIDI controller is not working in Sonar, it works fine in standalone VST applications (in the same moment)?   Here is what I have done:
 
-when MIDI controller stops working in Sonar, I keep Sonar open and open a VST app and they keyboard works.
-I then close Sonar, keyboard still works in VST app
-I then close the VST app, re-open Sonar, still doesn't work.
-I then reboot and then it SOMETIMES works again in Sonar.
 
The only problem app is Sonar here.

Adam, im not sure if I mentioned but don't rule out a bad USB port or bad USB able.
I wore a port out a while back and it difficult for me to find out what was wrong because the port was the last thing I expected but when we plug in our controllers, interfaces, exc in to a port a million times they get wasted eventually.
Of course this doesn't explain why it works with VSTs but not sonar. (maybe sonar is just finicky)
 
Also not sure if mentioned but don't use a USB hub.
Also important to sonar but not as much vst's, make sure to always plug the controller in to the same port you used to install the drivers. you will get it to work but inconsistently. Some devices are plug and play so that doesn't always apply.
 
I haven't experienced losing devices but I have had sonar hold my controller hostage a while back with an M audio Oxygen 49. However once I built a new system the problem disappeared. I blamed the combo of Sonar and the set up (An AMD FX/Gigabyte Mobo).

AdamGrossmanLG
 
Well, then can you explain how when the MIDI controller is not working in Sonar, it works fine in standalone VST applications (in the same moment)?   Here is what I have done:
 
-when MIDI controller stops working in Sonar, I keep Sonar open and open a VST app and they keyboard works.
-I then close Sonar, keyboard still works in VST app
-I then close the VST app, re-open Sonar, still doesn't work.
-I then reboot and then it SOMETIMES works again in Sonar.

Can you reproduce this using a different MIDI controller, or is it only happening to one particular device?

abacab

AdamGrossmanLG
 
Well, then can you explain how when the MIDI controller is not working in Sonar, it works fine in standalone VST applications (in the same moment)?   Here is what I have done:
 
-when MIDI controller stops working in Sonar, I keep Sonar open and open a VST app and they keyboard works.
-I then close Sonar, keyboard still works in VST app
-I then close the VST app, re-open Sonar, still doesn't work.
-I then reboot and then it SOMETIMES works again in Sonar.

Can you reproduce this using a different MIDI controller, or is it only happening to one particular device?

This problem has been happening for over 7 years now... going back to at least X1 with different computers and different keyboard controllers over the years.  Same exact symptoms though.
 
Its fine if it is a problem with Cakewalk, not looking to place blame, just looking to get a fix. 

AdamGrossmanLG

Anderton
If the problem is solved by exiting and opening SONAR, then that might point to some whacked SONAR preference. If the problem is solved by rebooting the computer, then it sounds like something computer-related. But I can't say for sure because I never needed to come up with a solution past "turn on the peripherals before turning on the computer." BUT that's not universally applicable advice, either 

Well, then can you explain how when the MIDI controller is not working in Sonar, it works fine in standalone VST applications (in the same moment)? 

In SONAR, MIDI is part of a system and has a different set of Preferences and constraints than a stand-alone VST. See TStorm's post above. He seems to confirm my thinking "then it might point to some whacked SONAR preference."
 
Also, are you sure that SONAR is not actually seeing MIDI as opposed to not producing sound? For example, only one device at a time can access ASIO. If you have a stand-alone VST that wants ASIO, and SONAR set to ASIO, only one of them will produce audio.
 

Hi Adam, without rereading the entire thread I can't remember if this has been suggested yet. Try deleting (or renaming) the TTSSEQ.ini file. It can be difficult to find (Users/roaming/ appdata?). But after deleting it when you restart SONAR it will build a new one. You will have to redo all of your friendly names but it can fix a lot of these type of midi issues. 
 
"If you have a stand-alone VST that wants ASIO, and SONAR set to ASIO, only one of them will produce audio."
 
Not to be argumentative, but I can run Dim Pro and Rap session (ASIO) standalone at the same time as SONAR through the same output pair of my Orion 32+. So not being able to run 2 ASIO apps at the same time is not universal. You can't however run 2 different ASIO interfaces at the same time AFAIK.

Base 57
Not to be argumentative, but I can run Dim Pro and Rap session (ASIO) standalone at the same time as SONAR through the same output pair of my Orion 32+. So not being able to run 2 ASIO apps at the same time is not universal. You can't however run 2 different ASIO interfaces at the same time AFAIK.

Good to know...maybe I need to use an ASIO interface with more outputs, and assign the devices to separate ASIO outs.

Base 57You can't however run 2 different ASIO interfaces at the same time AFAIK.

Well, you can if the device manufacturer's driver supports running more than one of their interfaces at a time, as e.g. RME's does. I'm a bit surprised more manufacturers don't issue multi-client ASIO/Core Audio drivers, it would probably help them sell more interfaces. There must be plenty of people who would like to be able to replace the rat's nest of wires more complex setups always tend to degrade into over time with shorter audio cables to a second interface and a USB/firewire/Thunderbolt cable back to the computer.

And if an interface supports ADAT you can always add more inputs/output that way of course.

Like RME, Antelope drivers do allow two Orions to be connected to the same computer for 64 analog I/0. However I don't think we would be able to hook your RME and my Antelope to the same computer and use them at the same time with ASIO.
 
And yeah, the rat's nest (I call it the snake pit) is ridiculous. But I don't have to do much re-patching and I can track through my analog board so latency is irrelevant.
 
Sorry to get off topic. We need to get Adam's midi working right. Did you try the TTSSeq thing?

Anderton

Base 57
Not to be argumentative, but I can run Dim Pro and Rap session (ASIO) standalone at the same time as SONAR through the same output pair of my Orion 32+. So not being able to run 2 ASIO apps at the same time is not universal. You can't however run 2 different ASIO interfaces at the same time AFAIK.

Good to know...maybe I need to use an ASIO interface with more outputs, and assign the devices to separate ASIO outs.

ASIO can share or pass multiple audio streams from different programs. A windows system just can't address multiple ASIO drivers.