On Thu, Sep 17, 2009 at 04:59:45PM -0700, 4625 wrote:IMHO this discussion is taking the wrong direction. I use MIDI a lot, exclusively on OpenBSD; both for playback, recording, editting and basic real-time "filtering". Feel free to ask for hints and to explain what you try to do with MIDI and -- most importantly -- with what MIDI hardware. Either privately or on the list, if you feel there's something others should know. To quickly summarize where OpenBSD is: - harware synths, keyboards, control surfaces etc... just work, and are fully usable for real-time stuff since few years. After all MIDI is a dumb serial port. - opl(4), pcppi(4) are almost useless and seem unmaintained, I have plans to work on them (or anything based on src/sys/dev/midisyn.h). - ports/audio/fluidsynth is almost usable as a real-time synth. There's a recent patch on ports@, making it look as hardware to MIDI players. It works, but is not as good as hardware synths, especially for real-time performance. I use hardware most of the time. - ports/audio/timidity: it's good for MIDI rendering. I'd love your issues to get solved, but I have much more urgent/fun things to work on. I use it sometimes to render .wav files. - midiplay(1) is in base. It works only with hardware, because it uses the (obsolete) sequencer(4) interface; this is being worked on, though. - ports/audio/midish works in all cases and does much more than midiplay(4), that's the tool i'm working on the most. HTH -- Alexandre
| Greg KH | Og dreams of kernels |
| Jens Axboe | [PATCH 31/33] Fusion: sg chaining support |
| Arnd Bergmann | Re: finding your own dead "CONFIG_" variables |
| Mark Brown | [PATCH 2/2] Subject: natsemi: Allow users to disable workaround for DspCfg reset |
| Tony Breeds | [LGUEST] Look in object dir for .config |
git: | |
| Brian Downing | Re: Git in a Nutshell guide |
| John Benes | Re: master has some toys |
| Matthias Lederhofer | [PATCH 4/7] introduce GIT_WORK_TREE to specify the work tree |
| Alexander Sulfrian |
