Hello Guys!

Regarding the 1st and - so far the - only one thread (about more stomps), I
would recommend to try the firmware Yourselves if it really will/won't fit
You. Use it for more than a few sessions to see if it really does not behave
the way You want to. Differentiate between important and irrelevant features
- as every change in the software requires some or more resources from the
developer leaving less for the most important issues. Personal experience
might change Your preferences.

I had some premise idea about the way stomp boxes should behave. They were
quite different from the way Xavier implemented it finally, but I am really
grateful that he did in his way, because the result is of very high quality
and ergonomic. I could easily accomodate myself to it.

Else:

I am still a very contented user of UnO 1.02b, but discovered that in
stompbox mode if I change the state one of the stomps and go into preset
edit (stepping for a long time on the down switch), I get to somewhere that
I am not familiar with. Shouldn't it go to the same preset programming menu
level that comes alive when I go to edit immediately after selecting a
patch?

Regards

Zsazsi

Hey Zsazsi,

you might have found a bug - and, if so, I couldn't tell if this one
is (accidentily) solved in the latest version 1.02.c.
If you think I can easily reproduce the error, I can check it out with
my latest UnO version.
On the other hand, it looks like a problem which you can easily work
around by (re-)selecting a patch before going into preset programming
mode ?
If so I might stick to just mentioning this in the "known issues"
file, without actually solving the problem (as most developers, I'm a
lazy *** you know...)


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

I am still a very contented user of UnO 1.02b, but discovered that in
stompbox mode if I change the state one of the stomps and go into

preset

edit (stepping for a long time on the down switch), I get to

somewhere that

I am not familiar with. Shouldn't it go to the same preset

programming menu

level that comes alive when I go to edit immediately after selecting

a

patch?

Hi Xavier!

If you think I can easily reproduce the error, I can check it out

with

my latest UnO version.

I do believe that You can easily check this behaviour. Just change
the state any of the stomps from its preprogrammed value, then go
into edit.

On the other hand, it looks like a problem which you can easily

work

around by (re-)selecting a patch before going into preset

programming

mode ?

Exactly, it is not a big issue.

Regards

Zsazsi

Damn, a power user... :-)
You're right, Zsazsi, this is clearly an annoying bug - also apparent
with the latest firmware. If I would be charging money for this
firmware, I would definitely rush into providing a quick hotfix for it.
But for now I'll just leave it as is (I didn't look into the firmware
for some time - getting into the meticulous details of it again would
take me quite some extra time) - the bug is easy to avoid if you're
aware of it. So I will not only add it to the known issues list, but
I'll also update the UserGuide.
Thanks for letting us know !