If I may, I can offer to help. I mean, just throwing an idea here. The community of UnO is quite techy so I can see a few extensive users which have background and can volunteer to be beta testers few

#UnO2

Thanks, I also tried if, else if and else constructs but had similar problems. I originally thought also that it might be "case" nesting problem. I may end up going back to my original UNO2 chip if I

#UnO2

I will have to look into it when I get home, which is not the first couple of days... Those hierarchical conditional statements (switch within a switch) were quite complicated to implement in assembly

#UnO2

That's interesting having problems as program flow and variables statements are fundamental. I am still waiting for a 1.3 to arrive so I cannot debug. Sorry, but yeah, ossandust can sort it out :-)

#UnO2

Yes, I know that $DEV is set correctly. I've spend hours on this and it seemed to work perfectly with the old UNO2 firmware so I'm pretty sure ether there is a bug in 1.3 or the 1.3 editor. Are you ru

#UnO2

The switch seems ok. However you did not include the call to the trigger so we cannot be sure that the$dev variable is other than Hammond. Try to debug that on entry to the function with Nord the $dev

#UnO2

I might end up going back to UNO2 1.2 . Many things that were working before no longer work on UNO2 1.3. I suspect that 1.3 has some serious bugs. Is anyone else experiencing issues with 1.3? Particul

#UnO2

Hey I'm not sure what I'm doing wrong here. If I have $DEV = "Hammond" then everything works fine in selecting different sweeps, but if it is not "Hammond" (it would be "Nord). All I get it the last H

#UnO2

The LG-FCB upgrade kit did exactly that (http://www.lg-fcb.com/) . It was on the market for a few years (with little to no success) - it has been replaced by the external TinyBox.

#UnO2

I agree with you. How many 30 year old electronic technology is still atound and being used today? I still own my Yamaha DX7 where I bought and installed a daughter board called E! that added numerous

#UnO2

Yes, it is amazing what you have done with 30 year old technology! You would think that at some point in time, Behringer could make an updated product with more memory and more functionality. But then

#UnO2

It might be nice to introduce this concept of a function in the UnO2 "programming language", (I would definitely call it "function", all programming languages do support parameterless functions withou

#UnO2

That would be awesome, thanks!

#UnO2

At some point in time constants have been part of the TinyBox (and now UnO2) programming language. I even used the exact same syntax "CONST #... ", next to "VAR $... " I removed it for the sake of sim

#UnO2

Any thought of using constants in Uno2? Right now I'm using a bunch of VARs that take up space but I don't modify. I could use absolute values in the cod but for readability I use VARS and maybe have

#UnO2

Maybe more of a Macro than a function as there are no function parameters or return value. I'm working on a project and tried this technique to reduce my footprint but was unsuccessful, because I stil

#UnO2

These commands are very similar : SwitchOn/SwitchOff sends all commands defined in the effect content, and adapts the switch LED if this effect is linked to an FCB1010 switch . SendTrigger sends all c

#UnO2

I noticed a few errors in the GuitRec Triggers (unfinished). Can't remember if that was me or you, but I fixed it and it works perfectly!! I am a bit confused about SendTrigger and SwitchOn but I'll d

#UnO2

The best way to save setup space, is by putting a series of commands which are sent by multiple presets in a trigger content, and then in all those presets have a single call to "SendTrigger nnn", ins

#UnO2

Hi, I'm going to explain too much but if you can, can you just tell me if my attached code can be condensed any more? Some information: I have the FCB1010 with UnO2 installed. I use Ableton live 11. I

#UnO2