Korg Forums

miden

I have an M50, but I daresay it is the same with the M3...

The sysex string I send is F0 42 30 00 01 05 4E 00 F7 which is a mode change for combi mode (same happens if it is for prog mode too which is 02 (second last byte)

Now, it changes the mode fine, BUT all audio from the L/R jacks is cancelled, and the only way to get it back is to re-boot. Even changing modes using the buttons makes no difference ONLY a reboot fixes it.

I have checked all mixer levels and whatever audio out controls I can find and they all have data in them...and I have tried moving them as well...nothing.

Has anyone else had the experience?

SanderXpander · Platinum Member Joined: 29 Jul 2011 Posts: 7860

Are you sure it isn't something like local control being switched off?

miden · Posted: Thu Sep 18, 2014 6:45 pm Post subject:

Thanks for replying Sander...I am sure that was one I checked, but it cannot hurt to check again....although why a mode change sysex string would also do this is hard to figure..might be a glitch in the OS.

I also wrote to Korg Support about it, but nothing from them as yet.

SanderXpander · Platinum Member Joined: 29 Jul 2011 Posts: 7860

I'm not an expert of SysEx, I know just enough to know what it is and to copy/paste strings I need. Perhaps you need a "closing" string or byte?

miden · Posted: Thu Sep 18, 2014 10:23 pm Post subject:

the F7 does that...

Interesting that when I turned it on this morning, the sysex strings all worked fine and audio was not cancelled....

The only thing I can think of was that the M50 was on for about 6 hours yesterday before I tried it. So I am going to leave it again today for a similar time and see if it does it again.

May (ONLY may) be linked to the capacitor issue...

miden · Posted: Fri Sep 19, 2014 3:10 am Post subject:

Seems like it was Sonar itself causing this...for some reason at boot it sends a Local Off message to any connected keyboard!

So this may be solved...I will check a couple of more times to be sure.

Thanks Sander for the suggestion re local on/off...I had no idea Sonar sent this. I must say I have never noticed it happening with any other synth I have had connected. Must just be something in the M3/M50 OS programming.

SanderXpander · Platinum Member Joined: 29 Jul 2011 Posts: 7860

Oh! Yes, I could have told you right away that Sonar does this haha. I didn't know that was what you were sending your string from. I think you can change that behavior in the aud.ini file if you want. Generally speaking it's a good idea to have local off when using a DAW based sequencer, that's why it does it.

Bald Eagle · Posted: Fri Sep 19, 2014 10:57 am Post subject:

SanderXpander · Platinum Member Joined: 29 Jul 2011 Posts: 7860

Yes, that! Thanks!

miden · Posted: Fri Sep 19, 2014 4:08 pm Post subject:

Thx BE and Sander - done! I prefer to set these sorts of things (work/data flow) myself when and as required.

Interesting that I have been using Sonar for years with many keyboards, and this M50 is the first that recognised and actually reacted to the command. Which is one of the reasons I have never noticed it before.

One never stops learning just what makes Sonar tick [ Wink

]

miden · Posted: Fri Sep 19, 2014 8:27 pm Post subject:

sorry, that does not work. I tried both 0 and 1 using the SendLocalOff= I even used cut and pasted it to be sure of the syntax.

miden · Posted: Sat Sep 20, 2014 5:34 pm Post subject:

Bald Eagle you neglected to also write that the text -Options- is also needed [ Wink

]

So the correct text to stop the local off message is:

[Options]

Sendlocaloff=0

Bald Eagle · Posted: Sun Sep 21, 2014 1:01 am Post subject:

miden · Posted: Sun Sep 21, 2014 3:40 am Post subject:

LOL, all good - I was only teasing. I really appreciated your post as it got me started in the right direction [ Smile

]