To ethnix73 and all NMG2 owners / or sysex users.

[moody33]

Hi !

Ethnix, I already see you at electro-music so I guess you are still a g2 owner !

I have some problem using sysex. I'm building an interface for the G2 and I like to store and send sysex directly in usine to restore patches without using the g2 editor.

I can send sysex request, it works. My problem is when i want to send the sysex store in usine to the G2, my g2 doesn't apply any changes. So could you please take a look in this patch and see if it works for you and if I'm made some mistakes? I'm quiet new in sysex and I'm not sure to do the right way.

First, plug your usine midi out to the g2 in, and your g2's midi out into usine's midi input. On your g2 settings , makes sure if sysex is set to "ALL"before clicking on a sysex request switch (performance/or slot). Then load another patch in your g2 before clicking to the "send" switch to see if changes are apply or not.

I'd really like to build such a sysex editor and why not post a link to the G2 community . Perhaps some future usine users are on this forum !

Thanks in advance for those who can help me.

Here is the patch: http://www.sensomusic.com/forums/upload ... 2sysex.pat

[ethnix73]

Hi moody33,

yes, i'm still a g2 owner. I will keep it forever (unless a g3 )...

I will try to test your patch today.

Why do you want to store and send sysex?
To load external patches?

One year ago i believe, I made a patch whith program changes to load patches from the G2 memory. I had a few difficulties with cc32 and cc0, but succeeded tomake a working patch



I will try to test your patch today moody.

[moody33]

Hi Ethnix and long life for your beloved G2 !

I've also made a patch (post yesterday in addon section ) to recall G2 patches and other stuffs via CC and PC using your own patch list, and it works fine. However, I'd like to store and recall patches directly in usine without having to save pch2 and prf2 files. If I understand correctly, it's possible to store/load patches via sysex. This avoid the need to store it in the synth internal patch memory. That's why I think sysex are very useful if we want to store preset directly in a project workspace. Then, if you have made a song in usine using G2 sounds, it's possible to store the patches used in this song directly within the workspace and all change made in the G2 editor can be saved in your workspace once you send a sysex request. A lot of time saved and no more pch2 files to save in your computer! I guess if I'm clear but I'm sure you will understand ! Thanks a lot to take a look.

Moody;

[ethnix73]

Ok, good idea to store data in a workspace...

I had a quick look. Apparently sysex received from the g2 with a dump one seems perhaps to have only patch data...Don't know if it have block id msb and block id lsb....

At first, i believe you should have perhaps to concatenate with another array F0, 33, 7F , 0A, 20...

I will a further look....

[ethnix73]

so,

As indicated in the manual, sysex dumps are splitted in different blocks. Each blocks have the same structure (F0, 33, 7F , 0A, 20...F7).

Have a look at the outlet receive from the midi in module, and you will clearly see this blocks.
I tried to stock this different blocks in different arrays. It seems to be ok...

But, for the moment, sending back this blocks ( by concacanating arrays) to the G2 gives "patch dump falied"...

I will try with an ultrasimple G2 patch

[moody33]

Thanks for your help.

I've also try to concatenate array , but with strange results when sending the result back to the g2 ( note was sent !), but I've had also a success loading a sysex even if it doesn't the result expected (loading a patch in a active slot). My concatenate patching wasn't really good and that's why it works and don't works ! So it seems to be possible but I need to go more deeply in the undertsanding of G2 sysex and I'm not sure on how to proceed to concatenate. Let me know if you are more lucky !