gregg1ep00
Member
Thanks Ron. I’ll try it out tonight and report if I find anything.Just released 4.0.2, which fixes some more reported bugs.
Thanks Ron. I’ll try it out tonight and report if I find anything.Just released 4.0.2, which fixes some more reported bugs.
Looks like my expression pedal fix didn't do the job, version 4.0.3 is now available and it should take care of it.
I have noticed in 4.0.3 that you can't scroll faster through a setlist or song bank by holding down bank up or bank down anymore.
Can only 1 expression pedal action be assigned at a time? I’d like to setup multiple expression settings with varying min - max values for several cc messages that are controlled with one physical pedal.
Thanks!
Only one settings block can be active at a time, but each block can send two CCs, to two different devices if desired.
I've noticed that song names are not displaying when in Songs and Setlist mode with 4.0.4
Mine display fine...make sure you have no page name for Page #1...it has to be blank in order for the song name to be displayed...
Thanks for getting back to me.
Maybe what's needed is the ability to assign the min/mx value of each continuous controller of an expression pedal through IA Actions? That way I could create an expression pedal for delay and reverb mix, and based on the preset selected, adjust the range for the specific continuous controller.
Also, is there are reason why there are only 2 continuous controllers per expression pedal?
I see what you mean, about the min/max, I will think about that.
Generally, the reason a feature isn't implemented is either:
1). No one has asked for it (or if it's a difficult feature, I tend to wait to hear requests from a lot of people before committing to it)
or
2). Or, I just haven't had time to do it yet.
Going beyond 2 CCs per pedal is mostly because there haven't been many requests for it. I'm also a bit concerned about the amount of data going over the MIDI connection. MIDI is very slow and four simultaneous streams of expression pedal data is not something I've tested. We can't have the GT producing a data stream faster than MIDI can transmit it. I can do some tricks to limit the number of CCs per second, but I'm not sure how well that will work.
I can think of two possibilities: either the CC is being sent before the PC, or pedal ignores MIDI messages for a while after it receives a CC (I've heard of it happening in some other deviecs, but never have tried that specific pedal)
How is the PC message being specified? Is it an action on a button, is it being sent by a preset using the PC Messages section or something else?
Thanks for getting back to me Ron. I'm using to separate IA Buttons. One to choose the preset via PC message and another to assign the parameter on the pedal via CC message.
Ok, and on preset change, you want both buttons to send their messages, correct? If that's the case: on preset change, buttons are processed in order starting with page 1, button 1, then button 2, through button 10. The Loops button is the last one processed on each page. Then it continues to the next page. You may be able to fix the problem just by swapping the position of the two buttons in question.