Midi coming to UAFX pedals

3.5 years since Release day ... asked for since Day 1 .... better late than never ! I good move I never thought UAD would do.
 
I know this is a big deal, and it’s great UA is finally learning that MIDI exists, but my first thought was “now we have another MIDI connection format to deal with”. Now some pedals need 5-pin, some need 1/8”, and some need USB. Yay.

Worth re-iterating.

Your Midi FSW Controller / Pedal *must* have a USB Host built in. If it doesnt youll need to use soething like the DoreMidi UMH-21 or the Behrringer Go Midi Host.

A 5 Pin Midi to USB Cable will not work

Sadly .... most Midi FSW Controller / Pedal do not have a USB Host built-in

Ben
 
Last edited:
USB MIDI is dumb, 3,5mm TRS is okay, as long as the device comes with a compatible Type A/B to DIN adapter, DIN is best.
 
All good. The [normal] MC6 does not have a USB Host built-in so even if you had it, it wouldn't work with these pedals. MC6 Pro or MC8 Pro both have the USB Host Built-in :)
Desaster Area have the USB Host. If you’d be fine with 3 buttons like clean/dirt/lead you could get the 3 buttons one for 150 bucks. Small and great.
 
Desaster Area have the USB Host. If you’d be fine with 3 buttons like clean/dirt/lead you could get the 3 buttons one for 150 bucks. Small and great.

And then add another one for the next UAFX pedal. And yet another one for a third. Unless they allow you to use a Hub, which could be possible. But in that case you'd likely have to deal with saving things on multiple pedals.

Anyhow, goes to show how lame UA were during development. They either had no decent testers or decided to not listen to them, because otherwise those pedals would've had genuine MIDI support straight from the start.
 
And then add another one for the next UAFX pedal. And yet another one for a third. Unless they allow you to use a Hub, which could be possible. But in that case you'd likely have to deal with saving things on multiple pedals.

Anyhow, goes to show how lame UA were during development. They either had no decent testers or decided to not listen to them, because otherwise those pedals would've had genuine MIDI support straight from the start.
It is puzzling. Just as pedal FW update before app update.
Just weird

But they do sound better for my use case then literally anything but my amps.
 
And then add another one for the next UAFX pedal. And yet another one for a third. Unless they allow you to use a Hub, which could be possible. But in that case you'd likely have to deal with saving things on multiple pedals.
I think you should be able to do something like this:

MIDI controller with USB host (or MIDI 5-pin -> USB box like the CME H2MIDI Pro) -> USB hub with 4+ ports -> UAFX pedals.
 
I think you should be able to do something like this:

MIDI controller with USB host (or MIDI 5-pin -> USB box like the CME H2MIDI Pro) -> USB hub with 4+ ports -> UAFX pedals.

Sure. There's one video (from Pauly maybe?) where that very scenario is described. But boy oh boy - you'd have to purchase and rearrange your entire MIDI infrastructure to get these pedals integrated - what a fail on UA's behalf.
 
Watching the Morningstar video..that save functionality seems really dumb. Every time you store the preset, instead of overwriting the current one it will create a new preset and automatically assign it to that PC slot. This will mean that for every stored tweak you start piling up unwanted presets visible in your mobile app.

It doesn't even seem to use the existing preset name for these. In the video the user saves a preset called "Blended rocks" and the new preset becomes "Lion 2", basically "pedal name + running number". Now imagine that you try to work with your pedal to build a set of presets for your live setup. By the time you are done, you'd likely have presets "Lion 2", "Lion 3", and "Lion 4". How do you know what each preset was based on, what it was supposed to do? You'd have to have the app open at all times to see this, rename those presets as you complete them or rely on your MIDI controller for preset naming. At minimum it should call the preset "Blended rocks 2" so you always have a reference to its starting point.

If they want to do it like that, why not use a versioning data model where it just collects versions under that preset instead of fully separate presets? With a version model you could always rollback your changes to a past version if needed.
 
Sure. There's one video (from Pauly maybe?) where that very scenario is described. But boy oh boy - you'd have to purchase and rearrange your entire MIDI infrastructure to get these pedals integrated - what a fail on UA's behalf.
The smallest 4 port USB hub I have is pretty tiny so it's not necessarily that difficult to cram under your board in the same way I cram my Strymon Conduit for 1/4" TRS MIDI.

While I agree it's a lot more cumbersome than having a 1/4" or 1/8" TRS MIDI jack, what can they really do when they have decided to paint themselves into a corner from day one?
 
Watching the Morningstar video..that save functionality seems really dumb. Every time you store the preset, instead of overwriting the current one it will create a new preset and automatically assign it to that PC slot. This will mean that for every stored tweak you start piling up unwanted presets visible in your mobile app.

Yeah, I've seen that in the Henning Pauly video already. It's every bit as stupid as it gets.

If they want to do it like that, why not use a versioning data model where it just collects versions under that preset instead of fully separate presets?

Or how about they'd just do it like any sane person on earth would expect? Such as in "saving is saving"? They could possibly offer an additional "safety net" doing things as they are right now in the background, but as a main solution?
 
While I agree it's a lot more cumbersome than having a 1/4" or 1/8" TRS MIDI jack, what can they really do when they have decided to paint themselves into a corner from day one?

Sure. And it's possibly still better than having no MIDI at all if you invested some money in their ecosystem already.
But as you've mentioned already as well: It must remain a mystery how they could just keep coming up with new MIDI-free pedals when everybody and their mum was already asking for it when they released the first UAFX models.

Let's take some bets: When they release anything new, will they add genuine MIDI support or just be like "hey, we have USB-MIDI, should be fine for our users!"?
 
Or how about they'd just do it like any sane person on earth would expect? Such as in "saving is saving"? They could possibly offer an additional "safety net" doing things as they are right now in the background, but as a main solution?
You mean "save = overwrite preset"? Yeah that would be the most sensible way to go about it. I don't think anyone expects their preset to change to a different one, and we are not talking about something complex here, just pedals with a limited amount of controls.

My guess is that this might have something to do with the artist presets. You wouldn't want people overwriting artist presets...but with those you could simply make a copy in user space with the same name and from then on, that's the preset that gets modified. That's afaik how HX Stadium will work for factory presets. Instead UA applied this functionality to all presets.
 
Back
Top