This is really bad! I am beginning to reconsider my options!

ORIGINAL: ronniebuss2

I also had this problem. I would tweak a sound, save it in a user slot and set up the track to choose that sound. When I would open the file and press play the sound would revert back to the original sound. I called CW and they told me to eliminate the track patch choice. Huh??? They told me to choose none as the patch. Sure enough that worked. I still don't understand that. Any one else out there have a guess as to why this is?
Ron

It's hard for me to setup a track with that patch. For some odd reason the TTS-1 uses numbers for patches, instead of words.

Setting the channel to none means "don't override the event channel numbers defined in the midi events".
I noticed after pasting in a riff from the Studio Instruments drum kit that the last note sounded like a piano instead of the symbol crash I expected.
Upon investigation I found that if I selected channel 10 for the track instead of none, it fixed the problem.
Sure enough, in the midi events for the track there was the last note and a few others randomly using channel 1 instead of 10.
Fixing the midi events to use channel 10 and resetting the track to prefer "none" kept the fix.

I suspect that when you open your project the TTS-1 gets loaded with factory presets then loads your preset to set up the patch/channel maps but doesn't load the sysx data needed to initialize any custom patch changes you made.

In the old days, what I did for every custom patch I made on my Korg M1 was to save the patch's sysx data and add it to my project and have the project automatically upload the sysx data to my M1 when the song loaded. This is likely what you have to do to overcome this for the TTS-1 - but I haven't tried it yet. I'm not even sure how I store sysx data for the TTS-1 patches.

Ok, upon further investigation this is just a sick bug.
Just try this:
edit channel 1 and turn on portamento and set the delay up high and listen to the preview of the sound - I hear and see the portamento is on.
do the same for channel 2 - I hear and see the portamento is now on for both channels
save you settings to a preset
Inspect the portamento switch on both channels - portamento is back off on both channels.

The simple act of saving your preset is loosing information and resetting the controls. This is just fundamentally screwed up.
Its the 80/20 rule again.

Put some deep chorus on to a part. Close the project (or even just TTS-1?) and then reopen. The chorus is still there but is "Static"....the Delay is the same but the Speed has set itself to absolute zero. Nudging the speed knob sets it going again.

Nick

ORIGINAL: Bob Damiano [Cakewalk]

So what you have to do is immediately after you open the project... as in, BEFORE YOU HIT PLAY you need to switch your patch selection to "none".

I was about to reply with this but I see you figured it out. It's a known issue with TTS-1 (in fact I think I logged it myself).

I have found that the trouble with this idea is that you then do not get the correct Piano Roll Drum Names. You can assign then, but then every time you close and reopen the PRV you have to do it again (another bug).

The way I worked out (with help) was to save a Bank in TTS-1, and then, again before you hit play, Load that bank (I am pretty sure you need to do one for Drums and one for Normal), and then you will be actually able to choose the correct Names instead of Standard Piano or Standard Set. The upshot is that you then get correct drum names in PRV.

Nick

Guys, just save the edited patch to a User bank.

left click on the name of the patch in it's editing window (the one you clcked the square above the track of TTs-1)

choose save bank. I use one of the user banks

Pick which slot you wish edited patch to be in (after saving, the name should show up in the slot of the user bank you picked)

Now you can specify which bank (again a user bank that you chose) and the patch number in the Midi track's settings. It will now "stick"

You can build you a couple of default banks of some patches that you will use somewhat regularly.

Hmn, this now, after I shot my mouth off, is not working for me now in ver7
*I have used it before in ver 6

somewhere I believe there is a setting that will disalow the resetting of patches upon hitting Play

will have to dig for that

OK, got it going, it entails needing to LOAD the user bank when you startup the program/project again

ORIGINAL: Kevinlane

OK, got it going, it entails needing to LOAD the user bank when you startup the program/project again

i don't often say this but i jus sed all that....


Nick