Here's an odd one. Has the TTS-1 been changed or exposed differently in the latest update?
 
I often use TTS-1 as a scratch pad for getting basic ideas down since it's so lightweight and is easy due to it being standard GM. A lot of my guitars a tuned to E flat, and its rudimentary to just do a -1 on the key in the inspector to get it all in tune.
 
I was roughing out a song today and while the key worked as intended during playback, it had no effect whatsoever while I was recording myself playing the notes on my controller. Other synths worked as intended, however.
 
I know TTS-1 could do this before this update.
 
Sure it's rudimentary to just use another synth and copy the MIDI into the TTS-1 track if I really want to use the sounds but it's an odd thing to happen.
 
Is this just local to me, or should I file a bug report?

HA! I fear I'm the only person still using TTS-1 judging by the tumbleweeds rolling through this thread right now! 

I'll try to circle back to this in a couple hours, to see what happens on my system, and will post my findings.
 
Bob Bone
 

I just created a new project (Everett) and inserted TTS-1, and the "Key+" in the inspector has no control over it (is that what you were seeing?) This may be related to the drum map issue in Everett (no idea honestly).
 
A workaround (and possibly simpler workflow for you) is there is a "Master Key Shift" in the settings that pop-up when you click the "System" button in TTS-1 itself. For tracks that this will muck up (like drums), you can offset them back (by track) by clicking the box at the top of each TTS-1 channel and adjusting the "Coarse tuning" (lower left) there.

^^ A-ha! Yep, exactly what I'm seeing. Cheers for testing it, guys! Looks like a bug. 

Right, external synths and multiple other softsynths work fine. It's odd; doesn't seem like it would be a per-synth function. But it's also that way for me in X2 - i.e. key+ doesn't work for TTS-1 play-thru. Version info says DXi version 1.00, file version 1.0.2.0, if that means anything.

Wow, that's interesting that this is happening in X2, as well.  I guess the good news is that this behavior does not appear to be introduced from the latest maintenance drop.
 
Bob Bone