Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[dnedwek]

Welcome to the forum, Ross.

This is more than likely due to an assignment (manual, page 54).

I have been saved from myself more than once by Gumtown's Incredible Editor software. The bright orange light in the Assign section of the main window usually means "Hey, take a look here for that assignment you forgot to correct."

[SLICK]

If you use one of the 'panning' pulsed patches and are not running stereo it wont be pulsed as the L Ch folls in the R Ch spaces. Fair enough really and not actually a 'bug' as such but....

Could not find a way around this other than using an assign and the wave pedal to turn the PCM tone on and off.
The GR-55 seems to struggle with faster BPMs though and you will struggle to get quavers at anything over 100BPM before it starts to 'miss' the Wave pedal transitions giving your 'pulsed' tone an odd rhythmic pattern to it.
Had a little more success by using the Wave pedal to change PCM volume which allowed me to push the BPM a little higher before the rhythmic patterning returned.
Anyone else confirm this 'effect?

[jwhitcomb3]

I think I may have discovered a GR-55 bug.
 
When I set the GK Vol to be the tone volume in the main controllers page (not the assigns page), setting only the modeling volume to “on”, and then turn the GK volume knob down, the model gets quieter. So far so good. But then, with the GK knob still down, if I push the EXP switch, the model volume pops back up to maximum, even while the GK knob is turned down.
 
This happens regardless whether the EXP or CTL or any assigns are programmed or enabled. Doesn’t seem to matter what controller the EXP switch is set to either.
 
Anyone else run into this?

[mbenigni]

the model volume pops back up to maximum, even while the GK knob is turned down.

I've had some variation of this problem, for sure.  I wasn't using the EXP switch at all, but I've had a couple of cases where the GK Volume (set to function exactly as you describe) just basically stops working, with the modeling tone sending at full volume.  In these cases I've basically scratched my head (maybe cursed once or twice depending on how late into the evening...) and switched patches back and forth, and then the problem mysteriously goes away.

Like every other "problem" I've had though, I never manage to duplicate them/isolate them precisely enough to rule out user error.  There's always so much going on at the same time with the GR-55, it's difficult to keep your wits about you. 

[bnew63]

Anyone had problems with the sound from one string failing after time.
I've had this happen about a dozen times.
Rebooting the gr55 solves the problem.
Could this be the 13 pin chord.

Brian

[ddlooping]

Could this be the 13 pin chord.

Quite likely.
Have you cleaned up the connector, as suggested in a thread here (you'll have to search, I can't remember where it is)?

[Elantric]

Yes - its very likely a bad connection in your 13 pin cable.

Read this thread for a solution.
http://www.vguitarforums.com/smf/index.php?topic=3132.msg20110#msg20110

[iancandler]

I found tonight that when navigating the drum kits in the PCM tones I was getting no output when changing them in floorboard, going in and resetting the tones on the GR 55 itself solved the problem instantly.

[jwhitcomb3]

I think I may have discovered a GR-55 bug.
 
When I set the GK Vol to be the tone volume in the main controllers page (not the assigns page), setting only the modeling volume to “on”, and then turn the GK volume knob down, the model gets quieter. So far so good. But then, with the GK knob still down, if I push the EXP switch, the model volume pops back up to maximum, even while the GK knob is turned down.
 
This happens regardless whether the EXP or CTL or any assigns are programmed or enabled. Doesn’t seem to matter what controller the EXP switch is set to either.
 
Anyone else run into this?

I think I’ve narrowed the scope of this bug.
 
The “tone volume” controller parameter allows you to set any of four sources to “on” or “off”: PCM#1, PCM#1, model, or pickup.
 
If you set mutually exclusive sets of these sources to “on” and assign them to different controllers, they will still conflict. For example, if you set the GK volume to control the model tone volume (off, off, on, off), and you set the EXP to control the PCM#1 and PCM#2 tone volume (on, on, off, off), the model volume will still pop back up to full when you step on the EXPSW.
 
You’d think that setting a source to “off” for a controller assigned to the tone volume would cause that controller to ignore the source set to “off.”
 
The work-around is to only use the “tone volume” target in one of the Pedal/controller parameters, and set up any others in the “assign” area, where there does not appear to be a conflict.

[mbenigni]

Thanks, Jonathan.  That's probably what was tripping me up as well.  Weird behavior!  I've gone over to using system-wide settings for the exp pedal and GK controls (with pretty much exactly what you describe, except no dependency on the Exp pedal switch) in order to simplify patch programming.

[Spider]

It first time when my GR55 freeze. I use AcComp/BassSplit patch (by Ian) and was noticed that the sound of the low E and A (modeling gitar, -12 alt. tuning) some times is terrible. It was some kind of self oscillation, vibration. I try check settings on the GR55 but in this moment it wasn't react. I coun'd event power it off.

But... I had connected the GR55 to my MacBook with running Gumtown editor.  Mac was closed so it was theoretically sleeping... but when I disconnected it GR came back to the life.

[Elantric]

It first time when my GR55 freeze. . . . . Mac was closed so it was theoretically sleeping... but when I disconnected it GR came back to the life.

If you connect the GR-55 via USB to a "sleeping" MacBook - Yes, the GR-55 WILL lockup. This is Normal.

Its part of the new "Green" electronics initiative which dictates that any peripherals connected to a sleeping computer must go into a "suspend / power save" mode, to conserve energy.

Avoid this by changing your MacBook's System settings  - disable "sleep mode" when you want to create music with the GR-55.
 

http://www.ehow.com/how_6339590_disable-sleep-mode-macbook.html

[A to the T]

I found tonight that when navigating the drum kits in the PCM tones I was getting no output when changing them in floorboard, going in and resetting the tones on the GR 55 itself solved the problem instantly.

I had this exact issue tonight myself...

[Click Sky Fade]

I had this exact issue tonight myself...

Me too. 

[ddlooping]

I found tonight that when navigating the drum kits in the PCM tones I was getting no output when changing them in floorboard, going in and resetting the tones on the GR 55 itself solved the problem instantly.

Unless I'm misunderstanding, isn't that a GR-55 Editor (Floorboard) bug?

[gumtown]

I think this thread is for issues from BUGS with the GR-55 hardware/equipment itself.

If there are issues with the editor software, please post in the Editor thread here
http://www.vguitarforums.com/smf/index.php?topic=2951.0

[Click Sky Fade]

The issue i had was regarding the hardware not the editor software. Basically all percussive samples were just noise and took a factory reset to put right. 

[Click Sky Fade]

Not so much of a bug as a progress report on a problem i've been having regarding the 'pulsating' and 'beat & groove' PCM's. Since i got the GR-55 i've had occasions where the unit just makes a drone when using any pcm that is tempo based. It happened again today (backup settings & factory reset. Again!!!) and following some reading on this forum, it hit me.

One of the threads was discussing 'tap tempo' and how it is not available when midi sync is enabled. Doh! That was it! These PCM's rely on a tempo and unless you have your unit synced at the time. You'll just not get owt!

No problem with the unit or the firmware, problem with the user!

On another note... I was not getting any sound from the unit apart from the guitar out. Scratched head!, factory reset, scratched head some more...

Expression pedal heel end down, minimum value. Doh X 2

Anyway I'm off to factory reset myself.

[ddlooping]

Anyway I'm off to factory reset myself.

Make a backup of yourself beforehand, just in case.

[synthgtr]

Make a backup of yourself beforehand, just in case.

LOL   

[FreeTime]

I don't know exactly how I did it, I was playing with some alternate tunings and  some 'user' tunings on the COSM guitars. After a while I went to tune my guitar (in individual string tune mode, I love that !!! ) and somehow all the strings were wrong ( Low E showed as A, A as a D etc. ). I tried disabling alt tunings, also setting the intervals back to zero, but it would'nt come back to normal until I did a factory reset.
I reloaded my custom patches and the tuner still worked

[derwin]

hi does anyone have any advice on buffer in/ out settings i am using my gr as an interface via usb to record into abelton 8 using an acer aspire 5536 laptop( vista 64) but the latency is terrible is it the buffer settings causing this also? is this laptop up to the job doesnt seem too, steady cpu load goes insane slows down playback ect any tips?

[gumtown]

Does Abelton support ASIO driver use? If it does, I recommend using ASIO mode as that provides minimal latency.
If you are using the GR-55 as the output audio device (since ASIO spec only allows one audio device at one time), then use "direct monitor" setting in the GR-55 instead, as the signal will be double buffered to send to the PC processed then sent back to the GR-55.

[frankvai]

Twice while using the Phrase looper and changing patches the unit freezes. Had to restart ,anyone else ? Can't get the RX PC Map
function working. Sending PC from Lexicon MPX floorboard
works fine on fixed but when switched to PROG nothing. Tested another unit same thing. Sent all types of PC from other devices no luck.

Have owned GR500  GR300  GR700  GM70  GR30  GR33

i have the same bug  in fix mode work fine but nothing in prg mode with many foot controller

[Nick M]

A few weeks ago, my Gr55 was  in a situation whereupon receiving a patch change from a Ground Control Midiboard its sound became completely muted. The only way to get the output sound back on, was pushing down on the GR55 pedals toe switch. This seemed to be the case with every patch I tried. -So basically every time I tried to change patch, it would just mute the unit 'til I went over to it and stomped on the toe switch.  Powering down the GR55 and back on again made no difference, it just stayed like that all day. The next day however everything was back to normal and it was fine again.
  Until a couple of days ago however, when exactly the same thing happened again. On neither occasion were there any different circumstances in the way the GR55 was set up to usual, or what other things it was connected to. I always send it patches from the Ground Control midiboard. So I can't see anything that might have triggered it to have behaved differently from all the other times I switch it on.

 - Anybody got any suggestions as to what might have been causing this problem?