Arturia MicroFreak - Midi Control Center problems

[krussedull]

I have an Arturia MicroFreak that comes with a propriotary setup software for windows.
It's called Midi Control Center, is used for backing up presets, upgrading firware etc, and is found here:
https://www.arturia.com/products/hardwa ... /resources

So, this is Window$ software, but it runs fine in Wine, except ...there is some problem.

It will not connect properly to the MicroFreak, it just hangs and then crash.

Here's the catch. This only happens in EndeavourOS! ..which happen to be the distro I've switched to from Linux Mint.
The thing is though, it works fine when I boot into a live-usb of LinuxMint.

So, Linux Mint has a lot of stuff pre-installed, so I’m guessing that's why.
I cannot find what exactly it is that I'm missing installed on my EndeavourOS,

any ideas?

I have read this, but cannot really understand what I’m missing
https://wiki.archlinux.org/title/Wine#Sound

…and I have installed lib32-pipewire (which made for example MIDI-OX work properly on Wine)

Thanks on any input here, I'm stuck!

[Impostor]

Maybe you need some of these? I needed them for midi in Wine for Rebirth:

libasound2
libasound2:i386
libasound2-plugins
libasound2-plugins:i386

[elerale]

Hello,

I have several Arturia gears but I was never able to get this bl**dy sofware running on Wine.
Most of all, I have never seen anybody that was able to.

It can be an interesting thread

Cheers
Erwan

[sysrqer]

Just tried it for my keystep but doesn't work. Such a shame, it would be so useful.

[krussedull]

Maybe you need some of these? I needed them for midi in Wine for Rebirth:
libasound2
libasound2:i386
libasound2-plugins
libasound2-plugins:i386

What distro are you on? I'm guessing I have these installed as I have all standard Alsa stuff installed, but I'm not sure, couldn't find out which package these you mention come from.

I have several Arturia gears but I was never able to get this bl**dy sofware running on Wine.
Most of all, I have never seen anybody that was able to.

Just tried it for my keystep but doesn't work. Such a shame, it would be so useful.

I tested quickly with the latest Linux Mint ISO and it found my MicroFreak, so I think there is hope!

I'm gonna boot into an EndeavourOS ISO one of these days and just install everything, brut force the whole damn thing.
I'm not reverting to Mint dammit

Still open for other suggestions!

[sysrqer]

Let us know if you find a way. I'm on arch as well but it's encouraging to hear that you got it to work in mint.

[Impostor]

Maybe you need some of these? I needed them for midi in Wine for Rebirth:
libasound2
libasound2:i386
libasound2-plugins
libasound2-plugins:i386

What distro are you on? I'm guessing I have these installed as I have all standard Alsa stuff installed, but I'm not sure, couldn't find out which package these you mention come from.

Mint. Their arch equivalents supposedly are:
alsa-lib
alsa-plugins
lib32-alsa-plugins
lib32-alsa-lib

But I may misunderstand your problem: I thought you needed to have midi in Wine for configuration software for your midi controller to work. But if a live mint.iso works for your problem, and since afaik a live mint.iso doesn't even come with wine (or has that changed?), I guess you have a different problem?

I see EndeavourOS comes with pipewire as audioserver. Mint (as of yet) doesn't. Does pipewire interfere with alsa midi and wine?

[sysrqer]

Just tried the udev suggestion here https://wiki.winehq.org/Hardware#USB

Didn't work

[krussedull]

Mint. Their arch equivalents supposedly are:
alsa-lib
alsa-plugins
lib32-alsa-plugins
lib32-alsa-lib

Thank you for posting the details man.
I checked and I actually got all those installed.
Unfortunately, the Midi Control Center software still just hangs when talking to the MicroFreak hw.

Code: Select all

$ pacman -Ss alsa-lib           

extra/alsa-lib 1.2.10-2 [installed]
    An alternative implementation of Linux sound support
multilib/lib32-alsa-lib 1.2.10-2 [installed]
    An alternative implementation of Linux sound support (32 bit)

$ pacman -Ss alsa-plugins
extra/alsa-plugins 1:1.2.7.1-2 [installed]
    Additional ALSA plugins
multilib/lib32-alsa-plugins 1.2.7.1-2
    Additional ALSA plugins (32-bit)

$ pacman -Ss lib32-alsa-plugins
multilib/lib32-alsa-plugins 1.2.7.1-2 [installed]
    Additional ALSA plugins (32-bit)

$ pacman -Ss lib32-alsa-lib
multilib/lib32-alsa-lib 1.2.10-2 [installed]
    An alternative implementation of Linux sound support (32 bit)

But I may misunderstand your problem: I thought you needed to have midi in Wine for configuration software for your midi controller to work. But if a live mint.iso works for your problem, and since afaik a live mint.iso doesn't even come with wine (or has that changed?), I guess you have a different problem?

No you understand correctly!
I want to get this software working with arch/endeavvouros through wine.

I wanted to debug if I could get it working at all, so I tried an Linux Mint ISO (since this was my previous distro and I know it comes preinstalled with shitloads of stuff to make things easy for users). I installed wine + this midi control center while in "iso modus" (basically just using ramdisk etc) and it worked, which confirms that this is not a general wine/linux problems, it actually does work. ...if I can just find all the requirements

I see EndeavourOS comes with pipewire as audioserver. Mint (as of yet) doesn't. Does pipewire interfere with alsa midi and wine?

Good point, maybe it's worth debugging. I'm not really sure how pipewire does the midi interfacing to also etc, but pipewire is getting really close to 1.0 release... Then again, maybe I just have to put on the gloves an digg into this direction.

..unless someone else has some brilliant obvious ideas

[sysrqer]

Is there any way to know what options the arch package of wine/wine-staging uses at compile time?

https://wiki.winehq.org/Building_Wine

libusb 1.0 libusb-1.0-0-dev libusbx-devel libusb USB device support Install only if you're using an application that accesses a USB device directly. (Note that many applications using USB devices do so through HID.) See also Hardware.

Interesting point about HID. The wiki says:

Wine includes support for HID kernel drivers, and user-space access via hid.dll and via direct ioctls.

I might try the AUR git version of wine and make sure that it libusb used as a dependency. I don't know what that HID stuff means though.

[krussedull]

@sysrqer
Interesting find!

Is there any way to know what options the arch package of wine/wine-staging uses at compile time?

Yes I believe there is. If I'm not wrong you can go here
https://archlinux.org/packages/multilib/x86_64/wine/
..then press "Source Files" in the upper right corner
..then press PKGBUILD
which sends you here
https://gitlab.archlinux.org/archlinux/ ... n/PKGBUILD

I could not see any referance to libusb here, nor in any of the AUR wine packages.You might be on a hot trail here..

So I tried the same approach for Linux Mint, which is based on Ubuntu, which is based on Debian.
https://packages.debian.org/bookworm/wine
-> "Developer Information" (right "menu")
https://tracker.debian.org/pkg/wine
-> "versioned links" (left "menu") -> 8.0.1 "box icon"
https://tracker.debian.org/media/packag ... .1repack-3
which lists libusb-1.0-0-dev as a dependency

I searched the changelog and found this ref to libusb
https://tracker.debian.org/media/packag ... .1repack-3

Code: Select all

wine-unstable (1.5.1-1) unstable; urgency=low

  [ Michael Gilbert ]
  * New upstream release 1.5.1, released Mar 30, 2012.
    - Built-in JavaScript now preferred over Gecko in most cases.
    - Support for scalable font resources.
    - Fixes for audio and video playback.
    - Support for script decoding in JScript.
    - Various bug fixes.
  * Set --git-ignore-branch in build scripts
  * Don't set wine as 'Multi-Arch: allowed' (closes: #676498)
  * Ship a wine64-bin helper package

  [ Hilko Bengen ]
  * Remove libusb dependency
  * Include localized manpages

 -- Michael Gilbert <mgilbert@debian.org>  Tue, 12 Jun 2012 18:08:15 -0400

...

wine-development (6.23~repack-2) unstable; urgency=medium

  * Correct shift-overflow flag for clang on arm64.
  * Add libusb-1.0-0-dev to the build dependencies.
  * Build with system zlib PE only on i386 and amd64.
  * Fix installation paths for fonts and nls files (closes: #1010269).

 -- Michael Gilbert <mgilbert@debian.org>  Thu, 05 May 2022 18:09:14 +0000

I'm not gonna pretend to know exactly what's going on here, but seems to be removed from "wine-unstable" in 2012 and added to "wine-development" in 2022.

I'm not to familiar with how to actually build stuff on arch, but I guess the next approach would be to make a copy of
https://gitlab.archlinux.org/archlinux/ ... n/PKGBUILD
locally and try to add libusb and then build..

..it's definitely not something I know how to do, and right now I don't have too much time to investigate, but if someone with knownledge on how to modify these PKGBUILD files could chip in maybe we can debug this to the end

[autostatic]

Can't help right away but I own a Beatstep Pro and last week I tried Midi Control Center with Wine but didn't work at all, wouldn't even install. Which Wine version are you using? And did you install it or just copy it over from an existing installation? If I can get it to work I might be able to help you debugging. Thanks!

[sysrqer]

Can't help right away but I own a Beatstep Pro and last week I tried Midi Control Center with Wine but didn't work at all, wouldn't even install. Which Wine version are you using? And did you install it or just copy it over from an existing installation? If I can get it to work I might be able to help you debugging. Thanks!

I wasn't able to get it installed, I can get the software centre working but installation of the Midi Control Center fails because it can't find the OS or something.

[sysrqer]

I'm not to familiar with how to actually build stuff on arch, but I guess the next approach would be to make a copy of
https://gitlab.archlinux.org/archlinux/ ... n/PKGBUILD
locally and try to add libusb and then build..

..it's definitely not something I know how to do, and right now I don't have too much time to investigate, but if someone with knownledge on how to modify these PKGBUILD files could chip in maybe we can debug this to the end

Nice digging! You should have libusb already because it's part of core. I think you can change the PKGBUILD when you install it through paru/yay so I would just use https://aur.archlinux.org/packages/wine-staging-git and add libusb to the right section (not sure which, I guess opts?). I don't know if this would work though. I'm a bit puzzled though because surely the machines that compiled the packages had core on them? Or can you build stuff just on base-devel?

I'll give it a try soon.

[autostatic]

I wasn't able to get it installed, I can get the software centre working but installation of the Midi Control Center fails because it can't find the OS or something.

If you skip installing the MIDI driver it will install.