View Single Post
  #2  
Old 05-31-2019, 11:23 PM
Top Jimmy's Avatar
Top Jimmy Top Jimmy is offline
Moderator
 
Join Date: Oct 2005
Location: Spokane, WA
Posts: 5,099
Default Re: Best way to report bugs to Avid?

Create a support case. It's not a quick process but eventually real bugs can be recognized and logged.

For it to be recognized, it has to be repeatable in newly created sessions with specific steps documented to recreate it. Pro Tools sessions can behave weird but if the behavior can't be recreated in a new session, it's viewed as session corruption rather than a bug.

Once a bug is recognized, it gets classified by how critical the effect is. Bugs with a greater impact will get addressed sooner while bugs that are merely a nuisance can last for decades.

Also be forewarned that when dealing with support personnel, you also have to campaign against their inherent bias. The last bug I reported wasn't recognized and admitted as a bug. I documented how it's possible for the sample rate of a session to get changed (something that was never previously possible) and the support person I dealt with argued that this wasn't a bug. I chose not to bang my head against the wall.


Sent from my iPad using Tapatalk
__________________
James Cadwallader

Hackintosh - Gigabyte Z77X-UP5TH, Intel Core i7-3770K, 32GB 1600Mhz DDR3, 2x SATA 6Gb/s 240GB SSD, 3x SATA 6Gb/s 1TB HDD, 1x Glyph 2TB USB3 HDD, Sierra 10.12.6.

Pro Tools HD 2019.10, Focusrite Red 8Pre, Mbox 3 (Mac)
Pro Tools 11.3.2, Mbox2 (Win 7)

Presonus Faderport, Pro Tools | Control
Reply With Quote