Hans Fugal wrote: What something Timidity++ -- it uses a variety of interfaces, including ncurses, slang, GTK+, etc. -- Rule of Feline Frustration: When your cat has fallen asleep on your lap and looks utterly content and adorable, you will suddenly have to go to the bathroom.

Yeah, that's true... it's a softsynth with a built-in sequencer... never mind. -- Rule of Feline Frustration: When your cat has fallen asleep on your lap and looks utterly content and adorable, you will suddenly have to go to the bathroom.

Eric Dantan Rzewnicki wrote: No, Timidity doesn't have an editor so far as I know -- it can only play back MIDI files. -- Brett

martedì, 05 ottobre 2004 alle 13:37:57, Hans Fugal ha scritto: Hi, I think that the "sequencing experience" on GNU/linux is improving day by day: muse and rosegarden can be well compared with the commercial counterparts, and if you consider them as part of a more wide "music production" experience on linux, with all his great tools (jack, LADSPA, the upcoming LASH and the number of all other wonderful apps), you can even get a more powerful and flexible environment, in which you can model your setup with more freedom than you can in other platforms (not always as user friendly, but often very powerful). They're not perfect, for sure... but they are more and more stable and they gain new features very fast. Having said that, I agree that these sequencers suffer from a "do all in one place" vision, and I've dreamed too an "ecasound for MIDI" in which you can mix, record, assign to multiple outputs, filter, etc... multiple MIDI files and streams. I proposed this vision also on #lad (tapas knows ;), but unfortunately I'm no programmer at all :( so I can only share my dreams ;) If you like I can elaborate on that. For answering the original question, there are other sequencers available: seq24 [0], for example, is a very light and clean MIDI sequencer that with the addition of jack_transport abilities could be very interesting (and already is). I've used also jazz++ [1] for long time, and it has a very rich (if not the richer) MIDI feature set. unfortunately this is discontinued, but there are plans [2] to port it to gtk2. There is also sted2 [3] which has (I never used it that way) a ncurses version, but I found it a bit difficult to use, but feasable if you like "list editing". Another project that's somewhat related (but that's not a realtime sequencer) is mma [4], a MIDI arranger. Please consider a command line tool "à la ecasound": this is a completely different paradigm than commercial/GUI sequencers but IMHO can offer a completely new (and creative) way of using MIDI (think for example of a library of chords and rythmic patterns that you can bind to a key), without having to struggle with a GUI... Sorry for the length and the malformed english :) Regards [0] http://www.filter24.org/seq24/ [1] http://www.jazzware.com/cgi-bin/Zope.cgi/jazzware/ [2] http://jazzplusplus.sourceforge.net/ [3] http://sted2.sourceforge.net/ [4] http://mypage.uniserve.ca/~bvdp/mma/mma.html -- Emiliano Grilli Linux user #209089 http://www.emillo.net

cubase

Am Mittwoch, 6. Oktober 2004 16:20 schrieb Marius Janßen: If you need Atari music software, take a look at http://tamw.atari-users.net/

On Wed, Oct 06, 2004 at 09:53:31 -0400, Brett W. McCoy wrote: Heh, I used an Amiga with a RS232 serial port MIDI dongle and gcc. Things have changed so much, now I use a USB serial port MIDI dongle and gcc. :) - Steve

On Wed, Oct 06, 2004 at 10:44:34 -0400, Brett W. McCoy wrote: Actually I used the SAS compiler before I got a good gcc build, but that isn't as amusing :) - Steve

Last Wednesday 06 October 2004 18:21, Brett W. McCoy was like: I still have a manual for cubase 2.01 ;D I've often wondered about the old ATARIs, I mean I know editing was a pain, but they usually played the flipping thing flawlessly without falling over. How come? cheers tim hall

On Wed, Oct 06, 2004 at 09:50:07PM -0700, Erik Steffl wrote: Actually, old home computers HW rather resembled _old_ consoles, while new consoles resemble modern PCs :) I think a huge point was (and is, for modern consoles) the fixed hardware. You can (or even have to) write your code 'straight to the metal' and optimize it to take full advantage of every aspect of the hardware while never worrying about different CPUs, graphic chips etc. Plus, with the absence of an OS and multitasking you can give guarantees about the timing of your code, up to a single clock cycle. And that is per definition RT capability. The result has of course little to do with today's general purpose computers and operating systems. cheers, Christian -- "Somewhere in Texas... a village is missing its idiot."

I have done some MIDI programming on the Atari. The Atari had the MIDI interface on board, and the chip was very simple to address. And you could easily use very accurate interrupts to do the scheduling. And it not only played flawlessly without falling over, but even falling over, literaly. I once stepped on a cable while performing on stage, the atari fell down from the table, and played on without a glitch :-) maarten