Hi..
 
I'm stumped. I have a Roland A-800 controller that had been working just fine with Sonar. What changed I do not know, but she work no more.
 
The A-Pro is listed and all entries are checked in the Midi Devices input and output lists. It's listed as a controller in the Controller section. In port is APRO-2 and out port is APRO. In the track meter when I fiddle with the keys the meter responds. However if I bring up a soft synth, no midi input is getting to it. The input is set to Midi Omni.
 
I downloaded a little vst called midi monitor and it shows no input when run within Sonar as well. However running MidiOx as a standalone shows midi input getting through just fine. Also vsts that run standalone respond to input from the controller. I have a couple of Arturia Moog soft synths that work stand-alone with the controller, but get no midi input when run in Sonar.
 
So Sonar can see the controller, the track meter responds to it, it's configured properly as far as I can tell, yet the meter seems to be as far as the midi gets. It seems something in the Sonar configuration must be wrong, but no clue what that would be.
 
And I just learned of Cakewalk shutting down.....my sympathies to all the developers who worked on it and are now looking for work. And a hearty 'boo' for Gibson. I've used Cakewalk stuff since the early 90's and sad to see it go.
 
Thanks in advance,
Bob
 

in the Windows explorer, enter "%APPDATA%\Cakewalk". Select your Sonar version folder. Delete TTSSEQ.INI.
Reconfigure Sonar MIDI devices.
 
If still no luck, on the Windows Device manager set option "show hidden devices" and remove all not existing MIDI devices.
 
Probably you have connected some device (f.e. Roland) to unusual USB port.

Hello,
 
As azzslow3 said will probably work My suggestions may be the long way but  I had similar issues and ended up .:
1. Deleting the controller config from preferences control surfaces
2. deleting the controller from Sonar midi devices
3. Deleting the device from windows
4. Rebooting and ensuring that the device is back in windows
5. Starting Sonar and reconfiguring both Midi and Contro Surface ares
 
I have also seen where a "project" gets corrupted. 
1. Open a new project and add an instrument track
2.Test to see if there are any issues. 
 
IHTH
 
Good Luck

I tried deleting the ttseq.ini file. No joy in Mudville. Set everything back up in Sonar re Midi and all looked the same. Also checked in Device Manager for hidden devices, and nothing there was not being used.
 
I also have a Kurzweil 2600 routed thru an Eiderol midi patch bay. Same deal with that machine. Meters respond but not getting any further than that.
 
I've already deleted the control surface from Sonar and uninstalled/reinstalled the driver for the A-800. Have also rebooted a time or three.
 
What I can't understand is if the Midi meters are responding, where is that midi scurrying off to? And as this is also happening with the Kurzweil (sorry...should have included that in the 1st message), it doesn't seem to be anything involving keyboards designated as control surfaces per se. I suspect it's just some setting somewhere I've managed to mess up, though what that is be a mystery.
 
Thanks for the suggestions though. That is appreciated.

Hello,
 
So in short the controller is not triggering any sounds for any given instrument? Are you using for the track simple instrument?.. If so do the same with an track that has the midi source and the audio track(s).  You should still see the midi track respond but no audio. At that point please review your audio routing for the track and master bus. Also look to see if all patches do not sound. Some instruments have patches that for whatever reason wont sound. 
 
IHTH.

Just thought of this.. Depending on your version of Soar.. It has a built in Keyboard. Does this fire the sounds if you have it?

I'm not sure why anyone isn't seeing the recent preponderance of midi issues where midi tracks are no longer playing, or controllers are no longer linking up to softsynths to make sound or even record midi data. This has never been an issue in the past and only recently have these issues started popping up. Seriously, go through the most recent posts in this forum and see how many of the same midi issues have started popping up. Was it something with the recent windows updates?

I've also had problems with the APro 800 with Home Studio - a few times when going through presets in soft synths I've found that various VSTi's seem to stop responding to the controller. I usually have to reboot for it to work again. Didn't have any similar problems until I updated from 8LE recently and from Win 7 and Win 10 at the same time
 
As you'll see from another thread I've also had VSTi's that haven't responded when I have tried to play them directly in the instrument's track but will respond when played via a midi track routed to the VSTi - very odd!
 
Good luck with resolving your problem!

bobulus
So Sonar can see the controller, the track meter responds to it, it's configured properly as far as I can tell, yet the meter seems to be as far as the midi gets.

If you're using a Simple Instrument (combined MIDI/Audio) track, then the meter is an audio meter and this is an audio routing/level issue rather than MIDI transmission/response issue. When troubleshooting 'no sound' issues with soft synths, it's best to split an Instrument track to separate MIDI and Audio tracks.
 
If the Audio track meter shows level, follow the output routing and check bus levels and hardware output assignments/levels.
 
If the MIDI track meter shows output (SONAR's MIDI meters are always  output meters, regardless of record arming status), and the Audio track doesn't, look for signs of MIDI activity and audio response in the UI of the soft synth (i.e. animated keyboard or MIDI activity indicators and audio output meters). If the particular synth you're using doesn't have MIDI/Audio indicators in it's UI, try using a different synth that does.
 
If the soft synth UI shows MIDI activity, but no audio output, check to see if Zero Controllers On Stop in MIDI Preferences or MIDI track volume setting is zeroing the synth's channel or master volume or possibly there's a problem with instrument/note range/channel/output assignments in the synth. It's even possible that the instrument's attack is so long that short MIDI notes don't generate any output.
 
If the synth UI shows audio output, and the track meter doesn't, you're back to troubleshooting audio routing/levels.

First....thanks to all who've responded and offered tips.
 
Here's what I've tried.
1. The initial situation was (Win7 64bit):
    A. MidiOX showed Midi input from midi devices.
    B. Soft synths that can run standalone worked.
    C. Vsts within Sonar did not work.
2. First tried many of the suggestions above. Thanks to all(!), however nothing I tried solved things unfortunately.
3. Downloaded a demo of Studio One (seems like it's that time anyways) and it exhibited the same issues as Sonar. No midi making it to the VSTs.
4. Once I saw the above, figured it was something Windows-wide.
5. Took the dive and upgraded to Win10.
6. Once upgraded, uninstalled the drivers for the A-800 and a Edirol UM-880 midi bay. Also uninstalled the driver for my cheapo UA-1G sound card.
7. Plugged the above devices back in and let Windows install the Win 10 drivers.
8. The UM-880 has no Win10 driver, so is currently out of the equation.
9. Reset the APRO back to factory defaults.
10. Checked the communication between the APRO and the APRO editor and all was well.
11. Fired up MidiOX and it showed Midi input.
12. Fired up a standalone soft synth and it worked fine.
13. Fired up Sonar and no midi input to the vst.
14. Fired up Studio One and no midi input to the vst.
 
So I am back where I started except I can't find stuff in Win10 yet, and something called Cortana just asked if I wanted to tell it a joke. WTF?
 
I'm a software developer by day and at this point all I can think of is to study up on how a DAW interacts with a VST, write a simple vst host, and write a simple vst that reports on its own state. And I most definitely do not want to have to do that.
 
If there is anyone with MIDI expertise familiar with how a DAW passes midi info to a VST (if that is indeed what happens) or can point me at any information that could help, please chime in.
 
Again thanks for the responses, and I'm completely baffled,
Bob