Currently Being ModeratedNov 28, 2011 11:35 AM (in response to rizzorock)Re: MIDI Set up w/ Voodoo Labs Ground Control Pro & POD HD Pro Rack?
Yes - I get where you are coming from with this.
What you want to do is effectively:
- make the POD HD Pro deaf to MIDI Program Change Messages so the patch on the pro always stays the same and delay trails being enabled within a single patch will work for you
- set up individual patches that don't send Program Change messages on the GCP, but just send the relevant CC messages to turn various options (FX) in your POD HD Pro on or off on selecting the relevant patch on your GCP
I don't have a GCP, so I'm only vaguely aware of all its capabilities to be honest.
But I do have an HD500 and an HD Pro, and I can control the HD Pro to a degree from the HD500 and change patches on the HD500 without changing patches in the HD Pro, whilst still having the ability to turn individual FX on/off on the HD Pro from the HD500.
I make the HD Pro deaf to Program Change messages sent by the HD500 by setting the HD Pro's base MIDI channel to a different channel to the HD500. I send the relevant CC messages from the HD500 on the base MIDI channel number for the HD Pro.
The only thing that doesn't work doing this is that the HD500 doesn't send the CC messages upon selecting the patch, but this might be different in terms of how your GCP works in that you might be able to force sending the CC messages upon selecting the patch in your GCP. It really depends on the level of fine tuned control you have with your GCP.
If delay trails were possible in the POD HD range when switching between patches that would be a good thing of course, but there would be a DSP overhead to offset the benefits.
Currently Being ModeratedNov 28, 2011 11:18 AM (in response to rizzorock)RE: MIDI Set up w/ Voodoo Labs Ground Control Pro & POD HD Pro Rack?
I agree with nickmattocks suggestion above. Give it a shot, and let us know your results. Like he mentioned "It really depends on the level of fine tuned control you have with your GCP."
We have the updated MIDI CC reference information available on pages C1-C4 of the POD HD PRO Advanced User guide at the link below:
Currently Being ModeratedNov 28, 2011 12:27 PM (in response to Line6Don)Re: RE: MIDI Set up w/ Voodoo Labs Ground Control Pro & POD HD Pro Rack?
jimsreynolds summed up my problem brilliantly.
"I am going to restate here what you found cause it will affect a number of people and I wanted to make clear what the problem you had was - when people come looking.
The issue in your case was that you wanted to be able to to retain reverb and delay trails when changing effects. Patch changes (via Midi or otherwise) normally cause delays to be cut off hard.
However, you noted that Reverb and delay trails are preserved when you stay within an HD patch but instead toggle the specific effects off. Your workaround would have been to stay within an HD patch and instead send a set of MIDI cc's from your Midi footpedal to force a group of effects to be flipped on or off. This would have achieved your aims.
Unfortunately the HD MIDI implementation does not appear to follow convention. Typically a cc value of 0-63 means 'off' and 64-127 means 'on'. However any value (0-127) sent to the HD simply flips an effect to its opposite state (on or off). Therefore it is impossible to predict and automate the required HD effect state using MIDI commands, within an HD Patch."
until Line 6 changes the CC messages my problem is not fixable. we will see with the next update.
Currently Being ModeratedDec 2, 2011 9:08 AM (in response to rizzorock)Re: RE: MIDI Set up w/ Voodoo Labs Ground Control Pro & POD HD Pro Rack?
This is currently how the MIDI implementation works on the POD HD Pro. If you would like to see this behaviour change, please forward your suggestions directly to our developers using the product feedback from at the link below:
Currently Being ModeratedDec 2, 2011 1:00 PM (in response to Line6Don)Re: RE: MIDI Set up w/ Voodoo Labs Ground Control Pro & POD HD Pro Rack?
already done. thank you.