On 09/06/2012 10:35 PM, Tom Breton (Tehom) wrote: > * We can only get a conflict when we're reading and writing at coarsely > the same time, ie the user is editing stuff while playing. That use case > is considered less crucial than playing smoothly while nothing is being > jiggled.
That's about the size of it. If weird things happen when editing while playing back, it's normally just weird glitches that aren't worth running down. One exception I can think of is the case where somebody has the transport in loop mode so they can work out some drum sequence. We want the next iteration of the loop to be reasonable, and not play notes that have been deleted, etc., so this can be a useful process. Wrapping glitches (ie. annoying pauses) on either end of looping via the transport are acceptable, so long as they're not ridiculous. No idea if any of the above comments were relevant. Just summarizing my understanding of a bit of historical project agreement. -- D. Michael McIntyre ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Rosegarden-devel mailing list Rosegarden-devel@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
