Midi / Instrument - First note doesn't copy properly in editor

[echopathy]

I've had this problem since pt7. Hadn't used midi before then in PT5/6.

Here's the thing:
I have a midi or instrument track quantized to grid.
I slice a few bars within grid mode (along with audio tracks) and try to paste the midi notes somewhere else in the timeline.

The 1st note never copies... Or is even selected.

I stumbled on this -
http://avid.force.com/pkb/articles/e...n&DocType=1078

Which says that midi tracks don't do that. Welp. They act the same way.

The best I can do is go into the midi editor and move things around in there - which is kind of a drag.

It's the same symptom with repeat, drag copy, etc. The first midi notes of a selected region/notes/block never copies. I've tried em all.

I even happened across a little trick with alt click while selecting a midi note region (in the editor), which captures the first note, but not it's recorded controller mods.

pain in the kahshnookledookle - As my ma' would say.

I will buy the first person who figures this out for me a pizza. For real. I'm sick of this.

Thanks,
dan b

I'm on a Windows 7 machine, BTW. Any of you mac kids seen something like this?

[daeron80]

Do you have any Realtime Properties enabled? It's a known issue that having an advance timing set will cause that bug. You can vote to have it fixed here. Oddly, it hasn't got many votes. Not that a bug should need user votes to be fixed... It's a pain to keep turning properties on and off to get editing to work right. But that's life.

[echopathy]

Thanks for the info and link.

I voted there and here as well

I've never used midi's real-time property buttons within the editor before...
But my Event Operation/Quantized notes dip into the same issue it seems.
Once i restored performance, then sliced,
the copying became a bit more predictable.
Still far from reliable.

Lemme know if you want that pizza.
First responder wins.

db

[echopathy]

or shall i say,

you were the first responder, daeron80...

[Shanegrla]

I've had this problem quite regularly since about 7.4 also (around 2007). Unfortunately I don't have any answers either. I once posted this exact same question back then and someone replied that it had been a known issue for years even back then.

My only workaround is to start the copy 1 grid line earlier than the note you want so you know it gets selected. Which of course means you have to paste 1 grid line earlier than where you want it to show up. Obvously kind of a PITA, but at least it gets the job done.

[smoking umbrella]

I had the same problem for a while and couldn't find any answers online. I know this is an old thread, but maybe this will help someone else.

Select the problematic track, open the Midi Real-time Properties dialog. In the dropdown menu, make sure the track you want is select. Deactivate the 'Quantize' button and hit 'Write to Track'. Then select the default track properties from the dropdown menu and do the same thing again. This will prevent Pro Tools from automatically quantizing your midi and causing you to lose your first notes.

[KimSira]

This bug with first midi notes has been driving me nuts for years as well.
Bout time I hit that voting scale thingy :)

If they'd fix it, it would definitely give me a reason to move on from version HD8.

[seff]

Is this problem by any chance related to why whenever you Rewire Reason to Pro Tools it never plays the first note of the song?

[echopathy]

Haven't listened for it on a Rewire, seff.
That's an interesting experiment.
gotta try that...

My guess is that the order of operations relies on midi notes being detected only at their initial recording/trigger time.
Quantized notes (on some level) aren't accounted for during the copy or paste method/function.
It seems to treat it like a flat audio track... Which makes me think it's tied into the elastic-audio realm of quantizing stuff.

This may dive deeper than a simple fix - who knows?
If it was open source, I (we) may be able to help.
btw, who's that guy behind the curtain?

[cramletram]

This fixed it for me: in the quantize dialog, click "Strength" and set to 100%. You'd think it would default to that.

Cheers