Sample Rounding Issue!!!!

[foxes]

Originally Posted by innesireinar

I also work with many other PT user everyday (unfortunately today only without physical contact) and found them focused especially on AAE errors and other issues. And by viewing this threads you can see that only few of us (duc registered) are posting here.

Again spot on.

[innesireinar]

Originally Posted by foxes

Again spot on.

Great that you are active here on this thread.
However today I was mixing the last track of an album and switched to PT11. Wonderful!!!
No AAE errors, no sample rounding when moving midi clips (also did some edit). Then I was thinking that at the end of 2017 I gave Avid 700 (at discount price) for the reinstatement, 339 in the 2018 and 339 some months ago for plan..... then back to PT11.........

[foxes]

Originally Posted by innesireinar

Great that you are active here on this thread.
However today I was mixing the last track of an album and switched to PT11. Wonderful!!!
No AAE errors, no sample rounding when moving midi clips (also did some edit). Then I was thinking that at the end of 2017 I gave Avid 700 (at discount price) for the reinstatement, 339 in the 2018 and 339 some months ago for plan..... then back to PT11.........

We got to try to keep some attention on this 'Avid ignored' bug.

I hear you, Avid have a time limit for me on fixing this bug or else it'll be where I get off this Avid "pay me upfront for practically nothing" train.

[musicman691]

Originally Posted by foxes

We got to try to keep some attention on this 'Avid ignored' bug.

I hear you, Avid have a time limit for me on fixing this bug or else it'll be where I get off this Avid "pay me upfront for practically nothing" train.

I was hoping for some MIDI fixes with 2020.3 but sadly nothing on what Avid had acknowledged and can repro. Makes me wonder if I should keep up with my renewal this year. Hell Logic X is only $199 US.

[Evermore]

Originally Posted by innesireinar

A couple of years ago, during the 2018.xxx era, I spent some days with Avid tech support sending them many sessions, some created with the 2018, some with pt11 at many different tempo and SR. They also stated that on the 2018 the bug was there while on pt11 not. I'm talking about midi stuff, especially when move/copy clips by alt-drag. We found that the only condition where this bug didn't happen was on a session at 48KHz 125bpm where every tick matched to a integer sample. They told me that they would have passed this to the tech staff. Nothing happened and after 2 years this bug is still here. I hope you will have better luck (for you and for all of us). It would be great to share this with you (and other). I can send you the same sessions that I sent them in the past (that I still have). But for this test you need also pt11 installed.

I was not aware it's been around for that long. I'm assuming the issue was introduced in PT12 which came out in 2015.

I cannot use PT11 but that would have been very helpful. I might need your help if you are willing to provide any gifs for comparisons between PT11 and PT12 and above.

Are gifs allowed on this forum? Either I will be creating short gifs of the issue to go along with my findings and workarounds.

[Evermore]

Originally Posted by foxes

We got to try to keep some attention on this 'Avid ignored' bug.

Yes, and I agree.

Short story... I bought Cubase 8.0 back in 2014 and was loving it. Soon after, I and a few many others found a major issue with the GUI on Macs affecting zoom functions and edits of audio. It was so slow that it was unusable working with a few tracks. Trust me it was terrible!

At first Steinberg was in denial and saying it was not reproducible on their end. Guess what? Everyone at the Steinberg forum came together to confirm the issue to make Steinberg aware and also pressuring and saying we will not update to the next version unless it is fixed. By Cubase 9.5, Steinberg had fixed it and it was a blessing for everyone being affected.

I'm hoping that we can bring more attention here soon. Even the ones that are not worried about this bug due to workflows can provide help by confirming the issue does happen on their systems. This would help greatly.

If it wasn't in PT11 like innesireinar mentioned, then it means it can be fixed.

[XJENSEN]

I gave up years ago. They just won't fix it. Pro Tools remains unusable for MIDI (well, not completely usable).

Reading this... I requested Avid to reopen all my cases relating to this issue. They responded it has now been escalated. Examples of cases I reported back in 2016 (!).

03106352 Separate MIDI clip (Command+E) doesn't adhere to grid Bug Logged/Known Defect 12/16/2016
03108869 MIDI loop trimming fails 12/21/2016
03106703 MIDI notes disappearing when switching MIDI track from sample- to tick-based Bug Logged/Known Defect 12/17/2016
03106464 Impossible to copy/paste/drag correct MIDI clips or selections 12/16/2016
03106431 MIDI notes randomly don't play, although visible in the clip 12/16/2016
03106402 Trimming looped MIDI clip end includes unexpected further notes 12/16/2016
03106397 MIDI range selection includes unexpected events 12/16/2016
03700600 MIDI events randomly disappearing when copying regions 5/9/2019

Will keep you posted when (if) I get any update from Avid.

[XJENSEN]

I also think this topic should live on in the Pro Tools 2020 forum instead of being tucked away in older sections.

[innesireinar]

Originally Posted by XJENSEN

I also think this topic should live on in the Pro Tools 2020 forum instead of being tucked away in older sections.

I was thinking the same thing

[foxes]

Originally Posted by musicman691

I was hoping for some MIDI fixes with 2020.3 but sadly nothing on what Avid had acknowledged and can repro. Makes me wonder if I should keep up with my renewal this year. Hell Logic X is only $199 US.

Me too.

Defo repro as well. I've given Avid all the money they are gonna get from me unless this fix this!