General
Roland GR-55 Patch Controller
Started by Heartmood on .
Sign in or create an account to join the conversation.
Screenshot 2014-05-02 17.51.34.jpg
Hello, I'm a newbie and free of knowledge;-)
What I want: A grid of 36 buttons (I tried switches) with each button representing a Gr-55 patch of my choice
Where I am: I managed to create the grid of 36 switches, but how can make each switch send an individual Sysex message? And why is the syses message text red?
Hello, I'm a newbie and free of knowledge;-)
What I want: A grid of 36 buttons (I tried switches) with each button representing a Gr-55 patch of my choice
Where I am: I managed to create the grid of 36 switches, but how can make each switch send an individual Sysex message? And why is the syses message text red?
I think the sysex message is red because you don't need the 0xF0 and 0xF7 (but I can't find that info in the manual).
I tend to use scripts for my sysex and inside a script I simply use a variable for any byte(s) that change. One of the other contributors that use this method of sending sysex can chime in for exactly how to phrase it.
I tend to use scripts for my sysex and inside a script I simply use a variable for any byte(s) that change. One of the other contributors that use this method of sending sysex can chime in for exactly how to phrase it.
Yep
Basically if a statement won't compile it will go red, as in this case . .
The key here, part from it being the basic mapping, is the 'data' bit . .
The field expects just the data, (no f0/f7) and really only static statements . .
For variable stuff try custom midi and for greater control use scripts
I have done some GR 55 stuff a long time ago that I may have posted ...
I'll dig it up - there is some custom midi sysex stuff in it to look at . . .
Should try to get back to that project as well
Basically if a statement won't compile it will go red, as in this case . .
The key here, part from it being the basic mapping, is the 'data' bit . .
The field expects just the data, (no f0/f7) and really only static statements . .
For variable stuff try custom midi and for greater control use scripts
I have done some GR 55 stuff a long time ago that I may have posted ...
I'll dig it up - there is some custom midi sysex stuff in it to look at . . .
Should try to get back to that project as well
Thank you for caring Macciza and oldgearguy!
Oldgearguy's suggestion didn't work.
I really want to learn Lemur but with the manual alone it seems very hard. Sysex data formats are not explained, with the "standard" midi messages I have no success, as far as I saw on the GR-55 (vguitarforums) user forum I'd have to send three messages, a quote from gumtown:
And for the sysex/script solution: is it correct that in the "trigger" field: x[0..35] x should represent the sysex info for the GR-55 patch?
I tried Maccizas suggestion from the GR-55 forum, though I don't understand every term in it:
Sorry maybe I'm sounding as a dumbass, but I know almost nothing but have the desire to learn.
I'm still reading the Lemur manual, but there's not enough information about sysex data formats.
Are there any good sources for learning about sysex data formats, 7-bit, 14-bit and hexadecimal versus decimal...
Oldgearguy's suggestion didn't work.
I really want to learn Lemur but with the manual alone it seems very hard. Sysex data formats are not explained, with the "standard" midi messages I have no success, as far as I saw on the GR-55 (vguitarforums) user forum I'd have to send three messages, a quote from gumtown:
But how do I accomplish that a button/switch will send three message (+ with 20ms separation) with Lemur?Patch change to GR-55 U01:1
B0 00 00
B0 20 00
C0 00
are sent as 3 separate messages (typically with 20ms separation between messages).
And for the sysex/script solution: is it correct that in the "trigger" field: x[0..35] x should represent the sysex info for the GR-55 patch?
I tried Maccizas suggestion from the GR-55 forum, though I don't understand every term in it:
What means "array" and what is the script in this case?Hi
Try using a Custom MIDI - call it msg perhaps . .
System exclusive triggering on x
And as an array as well
{0x0b0,0,0,0x0b0,0x20,0,0x0c0,floor(x*127)}
And you can use decimal rather than hex
{176,0,0,176,32,0,192,floor(x*127)}
Dont send anything from the x value - the script will handle it
Cheers
MM
Sorry maybe I'm sounding as a dumbass, but I know almost nothing but have the desire to learn.
I'm still reading the Lemur manual, but there's not enough information about sysex data formats.
Are there any good sources for learning about sysex data formats, 7-bit, 14-bit and hexadecimal versus decimal...
I'm confused. I created a custom Midi Message, called it "patch change" which data is: {0x0b0,0,0,0x0b0,0x20,0,0x0c0,floor(x*127)} and saved the project:
Screenshot 2014-05-03 14.45.27.jpg
As soon as I click anywhere in the the main window buttons (here its the "0" switch) it changes to:
Screenshot 2014-05-03 14.45.44.jpg
Screenshot 2014-05-03 14.45.27.jpg
As soon as I click anywhere in the the main window buttons (here its the "0" switch) it changes to:
Screenshot 2014-05-03 14.45.44.jpg
Hi
Yeah, theres a few things askew here . .
If you are just send Program change and Bank change stuff on Lemur to the GR you don't need to use sysex
If you are on the correct Bank already then standard Program Change messages should work , Bank change is needed to change banks only
Heres something I did up a very long time ago as a first draft - using lots of bad techniques for further development/interactivity but it did the job
Most of the stuff is simply hard coded - edit text objects to update names to suit your patches . . .
Will have a look for what else I did . . .
^^GR55_Patches.jzml
Yeah, theres a few things askew here . .
If you are just send Program change and Bank change stuff on Lemur to the GR you don't need to use sysex
If you are on the correct Bank already then standard Program Change messages should work , Bank change is needed to change banks only
Heres something I did up a very long time ago as a first draft - using lots of bad techniques for further development/interactivity but it did the job
Most of the stuff is simply hard coded - edit text objects to update names to suit your patches . . .
Will have a look for what else I did . . .
^^GR55_Patches.jzml
Wow, thank you so much Macciza!
That is more than I expected, it looks so great, if it would only work…
Maybe the MIDI settings are different from mine, the GR-55 doesn't receive anything…
The "Object Target" is set to Parent (Midi 5), could that be the problem?
BTW I rectified the numbers-text of the patches in User Patches "61-100?" tab from 61-90 instead of 31-60 and changed the title of the tab to "61-90" too.
GR55_PatchesMaccizaNumbersRectified.jzml.zip
Hope I didn't mess up anything else.
Can I delete the whole "PRESET PATCHS" folder in the Project without harming anything else? I don't use the presets and I'm in Bass-Mode not Guitar-Mode of the GR55.
That is more than I expected, it looks so great, if it would only work…
Maybe the MIDI settings are different from mine, the GR-55 doesn't receive anything…
The "Object Target" is set to Parent (Midi 5), could that be the problem?
BTW I rectified the numbers-text of the patches in User Patches "61-100?" tab from 61-90 instead of 31-60 and changed the title of the tab to "61-90" too.
GR55_PatchesMaccizaNumbersRectified.jzml.zip
Hope I didn't mess up anything else.
Can I delete the whole "PRESET PATCHS" folder in the Project without harming anything else? I don't use the presets and I'm in Bass-Mode not Guitar-Mode of the GR55.
Yeah sorry about that . .
I could have given you a bit more info though I hope you had fun poking about . . .
It looks like I have used a bit of a mix of parented mapping and some scripting as well . .
So, go to the top level of the Project tab and click on Project and select your Lemur MIDI Target
I was regularly using MIDI Target 5 (for 55) and MIDI target 6 for (for the 99) rather then just using 0
And also set MIDI_Out variable to the same Target - i.e. 5 or just 0 if using that . . .
You should be good to go, and yes you can just delete the whole presets patches if you want . . .
I don't really use them that much but it is a far better way to go through them then via the box.
They can also be surprising at times when you find hidden gems of ideas within them . .
You could just delete the names if you don't want to edit them ;~}
Cheers
I could have given you a bit more info though I hope you had fun poking about . . .
It looks like I have used a bit of a mix of parented mapping and some scripting as well . .
So, go to the top level of the Project tab and click on Project and select your Lemur MIDI Target
I was regularly using MIDI Target 5 (for 55) and MIDI target 6 for (for the 99) rather then just using 0
And also set MIDI_Out variable to the same Target - i.e. 5 or just 0 if using that . . .
You should be good to go, and yes you can just delete the whole presets patches if you want . . .
I don't really use them that much but it is a far better way to go through them then via the box.
They can also be surprising at times when you find hidden gems of ideas within them . .
You could just delete the names if you don't want to edit them ;~}
Cheers
Hey Macciza,
thank you so much, it works!!! I cleaned the text numbers a bit up and deleted the Factory Patches part. If I could get the patch names from the GR55 automatically I would be more than happy. But for now I#m very happy about my lightning fast switching of GR-55 patches, thanks again!
thank you so much, it works!!! I cleaned the text numbers a bit up and deleted the Factory Patches part. If I could get the patch names from the GR55 automatically I would be more than happy. But for now I#m very happy about my lightning fast switching of GR-55 patches, thanks again!
Cheeers
Getting patch names is certainly possible - just need to decide an appropriate way to do it . .
Will try to remember to look into it further at some point . . .
MM
Getting patch names is certainly possible - just need to decide an appropriate way to do it . .
Will try to remember to look into it further at some point . . .
MM
Dear Macciza, sorry to bother you, but I'm still free of knowledge (almost), and revived a project for the Roland-GR55. I need the GR-55 patch names reflected in the Lemur controller. My plan is to use an iPhone 6 as the Lemur controller and a Quicco mi.1 bluetooth Midi-Interface.
For this purpose I'd had to adapt your iPad Controller Version to the iPhone size, hope this will not be too hard…
Thank you for any help!
heartmood
For this purpose I'd had to adapt your iPad Controller Version to the iPhone size, hope this will not be too hard…
Thank you for any help!
heartmood