On Wednesday 02 Feb 2005 19:41, NadaSpam wrote: > If the sequencer works with seconds, why not change the gui and event > storage to also use seconds? Fundamentally using music time seems to > be a liability.
Because most of the time in the editor you want music time. For example, when editing notation, having everything in seconds would be incredibly unhelpful. You want to be able to tell easily what sort of note something is, or at least is closest to. And most of the time it's a good thing that the numbers remain the same when you change the tempo. The other point is that, while these distinctions are interesting and it's worth choosing your representation with a certain amount of care, it often doesn't actually matter that much. So long as everything you want to do is _possible_ with a given representation (which for us it is, given that we've taken a view that we have no interest in even thinking about the problem of running different tracks at different tempos, and we don't see it as even meaningful in a GUI like this), then that's generally enough. And it's often easier than you'd think to change things like this after the fact, too. We've never had any desire to switch to real time for the base representation in the editor, but we have changed the resolution of the musical time base before, without much trouble, and we've changed fundamental aspects of the event and segment storage several times without breaking things. > Yeah, I can see that. The pitch bend will affect everything on the > channel. So how does Cakewalk (Sonar) accomplish different tunings? It probably supports MIDI Tuning. > I was thinking that the difficulty would be in holding the actual > tablature data. There isn't a 1-1 mapping between the staff position > (note number) and the tablature value. The problem is not so much holding it (you can associate any data you like with an Event in Rosegarden, this sort of thing is what it's designed for) as editing it, as I think you go on to describe. > Maybe the solution is to have a "tablature edit mode", wherein you > could only enter notes via the tab staff. Yeah, there's no reason you shouldn't just have a separate tab staff that you enter through another option on the right-button menu on the segment canvas. It could guess fingerings for notes that don't have them associated yet. The NotationView is also in principle capable of showing multiple staffs that are not all plain notation staffs -- notation staff first, tab staff under it, drum staff third etc -- but since there are no other staff types (except the matrix, which is useless in that context) in existence yet, assumptions have crept in and it would need a bit of work and testing to get it right. Apart from the problem of how you select staff types in the GUI. Speaking for myself, I'm very interested in percussion staffs but I know next to nothing about tablature, so I'm probably going to be missing some important points here. Chris ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
