Hi,

I am struggling trying to make the midi ports work in Wine.
Wine is, and must be 32 because my programs are 32 only.
My system in a 64, based on Slackware but highly customized (lot of things recompiled, not much left from Slack)
The system is a little bit multilib, but maybe not perfect in its 32bit side.

In Cubase with Wine 32 I can see all midi ports, but when I send data to it, nothing arrives (no error).

I got told to install WineAsio but the compilation errors never end because of 32/64 gcc issues. And anyway, would WineAsio really fix that problem?
I do not need audio from Cubase, just MIDI, but audio works from WaveLab.

What I miss the most in this problem is a deep understanding of where the midi is going, the different layers from Wine Cubase to the Linux output (kernel level).

Thank you!

ADMINISTRATORS, PLEASE DELETE THIS THREAD.
There is no problem with Wine, I just realized jack is the issue. Working on it and will eventually create another topic if needed.
THANKS!

WineASIO is good only for audio, not MIDI. However, installing WineASIO is strongly recommended. With it your Wine application will be visible to JACK as "native" JACK applications, and underruns will be less likely.

MIDI works just fine for me in Wine. I do not understand exactly what problem do you have. If you have trouble with MIDI in jack, you may need a2j from a2jmidid package. I also recommend Cadence as JACK frontend.

Personally I use repositories from http://kxstudio.sourceforge.net/ to get WineASIO (this way installing WineASIO is as easy as "apt-get install wineasio && wine regsvr32 wineasio") and wine-rt, among other useful things. Only drawback is that KXStudio is good only for Debian-based distributions.