Apple Logic Pro /LogicExpress Discussion

(just suffered a kernel panic crash before sending these questions, so I'm typing this 
lengthy inquiry for the second time - please excuse me for my gruffness):

I have two issues:

1) This has been plaguing me for a long time (it even occurred in LP 7). Working last 
night in the piano scroll editor with MIDI data, the situation arose where moving note 
data (X or Y axis) caused the window to leap to the head of the region upon release of 
the mouse button, necessitating scrolling back to the data work locus. I don't know why 
this happens but it has happened before and it seems random. I have been unable to 
notice anything about my work state when it starts, but once it starts, it seems to be 
consistent behavior for that session. Sometimes just clicking in the editor widow causes a 
jump to the head of the track. Am I missing something? Can anyone help on this? It sure 
is an annoyance.

2) (and more importantly)

This one only appears in LP8:

Sometimes I'll be working with MIDI data, editing the velocities in the graphical controller 
and velocity data area, and, after performing some other work (on a different 
track/region, for instance), I'll re-select the track in which I was editing the velocities, but 
the velocity data goes missing from the editor - just a blank field below the piano scroll 
presents itself. Usually it's correctable in a few steps (e.g. turning the graphical editor off 
and re-opening it), but l sometimes I  can't get the "dots" to appear even after taking 
those steps or even re-loading the app.

And last night came this new diabolical variation:  pasted data from another region failed 
to display its controller data, while pre-existing data did show in the editor.

Here are links to two screenshot  jpgs I made showing the variations I've just relayed:

<http://i124.photobucket.com/albums/p36/msirt/MissingData1.jpg>
and:
<http://i124.photobucket.com/albums/p36/msirt/MissingData2.jpg>

Love to hear from someone (I'm going to preview this - please don't crash!)

MS

I have experienced some similar things - not exactly the same but roughly 
similar. Midi data disappearing in the matrix (piano roll) - solved by re-opening 
the window. The sample editor snapping inconveniently with a mind of its own. 
I think there are some more bugs to be worked out by Apple.


In a message dated 12/31/07 8:58:29 AM, msirt@... writes:
> (just suffered a kernel panic crash before sending these questions, so I'm 
> typing this
> lengthy inquiry for the second time - please excuse me for my gruffness):
> 
> I have two issues:
> 
> 1) This has been plaguing me for a long time (it even occurred in LP 7). 
> Working last
> night in the piano scroll editor with MIDI data, the situation arose where 
> moving note
> data (X or Y axis) caused the window to leap to the head of the region upon 
> release of
> the mouse button, necessitating scrolling back to the data work locus. I 
> don't know why
> this happens but it has happened before and it seems random. I have been 
> unable to
> notice anything about my work state when it starts, but once it starts, it 
> seems to be
> consistent behavior for that session. Sometimes just clicking in the editor 
> widow causes a
> jump to the head of the track. Am I missing something? Can anyone help on 
> this? It sure
> is an annoyance.
> 
> 2) (and more importantly)
> 
> This one only appears in LP8:
> 
> Sometimes I'll be working with MIDI data, editing the velocities in the 
> graphical controller
> and velocity data area, and, after performing some other work (on a 
> different
> track/region, for instance), I'll re-select the track in which I was editing 
> the velocities, but
> the velocity data goes missing from the editor - just a blank field below 
> the piano scroll
> presents itself. Usually it's correctable in a few steps (e.g. turning the 
> graphical editor off
> and re-opening it), but l sometimes I can't get the "dots" to appear even 
> after taking
> those steps or even re-loading the app.
> 
> And last night came this new diabolical variation: pasted data from another 
> region failed
> to display its controller data, while pre-existing data did show in the 
> editor.
> 
> Here are links to two screenshot jpgs I made showing the variations I've 
> just relayed:
> 




**************************************
See AOL's top rated recipes 
(http://food.aol.com/top-rated-recipes?NCID=aoltop00030000000004)


[Non-text portions of this message have been removed]

Thanks for the reply.  Nice to know I'm not crazy.  You say Apple has to fix these bugs.  
I wonder if Apple even knows of this issue.  I seem to be the only one addressing this on 
their discussion group (the missing velocity nodes, that is).  Have you seen this topic 
arise elsewhere by any chance?

--- In Logic_Cafe@yahoogroups.com, GAmoore@... wrote:

>
> I have experienced some similar things - not exactly the same but roughly 
> similar. Midi data disappearing in the matrix (piano roll) - solved by re-opening 
> the window. The sample editor snapping inconveniently with a mind of its own. 
> I think there are some more bugs to be worked out by Apple.
> 
> 
> In a message dated 12/31/07 8:58:29 AM, msirt@... writes:
> > (just suffered a kernel panic crash before sending these questions, so I'm 
> > typing this
> > lengthy inquiry for the second time - please excuse me for my gruffness):
> > 
> > I have two issues:
> > 
> > 1) This has been plaguing me for a long time (it even occurred in LP 7). 
> > Working last
> > night in the piano scroll editor with MIDI data, the situation arose where 
> > moving note
> > data (X or Y axis) caused the window to leap to the head of the region upon 
> > release of
> > the mouse button, necessitating scrolling back to the data work locus. I 
> > don't know why
> > this happens but it has happened before and it seems random. I have been 
> > unable to
> > notice anything about my work state when it starts, but once it starts, it 
> > seems to be
> > consistent behavior for that session. Sometimes just clicking in the editor 
> > widow causes a
> > jump to the head of the track. Am I missing something? Can anyone help on 
> > this? It sure
> > is an annoyance.
> > 
> > 2) (and more importantly)
> > 
> > This one only appears in LP8:
> > 
> > Sometimes I'll be working with MIDI data, editing the velocities in the 
> > graphical controller
> > and velocity data area, and, after performing some other work (on a 
> > different
> > track/region, for instance), I'll re-select the track in which I was editing 
> > the velocities, but
> > the velocity data goes missing from the editor - just a blank field below 
> > the piano scroll
> > presents itself. Usually it's correctable in a few steps (e.g. turning the 
> > graphical editor off
> > and re-opening it), but l sometimes I can't get the "dots" to appear even 
> > after taking
> > those steps or even re-loading the app.
> > 
> > And last night came this new diabolical variation: pasted data from another 
> > region failed
> > to display its controller data, while pre-existing data did show in the 
> > editor.
> > 
> > Here are links to two screenshot jpgs I made showing the variations I've 
> > just relayed:
> > 
> 
> 
> 
> 
> **************************************
> See AOL's top rated recipes 
> (http://food.aol.com/top-rated-recipes?NCID=aoltop00030000000004)
> 
> 
> [Non-text portions of this message have been removed]
>

Thanks for the reply.  Nice to know I'm not crazy.  You say Apple has to fix these bugs.  
I wonder if Apple even knows of this issue.  I seem to be the only one addressing this on 
their discussion group (the missing velocity nodes, that is).  Have you seen this topic 
arise elsewhere by any chance?

--- In Logic_Cafe@yahoogroups.com, GAmoore@... wrote:

>
> I have experienced some similar things - not exactly the same but roughly 
> similar. Midi data disappearing in the matrix (piano roll) - solved by re-opening 
> the window. The sample editor snapping inconveniently with a mind of its own. 
> I think there are some more bugs to be worked out by Apple.
> 
> 
> In a message dated 12/31/07 8:58:29 AM, msirt@... writes:
> > (just suffered a kernel panic crash before sending these questions, so I'm 
> > typing this
> > lengthy inquiry for the second time - please excuse me for my gruffness):
> > 
> > I have two issues:
> > 
> > 1) This has been plaguing me for a long time (it even occurred in LP 7). 
> > Working last
> > night in the piano scroll editor with MIDI data, the situation arose where 
> > moving note
> > data (X or Y axis) caused the window to leap to the head of the region upon 
> > release of
> > the mouse button, necessitating scrolling back to the data work locus. I 
> > don't know why
> > this happens but it has happened before and it seems random. I have been 
> > unable to
> > notice anything about my work state when it starts, but once it starts, it 
> > seems to be
> > consistent behavior for that session. Sometimes just clicking in the editor 
> > widow causes a
> > jump to the head of the track. Am I missing something? Can anyone help on 
> > this? It sure
> > is an annoyance.
> > 
> > 2) (and more importantly)
> > 
> > This one only appears in LP8:
> > 
> > Sometimes I'll be working with MIDI data, editing the velocities in the 
> > graphical controller
> > and velocity data area, and, after performing some other work (on a 
> > different
> > track/region, for instance), I'll re-select the track in which I was editing 
> > the velocities, but
> > the velocity data goes missing from the editor - just a blank field below 
> > the piano scroll
> > presents itself. Usually it's correctable in a few steps (e.g. turning the 
> > graphical editor off
> > and re-opening it), but l sometimes I can't get the "dots" to appear even 
> > after taking
> > those steps or even re-loading the app.
> > 
> > And last night came this new diabolical variation: pasted data from another 
> > region failed
> > to display its controller data, while pre-existing data did show in the 
> > editor.
> > 
> > Here are links to two screenshot jpgs I made showing the variations I've 
> > just relayed:
> > 
> 
> 
> 
> 
> **************************************
> See AOL's top rated recipes 
> (http://food.aol.com/top-rated-recipes?NCID=aoltop00030000000004)
> 
> 
> [Non-text portions of this message have been removed]
>

Its hard to say what Apple knows or doesn't know. Some of the original Emagic 
people (who continue to develop it) did subscribe to this list, but not sure 
how closely they monitor it.

I have seen other people confirm the problem with the missing notes in matrix 
on the message boards at gearslutz.com.


> I wonder if Apple even knows of this issue. I seem to be the only one 
> addressing this on
> their discussion group (the missing velocity nodes, that is). Have you seen 
> this topic
> arise elsewhere by any chance?
> 




**************************************
See AOL's top rated recipes 
(http://food.aol.com/top-rated-recipes?NCID=aoltop00030000000004)


[Non-text portions of this message have been removed]