14 Jan
2006
14 Jan
'06
3:59 p.m.
On Friday 13 January 2006 10:40, linux-audio-user-request(a)music.columbia.edu
wrote:
How can I get my WINE applications to see my alsa MIDI
ports?
I have the line about OSS in .wine/config uncommented. MIDI ALSA ports work
fine through their OSS emulation.
I have, if I remember, had mixed success with ALSA directly with different
WINE version working, others not.
I never had it work using Jack.
I have read some reports of people using Band-in-a-Box
and Jammer with
WINE, with varied success. I wanted to try using several of my Windows
MIDI apps (Jammer, OneManBand, some synth editors) under WINE, but when
I am able to get the application to work, it says there are no MIDI
devices available, except the MIDI mapper for output, which seems to do
nothing for me. How can I get these applications to see a MIDI input
and MIDI output port that I can route to somewhere useful?
Jammer will crash with newer wine versions. Previous versions had the program
come up and play. The style loading dialogs were usable but did not display
or work correctly.
Other apps:
XGEdit -- operates. Its rightmost column of buttons (sound program selection)
does not appear at all.
Tabledit -- works 100%
Abcmus -- works 100% . There is a wealth of music around in abc format which
is good old 7-bit ascii and was once the mainstay of unix music coding.
Tabledit will import abc files as well.
Tracktion -- come up, samples all the VSTs, displays but does not play. Its
child-dialogs do not appear but function control/F4 "closes" them. This one
is tantalizing close but so far!
Cakewalk -- heard tell old version once worked in WINE. New ones will not.
Most MIDI programs that worked or almost worked on older WINEs will crash now.
Their custom controls are usually the problem.