PT mixer headroom severely reduced to 20dB over 0dBFS. Bug?

[Rich Breen]

Originally Posted by seanmccoy

...Now can somebody tell me when one might need 20dB over full scale?

One needs to know that all the basic DSP operations are solid in the tool that you depend on for your living.

[seanmccoy]

Originally Posted by Rich Breen

One needs to know that all the basic DSP operations are solid in the tool that you depend on for your living.

Understood.

[Wolfgang Eller]

Originally Posted by Rich Breen

One needs to know that all the basic DSP operations are solid in the tool that you depend on for your living.

Rich, don't get me wrong, I'm completely with you but I'm totally amazed that someone found that bug.

[Reml@P]

Originally Posted by JFreak

If it is recorded wrong, record it again and do it right.

Not a helpful response in the slightest. As many have said, there are 1001 situations where poorly recorded audio is sent your way to correct.

If I had the same attitude as your reply, I'd be out of work in no time. Just saying.

[JFreak]

Originally Posted by Reml@P

Not a helpful response in the slightest. As many have said, there are 1001 situations where poorly recorded audio is sent your way to correct.

If I had the same attitude as your reply, I'd be out of work in no time. Just saying.

Some fights you win, some fights you lose. If you have used 20dB dynamics of your 120dB converter range, you just cannot polish a turd. If you have something to play with it is a different story. Maybe I am lucky and never ever have I even had to think about boosting +20dB but yea, if it is so bad I would ask if it could be done again properly.

[Eric Lambert]

It needs to be fixed, plain and simple. The good news is that it affects almost no one so we're not losing sleep (or work) as Avid addresses this.

[JFreak]

Originally Posted by Eric Lambert

It needs to be fixed, plain and simple. The good news is that it affects almost no one so we're not losing sleep (or work) as Avid addresses this.

True

[Franklyn]

does anyone know from which version this problem arose?

[Tweakhead]

Originally Posted by Wolfgang Eller

Rich, don't get me wrong, I'm completely with you but I'm totally amazed that someone found that bug.

Yes, thanks to some incredible detective work by Farhoof.

Although it's really not defined as a bug in my book, but a collossal F&*!-Up. To seemingly replace the floating-point mix engine with something that is not the floating-point mix engine is really not something simply malfunctioning in the code. The fact that this could even happen scares the crap out of me, and makes me wonder what else is going on.

We're a third of the way thru the year, and all I got so far for my $399 annual "support" fee is a popup "qwerty-MIDI-keyboard" (that doesn't even grey-out the a-z indicator when active), and a host-load of other bugs such as tab-to-transient, etc etc. Maybe that's why several bugs such as Zoom-Toggle, and double-clicking on folders when saving/loading etc are malfunctioning too.

[JFreak]

Originally Posted by Tweakhead

all I got so far for my $399 annual "support" fee is a popup "qwerty-MIDI-keyboard"

You also got Big Sur support and it is likely you would get M1 support this year too. Nobody knows but once Avid drivers are good to go I bet PT will be native as well