Korg Forums

Exactly. My conclusion (FWIW) is that this is a bug and not a feature.
To avoid this issue, I just touch the song time and use the data entry slider or wheel.

There's a nuisance related to program changes and the Locate button. When I press the Locate button to go to the song start point, this sends some reset messages and every external unit gets a program reset (and probably some other parameter resets as I've found elsewhere searching this forum). I ...

That will work similarly to the workaround I mentioned. I was pressing Rec and just scrolling (any) programs for a second on the miniNova, then returning and editing the program change event with the actual program I wanted. It's a little cumbersome, but it's doable. :D Btw I had not realized those ...

For now I've settled with this workaround: I record the program change in real time from my external hardware (miniNova on this case). Of course that's not practical in most cases. But then I go to Event edit, change the event time to the measure/beat I want and there I can insert bank number and ...

Unfortunately, it didn't worked that way. I went to Event Edit and unticked everything but Program Change . But on the editing menu the Insert button is greyed, so it clearly works just for editing available events. I guess I can edit the MIDI file with an external editor and insert the program ...

Thanks Bald Eagle. I'll try it as soon as I'm in front of the unit. Looking at the PG it seems pretty straight forward right now (no MSB/LSB stuff), which of course makes life a little easier.

Cheers!

I've set up MIDI channel 1 to EXT2 on sequencer mode to send program change to my miniNova.
I insert MSB:000 LSB:032. But then what?

And, is it possible to insert a program change somewhere inside a song in the internal sequencer?

Thanks a lot!

Hey, Pincho Paxton, I apologize too. I think michelkeijzers didn't meant it that way, though. There's a feeling of panicking when this things happen. Obviously the people with faulty units have some right to. But also people who have ok keyboards may fear they will have some problem eventually ...

I feel sorry for people with this problem. I would never respond with "I'm all-right Jack, so it's not a problem." Who answered in that way? :?: The reason I'm bothering to comment this thread is to be helpful to this people, otherwise I wouldn't care. I'm saying there is a way to know where the ...

I've seen problems like this in many keyboards, and I'm not much into forums... but I do recall Alesis having problems with Fusion and Andromeda, Roland having problems with the XP keyboards, and more recently and notably, the Juno G's, etc. People panic and is understandable to some degree. I would ...

Then it must be from an early batch...? I'm not sure we know precisely how early is early enough... That does not have to mean that every early unit will have problems though, I guess some units have manufacturing issues due to poor quality control or something like that, that apparently was taken ...

Total cases are 20-something. People that don't have issues probably won't bother to vote, but people with issues probably will want to be heard. As discussed in an earlier thread, the problem would be isolated to an early batch. People should post their serial numbers (in that thread) to get a clue ...

You should post serial numbers. There is a thread for that, where this issue was discussed before. In short, the freezing has occurred in all models, not only 61 keys, which is the most sold unit and maybe that's what confuses people. There is a case or two reported on the 88, and maybe a little ...

Do you guys gig or have travelled with it? How about the casing?

Mhh I don't see any 'latch' function for th normal chord triggers, as opposed to the Arpeggiators.
The best solution I can think of, is get an assignable switch pedal, and set it to sustain.