No Synth movement or audio- - only midi movement.

Is this a question about SONAR? If so, which version. If not, which DAW?

Unless you're direct-monitoring the Jupiter, you need to have an audio track with input set to the Jupiter, output set to Master, and Input Echo enabled to echo the the input to the ouput. Input monitoring through SONAR is the preferred setup for working with hardware synths.
 
EDIT: the same applies to soft synths except that Input Echo is always automatically and invisibly enabled in a 'Synth' track (i.e. and audio track with a synth output assigned as Input).

I would 'begin at the beginning' with a new project using separate MIDI and synth audio tracks with synths inserted in the Synth Rack (i.e. not in audio track FX bins) so you can easily follow MIDI and audio signal paths independently. Get that working, and then troubleshoot existing projects if they continue to be a problem.  One possibilty is that the soft synths in existing projects are not connected/loaded successfully.

Can't really help without some indication of where exactly the discontinuity is.
 
I'm thinking possibly you've always depended on 'Always Echo Current MIDI Track' being enabled in MIDI preferences, and it's not enabled by default in your new installation.

I'm assuming here that you can get Sonar to play back actual audio (a loop or previously recorded file)

Do you have
1. Sonar in ASIO driver mode in preferences
2. Your Quad Capture selected as I/O in preferences
3. Your midi in ports enabled in preferences
4. Midi routed to a softsynth (and checked that you can record midi notes)
5. The softsynth routed to your master bus
6. The master bus routed to the output on your QuadCapture that you want to use


If all that is checked, what happens if you change the buffer size in the ASIO control panel?
Are there any other applications open (browser etc) that might be using the soundcard?

How long has this been happening?   Have you been updating SPLAT each month?  Maybe you should try to rollback (in the command center) to a previous version just to check and see if it changes anything...  Good luck!!

Can you share a simple project using Cakewalk synths that's not working? Just want to confirm this is a system-specific issue.

Hawkthornhill4366
I don't have always echo current midi enabled - - I always have to check the echo box to enable it. Plus, my midi works just fine -- just no activity in audio tracks or when I put in a synth ie If I insert individual audio & midi tracks & then a synth in my third track, only the midi track of the three tracks respond.

What does this mean - three tracks to play a soft synth? What are the inputs and outputs of these tracks set to? If you use Insert>Softsynth>(softsynth name)>First audio output you get two tracks - a MIDI track and an audio output track.

Hawkthornhill4366
It's been a week now & still no solution. I did try to bring up the Sonar X3 version to check to see if it worked properly, but my computer froze. I'm going to have a local computer repairman check to see if my I have a virus or some other problem with my computer. Obviously he won't know anything about using a daw, but at least maybe I can rule a computer problem out, to make sure it is in fact Sonar Platinum causing he problem. I downloaded Ableton Live Trial and everything works properly in it - - even all my Sonar instruments.
 
Thanks for trying to help - - I'm going crazy trying to solve this problem.

What windows version? Win 10 can mess with some interface drivers...

John
I insert a MIDI track in it and whether echo is on or not when I press a key on the MIDI keyboard and the MIDI meter lights up.
...
...
The MIDI meters show activity on the track. Echo has nothing to do with it. It shouldn't matter what the condition of echo is for MIDI whether its coming from a keyboard or has been previously recorded.

Unless there's a config setting I don't know about, I think you're mistaken about this, John. MIDI track meters are output meters only. They only show activity if existing MIDI is playing back or live input is being echoed. Even arming the track does not switch the meters to the input side as you might expect.

Interesting, John. I haven't tried, but I'm guessing that it works that way when the project Clock is set to 'Internal', which is only possible in a pure MIDI project with no audio content, including the audio metronome.

Thanks to all of you who responded with suggestions re getting no audio/or track recording in my audio tracks - - only activity was in my midi tracks. I tired all of your suggestions + a few from a couple of email responses I got from Cakewalk. My Quad Capture and entire set up were found to be correct. I downloaded a trial of Ableton Live and all of my Platinum synths worked fine there. I even had my computer checked out (my two hard disk drives & if I had any viruses or other items that could have caused the problem). The drives are in good shape & all the junk files were removed, but still no Platinum audio action & still getting a lot of freezing up when I try to work with it. Bottom line: I'm done with Cakewalk & Sonar. It's a great program if it works, but I've had too many problems with it, & of course this is the worst problem I've ever had. Maybe if Gibson didn't buy Cakewalk, and you could still get help via the phone (like I always got in the past) I would stay with it - - but I'm not sure that would even help to solve this problem. I'll be going to Presonus Studio One 3 and/or Ableton Live. Sonar was my first, and only daw that I used. All of my equipment is Roland - - electric midi accordion, electric midi guitar, Quad Capture & Jupiter-80. Roland is a great company & still offers wonderful support - - that's why I got Sonar & the other items.
 
For review I have: Windows 7 (64bit), 12GB DDR3 - 1600MHz, 2TB 7200 rpm SATA hard drive, 1 TB 7200 SATA hard drive 1GB AMD Radeon HD 7570.
 
 
 
 
 
 
 
 

Hawkthornhill4366
After having to disconnect all my cables & move my equipment due to recarpeting my music studio area, I mistakenly attached my cables.

That would have been a useful piece of information to have for troubleshooting, and contradicts your statement early on that 'My input & outputs are the same they have been for years & they always worked."
 
I guess we on the forum made the rookie mistake of not explicitly asking if anything had changed since it last worked. In my day job I've learned not to rely on users to automatically mention recent changes without being prompted.
 
Hard to imagine how these changes weren't affecting other DAW software, though.
 
Oh, well, good to hear you got it figured in any case.