Re: KMid (was Re: [fluid-dev] Re: lost connection to Jack server)
On Wednesday, October 21, 2009, jimmy wrote: I used to use Kmid, but no one ported it to Qt4/Kde4 I'm already starting the adoption process. Alright, good to know. You got SVN/CVS, discussion group for it somewhere? Anonymous SVN repository (provisional) svn://anonsvn.kde.org/home/kde/trunk/playground/multimedia/kmid2/ Compile it with KDE 4.2 or later. Little user documentation, at this moment: http://userbase.kde.org/KMid2 Regards, Pedro ___ fluid-dev mailing list fluid-dev@nongnu.org http://lists.nongnu.org/mailman/listinfo/fluid-dev
Re: KMid (was Re: [fluid-dev] Re: lost connection to Jack server)
On Friday, October 23, 2009, j...@resonance.org wrote: Quoting Pedro Lopez-Cabanillas pedro.lopez.cabanil...@gmail.com: Jack MIDI may be the right thing for Ardour, but it is a big nuisance for everything else. For instance, FluidSynth. I'm NOT an Ardour user, and I'm certainly not going to use any application requiring exclusively Jack MIDI. I'm curious what you find to be a nuisance about Jack MIDI? I haven't used it much yet myself, so I don't yet have much of an opinion. FluidSynth now has support for Jack MIDI, if you weren't already aware of that. I usually end up having to run something like a2jmidid to bridge ALSA sequencer clients/devices with Jack MIDI. I like the idea of the whole audio and MIDI pipeline being synchronized though! The API seems easy enough (just a raw MIDI stream for the most part, without running status). I'm aware of your Jack MIDI driver for FluidSynth. It is included in 1.0.9, following the same design of other MIDI drivers. That is one of the problems and nuisances. Current Jack drivers in FluidSynth running independent Jack processes for audio and MIDI is against the goals of audio and MIDI pipelines being synchronized. Other synths have experienced the same nuisances recently :) http://article.gmane.org/gmane.linux.audio.users/56686/ IMO, or FluidSynth becomes a fair Jack MIDI client, or it should drop the driver entirely. Returning to the subject, the goal of having audio and MIDI aligned may be sound for a soft synth like FluidSynth, or a DAW application like Ardour, where MIDI is subordinated and auxiliary regarding to audio. But, where is the advantage of Jack MIDI for a pure MIDI/Karaoke player like KMid? Regards, Pedro ___ fluid-dev mailing list fluid-dev@nongnu.org http://lists.nongnu.org/mailman/listinfo/fluid-dev
Re: KMid (was Re: [fluid-dev] Re: lost connection to Jack server)
Quoting Pedro Lopez-Cabanillas pedro.lopez.cabanil...@gmail.com: I'm aware of your Jack MIDI driver for FluidSynth. It is included in 1.0.9, following the same design of other MIDI drivers. That is one of the problems and nuisances. Current Jack drivers in FluidSynth running independent Jack processes for audio and MIDI is against the goals of audio and MIDI pipelines being synchronized. Other synths have experienced the same nuisances recently :) http://article.gmane.org/gmane.linux.audio.users/56686/ IMO, or FluidSynth becomes a fair Jack MIDI client, or it should drop the driver entirely. Good to know! It hadn't occurred to me that they would be unsynchronized at that point. Will fix it. Thanks for mentioning this. Returning to the subject, the goal of having audio and MIDI aligned may be sound for a soft synth like FluidSynth, or a DAW application like Ardour, where MIDI is subordinated and auxiliary regarding to audio. But, where is the advantage of Jack MIDI for a pure MIDI/Karaoke player like KMid? If a user is already using Jack as their audio subsystem, it seems convenient to me to also use it for MIDI. Same clients, same routing software, etc. But yes, it does seem less useful when playing back pure MIDI files. Regards, Pedro Regards, Josh ___ fluid-dev mailing list fluid-dev@nongnu.org http://lists.nongnu.org/mailman/listinfo/fluid-dev
Re: KMid (was Re: [fluid-dev] Re: lost connection to Jack server)
On Wednesday, October 21, 2009, jimmy wrote: Would it be better depending on just QT4, or QT4.5, instead of KDE. I am a KDE user, so my preference is keeping KMid as a KDE application. Jack-midi could probably help on win32 and even Mac, I think??? Jack MIDI may be the right thing for Ardour, but it is a big nuisance for everything else. For instance, FluidSynth. I'm NOT an Ardour user, and I'm certainly not going to use any application requiring exclusively Jack MIDI. Regards, Pedro ___ fluid-dev mailing list fluid-dev@nongnu.org http://lists.nongnu.org/mailman/listinfo/fluid-dev
Re: KMid (was Re: [fluid-dev] Re: lost connection to Jack server)
Hello Pedro, Quoting Pedro Lopez-Cabanillas pedro.lopez.cabanil...@gmail.com: On Wednesday, October 21, 2009, jimmy wrote: Would it be better depending on just QT4, or QT4.5, instead of KDE. I am a KDE user, so my preference is keeping KMid as a KDE application. Jack-midi could probably help on win32 and even Mac, I think??? Jack MIDI may be the right thing for Ardour, but it is a big nuisance for everything else. For instance, FluidSynth. I'm NOT an Ardour user, and I'm certainly not going to use any application requiring exclusively Jack MIDI. I'm curious what you find to be a nuisance about Jack MIDI? I haven't used it much yet myself, so I don't yet have much of an opinion. FluidSynth now has support for Jack MIDI, if you weren't already aware of that. I usually end up having to run something like a2jmidid to bridge ALSA sequencer clients/devices with Jack MIDI. I like the idea of the whole audio and MIDI pipeline being synchronized though! The API seems easy enough (just a raw MIDI stream for the most part, without running status). Regards, Pedro Regards, Josh ___ fluid-dev mailing list fluid-dev@nongnu.org http://lists.nongnu.org/mailman/listinfo/fluid-dev
Re: KMid (was Re: [fluid-dev] Re: lost connection to Jack server)
--- On Wed, 10/21/09, Pedro Lopez-Cabanillas pedro.lopez.cabanil...@gmail.com wrote: I used to use Kmid, but no one ported it to Qt4/Kde4 yet, not sure how long before it would be called an orphan. I'm already starting the adoption process. Pedro, Alright, good to know. You got SVN/CVS, discussion group for it somewhere? Would it be better depending on just QT4, or QT4.5, instead of KDE. I prefer lighter-weight apps that works well with simple interface, nothing fancy. I just read a couple of articles on Slashdot about Pulse Audio. The project lead, and some of their developers want it on every desktop and claimed that latency is good (???, !...@#(!^#!!!), that 20-second audio buffer would help them make less interrupt calls to save power or so. Yeah, right... Saving energy on a few lousy hardware interrupts and blast away on the speakers, or their continuous reconfiguration daemon. Their idea of playing music is to use their couch-potato ears. No wonder the rap craps are everywhere and they think they are great musicians, too. KMid is about 10 years old. It is time for a revamp. My plans for it are: * Remove the deprecated OSS /dev/sequencer interface support. It has been dropped from OSSv4, anyway. * A fair ALSA sequencer implementation: don't create/destroy the client and port instances on each play/pause/stop action. This would allow the usage of KMid with a MIDI patchbay application like qjackctl. So you spent sometime with the adopted kid (uh... code) already :-) * MIDI Output implemented on pluggable backends. First one will be the ALSA sequencer backend, but I would like to develop win32 and Mac native backends some day. Jack-midi could probably help on win32 and even Mac, I think??? Also, a multiplatform backend based on libfluidsynth would be interesting for casual users, needing only to configure a SF2 file and the audio output. Some new features would be needed in libfluidsynth to create this backen Regards, Pedro d, for instance: parse and process the lyric and text SMF events. That is if libfluidsynth care to spend time with lyrics and midi-text events at all. Although, I think fluidsynth code is not pretty to add new functions to it. Haven't looked at Gleamsynth (a sort-of Fluidsynth in C++) since the Spring, but I think it did have some performance issues back then. I think the new kmid (or whatever its new name maybe) could do what it always does... send midi events to alsa-seq, or jack-midi, and also parse and display lyrics/midi-text. It may be interesting if it (or its library) also has a separate output port (output-only ???) for lyrics/midi-text events separately from the normal midi port. This way, people can make their own UI, or even network-UI if they want. Jimmy ___ fluid-dev mailing list fluid-dev@nongnu.org http://lists.nongnu.org/mailman/listinfo/fluid-dev
