2nd timbre in Combi mode is unsavable

[hightower]

Hi guys,

I have a weird problem in Combi mode. If I assign a program to timbre 2. And then save the combination it is not stored, but returns back to the original one. When I change any of the other timbres it is saved.

One other thing that probably has to do with this. In every init Combi the 2nd timbre is automatically assigned to the same bank/program number. For example. Combi U-E001 is an init combi. the 2nd timbre is automatically programmed to Program U-E001.

How is this possible?

[LZ]

I've never encountered this. Are you changing the program NUMBER assigned to track 2 of the combi, and it reverts back to a different program NUMBER, or are you editing the PROGRAM assigned to track 2 of the combi?

The programs in the combi just point to a location. If you want to change that sound, you edit that program (in program mode). That program has to be saved (in program mode) in order to be retained.

[SanderXpander]

Never heard of it either. Do you have any midi or USB gear hooked up?

[StephenKay]

Hi guys,

I have a weird problem in Combi mode. If I assign a program to timbre 2. And then save the combination it is not stored, but returns back to the original one. When I change any of the other timbres it is saved.

One other thing that probably has to do with this. In every init Combi the 2nd timbre is automatically assigned to the same bank/program number. For example. Combi U-E001 is an init combi. the 2nd timbre is automatically programmed to Program U-E001.

How is this possible?

Sounds to me like some other piece of gear is sending a program change or bank change message to the MIDI Channel of timbre 2. Try disconnecting all other gear...

[hightower]

Wow, thanks. That was it. Removed the usb cable.

I'm using Logic Pro to make a recording. How do I find out what is sent? Because the program changes are NOT in the midi event list of my logic pro project.

[SanderXpander]

Perhaps you have a midi loop - i.e. having midi thru enabled in Logic AND having local control set to "on" in the Kronos global menu.

[hightower]

Ok thanks I'll check that local control is probably at the default setting don't know whether that is off or on

[ed_f]

Wow, thanks. That was it. Removed the usb cable.

I'm using Logic Pro to make a recording. How do I find out what is sent? Because the program changes are NOT in the midi event list of my logic pro project.

If you have an external midi track check to see if you have the Program checked in the Inspector. If so, that will be sending a Program change message to that midi channel.

[hightower]

As far as I can see the midi tru is disabled in logic. Local control is enabled. But when I disable it I don't get sound when I press the keys. Then I cannot record anything!

Where do I find the inspector?

[SanderXpander]

The inspector is the bit on the left that changes depending on which track you have selected. It shows the track volume fader, the fader of the bus associated with the track, and midi track will have a couple of thing on the top like channel number, program, bank, etc.

[ed_f]

The inspector is the bit on the left that changes depending on which track you have selected. It shows the track volume fader, the fader of the bus associated with the track, and midi track will have a couple of thing on the top like channel number, program, bank, etc.

Exactly. Be aware that you can twirl up sections in the inspector so you might only see the heading with an expansion arrow.
I have had people tell me over and over it wasn't there because it was twirled up.

[hightower]

Ah, I see. Yes program is checked. So I unchecked it. So now everything should work fine?

We'll see.

[ed_f]

Ah, I see. Yes program is checked. So I unchecked it. So now everything should work fine?

We'll see.

No guarantees - but that sends a program change so it often a gotcha for people. You also have the option of setting that to the correct program change so Logic is taking care of it for you. That is my preferred method.