I don't think you want to check "Enable MIDI Out" unless you want the MIDI to also drive another soft synth. And, if any of your MIDI tracks still have their inputs open, you may get unwanted sounds, i.e. the MIDI may play through those tracks as well.
While TTS-1 usually plays softly, it may be distorting since it sums all the synths to 1 output. I've gotten into the habit of always lowering a synth's volume before hitting play. My hearing is bad enough. Learned that from DreamStation DXi.

As I said , you don't want to send midi info unless your using your outboard gear. SHUT ALL THAT OFF . 
Your probabley getting a midi loop back as the TTS_1 is playing, sending midi out and it's coming back again. 
 
Try this. 
Go to midi devices/output uncheck everything. 
OPEN a GM midi file. This should open a new project and insert the TTS-1 automaticly. 
 

Okay, johnny V, I did as you recommended. The only thing to uncheck in MIDI Out was the GS Wavetable. So now all the instruments show <default> where a synth is supposed to be, and default is deaf. No sound. 
 
So, with the same MIDI file resident, I loaded TTS-1. I took Greg's advice, and did NOT check Enable MIDI Out. I just clicked on the popup as it sat. I started off by configuring only one instrument to TTS-1. The rest I left at deaf (my spelling of 'default' for now). Playback sounds the same -- this weird sort of out of phase distorted sound. This is a new problem. I've been using TTS-1 without issues for a while now, and all of a sudden, this crops up. I had to have clicked on something I shouldn't have. I just haven't figured out yet what it is.
 

Hey - here is another thought.  With ANY keyboard containing on-board (local) sounds, that I hook into my computer, via either USB or an old-school midi connector, I go into the Edit parameters for that keyboard, and turn OFF a midi parameter called Local.
 
What that Local parameter controls is whether or not pressing a key on that keyboard will have the keyboard react to that to trigger a note.  With Local Off, it is like separating the pressing of keys from actually generating a sound.
 
Now, on the surface, that would seem rather silly, but because you have the keyboard connected into your computer (and as a midi input device and a midi output device in Sonar Preferences), even though the keyboard won't generate a sound directly from the pressing of a key, it WILL still generate a sound, because that midi data is sent into Sonar, and back again through the midi connection to the keyboard, which will THEN cause that key's associated sound to play.
 
There are 2 reasons the above will help:
 
1) It will almost always result in sounds from other tracks and sounds from the keyboard lining up properly, with it all essentially being processed in the same manner from within Sonar.
 
2)  With Local set to 'Off', you prevent a second note playing the sound for a second time.  If you DIDN'T turn your keyboard's midi Local parameter to 'Off'. then what usually happens is that you would get TWO notes sounding every time you played a single key on that keyboard.  The first note would sound from the keyboard reacting to the pressing of a key, and the midi data going into Sonar and back into the keyboard again would then trigger a SECOND sound for that same key, with a slight latency making it sound like an echo. (for sounds that are mono, or for synths where there are limited voices, you could also either goof up the sound heard or actually end up with sounds dropping off, because of the keyboard processing each key pressed a second time - if Local was left 'On').
 
SO - the general guideline would be that for keyboards with on-board sounds, versus midi controllers that do not have their own sounds, you would always go into the Edit functions on that keyboard and set midi parameter 'Local' to 'Off'.
 
Using the above approach, you may well never need to mess with manual setting of the Automatic Delay Compensation that Sonar defaults to doing for you.
 
Here is a link that explains Auto Delay Compensation:
 
http://homerecording.com/bbs/general-discussions/newbies/what-exactly-automatic-delay-compensation-314029/
 
I hope the above helps you with your situation.
 
Bob Bone
 
 
 

HI Bob, long time no see, good to see your still out there.
 
But he did say the only device in midi was the wavetable? Odd, as I would think his keyboard or the Delta midi ports would also show. 
 
You are looking in Preferances/ midi /Devices? 
 
Anyhow this sounds now like you are having a audio interface driver issue, Are you using the ASIO audio driver? Delta 66 is a real old card. They are known to die of old age too. 
 
And there is one more possiblity, lately I had the TTS'1 do as your saying from time to time. There is a bug in it that was never there in the past and there were a few issues starting back last August. Not sure if it's the version of SPLAT or W10. 
 
 

Guys, the only time the Casio shows up in Sonar is when I have it on. And even then, if I haven't been using it, it will time out after a while and shut itself off.
 
Next time I start it, I will check to make sure that Local is OFF.
 

I have a Casio 88-note piano that I use as a midi controller for piano parts, and by default, it will shut off if I haven't played on it for some number of minutes.
 
It has a way to override that behavior, which for me is to hold down the button on the far right of the buttons (might be Hall Reverb or something like that), anyways, when I hold that button down and power up the keyboard, it will then stay on forever, until I turn it off again.
 
If instead, SONAR is disconnecting your Casio after some period of time, that is the result of a Windows behavior, which is that it will by default disconnect USB-connected devices after some period of inactivity.  This is handled with Power Management options.
 
There are at least a couple of ways of getting to the Power Management option to change that behavior - one way is to go into the Advanced settings in Power Management *Control Panel\Hardware and Sound\Power Options\Edit Plan Settings>Change Advanced Power Settings), and after expanding the USB Settings options, set "USB Selective Suspend Setting" to 'Disabled', and apply/OK the change.  Another way is to go into Device Manager, and go to the Properties of each USB hub, then click on the Power Management tab, and remove the check from the option labeled "Allow the computer to turn off this device to save power", and apply/OK the change.
 
Hope any of the above helps, 
 
Bob Bone
 

A bit of digging around and there are lots of posts going way back with the TTS-1 playing distorted and most it was people using higher sample rates. So you either have to revert to 44.1 or 48 or abandon the tts_1.
 
As an experiment try this. 
 
Go into your preferences and change the sample rate to 44.1 or 48. APPLY. 
Make sure your using ASIO mode and the Delta is your timing master etc. anything to do with your on board sound needs to be unchecked. 
Now make sure there is no devices selected in MIDI/ output. 
Now OPEN a midi file. Do not import. 
I have midi files set to use Sonar as the default program to open, do this or using the FILE menu choose open and browse for a midi file. Open the midi file and TTS-1 should load and play the file perfectly. Tell us what happens. 

When you said "Horrendously out of phase" it immediately brought to mind a midi loop. This idea is reinforced with your report of dropouts. Disabling midi output of all your software synths is one way to reduce this possibility. Another important thing to do is set your midi track inputs to just one port & channel - your keyboard, so don't use "none" in a midi input. And then make sure your keyboard is configured to "local off" (Sonar can do this at startup, but if your keyboard has a habit of switching itself off, you may have to learn how to do this manually.)

mwmcbroom
"Horrendously out of phase"

 
Probably not that relevant but.. Have we established the soundcard type ?