From: Jaroslav K. <pe...@su...> - 2003-05-09 10:45:19
|
On Fri, 9 May 2003, Chris Cannam wrote: > Jaroslav Kysela wrote: > > Note that the SYNTH ports should support SNDRV_SEQ_EVENT_SAMPLE* events. > > It means direct wavetable synthesis not MIDI event communication. > > OK, now I'm confused again. Are you saying that a soft synth that > can only be driven via MIDI should not describe itself as a SYNTH? > If so, how do I know it's a synth? > > My interpretation so far has been that most soft synths should set > SYNTH, APPLICATION and possibly SAMPLE if they're sample-based, > whereas a sequencer like Rosegarden should set APPLICATION and > nothing else. Do I have that wrong? > > (And I don't know of any soft synths that are always GM devices, > so I'm doubtful -- as I mentioned in another email -- whether they > should be setting GM or not.) Note that we might change the define if it cause problems. But here is interpretation of flags: SNDRV_SEQ_PORT_TYPE_MIDI_* defines are for client which understands the midi v1.0 commands and extensions SNDRV_SEQ_PORT_TYPE_SYNTH define is for clients which can do direct wavetable synthesis (used by modplayers etc.) SNDRV_SEQ_PORT_TYPE_APPLICATION is for an application (sequencer or editor) - it doesn't apply for software MIDI synthesizers nor for wavetable direct synthesizers in the user space I think that your confusion is that we separate MIDI synthesizers (clients) and direct wavetable sythesizers (clients). Jaroslav ----- Jaroslav Kysela <pe...@su...> Linux Kernel Sound Maintainer ALSA Project, SuSE Labs |