MicroBrute = No show !

Discuss problems and solutions.
Post Reply
rotallicso
Newbie
Posts: 16
Joined: 03 Jan 2012 17:15

MicroBrute = No show !

Post by rotallicso »

The Arturia Microbrute is USB class compliant and does show up in other iOS apps no bother.
However, it does not show up in Lemur ! But why ?

Typically when I connect any usb device it is fine, same when I use a midi device, so it's not user error

The only light I can shed on this is that the Microbrute shows up as two device names in one of the apps

It shows as 'MicroBrute -' and also as
'MicroBrute - MIDI Interface'
For both in and out on one IOS app, but only the first shorter name works !

I wonder if Lemur has an issue with this, two names or difficulty parsing the '-' or is the name too long ?

I assume the issue is with Lemur, but it could be unfair to assume just because it works in other iOS apps

Arturia are really slow at updating so I can see this being an annoying issue for some time, I need the MIDI din port for other duties

Cheers for any thoughts or confirmations etc
jaytee
Newbie
Posts: 4
Joined: 08 Oct 2014 16:57

Re: MicroBrute = No show !

Post by jaytee »

No idea why it's showing up in some apps but not in Lemur, however....

The reason that it shows up twice in the apps that recognize it is almost because the "MIDI interface" version refers to the MIDI DIN information that gets passed to/from the USB port, while the other listing is the MIDI information sent directly over the USB port. Make sense? Basically, because there are two ways to send/receive MIDI on your synth, it gives you two different port options to select from.
Softcore
Regular
Posts: 1613
Joined: 04 Nov 2012 08:34

Re: MicroBrute = No show !

Post by Softcore »

Try using FreEWI as a "midi bridge". ;)
nick_liine
Liine Staff
Posts: 285
Joined: 01 Oct 2010 11:06

Re: MicroBrute = No show !

Post by nick_liine »

There was an issue reading the port names with certain devices (Novation X-Station for example). We didn't test specifically with MicroBrute, but hopefully it should be the same issue. Fix is included in the forthcoming 5.2 update.
Post Reply