GM-800 Bug Reports

[BROCKSTAR]

If you find any hardware bugs from the gm-800, then post it here and I also encourage you to sign up andf email roland / boss as well so they know.
https://www.boss.info/backstage/support

--------------------

I found something weird.

0 ) have your usb stick loaded with sound packs and in the gm-800
1 ) go to menu
2 ) hit > until you see usb memory
3 ) click knob below it then click knob below import tone
4 ) find a sound pack you wanna load then press select knob
5 ) load each tone in the sound pack and hit select and ok to load them
6 ) once loaded, hit your part 1 button (or whatever part you're on)
7 ) press browse button and scroll down to USER (user option should remain there after 2nd time so no need to scroll too it again)
8 ) now your tones from the sound pack is loaded on right and you can play each of them

The bug / issue comes next. Re-do step 1 through 8 and you'll find out that the 1st tone in the next sound pack is
still the same tone from last tone pack, so you have to move the knob below the tone screen down then back to the 1st tone to
get it to make the normal sound it's made to sound like.

[Elantric]

Try prior to  Step 6, remove the USB thumb drive

[shawnb]

Minor display bug - with the BTS GM-800 app, not the GM-800 directly. 

If you use a ctl to mute all 6 strings, upon initial display in BTS, string 5 is displayed as string 6:
You cannot view this attachment.

Note it is working perfectly.  It is reflected properly on the GM-800.  It will correct itself if you drill down.  It's only wrong on initial display.

Of course, my OCD kicks in and I dive in & correct it again again...   


(Reported to Roland.)

[Witelite]

I think I found a bug related to sending MIDI via the assign switches.

If you set it to send MIDI CC on CTL 1 or 2 It won't send anything on your first press. The second press triggers the midi commands . So in Momentary mode, pressing down triggers nothing and releasing triggers the MIDI CCs. In toggle mode the first press and release does nothing. The second sends commands.

I know this is pretty out there but interested if you guys can duplicate this. It is a killer to try and send commands like muting the guitar signal which the GR55 did internally.

(and for what its worth I've found the assign section of tone control to do some pretty weird things at times but I'll have to replicate it)

[admin_shawnb]

If you set it to send MIDI CC on CTL 1 or 2 It won't send anything on your first press. The second press triggers the midi commands . So in Momentary mode, pressing down triggers nothing and releasing triggers the MIDI CCs. In toggle mode the first press and release does nothing. The second sends commands.

I cannot replicate this.

However, I saw nearly identical behavior earlier - I was inadvertently setting the ACT ranges (assign page 2) instead of the actual MIDI CC# and values (assign page 3).  I think the order/layout of the ASSIGN screens is confusing.  It may help to triple-check all 3 pages.

I was in the midst of a classic ASSIGN epic battle: I have a synth daisy-chained via 5-pin MIDI off the GM-800 (an arpeggiator).  But I don't always want notes to sound on the 2nd synth, I was looking for a way to stop sending MIDI notes to the second one.  At first, I just assigned a CTL to enable/disble SCENE GUITAR TO MIDI.  But...  When you enable GTM, the GM-800 sends a bunch of initializing MIDI commands, that actually alter your downstream patch.  So that didn't work.  Next, I attempted to turn local control off on the remote synth via assign (standard CC#122).  That worked - I could control notes sounding or not!  But...  The remote synth was still responding to wheel events, so that would alter the running arpeggio when I used the whammy bar (which sounds like a bug with the remote synth, local off should also disable the wheel, IMO)...  Ultimately, I went with using a CTL to mute/unmute the 6 strings.  6 ASSIGNS, but it works perfectly. 

I spent the next couple of hours copying those 6 assigns to all my patches.  A 3-beer job.

This stuff requires a lot of patience & testing...

[Witelite]

I cannot replicate this.

However, I saw nearly identical behavior earlier - I was inadvertently setting the ACT ranges (assign page 2) instead of the actual MIDI CC# and values (assign page 3).  I think the order/layout of the ASSIGN screens is confusing.  It may help to triple-check all 3 pages.

I was in the midst of a classic ASSIGN epic battle: I have a synth daisy-chained via 5-pin MIDI off the GM-800 (an arpeggiator).  But I don't always want notes to sound on the 2nd synth, I was looking for a way to stop sending MIDI notes to the second one.  At first, I just assigned a CTL to enable/disble SCENE GUITAR TO MIDI.  But...  When you enable GTM, the GM-800 sends a bunch of initializing MIDI commands, that actually alter your downstream patch.  So that didn't work.  Next, I attempted to turn local control off on the remote synth via assign (standard CC#122).  That worked - I could control notes sounding or not!  But...  The remote synth was still responding to wheel events, so that would alter the running arpeggio when I used the whammy bar (which sounds like a bug with the remote synth, local off should also disable the wheel, IMO)...  Ultimately, I went with using a CTL to mute/unmute the 6 strings.  6 ASSIGNS, but it works perfectly. 

I spent the next couple of hours copying those 6 assigns to all my patches.  A 3-beer job.

This stuff requires a lot of patience & testing...

The Assign section has some weird stuff going on for sure but I definitely believe it is an issue in a particular circumstance.

When you are sending a cc command with a value of 0, it does not work on the initial press. In my case, I'm sending to an external device to turn a block or effect OFF so I had it set for a min of 127 and a max of 0. When you do that and switch to the preset, the first press to send the -0- does not recognize. Only after it reverts back to 127 does it then recognize the zero. This is definitely a bug.

SOLUTION - Set your value to 1 vs 0. In the case of bypassing an effect or block, anything less than 64 will turn it off and the GM800 recognizes the 1.

DROVE ME NUTS!!!!

UPDATE - This solution only works for momentary mode. In Toggle Mode if you set min to 127 and max to 0 (or something close), It will send the highest numerical value first in toggle mode. So you can't turn an external setting off initially using toggle. (or at least I can't)

MM