> > ...resulting in rediculous notes that are sustained for many,
> > many bars
> > (sometimes in the hundreds or more - going off right side of the matrix
> > editor).
> You need to introduce yourself to one my most commonly used keycommands in
> the matrix editor - the one that shortens the lengths so there is no overlap.
But what does that global operation do to notes whose duration is intended to go beyond
the onset of other notes?
it works really well on mono stuff - and makes no overlaps. surprisingly, it works pretty well on polyphonic stuff too - for example block chords. Its actually quite cleverly designed. However, once in a while, it messes up, so in those cases I hit UNDO, and select only the notes I want to process. That always works fine. This can also be used to get rid of duplicate notes.
I think its called "Note overlap correction" in various windows. Its really a pain to find how a keycommand is defined. In previous of logic, you could open the key command window and type a key and it would highlight its assignment. but not now, no matter what I do. I guess logic is 3 steps forward, 1 step back. There is also a "force legato" which extends the lengths to fill in the gaps.
> > And also , btw, I'm still seeking for the 'simple' method of preventing
>; > plug-in reload when
> > switching between multiple open songs. Someone on this group had mentioned
> I'd like to know that too. It can take a minute or more when switching songs.
> And despite that, it seems that RAM is filled up quite easily when both songs
>; are open.
Sometimes much more than a minute (it seems) in the case of EWQLSO plugs (well, it
seems like much more than a minute - a 'minute or more' can seem like an hour when
you're trying to work).
Oh I know. It drives me up the wall. also the error messages that memory is running out, and refusing to move notes or claiming something is frozen when its not. If you find out, please let us know.