Significant Bug

etnate · Post by **etnate** » Sat Jan 07, 2017 8:01 pm

This isn't related to the new firmware. I haven't updated yet. I was working on a song and got a new idea so I put the old song in a template and moved everything over to a new song slot. I got everything set up and recorded several measures on multiple tracks in the new song slot. After some time a weird glitch happened where the SW1 controller was changed on every program to toggle octave down and SW2 to lock ribbon. I figured this was something weird on this one song and I could just copy everything to a new song and it'd be fine. It turned out on EVERY song the SW controls were switched. I of course went through each song and reset the function of the SW controls. However now if I record control changes on any 1 track it applies it to all other tracks. Any ideas?

GregC · Post by **GregC** » Sat Jan 07, 2017 8:29 pm

etnate wrote:This isn't related to the new firmware. I haven't updated yet. I was working on a song and got a new idea so I put the old song in a template and moved everything over to a new song slot. I got everything set up and recorded several measures on multiple tracks in the new song slot. After some time a weird glitch happened where the SW1 controller was changed on every program to toggle octave down and SW2 to lock ribbon. I figured this was something weird on this one song and I could just copy everything to a new song and it'd be fine. It turned out on EVERY song the SW controls were switched. I of course went through each song and reset the function of the SW controls. However now if I record control changes on any 1 track it applies it to all other tracks. Any ideas?

Anything else, USB or laptop or other midi instrument plugged into your Kronos ?

etnate · Post by **etnate** » Sat Jan 07, 2017 8:55 pm

Nothing plugged in. I checked with a new initialized song and the behavior carries over. My next test I guess will be to load an entirely different song file and see if the behavior happens there.

etnate · Post by **etnate** » Sat Jan 07, 2017 9:10 pm

Tried it with a new song file and the behavior does happen there as well. If there's some setting where toggling a control will toggle the same control for all tracks (I'm not aware of this function) then I can go into each song and turn it off. But it's looking like I'll need an entire OS reinstall to fix after backing up my files but I'm afraid the bug will still be there when I put the files back in.

GregC · Post by **GregC** » Sat Jan 07, 2017 9:18 pm

my guess is that you made some type of global change

I would also look at the midi checkboxes

etnate · Post by **etnate** » Sat Jan 07, 2017 9:31 pm

I'm certain I didn't make any global changes and it's clearly a bug. I can uncheck the box for controls on each sound but that is only a temporary solution and not a good one if I'm recording control changes on multiple tracks. The only "weird" thing I did was the last song I was working on I was messing with assigning an insert wet/dry value to a control but moved away from that idea.

chris · Post by **chris** » Sat Jan 07, 2017 10:07 pm

I also think that this is linked to controllers assign in global mode. Maybe you did load a pcg file that was previously saved with global mode parameters as well, which could explain why you have these assigned to all your programs.

GregC · Post by **GregC** » Sat Jan 07, 2017 11:39 pm

etnate wrote:I'm certain I didn't make any global changes and it's clearly a bug. I can uncheck the box for controls on each sound but that is only a temporary solution and not a good one if I'm recording control changes on multiple tracks. The only "weird" thing I did was the last song I was working on I was messing with assigning an insert wet/dry value to a control but moved away from that idea.

Karma sends midi changes over to SW 1 and 2.

try going over to global/controllers and see what Karma is doing to SW1. 2

Another step is your foot switch and how it is assigned in global/controllers

etnate · Post by **etnate** » Sun Jan 08, 2017 12:25 am

Thanks but I don't use karma at all. I'm sure everyone wants me to go through the common steps of things that novices might overlook but I've had the kronos a couple years now. This is a system wide bug, apparently, that happened randomly while I was doing very common shallow tasks in sequencer mode with kronos unattached to any other gear or inputs. I appreciate any thoughts anyone has on this. I'll explore further but I didn't want to do too much without seeing if anyone has experienced any similar bugs as mine. So far my conclusions are that the entire board needs to be initialized and my fear is the bug is within the song files themselves rather than the system which means all my songs are useless and a loss. Here's to hope.

Mike Conway · Post by **Mike Conway** » Sun Jan 08, 2017 1:27 am

Early on, did you copy a program to the sequencer by using ENTER + REC/WRITE? The Sequencer will import the control settings of that program as well. Copying to other Songs is going to copy the controller setting, too.

Have you gone in Sequencer mode to EQ/VECTOR CONTROL - - CONTROLLERS and checked your SW1 setting? SW1 globally affects all 16 MIDI tracks. Simply set SW1 from Octave up or down back to the CC#88 setting.

I apologize in advance, if the error is something else and this is what you already covered

19naia · Post by **19naia** » Sun Jan 08, 2017 4:59 am

Template option may be where the hang up is.
I would suggest setting the program line up in Combi and then get the combi to song and see if it still happens. As a work around rather than a fix to the glitch. It may be how Templating function works. Try without making a template.
Combi and song Controllers set up is universal over all midi channels/tracks/timbers but the slotted programs are still supposed to retain their own controllers assignment that then all get contorlled together by the song or combi combi controllers as long as the controllers are set to their dedicated #CC. (#CC 80 & 81 for SW 1&2).
Try any options that do not involve making a template and see if any difference.
I am just saying this out of curiosity and a guess work elimination process. Not saying i know for sure. I would like to learn from it either way.

SeedyLee · Post by **SeedyLee** » Mon Jan 09, 2017 1:07 am

I'm not sure I'm understanding your issue completely, but it sounds like Mike might be on to something.

The controller assignments in sequencer mode are per song, not per program. If you use the "Copy From Program" menu option, then the controller assignments for the entire song will be overwritten with the settings from that one program.

If you then copy that song, either using template songs or otherwise, the new sequences will have the same controller settings for all 16 tracks.

There's no way in sequencer mode you can have different controller settings for each individual track/program (which makes sense given you can record multiple tracks simultaneously).

etnate · Post by **etnate** » Mon Jan 09, 2017 4:36 am

I think everyone is missing the actual problem. The bug messed up the control assignments on every song which I was able to correct. That's not the problem. I'll explain using an example. Let's say on track one I have a synth sound that is just a running saw sound but when you engage the SW1 control it turns it into a filtered stab which is the sound I really want. When I record the midi data I engage the SW1 to get the correct sound. However in addition to recording the controller changes on track 1 it records it on ALL channels. Obviously each channel is its own midi channel. I haven't imported anything in from another sound and this behavior happens on all songs now even when loading a different song file.

etnate · Post by **etnate** » Mon Jan 09, 2017 4:45 am

I'd also like to say that I used and was very familiar with the Alesis Fusion which was extremely buggy. A common bug would be random changes to settings that were far away from anything related to what you were doing, so this could be the case with this bug on my kronos where the bug affected a setting I'm not aware of.

SeedyLee · Post by **SeedyLee** » Mon Jan 09, 2017 5:59 am

etnate wrote:I think everyone is missing the actual problem. The bug messed up the control assignments on every song which I was able to correct. That's not the problem. I'll explain using an example. Let's say on track one I have a synth sound that is just a running saw sound but when you engage the SW1 control it turns it into a filtered stab which is the sound I really want. When I record the midi data I engage the SW1 to get the correct sound. However in addition to recording the controller changes on track 1 it records it on ALL channels. Obviously each channel is its own midi channel. I haven't imported anything in from another sound and this behavior happens on all songs now even when loading a different song file.

Well that is very weird. Any chance you can share the SNG file with us to see if others can reproduce the problem? Or are you able to document the steps to reproduce in detail so others can experiment?

When you say it records it on all channels, is the sequencer actually recording the continuous controller message for SW1 on all tracks (ie visible in the event list), or is it recording on one track and then affecting all channels?

Korg Forums

Significant Bug

Significant Bug

Re: Significant Bug