Midi Controller Problem

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.

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.

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'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!

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
 
 
 
 
 
 
 
 

This would be real dumb... Is input echo on? 
 
And to the guy who thinks Sonar is "broken" as far as midi goes,, the recent threads, and I think I've been part of all of them, are all midi newbies and possibly one thing in common is not understanding midi routing. I think these people  with issues are all using those simple instrument tracks... They might be why things don't work. I've never used them being one who likes my audio and midi separated. 
One person I helped took my advice and is now using  separate midi tracks and reports all is now working for them. 
 
1- Audio track - Records audio from your audio interface via ASIO drivers. Can also drop WAVE loops here.
2- Midi Track - Records midi from your midi controller, Keys or drums pads. Can also drop midi loops, draw them etc, outputs to a VST instrument or MIDI output to hardware. Makes no sound on it's own. 
3- VST instrument track plays midi data from a track or a live input from midi controller. Treated as an audio track. 
4- Simple instrument track combo of a midi and a VST instrument track 

So, you get no sound from VST, independent from Live/Recorded. Also in case a VST has build-in keys, they are also not working (when "played" with moused). Do I understand you right?
 
General settings to check: Audio buffer size (under 1024), MIDI prepare size (1000 or so)
 
 

Hi azslow3....(I misspelled you moniker earlier....my humble apologies!)
 
Let me tell you the settings I have. I tried inserting an image, couldn't see, so I'll type it out.
 
Warning......I'm gonna sound like a newbie because sound drivers are not anything I really understand. I've been plug and play and ignore it with this stuff.
 
Wordy....but here's anything I saw that looked relevant:
 
AUDIO
 
ASIO dialog.
I've got a UA-1G sound card (mine says Cakewalk) using an ASIO driver. If I bring up the ASIO settings thingie, it shows me first an Audio Buffer Size with a scale of 1-10. It looks like the default is 6 as there is a little green arrow under that number. Mine is set to 4 which the dialog reports is favoring real-time slightly over stability.
 
Under that is
ASIO Buffer size set to 160 samples.
Use Smaller ASIO Buffer size is unchecked
Use ASIO Direct Monitor is checked.
 
SONAR AUDIO DRIVER SETTINGS
Playback Timing Master - None
Record Timing Master 1: UA-1G IN
Audio Driver Bit Depth 24
64-bit Double Precision Engine is Checked
Stereo panning Law: 0dB/center...argle, bargle don't feel like typing it
Dim Solo Gain -12 dB
 
Sampling Rate 48000
Buffers in Playback Queue 2 (cannot edit)
Buffer Size: (set at far left i.e. fast, and the slider control is disabled)
 
ASIO Reported Latencies
Let me know if this info is at all useful.
 
SONAR AUDIO PLAYBACK AND RECORDING SETTINGS
Driver Mode : ASIO
Dithering : Triangular
Items checked are:
Use Multiprocessing Engine (Plug-in Load Balancing not checked)
Use MMCSS
Always stream audio through FX
Always open all devices.
 
Let me know if anything else here is at all useful.
 
 
MIDI
All my devices that I expect to be listed are listed. For inputs there's APROs midi in, APRO 1 and APRO 2 and a TD-25 checked as well as at 64 I decided it was finally time to take up drums. Outputs all look right as well.
 
Driver Mode (?) is set to MME. Closed a project and saw the other option is UWP or something like that.
 
Record
Everything is checked, number of buffers is 64, Echo Sys Exclusive is also checked. The Sys exclusive echo port is set to APRO.
 
Playback
250 Millisecond Buffers.
Always Echo Current Midi Track is checked.
 
Nothing interesting looking under Midi files. Let me know if otherwise.
 
Instruments
Everything there....all instruments, all midi channels, etc.
 
Control Surfaces
The APRO is there with In Port APRO 2 and out port APRO. The refresh frequency whatever it is be set at 75 milliseconds.
 
I hope somewhere in there is the information you referred to. And thanks again!
 
Bob
 
 
 
 
 
 
 
 
 
[image]file://c:/apps/ASIO.jpg[/image]
[image]file://c:/apps/ASIO.jpg[/image]
 

SONAR AUDIO DRIVER SETTINGS
Playback Timing Master - None           THIS SHOULD SAY THE SAME AS RECORD TIMING MASTER
Record Timing Master 1: UA-1G IN
Audio Driver Bit Depth 24
64-bit Double Precision Engine is Checked
 
This is why your not hearing anything I would guess. 
Your worrying and the location of your VST's and that's not your problem.
 
You need to get your Audio interface working properly. 
 
If you can open a VST instrument you should hear sound when you play the virtual interface in the GUI. Like if it's a Keyboard or drum VST you can play the instrument. You need to get that working. It would seem you need to make sure you have the most up to date drivers for your audio interface and install them again. 
Is there a audio driver for that interface for what ever version of windows your using? 
 
And you've ended up with more than one driver for your keyboard in all this, you should not have A 800 "2" that will certainly cause a problem. See if you can uninstall all these drivers and start fresh. 
 
 
Playback
250 Millisecond Buffers.   THIS SHOULD BE HiGHER  500- 750
 

Hello Cactus Music.....
 
I owe you one. Weird sequence of events though. I set the playback timing master to the ua-1g out and then brought up a soft synth with a virtual keyboard. Sound when I mouse'd the key, but no response to the controller. So I started composing you a 'thanks, I'm halfway there!!' response, took a quick look-see back at Sonar, twiddled a few notes on the controller, et voila, sound. Brought up the plug-in again, twiddled some more keys and the little virtual keyboard twiddled along.
 
So now it's 'thanks, it's fixed!!!!!'. I must have fumble-fingered that playback timing master setting. As I mentioned earlier, once I've got this stuff set and working I forget all about it. Things have been working for years now, and it's probably been about that long since I even looked at those settings. I would have never noticed my fumble-finger'ed-ness without your help. 
 
So thanks to everyone who chipped in with tips and I am good to go!!!!!
 
Completely off-topic.....where it looks like Gibson isn't selling Cakewalk, but just basically throwing it away, has anybody proposed the idea of releasing the source and continuing it as an open source project? Is that a naïve question business-wise? It seems a shame to just toss all that hard work and effort away, and if they aren't going to sell it and it's bound for the bit bucket, why not make some open source arrangement instead? I write software for a living, I'd chip in to such a project and my guess is there are others who would do the same. 
 
And again, my condolences to everybody who worked at Cakewalk. I've been using your stuff since it was Twelve Tone systems, am old enough to still be amazed at what is now possible to do musically in a little studio in a little room, and appreciate the work put in to make Sonar a pretty darn good DAW. May you all land somewhere you like.
 
Bob