The MIDI Forum

  1. Lee T.
  2. Getting Started with MIDI
  3. Friday, 02 February 2018
  4.  Subscribe via email
Greetings Humans,
Ok, so I had this desire to get back into MIDI after 35+ years starting with Roland Juno-60 to Juno-106 migration.
These were pre General Midi and I helped write an editor librarian for a mainframe computer connected by serial to midi
box I had designed and built.

Later in the 1980's I met a Kurzweil employee who help me get a piano module upgraded to the top of the line
KX-1000 Pro just before the Waltham warehouse was closed after sale of the company.

I found another editor librarian for DOS (Kurle) and a Librarian for Windows (Kurlwin) which was able to get it cryptically
working with Rosegarden on Ubuntu 10 years ago and more in 2017.

This year 2018 I got email from Roland and bought first General MIDI device , the Go:Keys 61.
It also has GM2 so I joined Midi Association here.

I flashed the January 2018 FIRMWARE Ver1.21 to use it with Scratch programming language but the Tech support could not provide the
MIDI Implementation documents for the Go:Keys like that I had used on the Roland JUNO-106 years earlier.
open Source to the Scratch Extensions could help determine some parts of the Midi implementation.

After asking the Kurle developer what it took to develop on system exclusive message dumps I decided to ask here for help.

Anyone here know where to turn next ?
  Groton, MA 01450, USA
Visit 
Comment
There are no comments made yet.
Accepted Answer
Accepted Answer Pending Moderation
0
Votes
Undo
ScratchX is an MIT Life Long Kindergarten (LLK) project to make programming tools to teach concepts to young students.
It is considered LEGO like programming and has an interest in LEGO hardware as well.

The underlying part is BLOCKLY from Google and ScratchX is an experimental version already in maintenance mode
while Scratch version 3 is developed to eliminate the Adobe Flash requirement.

It uses WebMIDI and will be easy to use.
Not all functionality will be available in Scratch 3.0 so regular MIDI tools will still work on the NPRN written
into the firmware.

Since I am not a programmer it was difficult to uncover the actual MIDI code in the ScratchX extension.
As a non-programmer I find the charts alow insight into what the device can do.
I now can use it more intuitively as documented in manuals and videos.

I like editing and changing things that I dslike when I hear the playback.
The builtin function requires a level of accuracy I don't achive in real time.

Alternatively the Go:Keys is able to be used in live situation but no where like a workstation.

I hope performers share their compositions by way of uploading the GO-61 backups to a sharing space.
No filenames are editable so all will be SONG01.MID etc
I tried putting filenames in the RESTORE GO-61 and although it worked it was prone to crashing the synth.
I also tried using Rosegarden to make a recording using the Go:Keys feature and it reassigned the sounds when played back.

I don't see the GM2 requisites as a valid argument for not having the MIDI Implementation Chart V2.0.
I also don't see the YouTube videos as a replacement for written instructions for how to create a live and layered sequence.

Eventually I see this product influencing young and old as well as home and professional musicians.
Again, it replaced a 20 year old Yamaha PSR-160 which had General Midi with batteries and speakers for portability.
I couldn't download songs to that one either to play along.
Maybe I will get that to work on the Go:Keys.
For now it will pair as speakers to stream music from the recorded songs on a phone or other Bluetooth device.

And now a word from the manufacturer.
https://www.roland.com/us/products/gokeys_go-61k/
"GO:KEYS is a fun, easy-to-use keyboard that lets you play along with your favorite music—streamed wirelessly through its powerful onboard speakers. Just connect your smartphone via Bluetooth®, pick a song, and play along!"

It is also shown in the ads using the preset patterns and sequences.
This is where the sharing of GO-61 BACKUP could begin.

(Hope this sheds some light on my reason for wasting my time getting the chart.)

I still really like this keyboard at 66 years old.
The kids can use the Yamaha for now and it's built in library of tunes.

Lee
Comment
There are no comments made yet.
Accepted Answer Pending Moderation
0
Votes
Undo
I may be wrong where but there is no midi sent to the unit only audio, but it do send midi out over bluetooth.
Would not the best be to just monitor the package received at computer by pushing buttons and twisting knobs?

Because i guess the bluetooth show up as a midiinterface?
Comment
There are no comments made yet.
  1. more than a month ago
  2. Getting Started with MIDI
  3. # 1
Accepted Answer Pending Moderation
0
Votes
Undo
Thanks for posting all that, Lee T. It's just Greek to me, alas.

Last night I posted two wrongful replies, having forgotten I'd already unburdened myself here (though I did peruse much of the page before doing so). The first wouldn't show up as posted so I tried a second, which vanished too. Today they both showed. I deleted the 1st and the 2nd seems to have gone with it. If either shows up again, everybody please ignore.
Comment
There are no comments made yet.
  1. more than a month ago
  2. Getting Started with MIDI
  3. # 2
Accepted Answer Pending Moderation
0
Votes
Undo
I posted here but doesn't seem to have taken. Is it possible to MIDI sequence on the Go Keys via computer over hardware interface? Habitual Cakewalk Sonar 7 guy here. If somebody's actually done it, please describe exactly how. I've combed 3 pages on the subject here but it still seems to hang in midair. Thank you!
Comment
There are no comments made yet.
  1. more than a month ago
  2. Getting Started with MIDI
  3. # 3
Accepted Answer Pending Moderation
0
Votes
Undo
Search for a blog post "Roland GO:KEYS is GONE:KEYS" to find some missing pieces of information

"The GO:KEYS tones follow the Roland JUNO-DS patch map. This is further proof that the GO:KEYS is directly derived from the JUNO-DS. I recommend downloading the JUNO-DS Parameter Guide which contains the JUNO-DS patch list. Finding the bank select and program change for a GO:KEYS tone is simply a matter of scanning the JUNO-DS patch list for the equivalent voice."

Ch# Part Allocation
--- --------- ----------
1 PIANO User/Panel
2 ORGAN User/Panel
3 STRINGS User/Panel
4 BRASS User/Panel
5 BASS User/Panel
6 SYNTH User/Panel
7 FX/GUITAR User/Panel
8 Bass Loop Mix
9 Part A Loop Mix
10 DRUM User/Panel
11 Part B Loop Mix
12 Part X Loop Mix
13 Part X Loop Mix
14 Part X Loop Mix
15 Part X Loop Mix
16 Drum Loop Mix
References
  1. https://sandsoftwaresound.net/roland-gokeys-is-gonekeys/
Comment
There are no comments made yet.
  1. more than a month ago
  2. Getting Started with MIDI
  3. # 4
Accepted Answer Pending Moderation
0
Votes
Undo
It's ironic really because there's a discussion here about what MIDI features Go:Piano does or doesn't implement. Answering that question is actually the purpose of the MIDI Implementation Chart that all MIDI-supporting devices are supposed to have. So if that chart existed for Go:Piano, then there would be no need for that discussion :)

The reason I'm looking for a MIDI Implementation Chart is that I'm wondering if there is a MIDI controller code transmitted by Go:Piano that I can use as a page-turner command in forScore on the iPad. I can teach forScore to turn pages with my Yamaha P-105 using the "+" and "-" buttons - and I found that out from the P-105's MIDI Implementation Chart, Does anyone here know if I could use one of the Go:Piano's buttons for that purpose? Thanks for any insights!


I have the GO:Keys and could tell you what it sends if you can tell me what you want to see.
I think you want to use a key or button assigned to be the page turner.
The Go:Piano may only be a MIDI I/O of key and program and not usable as an assignable CC controller as is true for the Go:Keys so there may be no assignable buttons to press.
I also have AKAI LPD8 and M-Audio Keystation 88 keyboard controller that have Midi USB with buttons and ports to be user assignable as controllers.

Hope this helps.
Comment
There are no comments made yet.
  1. more than a month ago
  2. Getting Started with MIDI
  3. # 5
Accepted Answer Pending Moderation
0
Votes
Undo
Welcome to 2020 with V2 on 20.04 !

Ok, So I been accumulating stuff for holidays and birthday and now that the world is staying home I decided to learn MIDI and program development.

I have an Odroid N2 running Ubuntu 20.04 with Mate desktop and a couple MIDI devices.
I am using Chromium Version 83.0.4103.61 (Official Build) snap (64-bit) which seems to be unable to do WebMidi as it exists today.

It makes a nice test bed for development on the living room couch and coffee table.
I added an AKAI MPK mini play and Numark party mix.
These are small and inexpensive MIDI V1.0 USB devices with General Midi sound and DJ controller features into 6 channels of sound.

I can easily switch to Android 9 as it is an ARM64 device as well.

This is in contrast to the larger Ubuntu Studio 20.04 system(s) with Roland Go Keys 61k from 2018
and older Juno 106 from the 1980's when Midi started.
Both have system exclusives up the wazoo that I have documentation to drill down into the workings.

I have given up with the Kurzweil pair (K1000 Pro and K1200 keyboard) as too complex and unfriendly for Midi development.

Today is June 5, 2020 at 3 PM eastern US time.
Links I will be using to trace and find how to get WebMIDI working as it had in the past.
I started with search for WebMIDI in Chrome Blog
This means that using Web MIDI on insecure origins will no longer be allowed.


Chrome Platform Status

Historic links to Chrome WebMIDI

I tried to get the above devices revealed and get that webmidi is supported but never see a request to access the devices.
Attached are my notes and logs to date.
Attachments (1)
Comment
There are no comments made yet.
  1. more than a month ago
  2. Getting Started with MIDI
  3. # 6
Accepted Answer Pending Moderation
0
Votes
Undo
Thanks so much, Lee. It's been such a whirlwind of research etc. (picked up the Go:Keys at GuitarCenter Saturday) I'd forgotten this Scratch possibility. This is a definite 'no' for now on normally sequencing MIDI on the Go:Keys -- correct? I tried connecting them with my phone's spiffy new presumably state-of-the-art data cable -- no luck. (USB-C with micro adapter.) Thought it might work since so many keyboards are made now for sequencing over a printer cable.
Comment
There are no comments made yet.
  1. more than a month ago
  2. Getting Started with MIDI
  3. # 7
Accepted Answer Pending Moderation
0
Votes
Undo
Nelson,
I am not sure where Fran is mentioned as I read this thread.
I have been away from the Roland and now have a Akai MPK mini play on my laptop and the Roland on a larger desktop (using USB on both).
Would like to be sharing your Cakewalk experience though I have started using Cross Platform LMMS for sharing learning about MIDI.

Last contact with Roland stated that no further effort will be made on the ScratchX for Scratch 3 migration so there is NO Scratch version able to
communicate with the Go:Keys 61k.
The message did say that Roland was working toward a Roland inclusive Scratch extension so that may be worth waiting for.



Hidemasa Togai <Hidemasa.Togai@roland.com>
Mar 14, 2019, 7:55 PM
to me, Lee, Roger, Corey, Hidemasa

Hello Mr. Davy –san,



Thank you for your activity with our GO:KEYS and Scratch.



For Scratch 3.0,

we were making a beta version of Scratch extension for MIDI as well as pitch to MIDI.



Currently we are busy with other projects. (Sorry !)



This Scratch extension would be not only for GO:KEYS but also all the musical instruments.

(We hope so)



Best Regards,

Hidemasa Togai







Corey Fournier <Corey.Fournier@roland.com>
Wed, Mar 27, 1:30 PM
to me, Roger, Hidemasa

Hello Mr. Davy -


Thank you for your continued interest and support of GO:KEYS.


We are still developing our implementation for Scratch 3 and it is not ready for demonstration at this time.


We will keep you posted and let you know as soon as we have an update that we can share.


Thank you for your understanding,

Corey


Corey Fournier / Market Development Manager
Roland Corporation U.S.
5100 S. Eastern Ave.
Los Angeles, CA 90040
(323) 890-3700 ext. 2328
http://www.RolandUS.com / http://www.BossUS.com / http://www.V-MODA.com
Comment
There are no comments made yet.
  1. more than a month ago
  2. Getting Started with MIDI
  3. # 8
Accepted Answer Pending Moderation
0
Votes
Undo
Do I understand correctly that Fran has succeeded in making MIDI tracks with the Go:Keys and others haven't -- playback changed sound choices or whatever? Did you go through the micro-USB jack, Fran? Connectig how? I need to know because I ordered the Go:Keys a month ago and it's supposed to be arriving soon. If it won't do for my normal Cakewalk stuff maybe I'll just hand the package right back to 'em at Guitar Center. That would be a disappointment since it's so compact and sounds so great in YT demonstrations.

The Go:Keys manual tells how to use bluetooth, so maybe with the dongles I've also ordered -- keeping fingers crossed. Of course Roland was only thinking of using Ipad or whatever.
Comment
There are no comments made yet.
  1. more than a month ago
  2. Getting Started with MIDI
  3. # 9
Accepted Answer Pending Moderation
0
Votes
Undo
Hello,

I am quite a new owner of GO:KEYS and having searched for its possibilities, I discover ScratchX which fascinated me as an alternative workflow for creating music. I thought instantly how cool it would be if I could specify my own LOOP MIX loops and sequences. This anxiety brought me to this thread which I read thoroughly from the top to the bottom. I know this problem you tried to resolve is outdated nowadays BUT I would like to ask you whether You have found any way how to deal with the stubbornness of GO:KEYS and occasionally a recipe for creating own LOOP MIX sequences which can be implemented in the ScratchX workflow.

Thanks

John


No progress with or from Roland Go:Keys.
Scratch 3 is due to be released January 2, 2019 and the Go:Keys 61k Scratchx extension will become almost useless with no response from Roland as to if there will be a rewrite for Scratch 3.

For Christmas 2018 I got a AKAI MPK mini Play and have started to collaborate with a developer on GITHUB for how to write code for the mpd-utils
Read the ISSUE 1 to see my contribution.

Akai says PLAY is General MIDI but I have caused it to lock up requiring power cycle to recover while using with Rosegarden and aplaymidi on Linux.
I hope to find or write a simple external MIDI extension for Scratch 3.
The PLAY is a much smaller GM device than the Go:Keys so I can move it around and leave setup for development.
Also trying to get a Arduino class compliant with Fluxamasynth working to have a really small well documented Dream Industries SAM2695 GM2 USB Class Compliant device for use
with Raspian LITE (Pi) running Scratch 3 with Node.JS

I'll check in as much as I can as project progresses (or not).
Comment
There are no comments made yet.
  1. more than a month ago
  2. Getting Started with MIDI
  3. # 10
Accepted Answer Pending Moderation
0
Votes
Undo
It's ironic really because there's a discussion here about what MIDI features Go:Piano does or doesn't implement. Answering that question is actually the purpose of the MIDI Implementation Chart that all MIDI-supporting devices are supposed to have. So if that chart existed for Go:Piano, then there would be no need for that discussion :)

The reason I'm looking for a MIDI Implementation Chart is that I'm wondering if there is a MIDI controller code transmitted by Go:Piano that I can use as a page-turner command in forScore on the iPad. I can teach forScore to turn pages with my Yamaha P-105 using the "+" and "-" buttons - and I found that out from the P-105's MIDI Implementation Chart, Does anyone here know if I could use one of the Go:Piano's buttons for that purpose? Thanks for any insights!
Comment
There are no comments made yet.
  1. more than a month ago
  2. Getting Started with MIDI
  3. # 11
Accepted Answer Pending Moderation
0
Votes
Undo
Hello,

I am quite a new owner of GO:KEYS and having searched for its possibilities, I discover ScratchX which fascinated me as an alternative workflow for creating music. I thought instantly how cool it would be if I could specify my own LOOP MIX loops and sequences. This anxiety brought me to this thread which I read thoroughly from the top to the bottom. I know this problem you tried to resolve is outdated nowadays BUT I would like to ask you whether You have found any way how to deal with the stubbornness of GO:KEYS and occasionally a recipe for creating own LOOP MIX sequences which can be implemented in the ScratchX workflow.

Thanks

John
Comment
There are no comments made yet.
  1. more than a month ago
  2. Getting Started with MIDI
  3. # 12
Accepted Answer Pending Moderation
0
Votes
Undo
No MIDI from recording sent except

I set tempo to 30 and pressed a key in each PART for one measure.
The GO-61 backup is attached in ZIP.
The text file is RECEIVEMIDI capture during record with time stamp for comparison.
I left it to run for 20 measures in ZIP file although OFF pressed for each PART much earlier.


09:13:57.896 channel 8 control-change 0 87
09:13:57.896 channel 8 control-change 32 66
09:13:57.896 channel 8 program-change 51
09:13:57.897 channel 9 control-change 0 87
09:13:57.897 channel 9 control-change 32 70
09:13:57.897 channel 9 program-change 8
09:13:57.898 channel 11 control-change 0 87
09:13:57.898 channel 11 control-change 32 65
09:13:57.898 channel 11 program-change 65
09:13:57.900 channel 12 control-change 0 87
09:13:57.900 channel 12 control-change 32 65
09:13:57.900 channel 12 program-change 14
09:13:57.901 channel 13 control-change 0 87
09:13:57.901 channel 13 control-change 32 67
09:13:57.901 channel 13 program-change 80
09:13:57.902 channel 14 control-change 0 87
09:13:57.902 channel 14 control-change 32 70
09:13:57.903 channel 14 program-change 66
09:13:57.904 channel 15 control-change 0 87
09:13:57.904 channel 15 control-change 32 66
09:13:57.904 channel 15 program-change 6
09:13:57.905 channel 16 control-change 0 86
09:13:57.905 channel 16 control-change 32 64
09:13:57.906 channel 16 program-change 1

Attachments (3)
Comment
There are no comments made yet.
  1. more than a month ago
  2. Getting Started with MIDI
  3. # 13
Accepted Answer Pending Moderation
0
Votes
Undo
As far as NPRN...

Could you share the NRPN numbers for phrase selection and LOOP mix key, please?

No, I am not to disclose the chart because it is preliminary but I will give an example and point to the public code that is experimental.


https://github.com/gbevin/SendMIDI


My command line history and should work on any Go:Keys as USB MIDI device.

Here I was selecting the LOOP MIX set shown in the ScratchX examples on previous link to manufacturer's page.

The LIST of choices can be seen in the SOURCE CODE linked to below.
The code generated I never could find due to my lack of programming skills.
I used the implementation charts to determine the combination.

RAW worked when NPRN failed due to variations in the implementation.
Some errors may have been passed on as well 15 versus 15M for override hex earlier in line for 16 Bossa Lounge (15 offset from 0 as 1).

I used the RECEIVEMIDI counter part instead of kmidimon as it was friendlier.
I set tempo to slower (5 is lowest) to not be over run with clock on screen.
I can put some up to compare recorded and MIX LOOP live channels.
You may be right as I did not investigate that yet.


sendmidi dev "GO:KEYS MIDI 1" hex raw BF 63 00 BF 62 00 BF 06 00 BF 26 11
sendmidi dev "GO:KEYS MIDI 1" hex raw BF 63 00 BF 62 00 BF 06 00 BF 26 12
sendmidi dev "GO:KEYS MIDI 1" hex raw BF 63 00 BF 62 00 BF 06 00 BF 26 21
sendmidi dev "GO:KEYS MIDI 1" hex raw BF 63 00 BF 62 00 BF 06 00 BF 26 20
sendmidi dev "GO:KEYS MIDI 1" hex raw BF 63 00 BF 62 00 BF 06 00 BF 26 1
sendmidi dev "GO:KEYS MIDI 1" hex raw BF 63 00 BF 62 00 BF 06 00 BF 26 15
sendmidi dev "GO:KEYS MIDI 1" hex raw BF 63 00 BF 62 00 BF 06 00 BF 26 15M
sendmidi dev "GO:KEYS MIDI 1" hex raw BF 63 00 BF 62 00 BF 06 00 BF 26 21M
sendmidi dev "GO:KEYS MIDI 1" hex raw BF 63 00 BF 62 02 BF 06 00 BF 26 11M
sendmidi dev "GO:KEYS MIDI 1" hex raw BF 63 00 BF 62 02 BF 06 00 BF 26 09M
sendmidi dev "GO:KEYS MIDI 1" hex raw BF 63 00 BF 62 02 BF 06 00 BF 26 02M
sendmidi dev "GO:KEYS MIDI 1" hex raw BF 63 00 BF 62 00 BF 06 00 BF 26 11
sendmidi dev "GO:KEYS MIDI 1" hex raw BF 63 00 BF 62 01 BF 06 01 BF 26 05
sendmidi dev "GO:KEYS MIDI 1" hex raw BF 63 00 BF 62 01 BF 06 01 BF 26 06
sendmidi dev "GO:KEYS MIDI 1" hex raw BF 63 00 BF 62 01 BF 06 02 BF 26 06
sendmidi dev "GO:KEYS MIDI 1" hex raw BF 63 00 BF 62 01 BF 06 01 BF 26 06
sendmidi dev "GO:KEYS MIDI 1" hex raw BF 63 00 BF 62 01 BF 06 00 BF 26 06
sendmidi dev "GO:KEYS MIDI 1" hex raw BF 63 00 BF 62 01 BF 06 03 BF 26 06
sendmidi dev "GO:KEYS MIDI 1" hex raw BF 63 00 BF 62 01 BF 06 03 BF 26 04




https://rolandcom.github.io/gokeys-scratch-extension/


Bottom of page is link to SOURCE CODE

The chart said BF but code was B0 so this again reflects preliminary nature of my copy.
Note: 63 , 62, 06, 26 as separators


function sendNRPN(ch, nrpn_msb, nrpn_lsb, data_msb, data_lsb)
{
sendMIDI(0xB0 | ch, 0x63, nrpn_msb);
sendMIDI(0xB0 | ch, 0x62, nrpn_lsb);
sendMIDI(0xB0 | ch, 0x06, data_msb);
sendMIDI(0xB0 | ch, 0x26, data_lsb);
}




I believe the loop record uses the channels 12-15.. When I get a chance I will look into this..


Not quite the recorded channels but part of the actual MIX LOOP code.

This selects Melody B phrase as last val changes.


sendmidi dev "GO:KEYS MIDI 1" hex raw BF 63 00 BF 62 01 BF 06 03 BF 26 04

ext.func_play = function(part, val) {
val--;
if (val < 0) val = 0;
if (val > 10) val = 10;
switch (part) {
case 'Drums':
sendNRPN(0x0F, 0, 1, 0, val);
break;
case 'Bass':
sendNRPN(0x0F, 0, 1, 1, val);
break;
case 'Melody A':
sendNRPN(0x0F, 0, 1, 2, val);
break;
case 'Melody B':
sendNRPN(0x0F, 0, 1, 3, val);
break;
}
};



Here is an example I tested doing PART select then change Melody B ( 0 to 10 is 11 possible val) and all off.


sendmidi dev "GO:KEYS MIDI 1" hex raw BF 63 00 BF 62 01 BF 06 00 BF 26 05
sendmidi dev "GO:KEYS MIDI 1" hex raw BF 63 00 BF 62 01 BF 06 01 BF 26 05
sendmidi dev "GO:KEYS MIDI 1" hex raw BF 63 00 BF 62 01 BF 06 02 BF 26 05
sendmidi dev "GO:KEYS MIDI 1" hex raw BF 63 00 BF 62 01 BF 06 03 BF 26 05
sendmidi dev "GO:KEYS MIDI 1" hex raw BF 63 00 BF 62 01 BF 06 03 BF 26 02

sendmidi dev "GO:KEYS MIDI 1" hex raw BF 63 00 BF 62 03 BF 06 00 BF 26 00





Is this helping Go:Key owners here ?
;)
Comment
There are no comments made yet.
  1. more than a month ago
  2. Getting Started with MIDI
  3. # 14
Accepted Answer Pending Moderation
0
Votes
Undo
Hugo,

Regarding Scratch, I suggest that you look at the first two posts in this thread from Lee, where he says something about Scratch/ScratchX, and provides some links to further information about it.

From that, I understand that it's a programming system, allowing access to the Web Midi API.

Geoff
Comment
There are no comments made yet.
  1. more than a month ago
  2. Getting Started with MIDI
  3. # 15
Accepted Answer Pending Moderation
0
Votes
Undo
Hello, Lee.

As for the implementation, in the published "specs" in the official website, you can see "conforms to GM2" in the part of MIDI data format.

That means that you can actually re-create a midi implementation chart only from the published requisites for GM2 and include the ones for GM, so I think you didn't have to go through all that trouble to get the information you wanted.

If you want to write an editor for the unit all you need to do is write a standard editor for GM2. It would include all the recognized parameters like bank select, volume and pan, but also the ones for vibrato speed, rev send level and so on.

All RPN messages are defined.

There are Melody channels and rhythm channels defined in the specs. You can set any channel as melody channel by sending bank select messages 79H/xxH, where xx would be the actual bank number.
Similarly, channels 10 and 11 can be set as rhythm channels if you send the bank select message 78H/xxH.

If you say that the unit presents 4 rhythm channels, this means that it implements an optional part of the GM2 spec that allows any channel to be defined as rhythm channel by sending the bank select messages 78H/xxH through it.

About the notes, the unit must have true voice, i.e. should be able to play some sound when any note number arrives. (notes 0-127)

Note off messages are ignored on rhythm channels.

And there's more in there, but I assume you already did your homework and read it.

What you mention about NRPN messages being used to select phrases is not included in the GM2 spec, though.

Could you share the NRPN numbers for phrase selection and LOOP mix key, please?

Also, I don't really know what you mean by ScratchX. Isn't it a website?

Thanks.
Comment
There are no comments made yet.
  1. more than a month ago
  2. Getting Started with MIDI
  3. # 16
Accepted Answer Pending Moderation
0
Votes
Undo
I received the preliminary MIDI chart but can't share publically.
The implementation is using a lot of NPRN .

It follows tightly how the ScratchX experimental code was being defined.
There is a MIDI Clock when ever there is a loop mix and all 16 channels are concurrently active with low 7 banks each a button on control panel plus drums on 10.
The other 8 channels 8-16 are loop mix with NPRN selecting the phrase 0-10 and part not NOTE ON as I expected.
Channels are similar to live analogy on 5 octave keyboard split by Bass, Part (Melody A) , Part (Melody B) , Drums.
The values can be seen at the GITHUB Extension

I am not sure what PartX1-4 is in the chart for channels 12 to 15.

I have been using receivemidi and sendmidi from Linux command line.
I will experiment more !


Maybe a way to get 8 parts instead of 4 plus drums plus 4 recorded for sequencing.

If you watch the videos and read the code you can see how chart was derived.
I plan to try to follow the Roland GO:KEYS ScratchX Extension and Youtube Tutorials.

One playlist is for SCRATCHX.

Another is Quick Start for learning to use the GO:KEYS

NPRN also selects Loop Mix KEY as 1 of 12 as done for real after pressing chord button.

A second version of the extension Extension2.js
shows additional menu choices for more of the instruments which are listed in the MANUALS.

Data reception and transmission is Note ON / OFF , Bank Select, Modulation , Program Change, Pitch Bend.
Also included are volume, panpot, expression, resonance, cutoff, decay, attack and release time

Transmission also has Real Time messages for clock, continue, and stop.
Comment
There are no comments made yet.
  1. more than a month ago
  2. Getting Started with MIDI
  3. # 17
Accepted Answer Pending Moderation
0
Votes
Undo
Thanks - some clarification there.

When I was looking at Lee's midi file - mentioned above - I wondered how come the data was in ch 12-15. Looks like Lee was using the Loop Record facility, and that's what that does!

As for the instrument select, yes, I could see in the midi file that all the sounds seemed to be being selected using LSB/MSB (which is usually JUST for the Bank Select), then followed by a PC (Program Change) standard controller to select the actual instrument. Are you saying that the instruments can be selected via LSB/MSB ONLY? The data in the midi file certainly seemed a little odd??

Geoff
Comment
There are no comments made yet.
  1. more than a month ago
  2. Getting Started with MIDI
  3. # 18
Accepted Answer Pending Moderation
0
Votes
Undo
I have only owned the Go keys a few days...The Go Keys responds via my DAW using LSB 0 and MSB 0, 1, 2,,3. (these are the Go Key sounds) GM2 are LSB 121 and MSB 1,2,3.
I send this info via my Code 61 controller and the sound patch shows in the Go Keys screen.

I believe the loop record uses the channels 12-15.. When I get a chance I will look into this..
Comment
There are no comments made yet.
  1. more than a month ago
  2. Getting Started with MIDI
  3. # 19
Accepted Answer Pending Moderation
0
Votes
Undo
Hello Lee,

Sorry to hear you're having such a problem getting the Midi Implementation Chart. As I think I noted before, I THOUGHT that most midi devices would come with one. So how come Roland cannot just send you a copy of one for the specific keyboard, I don't understand.

I do NOT follow, at all, one of your comments above. Maybe it's something peculiar to the specific keyboard, or to something you were doing, but bank select should NOT have anything to do with channel select, and nothing to do with 'allowing instruments to be played in parallel'.

Of course, Bank select (like any other CC), is specific to a channel, but it's a channel YOU define, not 'automatic'.

You could easily use multiple bank select (and program change) in a single channel, although it would be a total pain in the ass and no sense at all in most cases. No problem if a specific channel starts as one instrument, then changes to something else later. Setting a specific channel to a specific instrument is just a massive convenience, otherwise you'd end up with as many bank select/program change commands as note commands in your piece. Is it just me, but I hate it when some system starts doing something automatically that ought NOT to be automatic, that I should have control over (like how to use channels).

Geoff
Comment
There are no comments made yet.
  1. more than a month ago
  2. Getting Started with MIDI
  3. # 20
  • Page :
  • 1
  • 2


There are no replies made for this post yet.
Be one of the first to reply to this post!