Multiple Causes of Noise Blasts in Pro Tools 12.4, 12.5, 12.5.2 (?), 12.7, 12.7.1

[TheNeil]

Originally Posted by DarkandKurious

A hard limit on the output won't solve anything, as the DA can't produce above 0dBFS anyway - the hardware simply cannot produce a dynamic range of 800 odd dB. a 300dB noise blast will be just as loud as a 700dB one at the output if heard at the same monitor volume - it will be at the full volume of the DA. As we often mix needing to hear how much range there is to full scale, a limiter will not help.



Ice9 from what I understand (which I haven't tested) works by muting the sound if the threshold is reached, so a limiter with a 1:negative infinity ratio, rather than a limiter with with a 1: positive infinity ratio.

Either way, if PT could have something like that functionality built in, it seems like it would allow people to work in much greater ease, rather than having to use workaround plugins like the above.

[lemix]

Isn't there a function in current PT releases that pre scans and identify potential non compliant plugins upon starting up ?
Steinberg now using "Plugin Sentinel" to blacklist these.

[TheNeil]

So for what it's worth, I've submitted an Ideascale entry for an app-wide failsafe against dangerous output volumes: http://protools.ideascale.com/a/dtd/...ts/266672-3779

As per the above, I'm not saying it's an alternative to tracking down & fixing the bugs (@unkJE, I'm not out to undermine you here), but it makes sense for the app to fail gracefully in the meantime and not endanger people's ears. Not to mention reducing fear of another instance surfacing in the future. @DarkandKurious, I also kept the suggestion high-level, as you guys clearly know more about how such protection could be achieved, but if Ice9 can do it, so can PT.

Would appreciate if anyone in support of this idea gives it a vote; maybe it will get Avid's consideration if there's enough support.

[unkJE]

Originally Posted by TheNeil

So for what it's worth, I've submitted an Ideascale entry for an app-wide failsafe against dangerous output volumes: http://protools.ideascale.com/a/dtd/...ts/266672-3779

Would appreciate if anyone in support of this idea gives it a vote; maybe it will get Avid's consideration if there's enough support.

Fantastic - thanks for posting!

Just voted

[unkJE]

Originally Posted by TheNeil

So for what it's worth, I've submitted an Ideascale entry for an app-wide failsafe against dangerous output volumes: http://protools.ideascale.com/a/dtd/...ts/266672-3779

Just in case these Threads don’t get merged, fellow Member propower added this:

http://duc.avid.com/showpost.php?p=2421855&postcount=19

Voted on it FWIW. Yes the software should just not allow a > x jump in level in any output level in less than y amount of time. The max rate of change for a 20kHz signal is well known. Pretty much anything above that is a warning and more than a few samples in a row that exceed that rate of change (or a single sample at let's say 2X that rate of change) should result in an error stoppage or mute event. Simple math really. Using this method one could monitor at - 20dBFS and be well protected long before the output reaches 0dBFS. Protecting me at -1dBFS is not really protection. -1dBFS of pure noise is just as damaging. Any chance the company will implement anything like this though?

[grayter1]

If Reaper can do it, so can Avid...



tg

[unkJE]

Originally Posted by grayter1

If Reaper can do it, so can Avid...



tg

Thanks for helping to solve this - it definitely should come with Pro Tools, too!

[TheNeil]

Originally Posted by grayter1

If Reaper can do it, so can Avid...

Couldn't agree more!

[unkJE]

Originally Posted by grayter1

If Reaper can do it, so can Avid...



tg

Just posted your idea on IdeaScale & used your pic:

Please include this "Stop the Noise Blasts" Feature in Pro Tools immediately!

Vote it up!
http://protools.ideascale.com/a/dtd/...y!/266921-3779

Thanks again ... much appreciated

[grayter1]

Thanks. I voted.

tg