Installing Timidity or FluidSynth is not enough. Software sequencers like Timidity and FluidSynth This is not necessarily enough to make it work in Wine because Wine may end up using the silence "MIDI through" port. Sound from aplaymidi -px:y file.mid is the basic proof that your MIDI setup is working in Linux. That's how applications using the OSS API to play MIDI still get output from ALSA sequencers like Timidity. The Linux kernel includes a mapper from OSS to ALSA. Here's output from a system equipped with both FluidSynth and Timidity simultaneously (and FluidSynth started first):Ĭlient 128: 'FLUID Synth (31186)' 128 is the port number that software sequencers like Timidity and FluidSynth use by default. If other ports are listed along with their number, verify that aplaymidi -p128:0 myfile.mid produces sound. It (presumably) sends bytes down the serial port where you have no HW connected, so you hear no music. Of these, MIDI through is of no use to you unless you have dedicated MIDI hardware. On Linux, aconnect -o lists the MIDI output ports known to ALSA. There is no point in writing to the Wine bug tracker if MIDI does not work on your UNIX system. 3.1 Useful information to include in your bug report.2.2 Selecting the Output - the MIDI mapper.1.1 Software sequencers like Timidity and FluidSynth.MIDI playback on Mac OS was historically QuickTime-based, I believe. It used a simple and familiar-sounding Roland SoundCanvas-based instrument set, similarly to Windows' built-in midi playback, though with some annoying oddities and idiosyncrasies. (And reverb.) As of the past couple of OS versions, though, I don't know of any simple and functional way to just play a damn midi file without opening it in my Win7 VM, which is disappointing. It would be really nice if someone would make a simple and functional freeware midi player that could take up the task since QuickTime dropped support for it. I've not found one that really does the job satisfactorily. To expand on what Fraggle said about high-quality instrument sets, though, Apple has bundled a ton of their old products and newer acquisitions into their music production software and is selling it for pennies on the dollar compared to what any competitor can afford to do. Last I checked you could get MainStage, a program intended to assist with live performances, for $15 on the app store, and it includes the entire GarageBand instrument/sample/loop library and all of the expansion packs that were ever released for it. There are definitely some exceptionally nice instruments in there, some of which I've even ported over for my own personal use in Reason, but it's not relevant to standard MIDI playback (which IMO is best suited to the simple and familiar sounds that most MIDIs are being composed with in the first place). In general the built-in MIDI on Macs is really good, I expect they've invested a lot in making it good since lots of musicians use Macs. I dunno where this came from, but it's never been the case. MIDI as an interface is "really good" in OS X. But, the software synth used to play back SMF sequences is hot garbage. The issue is that people confuse SMF sequences with MIDI as a standard - they are not the same. Here are the problems with any SMF playback through OSX "Software synth": The problem is QuickTime does not handle MIDI program changes properly. Program change messages are not acknowledged until a note plays, so there is a lag behind by one note. * Some effects are not supported or interpreted incorrectly. The best example I can give is Doom II's Title screen music that inserts pitch bends after keyoffs.
0 Comments
Leave a Reply. |