Hi,

I'm pretty sure that someone already has posted somthing on this topic, but just to make sure I'll post it myself .

Are there any reasons for the note editors in the sequencer and in the midi part not to behave exacly the same? As I see it they do the same thing, thus they should act the same as well.

Examples on how the editors differ (assuming that you are in step recording mode):

- Example 1: If you have selected a number of notes and press ctrl+down a couple of times, you would expect the notes to move as many steps downwards in the note sheet as you push the down button. In the midi part this do happen but in the sequencer the notes take one step downwards and then all notes, except for the note selected by the red cursor, become deselected. Only the note selected by the cursor will moved more that one step.

- Example 2: If you move a note sideways and it ends up on top of another note ("the overlapped note") and you - without releasing ctrl - move it off the note, you would probably expect something of the following:

a. The overlapped note is erased and only the overlapping note remains.
b. The overlapped note remains and is still there when the overlapping note is moved away.
c. Somthing else.

Personally I prefer the b alternative. Either way, you would expect the behaviour to be consistent between the sequencer and the midi part. As it is now, the sequencer display the behaviour described by alternative a and the midi part display the b alternative.

I guess the differences in behaviour has something to do with the fact that, when step recording, midi part moves the notes regardless of the red cursor but the sequencer will require the red cursor to be on top of the note that is to be moved (which is why only one note can be moved several steps . Overall there is some rather significant discrepancies between the two editors.

I see that each part in the sequencer is editable in the midi part mode of editing, this is nice since that allows the user to edit notes consistently in both places, but why does the note editors behave differently in the first place?

Does this make any sense?

Best regards,
Tomas

Oh, and I have tried this in the latest beta - standalone as well as VSTi.

//Tomas

elfan wrote:

Does this make any sense?

No...not really

(Edit)...sorry but your post just confused me. couldn't repeat the same behavior here, so I can only assume I don't understand. Here on my machine when I select multiple notes in STEP REC mode and Cntrl+Down 5 steps the notes all move 5 step down...the same in both MidiPart and Seq MidiPart.



(Edit #2) Ok...I see what you mean by example #1:
This onlt happens when using In-Track Editing, not when you open the sequencers MidiPart in it's own window. That wasn't clear to me, and I was testing by opening the sequencers part by double clicking.

nF

elfan,

example 1, I agree, good point. Will fix.

example 2, I don't see this as a problem. I work a lot with keybaord shortcuts and I often move a section of notes past another section, and I wouldn't want to change the 'moved over' notes to be afected in any way...

thanks
jorgen

>I wouldn't want to change the 'moved over' notes to be afected in any way

I think he's saying that, when you edit notes like this 'in track', they do change the notes underneath. Can't confirm since I'm not at my daw.

What's actually happening when 'In-Track' editing in step mode...The notes are picked up under the red cursor as you Cntrl-Move over them. They aren't changed, just dragged with your selection.

nF

NicFit: Yes, that's true, they are not deleted . However, they are piled together under the note being moved so the ordering of the notes and possible pauses between the notes are lost. There is no way of getting back that information later (by moving the note away from the other notes). So it's pretty destructive in any sense.

Since you can do a midi part edit as well as the "in-track" edit in the sequencer, should you stick to the midi part edit and forget about the in-track edit in order to get consistency? Or what is the purpose of in-track editing if there is midi part editing directly available from the in-track edit? Is in-track editing more of a way of getting an overview of several tracks at once? How do people generally work with this functionality? I'm just curious.

//Tomas

elfan wrote:

NicFit: Yes, that's true, they are not deleted . However, they are piled together under the note being moved so the ordering of the notes and possible pauses between the notes are lost. There is no way of getting back that information later (by moving the note away from the other notes). So it's pretty destructive in any sense. Since you can do a midi part edit as well as the "in-track" edit in the sequencer, should you stick to the midi part edit and forget about the in-track edit in order to get consistency? Or what is the purpose of in-track editing if there is midi part editing directly available from the in-track edit? Is in-track editing more of a way of getting an overview of several tracks at once? How do people generally work with this functionality? I'm just curious. //Tomas

I'm with 100% Tomas. Fortunately(for me) I'm not affected by it since I work at 1600x1200 resolution most of the time so for me the In-Track editing feels a little constricted(not enough height). I prefer to open my sequencers parts in a seperate MidiPart display where I can adjust the height and get a view of controllers. You only need to open oneMidiPart display, then as you double-click the parts in the sequencer view, they will display in the same MidiPart display. I'm sure jorgen will try to sort it out now that it's been reported.

nF

elfan wrote:

Or what is the purpose of in-track editing if there is midi part editing directly available from the in-track edit? Is in-track editing more of a way of getting an overview of several tracks at once? How do people generally work with this functionality?

it's to have an overview over several tracks at once and to see where it lacks of timing or if there are sync problems within tracks which is where i see the advantage.
i don't use it for in-depth editing though - that's what the midi-part is for .
the in-track view mustn't be too complex IMO.

Ok, good points!

Thanks everybody .

//Tomas