On Friday 07 Oct 2005 23:26, Silvan wrote: > Another passing thought is that the above scenario is starting to > sound like a new, independant, free-standing advanced notation editor > to me. [...] The sequencer-editor would be for people more concerned > with the best MIDI performance (and audio and other stuff) while the > separate, advanced notation editor would produce files readable by the > sequencer, but not editable in a backward-compatible way. [...] > > OK, that last thought is pretty far out there, I admit.
Well, not especially -- that's basically what you have in other projects, isn't it? Notation editors that write MIDI, MIDI sequencers that read it and do basic notation. That's pretty much exactly what the purpose of Rosegarden is to avoid. I'd like to find some interesting solutions for some of these problems that have basically been avoided in notation and sequencing programs for the last twenty years, not just avoid them in the same way again. Apart from anything else, many of the problems we're talking about have to do with arranging music, not particularly to do with the fiddly details of drawing the notation. The fiddly details of drawing it are usually easy -- hard to get right, but easy to reason about. Something like cue-size notes or percussion staffs is basically a solved problem that's just waiting for someone to find the time to implement it. The arrangement and time-flow (repeats, tempi) problems are more interesting, and it seems to me that they're often problems that affect composing music in general, not always just dealing with notation. Chris ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
