Date 1 - 5 of 5
Missing Stomps (CC's) after PC
I wonder if anyone else is having this problem. Mike and I have
discussed this at length, and he doesn't experience the problem that
I do on my Vetta with his POD. The problem is that the Vetta takes
enough time to process a PC (understandable since it stores a ton of
information in each patch) that it is still processing while the
stomps are sent. At about a 10% rate, the Vetta will either miss a
stomp (or more than one) or activate one that isn't supposed to be
activated. I have a maximum of 3 stomps programmed to be activated
by the FCB1010 (with "on" commands) so that the pedal lights are
right with the amp. It will miss random combinations of the stomps
as well as having random stomps light up on the amp that are
programmed with offs on the FCB (that is a big problem because even
if I have all of the stomps set to off the amp gets comfused when
changing patches after I have activated any stomps - the only safe
method is for me to turn them off before a patch change). It is not
failing to turn the last patches stomps off (it stores the on/off
value in the patch and ignores an off that is not needed), but is
actually re-activating incorrect stomps because of the confusion of
still processing a PC. I am sure of the cause because I can send
(on or off) any amount of CC's (or stomps) at once (without error)
as long as they are not following a PC. I know I'm rambling, but I
wonder if someone else can check this behavior on their gear. Set
up a series of PC's with simultanious stomp CC's. Check the ACTUAL
activation or deactivation of the CC controlled effects. I find it
hard to believe that the Vetta is unique in it's need for a delay
between PC and CC's. Ossandust, how imposible of a request would it
be to have a slight delay (possibly with the ability to turn it off
for those folks whose equipment can process the simultanious
request) after any PC's? I had this problem before UnO, but it
didn't matter. Before the stomps (and the ability to have the
lights be reflective of their state), sending simultanious PC's and
CC's was of no use (I could save any of the activations in the
Hi Chris!toggle quoted message Show quoted text
I own a POD2 with the latest 2.3 firmware version and fortunately don't have
the trouble You are in. The POD does recieve every bit correctly. You might
check in the Files/Application folder my sysex, no less than 8 CCs follow
the PC. I seem to recall that You are a senior member, but a few ideas I
- Do You go directly into the Vetta or You have some equipment between them?
In the latter case I would go directly, just to elliminate any other cause.
- Does Line6 offer an updated firmware that might address this, or similar
behaviour? I would update if it is feasible.
- You do have the MIDI cable disconnected from the FCB's in, don't You?
- Eventually any of Your equipment can be faulty, do You have the
opportunity to try another pedal or amp?
You have probably gone through the suggestions above, already, but that's
all I can think of right now.
An _optional_ delay probably would be handy for people owning older gear,
but the FCB firmware should default to 0 in case Ossandust decides to solve
this issue in my opinion.
Thanks for the reply Zsazsi. I have tried every combination of
direct, indirect, FCB in disconnected, etc. I even tried turning
off Running Status for the heck of it. As far as the direct
connection goes, I actually had a higher fail rate than running it
thru my G-Major. The Midi in makes no difference because the Vetta
doesn't pass it's midi thru (I did try it however). There are no
updates more current than I have, and NONE of their updates have
ever addressed midi concerns. I do not have the ability to try
another amp. I am sure that both the amp and the UnO chip are
functioning fine. I have monitored all of the UnO output in Midi-
OX, and the amp is not failing, it is just choking on the data
occasionaly. As I mentioned in my post, any delay would HAVE to be
optional to be implimented. You are right about the senior member
thing. I have been using the FCB for years (and many EPROMs), and I
own this group. My findings are pretty solid, I just would like to
know if anyone else can verify them on other gear (the POD seems OK -
both you and Mike have confirmed).
--- In fcb1010_uno@..., "Zsazsi" <m-zsolt@...> wrote:
the trouble You are in. The POD does recieve every bit correctly.You might
check in the Files/Application folder my sysex, no less than 8 CCsfollow
the PC. I seem to recall that You are a senior member, but a fewideas I
would check:between them?
In the latter case I would go directly, just to elliminate anyother cause.
- Does Line6 offer an updated firmware that might address this, orsimilar
behaviour? I would update if it is feasible.You?
- Eventually any of Your equipment can be faulty, do You have thethat's
all I can think of right now.older gear,
but the FCB firmware should default to 0 in case Ossandust decidesto solve
this issue in my opinion.[mailto:fcb1010_uno@...] On
thatBehalf Of sliding_billy_hamilton
takesI do on my Vetta with his POD. The problem is that the Vetta
ton ofenough time to process a PC (understandable since it stores a
miss ainformation in each patch) that it is still processing while the
bestomp (or more than one) or activate one that isn't supposed to
I put this issue on the todo list for a next UnO version...
--- In fcb1010_uno@..., "sliding_billy_hamilton"
Thank You.toggle quoted message Show quoted text
--- In fcb1010_uno@..., "ossandust" <ossan.dust@...> wrote:
|1 - 5 of 5|