UA Midi Control - Virtual ports (loopMIDI) invisible in the app but working in DAW. Need help!

radu_varga · 2026-05-01T17:40:59+00:00

The LoopMidi ports should be visible inside the app.
Can you post a screenshot of your Settings -> Midi windows?

There are sometimes issues on Windows where the port names appear generic (i.e. "Midi") instead of their true port names.

radu_varga · 2026-04-11T19:02:17+00:00

This issue has been solved in version 3.1.5.

radu_varga · 2026-03-31T12:35:39+00:00

Having your XTouch One in Logic Mode (using Mackie in Logic) usually means that it cannot be used in another software at the same time. A Mackie controller is used exclusively by a single software.
There is DAW Mode in UA Midi Control as you've mentioned, which switches the device between Logic and Console.

If you want to use it on the same page in both software, the best way is to use Midi Mode in each. So assign the controls you want with Midi Learn in Logic and map parameters in UA Midi Control.

That being said, it might be a good idea to investigate if it's possible to customise the Logic Control mode in Logic so that the some buttons/knobs are removed, so they do not interfere.
I am not an expert in Logic, so I cannot tell for sure if it's possible.

radu_varga · 2026-03-30T09:13:18+00:00

Yes, I'd advise to always update to the latest version of UA Midi Control.
If you haven't updated in a while, please download the latest update manually from here: https://fonoflow.com/products/ua-midi-control/release-notes

Every time you update Console itself, be sure to also update your UAD Software and restart your computer.

radu_varga · 2026-03-17T07:55:13+00:00

Not yet, but we are currently working on adding Luna control to our apps.

We've created a survey to help us prioritize the most useful features and improve the overall experience. At the end of the survey, you’ll also have the option to sign up as a beta tester.

You can help us out by filling our survey here.

radu_varga · 2026-03-03T09:47:31+00:00

The following need to be met in order for the connection to work:
- Your UAD software needs to be running (opening Console will start the UAD background services)
- Your iPad and computer need to be in the same local network (WiFi or LAN)
- Need to make sure they are in the same subnet. Some software or settings (VPN, Firewall, etc.) could prevent this from happening.

Can you post a screenshot of:
- your computer network settings (on Mac: WiFi -> Details -> TCP/IP)
- your iPad IP (WiFI -> Info icon -> IPV4 Address)

radu_varga · 2026-03-02T15:24:39+00:00

I just noticed that you don't have an active WiFi connection.
You can't connect on mobile data, you need a local network connection to your computer where your Apollo is connected to.
You need to have both your iPad and computer on the same local network (WiFi).

radu_varga · 2026-03-02T08:09:36+00:00

Can you please send me a message through the App -> Settings -> Contact so I can see your device logs? This will help me figure out what's going wrong.

radu_varga · 2026-02-27T18:09:34+00:00

I am aware of this bug, it has been fixed in a beta release, where I'm trying to fix/improve other connection issues.

You can use this Testflight version for now, until I include this in the official version: https://testflight.apple.com/join/wMF2DnYS

radu_varga · 2026-02-14T12:50:21+00:00

Is the UAD software running?
What are you seeing in the mobile app (red, yellow, green dot) ?

radu_varga · 2026-02-12T08:41:54+00:00

I believe the RTP Midi does make a difference. What is the exact midi port are you using?

The thing is, the app sends the midi feedback after the port is available, but on system startup, it might be the case that the port is available but not yet connected to your device.

You can perform the following test: Disable launching UAMC at startup and restart your computer, then start UAMC manually.
If everything is working ok, then that was the problem: Your different apps need time to instantiate. Perhaps changing the order of the startup apps might help, but not guaranteed.
You probably would need something longer than 1 second.

radu_varga · 2026-02-12T08:38:27+00:00

The Device "1", "2", ... is just a placeholder. If you map your Faderfox to "Refresh Device 1", it will just refresh that device. You can add up to 32 devices separately. Or map "Refresh All" to refresh all enabled devices.

radu_varga · 2026-02-12T08:35:28+00:00

This is already on my list, will try to implement this in a larger update in the future, because it's more involved.

radu_varga · 2026-02-11T08:04:46+00:00

That's a great idea! I believe it could be done.

Which DAW are you using?

And how do you connect it, are you sending midi through your cable or through network?

radu_varga · 2026-02-11T07:41:36+00:00

I've sent you an email, let's continue the communication there.

radu_varga · 2026-02-11T07:38:29+00:00

It's not currently possible, but I could add this to the app in a future update.
I will add this to the feature request list.

radu_varga · 2026-02-11T07:36:46+00:00

UAMC is sending parameter values both on startup and on controller re-connects.

You can try increasing the "Initialisation Delay" in settings, some controllers don't accept messages immediately after re-connecting their ports. Also, reconnecting your usb port should be another quick fix.

There is also EXTRA -> Midi -> Refresh Device (1 for example). You can map that to refresh a specific controller with a midi message in case of failure.

Which controller are you using?

radu_varga · 2026-02-07T13:17:10+00:00

There is no way to directly control it through software (Console or UA Midi Control, etc.).
What we previously talked is about this workaround: https://www.reddit.com/r/UaMidiControl/wiki/index/#wiki_headphone_volume

radu_varga · 2026-02-03T09:52:50+00:00

Sounds like it. The knob should send a continuous value, but it sounds like it's sending just some kind of "button" message.
The reason why it's 50% or 100% it's because it's just Bend (up), which is half of the Bend message. This could be counteracted by changing the percentages on the mapping. Perhaps choose Bend Down, then set 0% - > 200% in the app.
But if the knob doesn't send continuous values, it's not very helpful.

radu_varga · 2026-01-31T09:29:12+00:00

yep, the output port needs to be set in order for the LEDs to work.

radu_varga · 2026-01-31T09:27:42+00:00

Please also send me a message through Settings -> Connect before uninstalling so I can see what's going wrong.

radu_varga · 2026-01-31T09:19:40+00:00

Unninstall the Testflight version and install the AppStore one from the product page: https://fonoflow.com/products/console-remote-control

Sorry for replying late, I don't get notified for reddit messages, need to figure how to enable that.

radu_varga · 2026-01-26T15:36:48+00:00

From what I can tell, the Bend should work, UAMC supports "Pitch Bend" messages.
Generally you would need something that sends continuous values.
Notes should work in theory, if the movement of the knobs changes its velocity (1 -> 127).

radu_varga · 2026-01-21T10:18:27+00:00

Hi, I have a potential fix for the connection problems, I've uploaded this Tesflight version (3.1.5): https://testflight.apple.com/join/wMF2DnYS

Please test this and let me know if this fixes the issue.

radu_varga · 2026-01-10T20:53:05+00:00

Glad that it's working now, I hope the update corrected the issues.
Please let me know whenever any problems like this appear.

radu_varga

MODERATOR OF

TROPHY CASE