Hi,

just to let you know recently an issue popped up with the way the 2
switches (relays) are working in the UnO firmware. Actually there
seems to be a bug when using the FCB in UnO "stompbox mode", which
causes the relay settings, programmed in "regular" patches, to be
ignored. If you use any of the 5 "stomp box" patches to set the
switches, you'll have no problem. Also, when not using stompbox mode,
there is no problem.
I consider this as a blocking issue (some of the promoted
functionality actually doesn't work) so I'm currently working on a
bugfix, which should be ready in a week or so. This will be the really
final UnO firmware upgrade (or did I say this a few times before
already?....)

X.

Hi X!

Any chance, that a community suggested feature can be implemented (I think
of the tuner aka delayed patch send possibility first of all)?

Thanks for Your time and effort.

Zsazsi

Hoi Zsazsi, good try ! ;-)

I opened the FCB code one last time (well...) and I really pushed hard
to get those few extra lines of code inside. No more, sorry... (in the
fcb2020 on the other hand, once I have time to continue on that
project ... ;-)

What I mean by "(well...)" :
there is one final pending issue, mentioned by Sliding Billy Hamilton
(you know - the thread "Missing Stomps (CC's) after PC "). As promised
I'm starting some testing around that issue.
Only problem about that : as you mentioned yourself, adding a short
delay after each PC message should be optional, if at all added. In
practice, this means (no more extra global setup code - you know) that
an existing global setting has to go away in order to support this.
I'll launch another message to find out which one.

Greetz (and don't shoot me:-),
Xavier


--- In fcb1010_uno@..., "Zsazsi" <m-zsolt@...> wrote:

Hi X!

Any chance, that a community suggested feature can be implemented (I

think

of the tuner aka delayed patch send possibility first of all)?

Thanks for Your time and effort.

Zsazsi

Xavier!

You can't be fooled, I see. I was just trying to grasp a straw :)

Thanks again for your work!

Regards

Zsazsi

I do not really know much about the Vettas, but suspect that they work
similarly to the PODs and with an appropriate FCB stomp layout a possible
workaround for Chris would be to keep the presets of the Vetta and the fcb
synchronised. I mean after programming the on/off status of the stomps I
would hit save on the Vetta as well. If it only chokes messages, the stomps
would reflect the sound image I believe.

Just a thought

Zsazsi

I HAVE tried turning off all of the stomps on the Vetta (using the
FCB to activate them) AND syncing them between the 2. If you read
my original post, you will see the problem. The Vetta doesn't just
miss CC's, it misinterprets them while processing the PC. For
example, the patch I am on has stomps 2 and 3 live, the patch I am
going to has no stomps live. I hit the second patch and one of the
stomps accidentaly lights on the Vetta (not the FCB). Believe it or
not, it will do this even with "no change" selected. What you need
to keep in mind is that the Vetta and POD are VERY different in the
amount of settings that are stored within each preset. In human
terms, the amount of time it takes the Vetta to process a patch
change is (like any amp) a slight latent period. In terms of midi
data, that slight period is a life time. If you need to see this in
action (with pretty much any piece of gear), hook up a 2-in 1-out
midi thru box to the gear. While moving an expression pedal back
and forth, try firing commands at you gear with Midi-OX. I suspect
you will experience some data loss. I am of the opinion (because of
the fact that the Vetta fails at about a 10% rate instead of
anywhere near 100%) that about 1 5ms delay between PC and CC's will
probably solve the problem. We (Xavier and I) are going to be
testing it shortly. FWIW, if you can detect a 5 ms delay in
something that already has an inherent latency (unlike an expression
pedal) like a patch change, you have a far superior ear than I.

Chris

--- In fcb1010_uno@..., "Zsazsi" <m-zsolt@...> wrote:

I do not really know much about the Vettas, but suspect that they

work

similarly to the PODs and with an appropriate FCB stomp layout a

possible

workaround for Chris would be to keep the presets of the Vetta and

the fcb

synchronised. I mean after programming the on/off status of the

stomps I

would hit save on the Vetta as well. If it only chokes messages,

the stomps

would reflect the sound image I believe.

Just a thought

Zsazsi

-----Original Message-----
From: fcb1010_uno@...

[mailto:fcb1010_uno@...] On

Behalf Of ossandust

What I mean by "(well...)" :
there is one final pending issue, mentioned by Sliding Billy

Hamilton

(you know - the thread "Missing Stomps (CC's) after PC "). As

promised

I'm starting some testing around that issue.
Only problem about that : as you mentioned yourself, adding a

short

delay after each PC message should be optional, if at all added.

In

practice, this means (no more extra global setup code - you

know) that

an existing global setting has to go away in order to support

this.

I'll launch another message to find out which one.

EDIT: "it will do this with "no change" selected on the stomp that
mistakenly lights - obviously if all three say "no change" it will
not misinterpret anything because it isn't receiving any data"

Chris

--- In fcb1010_uno@..., "sliding_billy_hamilton"
<sliding_billy@...> wrote:

I HAVE tried turning off all of the stomps on the Vetta (using the
FCB to activate them) AND syncing them between the 2. If you read
my original post, you will see the problem. The Vetta doesn't

just

miss CC's, it misinterprets them while processing the PC. For
example, the patch I am on has stomps 2 and 3 live, the patch I am
going to has no stomps live. I hit the second patch and one of

the

stomps accidentaly lights on the Vetta (not the FCB). Believe it

or

not, it will do this even with "no change" selected. What you

need

to keep in mind is that the Vetta and POD are VERY different in

the

amount of settings that are stored within each preset. In human
terms, the amount of time it takes the Vetta to process a patch
change is (like any amp) a slight latent period. In terms of midi
data, that slight period is a life time. If you need to see this

in

action (with pretty much any piece of gear), hook up a 2-in 1-out
midi thru box to the gear. While moving an expression pedal back
and forth, try firing commands at you gear with Midi-OX. I

suspect

you will experience some data loss. I am of the opinion (because

of

the fact that the Vetta fails at about a 10% rate instead of
anywhere near 100%) that about 1 5ms delay between PC and CC's

will

probably solve the problem. We (Xavier and I) are going to be
testing it shortly. FWIW, if you can detect a 5 ms delay in
something that already has an inherent latency (unlike an

expression

pedal) like a patch change, you have a far superior ear than I.

Chris

--- In fcb1010_uno@..., "Zsazsi" <m-zsolt@> wrote:

I do not really know much about the Vettas, but suspect that

they

work

similarly to the PODs and with an appropriate FCB stomp layout a

possible

workaround for Chris would be to keep the presets of the Vetta

and

the fcb

synchronised. I mean after programming the on/off status of the

stomps I

would hit save on the Vetta as well. If it only chokes messages,

the stomps

would reflect the sound image I believe.

Just a thought

Zsazsi

-----Original Message-----
From: fcb1010_uno@...

[mailto:fcb1010_uno@...] On

Behalf Of ossandust

What I mean by "(well...)" :
there is one final pending issue, mentioned by Sliding Billy

Hamilton

(you know - the thread "Missing Stomps (CC's) after PC "). As

promised

I'm starting some testing around that issue.
Only problem about that : as you mentioned yourself, adding a

short

delay after each PC message should be optional, if at all

added.

In

practice, this means (no more extra global setup code - you

know) that

an existing global setting has to go away in order to support

this.

I'll launch another message to find out which one.

Hi Chris!

I do believe every word you have written, of course. I just have jumped in
because I find myself forgetting about the most obvious thing many times. It
was not your case, I see. Sorry if it seemed some kind of stupid or waste
reaction, it was not my intent. I hope that Xavier implement a good
workaround for Your issue.

About the 5 ms delay. I programmed my patch pedals to transmit PC and tap
tempo immediately - it works fine with the blocking repetitive PC messages
global parameter. I believe that 5 msecs - although just a bit - but would
be clearly audible for anyone.

Regards

Zsazsi

Hoi Zsazsi,

Just to ket you know: I shared your concern about taptempo - so I did
a small test, by listening to NoteOn messages : using a test version
of the firmware (with added delay) I selected a patch and a linked
stompbox, both with NoteOn messages. Resulting in: NoteOn - 5ms delay
- NoteOn. The delay is hardly noticable . You can hear it, but the
time differences between the different notes of a chord played on the
keyboard are really more noticable... (ok, I'm not an educated
pianist, but still)

By the way, the built-in (CC-based) taptempo system is not influenced
at all by the delay : depressing a footswitch is only used to
calculate the tempo (time between 2 consecutive keypresses - averaged
over a few key presses), so an added delay wouldn't influence this.
The actual tap tempo CC message (which contains the calculated value)
is sent on key release(?!), so this too wouldn't be influenced by the
added delay.


--- In fcb1010_uno@..., "Zsazsi" <m-zsolt@...> wrote:

About the 5 ms delay. I programmed my patch pedals to transmit PC

and tap

tempo immediately - it works fine with the blocking repetitive PC

messages

global parameter. I believe that 5 msecs - although just a bit - but

would

be clearly audible for anyone.

I didn't mean to sound so offended either. With regards to the 5ms
thing, I was referring to hearing an EXTRA 5ms in an already latent
patch change (or other latent control). As I said, with any real
time control (like an expression) the 5ms would certainly be
noticeable. I hope that makes sense.

Chris

--- In fcb1010_uno@..., "Zsazsi" <m-zsolt@...> wrote:

Hi Chris!

I do believe every word you have written, of course. I just have

jumped in

because I find myself forgetting about the most obvious thing many

times. It

was not your case, I see. Sorry if it seemed some kind of stupid

or waste

reaction, it was not my intent. I hope that Xavier implement a good
workaround for Your issue.

About the 5 ms delay. I programmed my patch pedals to transmit PC

and tap

tempo immediately - it works fine with the blocking repetitive PC

messages

global parameter. I believe that 5 msecs - although just a bit -

but would

be clearly audible for anyone.

Regards

Zsazsi

-----Original Message-----
From: fcb1010_uno@...

[mailto:fcb1010_uno@...] On

Behalf Of sliding_billy_hamilton

I HAVE tried turning off all of the stomps on the Vetta (using

the

FCB to activate them) AND syncing them between the 2. If you

read

my original post, you will see the problem. The Vetta doesn't

just

miss CC's, it misinterprets them while processing the PC. For
example, the patch I am on has stomps 2 and 3 live, the patch I

am

going to has no stomps live. I hit the second patch and one of

the

stomps accidentaly lights on the Vetta (not the FCB). Believe

it or

not, it will do this even with "no change" selected. What you

need

to keep in mind is that the Vetta and POD are VERY different in

the

amount of settings that are stored within each preset. In human
terms, the amount of time it takes the Vetta to process a patch
change is (like any amp) a slight latent period. In terms of

midi

data, that slight period is a life time. If you need to see

this in

action (with pretty much any piece of gear), hook up a 2-in 1-out
midi thru box to the gear. While moving an expression pedal back
and forth, try firing commands at you gear with Midi-OX. I

suspect

you will experience some data loss. I am of the opinion

(because of

the fact that the Vetta fails at about a 10% rate instead of
anywhere near 100%) that about 1 5ms delay between PC and CC's

will

probably solve the problem. We (Xavier and I) are going to be
testing it shortly. FWIW, if you can detect a 5 ms delay in
something that already has an inherent latency (unlike an

expression

pedal) like a patch change, you have a far superior ear than I.

Chris

Hi Xavier!

Thanks for shearing Your experience and giving me some insight. I've never
used the calculated tap tempo since the POD supports it natively. My only
concern was that the delay sums up. When controlling an echo e.g., it would
give us 20 ms on the fourth generation of repeat etc...

Regards

P.s: You are the designer anyway, so that's just a brainstorming, it's up to
You how You are going to implement it, I trust You.