Re: 2022.6 MIDI Quantize/Selection Weirdness BUG
 

So is Avid going to provide a fix after almost 3 weeks?!?!?!
I've tried different audio interfaces and a ton of other things and nothing works.
At least provide an easy way to downgrade to 2022.5. When I download it from Avid (instead of Avid link), it doesn't start. Very unprofessional to send out an upgrade that has such obvious flaws!

Re: 2022.6 MIDI Quantize/Selection Weirdness BUG
 

I have this problem as well. And, to add to the problem: if you copied a midi clip to a different section in the song, and then edit a few notes in the copied clip, the original (and all copied clips) are changed. So dragging a note one up, makes that note in ALL other copies go one up. That is just soooooo lame and unusable!!

Avid, WHEN will you fix this MIDI issue? It was'nt there in the previous version, so you changed something that ffed this all up. Please fix this asap, as I am in the middle of a project, and I cannot continue now.

Re: 2022.6 MIDI Quantize/Selection Weirdness BUG
 

Thank you for the tip:-)
I am not an advanced midi user but this took care of the midi issues I had that was mentioned in this thread
tom :-)

Re: 2022.6 MIDI Quantize/Selection Weirdness BUG
 

Unfortunately, after a few days without the midi editing bug, i've just experienced it again :(
Out of the blue, I cannot select the MIDI notes on an instrument track. Escalating my support ticket with Avid.

Re: 2022.6 MIDI Quantize/Selection Weirdness BUG
 

I just had this for the first time yesterday, on an old session I needed to work from. I filed a support ticket, but told them I considered it just a bug report.

Re: 2022.6 MIDI Quantize/Selection Weirdness BUG
 

Same here. Total weirdness! I have had to roll back to 2022.5

Stephen

Re: 2022.6 MIDI Quantize/Selection Weirdness BUG
 

I sent a report to Avid as suggested.
(I'll probably wait until the update but there are some solutions for those who may need this to work now. Reverting to 2022.5 or.4 is also an option. I'm checking on if they have an ETA on the new update).

Here's their answer:

The issue was logged and our development database with issue#:

PT-288914

and
it has already been fixed in the next update of Pro Tools.

It seems the issue occurs with Sample-based MIDI/Instrument Tracks in many cases.
Please try one of the workarounds below
till the next update is released.

-Edit notes in slip mode when track is set to “Samples” time base w. Bars|Beats grid.
-Change track to Ticks time base when using Trim Tool in Grid mode w. Bars|Beats grid.
-Set MIDI Editor Grid to something different than Bars|Beats.

Re: 2022.6 MIDI Quantize/Selection Weirdness BUG
 

Ah. Good to hear. I had one instance of it happening, but it worked fine the next day

Re: 2022.6 MIDI Quantize/Selection Weirdness BUG
 

Did you have to uninstall PT to roll back? These midi issues are killing me!

Re: 2022.6 MIDI Quantize/Selection Weirdness BUG
 

Some of the Midi weirdness I am experiencing on a Windows based system:

After 20 or 30 minutes of midi note editing on a piano part when adding or moving a note, 2022.6 just locks up with a spinning doughnut. Prior version does not do this.

Very skittish mouse interaction sometimes just clicking a note deletes it when I just want to grab and move it.

If I need to click out on the timeline just after editing in the midi editor, when
I click back into the Midi Editor, the project jumps to the start of the performance instead of where I was working. Very annoying.

MIDI Weirdness Persists in 2022.7
 

I installed 2022.7 for a test run, but almost immediately rolled back to 2022.5 after finding MIDI unusable. I converted 4 bars of audio to MIDI and pasted it into an instrument track. The resulting MIDI wasn't perfect so I tried to edit it in the MIDI edit window only to discover the mouse tools weren't working. Notes could be resized and quantized, but couldn't be moved with the mouse. Velocity couldn't be changed with the mouse. I also noticed weirdness with the mouse tools shape-shifting when trying to edit an audio clipgain line. I was in the middle of a project and didn't have time time to investigate further, so I quickly uninstalled PT and rolled back.

This is disgraceful, Avid. Two versions in a row with badly broken MIDI? Please fix the bugs immediately. There was another report here about stuck graphics in the mix window. Please fix that too, and don't mess with anything else... MIDI isn't great in PT, but it's been very usable in previous versions. Please stop messing with it and breaking it. Let's just have one good working version with functional MIDI and graphics, thank you.

Re: MIDI Weirdness Persists in 2022.7
 

Originally Posted by mtmusic :

However, I discovered a new aspect of my bug. If I follow my same operations while in Grid mode, everything works the way it should. My bug only happens when I create the clip by consolidating in Slip mode, which could be why some may have trouble reproducing this bug.

When you consolidate to create an empty region WHILE in slip mode, the notes entered into the clip cannot be selected/quantized/moved. BUT, if you do not consolidate to create a region and simply record the notes creating a new region, everything works as it should....

This is still going on in 2022.7

Re: MIDI Weirdness Persists in 2022.7
 

I totally agree! Please Avid, FIX THIS ASAP!!

Re: MIDI Weirdness Persists in 2022.7
 

Yes, something went wrong in .6 and now .7 that was fine in .5.

This in Windows 11 as well but from other threads here also the on Mac.

My guess is that it has something to do with undo buffers or buffers allowed for making midi edits because it seems to occur between 100 to 200 edits into building a midi track. Things just lock up. Not to mention erratic mouse interaction along the way.

Re: MIDI Weirdness Persists in 2022.7
 

Yes, it is broken, but what I’ve noticed on my system (mac) is that if I use the docked editor, MIDI edits, selection, etc. seem to work most of the time.

Re: MIDI Weirdness Persists in 2022.7
 

This is beyond a joke.

Re: MIDI Weirdness Persists in 2022.7
 

I haven't been able to repro the MIDI problems in a brand new 2022.7 session.
Only able to repro when working with MIDI in previous sessions (Sessions created in PT12 to PT Studio 2022.5 - Issues duplicating accurately).
But no issues in sessions created before PT12 (PT10 thru 11 - When there were no issues duplicating accurately).
Turns out a lot of my drum tracks were created in 10 & 11.
I opened those sessions as a test and didn't have any issues that I can repro right off in sessions created in PT12 - PT Studio 2022.5)

So my thought is that The new MIDI framework and any session from PT12-2022.5 are incompatible. For MIDI editing in my sessions anyway.

With fresh new MIDI data in a 2022.7 session I've been able to work without issue so far.
When I say "new session" I don't mean importing previous session data into 2022.7.
Everything has to be from scratch.

I tested a new session with 4 instrument tracks, dragging & dropping a bunch of random drum loops onto the tracks. Then started quantizing & editing randomly all over the tracks.
No issues so far with new tracks created in 2022.7.
But if I open a session with previous MIDI session data (PT12-2022.5) I can repro bugs old & new right away.

You can read a few more details about my recent test session here:
Comment #8.

http://duc.avid.com/showthread.php?p...03#post2643203

Re: MIDI Weirdness Persists in 2022.7
 

I experienced this midi issue in .7 in a new session.

The work around was to change the track to samples instead of tick.

I went back to.4 it seems to be the more stable of the bunch.

This is getting so old.

Re: MIDI Weirdness Persists in 2022.7
 

Thanks for the workaround tip.

So far I've been able to work fine in new 2022.7 sessions and only repro problems in previous sessions.
Update: Only if those sessions were created from PT12 up to 2022.5.

I opened up sessions created in PT 10 & 11 last night and was able to work without issue in those sessions also.
Those versions are when I didn't have the issues that existed from PT12 up to 2022.5 (Unable to duplicate accurately - Notes getting misaligned).

So basically, this creates a personal PT version compatibility chart for my MIDI editing sessions:

New sessions and previous sessions (PT10-11) work well in PT 2022.7.

Session created in PT12-2022.5 do not work well in 2022.7 and are outright broken in those previous versions for me when it comes to duplicating and cutting and inserting MIDI arrangements.
Those version have been broken for over 2 years for myself and others.

I'm thinking we now have two different MIDI frameworks that are mathematically incompatible & will be flawed or fixed depending on when your sessions were created and what your workflows are.

I've still yet to test MIDI combined with Audio in 2022.7 though.
But last night, I was finally able to arrange (cut/insert) & edit drum tracks easily like I used to in PT 10 & 11.
So that makes 2022.7 my version of choice for now.

To finally have all the latest features paid for the past two years AND be able to drag, drop & duplicate a drum loop. Wow...

Re: MIDI Weirdness Persists in 2022.7
 

Thanks for the update. What steps did you take to repro?

I was finally able to repro not being able to select a MIDI note in a new session. It took a while though.
It was after using the Space Clips function (just after quantizing a group of clips).
I was able to quantize, select & trim notes every which way but loose before that.

I also discovered that by simply sliding the clip over a bit and back into place (in Grid Mode) I could then select & move the notes again.

Let me know if that works easily enough for now.

2022.7.0 MIDI Problems
 

in 2022.6 and 2022.7 I have had midi issues. Everything will work fine for hours. Suddenly I can't move midi notes, delete them, change velocity, etc. I can however create new midi notes, but once they are in place they can't be modified. Has anyone experienced this? Im not a midi expert - its possible I am accidentally activating some midi lock or something, but I don't think so. Restarting Pro Tools fixes the issue for a while.

Weirdest Midi thing ever..
 

Did I miss a new feature or is this a bug; when I move midi from one track to another I can`t edit it anymore..
super weirdo
thx for help this is kinda urgent

Protools 2022.7 on a M1 Macbook pro with 12.4

Re: Weirdest Midi thing ever..
 

Yes this is a confirmed bug in 2022.6/7 that is affecting others on both Mac & Windows.
Hopefully, it will get fixed soon. But for good measure, please submit a case regarding your issue.

As a workaround when this happens:

Temporarily switch the track to sample mode, carry out your edit and then switch back to tick mode.
(Assuming your were in tick mode when the bug occurred)

I experience the bug in tick mode but very rarely in a new session.
If notes do become stuck, switching to sample mode enables me to move/trim the notes. After which, I can switch back to tick mode.

Try this before restarting the session. Otherwise, you MIGHT get an error when closing the session and lose 5 minutes of work (or whatever your backup is set too). That's happened to me only once so far.

Re: Weirdest Midi thing ever..
 

Thanks for all the info you provided. I went back to 22.7 after reading your posts. I had rolled back to 22.5 after encountering the midi editing issue, but I'm now able to do normal midi editing in 22.7. I hope it does get fixed soon though (without breaking anything else).

Re: MIDI Weirdness Persists in 2022.7
 

Is there a consistent phrase/ bug tracker at Avid that we can use to make sure all of our support requests are recognized and collated? I am troubled by the same issues and would like the MIDI weirdness addressed ASAP. When filing a support ticket, what words will they readily recognize?

Re: MIDI Weirdness Persists in 2022.7
 

I wish there was, in fact, some sort of bug log/tracker/reporter. Against my instinct, I opened a support case for this issue (because not being able to edit MIDI completely screws with my income-earning ability), and although I was very clear that this was a new issue that started with 2022.6, that other people here were noticing it, and that I had done all of the standard 101-level, and 201-level troubleshooting on my system (which is still unfortunately an old-school cheesegrater running Mojave, so they jumped to "not-supported/tested system") I still got the "trying to help me fix the issues with my system" "support" treatment, which of course, didn't solve it, and just cost me time that I was not being paid for, but that the Support Techs were being paid to recommend and review. I just wanted to add my voice to the chorus, so that maybe they'd prioritize this bug.

Re: Weirdest Midi thing ever..
 

ok could you check this: just close and reopen the session - I know it sounds crazy but for me it fixed the problem (at least in the song I`m working on right now)

Re: Weirdest Midi thing ever..
 

I noticed something similar. Before I read take77's posts, i found that a session in which midi notes were fixed rigid was now normal. I could now edit the midi. But I wasn't having any of what seemed like a fluke. I still rolled back to 22.5.
There's definitely something to what you are saying.

Re: Weirdest Midi thing ever..
 

You are very welcome.
I've benefited from your posts as well.
Glad to hear that you are able to go forward in your sessions using the latest version.

Looking forward to a fix also.
Fixing this without trading one bug for another would make it the keeper version.

Re: Weirdest Midi thing ever..
 

As this seems to be an issue caused by certain older versions of PT, has anyone tried re-importing the session data into a new project?

This might be a more robust way of fixing the issue (backwards compatibility may be an issue tho').

Re: Weirdest Midi thing ever..
 

Definitely!

Re: 2022.7.0 MIDI Problems
 

Yes,
Facing the same irritating issue.
Hope Avid resolve it soon.

Re: 2022.7.0 MIDI Problems
 

They are releasing a fix in the upcoming release, but not sure when that is. They are aware of this. I have a fix here, but only had to use it one time. I just closed the session and re-opened and the midi issue went away. There are fixes for various MIDI operations in the current beta which will fold into the next release.

G

Re: MIDI Quantize/Selection BUG 2022.6
 

A question to Mr.Gregory Ives:

Is there any incentive of fixing the midi timing of Pro Tools? The midi data is recorded early, and it messes up any performance. Are they taking Midi seriously at Avid? One could dream of a midi stable-reliable M1 native Pro Tools, that would be a comeback.....

Re: MIDI Quantize/Selection BUG 2022.6
 

Well, after three months of "support" and everyone (of support) telling me that the problem was with my machines, with my system, (Yes, avid made me buy a new machine after making me believe it, upload and reinstall more than 6 different systems for testing and nothings change the bugs), send your system report, make new user account admin, delete preferences, reinstall, try this, try that... and my deadlines running.
After try in 3 different machines and I found out that it was resolved when I installed 2022.5 - they were left speechless. But they didn't recognize the error, let's investigate, be happy!
Only after creating a bug list with more than 40 people involved did they listen to me and after I start publishing my unworthiness in the networks…

Avid e-mail response:
"Thank you for your response and sorry for the inconvenience.

Since this is a confirmed bug that has been logged on our end. Here are the bug number for reference: PT-289553 and PTSW-196673.
and there is also no ETA (estimated time of arrival) on when it will be fixed. The standard procedure is to close the case, but reopen the case if you need an update. If the case is unable to be reopened, feel free to reach out to us through the following channels:"


But in attach you can see 2 bugs > that they only recognized 2 bugs out of 15 or more... for you to have an idea the previous email sent me a link with "gifts" from the inner circle that I had… just for “almost” told me: "calm down we have gifts do not get angry".
I just want a software that works without problems and a software reliable. I pay for it. All we pay for it and we use this software all day… Being treated like “I'm the problem” I think is a veiled lack of respect. I'm not a new avid user, over 10 years. I'm not happy at all. I see other companies as good as treating customers much better. Avid support just made me waste my time and money. it’s really bad and at the same time ridiculous. I'm sure that when they implemented the “quantize function with follow grid” they erased some code line. All they should do is say thanks and fix the bug that wasn't in the previous version and ask the great team at GlobalLogic to put someone to oversee this problem. I'm sure it will make the tens of dollars we spend every year worth a lot. . It's been months with one-legged software or call me at least to be a beta tester, since I'm paid to be anyway.


All the best, guys!

Thanks for the space.

Re: MIDI Quantize/Selection BUG 2022.6
 

Well, after three months of "support" and everyone (of support) telling me that the problem was with my machines, with my system, (Yes, avid made me buy a new machine after making me believe it, upload and reinstall more than 6 different systems for testing and nothings change the bugs), send your system report, make new user account admin, delete preferences, reinstall, try this, try that... and my deadlines running.
After try in 3 different machines and I found out that it was resolved when I installed 2022.5 - they were left speechless. But they didn't recognize the error, let's investigate, be happy!
Only after creating a bug list with more than 40 people involved did they listen to me and after I start publishing my unworthiness in the networks…

Avid e-mail response:
"Thank you for your response and sorry for the inconvenience.

Since this is a confirmed bug that has been logged on our end. Here are the bug number for reference: PT-289553 and PTSW-196673.
and there is also no ETA (estimated time of arrival) on when it will be fixed. The standard procedure is to close the case, but reopen the case if you need an update. If the case is unable to be reopened, feel free to reach out to us through the following channels:"


But in attach you can see 2 bugs > that they only recognized 2 bugs out of 15 or more... for you to have an idea the previous email sent me a link with "gifts" from the inner circle that I had… just for “almost” told me: "calm down we have gifts do not get angry".
I just want a software that works without problems and a software reliable. I pay for it. All we pay for it and we use this software all day… Being treated like “I'm the problem” I think is a veiled lack of respect. I'm not a new avid user, over 10 years. I'm not happy at all. I see other companies as good as treating customers much better. Avid support just made me waste my time and money. it’s really bad and at the same time ridiculous. I'm sure that when they implemented the “quantize function with follow grid” they erased some code line. All they should do is say thanks and fix the bug that wasn't in the previous version and ask the great team at GlobalLogic to put someone to oversee this problem. I'm sure it will make the tens of dollars we spend every year worth a lot. . It's been months with one-legged software or call me at least to be a beta tester, since I'm paid to be anyway.


All the best, guys!

Thanks for the space.

Re: MIDI Quantize/Selection BUG 2022.6
 

No sure I understand the question, but I'm a proficient player so have not had a lot of trouble with that thru the years too be honest.. If you record in a a low buffer size that will help you. If you are doing it another way and are just quantizing it, then there some things to be aware of on any DAW. ProTools Midi has come a long way in my opinion. Even Olafur Arnald says it's light years from what it was, so a lot of what I hear on the midi side to me is just that some folks are used to too many options. I used to be a HUGE power user of Digital Performer and still use it sometimes. All of the DAW have their strengths. I know a lot of folks that like Cubase for midi and used to be big Live users, but had to switch to Cubase because of the limitations in Film arena.

There IS that new thing that is bugging a lot of people with the Quantizing that you can turn off. A couple of composer buddies of mine in LA did that. Also one of them uses VSL Pro for their interface with VI's.. I used to but found that my Templates are not that big and when I used that stuff it was creating bigger and bigger ones, so I don't use that anymore.
Sorry for the late response. I was doing a big project and took yesterday out of the room.

You can read about it here: Quantize Enhancements.


(Pro Tools Artist / Studio / Ultimate)
Quantize can “Follow Bars|Beats Grid”
Quantize MIDI events via key command, without needing to open the Event Operations Window
https://avid.secure.force.com/pkb/ar...s?retURL=%2F_1

Re: 2022.6 MIDI Quantize/Selection Weirdness BUG
 

ughh, I have to stop doing this.......got to change my ways and make it a habit to check the forums for at least a week or two before upgrading....

Re: MIDI Quantize/Selection BUG 2022.6/2022.7 Support Case Situation
 

Well, after three months of "support" and everyone (of support) telling me that the problem was with my machines, with my system, (Yes, avid made me buy a new machine after making me believe it, upload and reinstall more than 6 different systems for testing and nothings change the bugs), send your system report, make new user account admin, delete preferences, reinstall, try this, try that... and my deadlines running.
After try in 3 different machines and I found out that it was resolved when I installed 2022.5 - they were left speechless. But they didn't recognize the error, let's investigate, be happy!
Only after creating a bug list with more than 40 people involved did they listen to me and after I start publishing my unworthiness in the networks…

Avid e-mail response:
"Thank you for your response and sorry for the inconvenience.

Since this is a confirmed bug that has been logged on our end. Here are the bug number for reference: PT-289553 and PTSW-196673.
and there is also no ETA (estimated time of arrival) on when it will be fixed. The standard procedure is to close the case, but reopen the case if you need an update. If the case is unable to be reopened, feel free to reach out to us through the following channels:"

When I reply ask for this details:

"Thank you for your response and sorry for the inconvenience.

PT-289553 is about MIDI notes that can no longer be selected or edited
PTSW-196673. is about nudging

In the meantime, while waiting for the fixes,
the workaround is to install PT2022.5."

But in attach you can see 2 bugs > that they only recognized 2 bugs out of 15 or more... for you to have an idea the previous email sent me a link with "gifts" from the inner circle that I had… just for “almost” told me: "calm down we have gifts do not get angry".
I just want a software that works without problems and a software reliable. I pay for it. All we pay for it and we use this software all day… Being treated like “I'm the problem” I think is a veiled lack of respect. I'm not a new avid user, over 10 years. I'm not happy at all. I see other companies as good as treating customers much better. Avid support just made me waste my time and money. it’s really bad and at the same time ridiculous. I'm sure that when they implemented the “quantize function with follow grid” they erased some code line. All they should do is say thanks and fix the bug that wasn't in the previous version and ask the great team at GlobalLogic to put someone to oversee this problem. I'm sure it will make the tens of dollars we spend every year worth a lot. . It's been months with one-legged software or call me at least to be a beta tester, since I'm paid to be anyway.


All the best, guys!

Thanks for the space.

Re: MIDI Quantize/Selection BUG 2022.6
 

This is absurd!

Well, after three months of "support" and everyone (of support) telling me that the problem was with my machines, with my system, (Yes, avid made me buy a new machine after making me believe it, upload and reinstall more than 6 different systems for testing and nothings change the bugs), send your system report, make new user account admin, delete preferences, reinstall, try this, try that... and my deadlines running.
After try in 3 different machines and I found out that it was resolved when I installed 2022.5 - they were left speechless. But they didn't recognize the error, let's investigate, be happy!
Only after creating a bug list with more than 40 people involved did they listen to me and after I start publishing my unworthiness in the networks…

Avid e-mail response:
"Thank you for your response and sorry for the inconvenience.

Since this is a confirmed bug that has been logged on our end. Here are the bug number for reference: PT-289553 and PTSW-196673.
and there is also no ETA (estimated time of arrival) on when it will be fixed. The standard procedure is to close the case, but reopen the case if you need an update. If the case is unable to be reopened, feel free to reach out to us through the following channels:"

When I reply ask for this details:

"Thank you for your response and sorry for the inconvenience.

PT-289553 is about MIDI notes that can no longer be selected or edited
PTSW-196673. is about nudging

In the meantime, while waiting for the fixes,
the workaround is to install PT2022.5."

But in attach you can see 2 bugs > that they only recognized 2 bugs out of 15 or more... for you to have an idea the previous email sent me a link with "gifts" from the inner circle that I had… just for “almost” told me: "calm down we have gifts do not get angry".
I just want a software that works without problems and a software reliable. I pay for it. All we pay for it and we use this software all day… Being treated like “I'm the problem” I think is a veiled lack of respect. I'm not a new avid user, over 10 years. I'm not happy at all. I see other companies as good as treating customers much better. Avid support just made me waste my time and money. it’s really bad and at the same time ridiculous. I'm sure that when they implemented the “quantize function with follow grid” they erased some code line. All they should do is say thanks and fix the bug that wasn't in the previous version and ask the great team at GlobalLogic to put someone to oversee this problem. I'm sure it will make the tens of dollars we spend every year worth a lot. . It's been months with one-legged software or call me at least to be a beta tester, since I'm paid to be anyway.


All the best, guys!

Thanks for the space.