search for: qsynth

Try opening the sound tab in winecfg. It'll create a ALSA-based default configuration for you, which might automatically find the right MIDI channels. If it doesn't, try using a soft synth solution like timidity or qsynth. I think these automatically pick up on MIDI-supporting sound cards, too, plus extra MIDI channels that will definitely be detected by Wine will be exposed.

Hi, I have recently started using WINE with the wineasio driver to run my Windows audio apps. In Windows I did a lot of work using MIDI Yoke (a virtual 'MIDI cable' driver). The Linux equivalent is the snd-virmidi ALSA driver. I find, however, that WINE does not send MIDI messages throught the virmidi ports to Linux Apps. I have tried this on Ubuntu 8.04 and Puppy Linux 4.0 using WINE

Hey there, I'm a bit new to WINE, not used it much outside of when I used to play Diablo II on it a year or two ago. Anyways, another thing I'm currently experimenting with is music composition. I've got my Rosegarden (sequencer) and qsynth running over JACK, but frankly, the free soundfonts I've found have been pretty dire. The level of cheese involved is enough to kill a man. So I'm wondering whether anybody has any experience with having WINE doing terrible, horrible things with midi and JACK, since Propellerheads and d-lu...

...Print preview worked there OK. Also as I am a long time user of Noteworthy, I had to first install Noteworthy 1.75 from a CD then get the upgrade to v2.0 from the Noteworthy website. Print preview also worked OK in Noteworthy 1.75. I have Wine 1.1.21, Ubuntu Linux 8.10 and I am using fluidsynth/QSynth for midi playback.

Hi. Until Fedora 15, I used qsynth+Fluidsynth+alsa+biab and everything worked fine. But not anymore with Fedora 16. I can't see any midi drivers in band-in-a-box. I'm sure about my setup. Everything seems fine. I dont know which one is failing, but I suspect wine. The midi ports are ready: $ aconnect -o client 14: 'M...