search for: aconnect

I can run most midi apps in wine through timidity with no problem but there are quite a few apps which don't allow you to assign the midi output to timidity such as Media Player Classic or WM player 6. They try to use the windows default which is of course MS synth or Emu10k1. There must be a way of mapping the midi output in wine from such apps to timidity but I just can't get it to

...Using timidity, I've been able to listen to MIDI files with Linux on a machine with an Intel 801/AC'97 chip. However, with Wine, I've had trouble. Log messages show that the first MIDI output port is used. This happens to be 'MIDI Through' 62:0, not Timidity on port 128:0. $ aconnect -ol shows the list of output ports. I have no idea what port 62:0 does (perhaps send bytes down the serial port??) $ aplaymidi -p 128:0 foo.mid is needed to hear something. $ aplaymidi -p 62:0 foo.mid causes nothing to happen. It exits after some time. How can I have w...

...playmid -p128:0 LVL1.MID worked fine as well. 2) in Wine-- I downloaded the MCI shell as advised by the Wiki (http://wiki.winehq.org/MIDI?highlight=%28midi%29) and was able to play LVL1.MID after selecting the mapper as instructed in the "Since wine-1.1.41.." instruction set. Because my aconnect -o reads as follows Code: za dec 17 02:06 motub Marbles $: aconnect -o client 14: 'Midi Through' [type=kernel] 0 'Midi Through Port-0' client 16: 'C-Media CMI8738' [type=kernel] 0 'C-Media CMI8738 MIDI' client 17: 'OPL3 FM synth' [type=kernel]...

...onics Nova System). I have an M-Audio Uno USB MIDI interface on my Fedora 15 laptop and it is working correctly (I can successfully capture SysEx dumps using amidi, etc.). The output of `amidi -l` is: > Dir Device Name > IO hw:1,0,0 USB Uno MIDI Interface MIDI 1 > The output of `aconnect -o` is: > client 14: 'Midi Through' [type=kernel] > 0 'Midi Through Port-0' > client 20: 'USB Uno MIDI Interface' [type=kernel] > 0 'USB Uno MIDI Interface MIDI 1' > Winecfg (version 1.3.24) shows the device in the Audio tab on the ALSA Dr...

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

...ntil 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: 'Midi Through' [type=kernel] 0 'Midi Through Port-0' client 129: 'FLUID Synth (6500)' [type=user] 0 'Synth input port (6500:0)' And I can clearly listen this: $ aplaymidi -p129:0 LullabyBrahms-C.mid But BIAB doesnt find midi drivers. The sam...

I am a rank newbie to Linux and wine. I am running Ubuntu Dapper on an AMD 1800 mhz machine, wine 0.9.15 Everything I have read says use the installer to load windows programs. Where is the installer? Thanks, -- Ron Thompson On the Beautiful Florida Space Coast, right beside the Kennedy Space Center, USA http://www.plansandprojects.com My hobby pages are here: