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

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

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

My guess is you are seeing the values as hex on output and entering them as decimal into the variables.

For users that don't want a programming language I think UNO 1.0.4 and the editor are super! I guess you will never please everyone, but I'm happy !

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

Roland implements checksum into most (if not all) of it's products and the same way. Without a valid checksum, I doubt if SysEX would work for any Roland product. If you can make VALUE a readable vari

That would be awesome, thanks!

#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

Maybe you have midi thru turned on when you are running the test. I think it has to be off but I might have that backwards.

You will need to write an UNO2 program of some sort, otherwise, you will get no MIDI. You should be able to find an example somewhere on this board. Essentially a new UNO2 controller is a blank slate

#UnO2

Well I'm on Windows and I have a stand-alone MIDI Monitor application on my system. I think when I downloaded UNO2 Control center it installed the stand alone MIDI Monitor application as well. So I ju

#UnO2

I can use MIDI Monitor with other devices and no pedals attached. You will not be able to use UNO2 editor however, unless the FCB-1010 is attached. I typically use MIDI Tools from Mountain Utilities f

#UnO2

I'm afraid not, Best to keep a backup copy of the text file. I ran into this too.

If I remember, I had to do some sort of memory initialization (in addition to exp pedal calibration), when I put my UNO firmware in. There should be no reason 1.0.4 should not work unless you have a b

#UnO2

As far as I know you cannot use SysEX output for Sweeps. I think I asked this question when I got UNO2 about a month ago. You would need to run your SysEX through an external program such as Bome MIDI

#UnO2

My guess is the issue iw with the Pedal 1 or Pedal 2 Commands which should only have 1 parameter (the sweep name) SWEEP A1 = SendMidi MyController CntrlChange 7 0-127 SWEEP A2 = SendMidi MyController

I noticed you have some stomps set so check to see if it is programmed into one of your stomps.