No audible MIDI output

I am slowly updating my system to X3 on a new pc. I am up to sonar 8.53 (which I what I used to use with a Win 7 pc and rarely had any issues of any kind).
 
 I have a 1st gen Focusrite 2i4 installed and just installed my nanokey, also the 1st "gen" (drivers for win 10). I have a 2nd HD for projects installed and will soon be installing a Roland A-500s before installing the rest of Sonar and then plugins, etc.
 
Now I am just checking as I go along and find I cannot get any sound out of a synth. I have created audio tracks and recorded guitar. All is well.
 
So I click the + to insert a synth, select midi source and all analog outs (something like that). When Dim Pro comes up, I select a preset.
 
The top track has input set to Dim Pro X64 (v. 1.2) and output set to master.
 
The midi track has:
i: nanokey omni
o: Dim Pro X64
ch: 1 Dim Pro or none or anything else
bank: bank or none
patch: none
 
also input echo: either auto thru or on
 
I get midi lights in the taskbar icon (little red flashing lights), and there is a peak in the midi meter for each note played on the nanokey.
 
R for recording armed or off.
 
I can play the guitar track and hear it.
 
I've tried all kinds of changes to the midi settings but no sound.
 
Does anyone have an idea, I use the nanokey for creating rough ideas (bass, for instance) or checking patches. I hope all is well and my sonar isn't hosed. Is it just something I am missing. Focusrite and nanokey are listed and checked in midi devices, in device mngr so I can figure out what I have missed.
 
But no sound.
 
I really could use some help. Thanks!

Good point, I did try that to no avail. I also used TTS and nothing. Today, I'll write some notes in PRV and see if that gives anything.
 
Thanks for the suggestion. I'm really bummed this has stopped my progress.
 
My pc must have been on the shelf for a while as last week, I just got the Fall Creator's updates, then another windows update and then Dell flashed the bios so I am getting (probably unjustly) paranoid.
 
Could something in my system be disallowing midi to be heard, or is it sonar? I'm lost on this...

Thanks randyman, I will double and triple check today
 
But I ran into this days ago and have done this over and over, with new projects, new synths, etc, just clicking on different settings hoping I've just done something blindly and incorrectly, but always with a midi track and an audio track as I've done since 2007 when I first began working in Sonar.
 
I'm not sure if a vst, or a driver or Sonar is corrupted or what, I am way more than you, no expert whatsoever and I'm completely at a loss, so much so I don't think I can enjoy the Vikings game tonight!
 
I see there is another post with apparently the same exact issue and I will be following it closely. If no cigar, I guess I have to give up because I am clueless in Seattle and everywhere else :)

Cactus Music
 
You're the best, I owe you a brew and a bundle of thanks.
 
What you describe above you have expertly done in other posts as well (thank you for your gracious time) and I have followed those to no avail.
 
Today, however, I created a new project (in case the other test project was corrupt) and used TTS rather than dim pro. The only other difference is I de-selected midi source and added later as you describe. It played audibly! I did this over and over to be sure.
 
Then I added dim pro and still no sound. So that is the culprit. In the past, when I tried other projects, I always started with dim pro, which didn't work, and then nothing worked, in fact Sonar often froze or stopped working.
 
So now, I have the basic Dim Pro 1.2 which came with Sonar 8.5 producer. I believe there is a patch and I have three other Dim Pro 1.5's in my Cakewalk account. I will try the patch and, if not, upgrade to 1.5 and then all should be well I suspect.
 
Finally some progress again. Wahoo!
 
Again thank so much Cactus Music!

scook

robbyk
 
Then I added dim pro and still no sound. So that is the culprit. In the past, when I tried other projects, I always started with dim pro, which didn't work, and then nothing worked, in fact Sonar often froze or stopped working.
 

In no post do I see where a program is selected in DPro. By default DPro makes no sound. A program must be selected from the DPro program browser before the synth will make a sound.

Yes, I normally pick a pad and then a bass, just to try. Sorry, I should have made that more clear. Thanks!

Great info, as usual, scook, you are a master at this and you have benefitted me over and over (for years) with your expertise, great explanations and depth of knowledge.
 
I will check those settings as I did not know about them.
 
My little nanokey has an octave up and down which I usually check from top to bottom if the preset is not really known well by me. And thanks for the DX support info but I have only two projects in the pipeline as I had completed all other ongoing projects when my old pc died and they used Dim Pro 1.5.
 
So just to check this again, I brought up a new project, loaded Dim Pro 1.2, a midi track, set input/ output, loaded a pad, no sound. Then sonar froze for a time and I exited. Brought up the project and no instrumented worked whatsoever.
 
I restarted the pc, went into the project, loaded TTS, etc and played the fantasia. so much fun.
 
Today Vikings football, tomorrow Dim Pro 1.5 and move on!
 
Thanks Scook and Cactus Music and all others who helped me out of this glitch. I'm suspect there may be more to come...

Cactus Music
Not sure about older versions but you have to authorize Dim Pro before it will work. You would get a warning about this.
So after I install Dim Pro I copy my serial to the clipboard, OPEN the stand alone version using RUN AS ADMINISTRATOR and enter the serial. 
 

Yup, that's how it was for me too, authorized and I also use the Run as Admin, always out of habit, and both Rapture and Dim Pro are to be authorized in stand alone is what I have in my notes from original install.
 
Thanks again!