Pan values in Event list do not correspond to pan values in Step Editor

[Channel10]

In the screenshot below you can see (midi) pan values for the region called "Strange". Why do the pan values displayed in the Step editor not correspond to the pan values in the Event list? In the Event list there are 20 midi pan values, in the Step editor there are much much more.

 

[David Nahmani]

Click the Additional Info button in the Event List. 

[Channel10]

Yes, thank you.  

[David Nahmani]

You're welcome. 

[Channel10]

The behavior in the case the "Additional behavior" button is on is really strange. Deleting events just does not seem to work as expected. 

 

I keep on deleting events  but it still says 149 events. 

[David Nahmani]

I keep on deleting notes but it still says 149 events. 

Are you deleting notes? Or CC events?

[Channel10]

Sorry, events, I delete them in the event editor btw. Removing pan events from the step editor works fine. 

[David Nahmani]

The Event List with Add'l Info selected behaves like MIDI Draw: it automatically recreates all the events necessary for a smooth transition between two control points. So for example if your pan goes from 10 to 20, it will create events 11, 12, 13... 18 and 19 automatically for you. 

[Channel10]

Good you mention this. However . . . I thought we had automation for that?!

[David Nahmani]

Good you mention this. However . . . I thought we had automation for that?!

Sure. You can use track or region automation for panning, it works pretty much the same though, under the hood it's a long list of discrete values that represent the nice smooth curve you see on your screen.

[Channel10]

Now I think I miss something. I was not thinking about the difference between track or region automation. I was thinking about the difference between midi-cc data for controlling synth or mixer parameters versus automation data for controlling parameters. With the current behavior there is not a big difference between them, is it?  In fact, what was the reason for implementing automation (for over 15 years Logic has it, I know) in Logic?

 

What I appreciate about midi-cc data is that it is plain/easy/raw. But with the current implementation in Logic it is not so easy anymore.  

[David Nahmani]

With the current behavior there is not a big difference between them, is it?  In fact, what was the reason for implementing automation (for over 15 years Logic has it, I know) in Logic?

The difference is in the way you handle them. When using automation you deal with a specific Mixer parameter such as "compressor ratio." When using MIDI CC you deal with a MIDI CC number that could then be used for anything you'd like. Automation uses an automation lane superimposed over the track, while MIDI CC is typically edited in MIDI editors, although you can also view MIDI Draw in the Tracks area. Automation has its own record modes (Touch, Latch...) and can be recorded during playback, MIDI CC is recorded like any other material, audio or MIDI: you press record. Automation uses mostly internal Logic's own internal Fader events vs MIDI CC uses standard MIDI data. Most people wouldn't use MIDI CC on an audio track. 

 

Automation was implemented in Logic to emulate the automation of the large analog mixing consoles used in recording studios.