Tab To Transient Broken in 2021.3.1 [PT-271892 FIXED]

[Benny_Cha_Cha]

Originally Posted by ZEUSS

Then they were pulling our leg the whole time saying they re-wrote it from the ground up with 11 and AAX and all of that BS.... This is definitely getting tiring! They need to fix these OLD BS bugs.... Every year. Same issues. Same tired old error codes popping up. Same crappy VI performance... Same lame Midi bugs.... WHO tests this stuff????? Unreal!!!


I can usually come across most of these things people mention here right off the bat!! There should be NO excuses for what they charge yearly. They are supposed to be the "Industry Standard".....LOL

+10000000000000. They never rewrote anything.


Sent from my iPhone using Tapatalk

[Patheticus]

Avid FINALLY got back to me and all they said was to "Trash my preferences" which did nothing. SMFH. Waiting to hear back again.

[Obsidian Dragon]

Originally Posted by Patheticus

Avid FINALLY got back to me and all they said was to "Trash my preferences" which did nothing. SMFH. Waiting to hear back again.

Does anyone know of another program that needs to have preferences trashed? I don't claim to know every program, but none of the programs I use, other than Protools, requires this procedure. SMH

[JingleDjango]

I think that's a support tech just having a laugh. They can't have thought that would do anything. Sometimes I think they respond with gibberish like that just so they can update/clear the ticket and tell their supervisor they knocked off another support case. Job done, great work.

[bolooki]

Originally Posted by mattrixx

I have found that the area on which you click the waveform prior to Tab to transient is important.
You need to click on the lower half of the waveform for it to work correctly.

this have anything to do with smart tool vs other tools?

[mattrixx]

That is when using the smart tool. Sorry, should have included that.

[rinky]

Originally Posted by Obsidian Dragon

I don't claim to know what has been going on inside Avid development. I suspect even the developers from Protools 11 have been changed. Perhaps they outsource their development and code maintenance where the actual coders are always rotating in and out. I'm not knocking outsourcing as I've been in software development projects for over 20 years and can attest that outsourcing is a fact of life and economics. Ideally, detailed documentation and proper knowledge transfer take place, but more often than not, it doesn't. Avid is not the only company that faces these challenges but we, the end users, are the ones to suffer.

You'd think that their beta testers would catch this bug or other bugs that we get almost each update!

[Benny_Cha_Cha]

Originally Posted by rinky

You'd think that their beta testers would catch this bug or other bugs that we get almost each update!

WE are the beta testers...


Sent from my iPhone using Tapatalk

[zachxweeks]

I know this sounds sort of crazy (or really, really crazy), but I just updated to 2021.3.1 (on Windows 10) from 2020.11 and it seems like tab-to-transient isn't working as well as it used to. Yeah, I know, it feels insane to type this



Basically it seems to skip over transients that it absolutely should be catching. In this instance, I'm editing drums that have pretty sharp transients and it's very bizarre to me that this is happening. Tab-to-transient has been a huge part of my workflow and seemed to have the same threshold/sensitivity for the past 12 years that I have been a Pro Tools user.


I don't have elastic audio enabled on the tracks and usually don't need to, but I know that you can increase the "event sensitivity" on that right? I guess that would be an acceptable workaround?

I mostly just want to know if something changed in the PT software or if I'm running into some obscure issue here. And yes, it happens across multiple sessions, multiple different audio tracks, etc etc.

[Obsidian Dragon]

There is already a long thread about this issue here.