Re: [LAD] Tux Paint for music?
Paul Coccoli pcocc...@gmail.com writes: Well, since you're thinking SDL, you should consider using a gamepad as the primary input device. I understand it is a somewhat popular interface for kids these days. Yes, in particular it would be great fun to have some toy like that on running on my GP2X. :) -- /Pelle ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
Re: [LAD] Writing a library?
Anders Dahnielson [EMAIL PROTECTED] writes: Here's a simple tokenizer for SFZ I wrote once upon a time in Python. Not sure if I got it completely right. *snip* I was just about to suggest checking out the sampler/synth/sequencer/tracker engine libzzub, that happens to include Python bindings: http://trac.zeitherrschaft.org/zzub/ http://trac.zeitherrschaft.org/aldrin I haven't looked much at it myself yet, but Aldrin works very well (built on top of libzzub) and it seems like a good design, supporting different types of plugins and audio outputs and handling sequencing and the directed graph of plugins. -- /Pelle ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
Re: [LAD] starting out with tux audio
Jens M Andreasen [EMAIL PROTECTED] writes: Do you have any midi-keyboard around? Because stdio won't tell you that a key has been released, only that it has been hit. This limits the toy Casio experience somewhat ... There is of course a workaround - given that you have root permission, you could read the keyboard from /dev/input/ instead. This is unfortunately a bit like having a keyboard sniffer installed, which may not be ideal in your environment. Next step up the ladder I think is fullblown X ... There was a very nice curses based midi keyboard for OSS, called midikb or something like that. It solved this problem very neatly by allowing you to switch between a few different modes. IIRC one was to send note off when a new key was pressed (ie like a monophonic synth), one was to always play each note for a set time, and last I remember was to press key a second time for note off. I wonder what happened to that application. It used to be in Debian. I used it all the time. Often these modes of playback made it easier to play some parts than a real midi keyboard (or vkeybd). On the other hand of course at other times it was annoying that it could not function more like a real midi keyboard. I think/hope I have the source somewhere. Even did some modifications to it to send specific control change event easily for some hardware synth I used at the time. -- /Pelle ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
Re: [LAD] Packaging advice
Hi, Pete Black [EMAIL PROTECTED] writes: The actual electribe hardware has a 'virtual keyboard' mode where the 16 step keys can be used as a 1-and-a-bit octave keyboard, but i think i may just implement midi recording + midi thru to allow a real keyboard to be used, or the virtual keyboard of your choice - i really want to make this sequencer simple and modular, rather than an all-things-to-all-people sequencer. I agree about making things simple and modular, but I still think it would be preferable to have keys mapped to all the buttons on the screen (single keys for often used buttons like the 16 steps or to change to other parts, no combos), and that the step keys could also be switched to act as a virtual keyboard. It would really increase usability to not have to switch window to a virtual keyboard to do on of the most important functions of the application, editing notes. More sequencers could really be improved by adding the ability to play on the computer keyboard, and in general making sure it is possible to control everything from the keyboard, IMHO. Trackers have been doing it forever. I know that has historic reasons, but I don't see any of the newer trackers, on linux or elsewhere, requiring an external (virtual) keyboard to play/edit. The only good alternative I can see would be to have some kind of application that could be triggered in the desktop environment to temporarily take over keyboard events from all other applications and map them to ALSA/JACK MIDI events instead, without having to switch to another window. I'm not sure how easy that would be to do in a portable way (working with Gnome/KDE etc). But even with a tool like that I would not mind if a virtual electribe to behave more like an electribe with the same specific keys tied to the 16 step/note keys just like on a real electribe. -- /Pelle ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
