MP 7,1 QT and Afterburner

[bxs]

Can anyone explain clearly what benefits the Afterburner provides for "QuickTime Player X" use ? Thanks

 

[deconstruct60]

Can anyone explain clearly what benefits the Afterburner provides for "QuickTime Player X" use ? Thanks

The same as the rest of the places where apps open and view ( so by side effect decompress ) ProRes files. The basic foundational ProRes support in Apple's libraries can farm work off to Afterburner if it is present. Otherwise, they use the software decoders that Apple has developed over time. There is little special apps have to do to engage Afterburner in they are simply using the provided Apple API for using ProRes. They aren't trying to keep apps from using it at all if on the usage path they have previously outlined for ProRes support.

It would actually be odd if other apps that accessed ProRes actually did not engage Afterburner when dealing with these files if they are using the standard APIs.

This core issue is there was no reason for QuickTime Player" to reinvent the wheel and use different ProRes file handlers than the rest the of API already in macOS. Afterburner speeds up the API not segregated apps.

P.S. the reason why Apple docs say "other supported 3rd party apps" (or something to that effect) in the Afterburner docs is that they have no absolute control over what folks don't call in their apps. If Apple provides an API for something and they run off an re-invent the wheel (for whatever reason) then they don't get it. But it isn't like apple is hiding or granting special "lordship of burner-ness" to only a select few apps.

 

[bxs]

The same as the rest of the places where apps open and view ( so by side effect decompress ) ProRes files. The basic foundational ProRes support in Apple's libraries can farm work off to Afterburner if it is present. Otherwise, they use the software decoders that Apple has developed over time. There is little special apps have to do to engage Afterburner in they are simply using the provided Apple API for using ProRes. They aren't trying to keep apps from using it at all if on the usage path they have previously outlined for ProRes support.

It would actually be odd if other apps that accessed ProRes actually did not engage Afterburner when dealing with these files if they are using the standard APIs.

This core issue is there was no reason for QuickTime Player" to reinvent the wheel and use different ProRes file handlers than the rest the of API already in macOS. Afterburner speeds up the API not segregated apps.

P.S. the reason why Apple docs say "other supported 3rd party apps" (or something to that effect) in the Afterburner docs is that they have no absolute control over what folks don't call in their apps. If Apple provides an API for something and they run off an re-invent the wheel (for whatever reason) then they don't get it. But it isn't like apple is hiding or granting special "lordship of burner-ness" to only a select few apps.

Thanks....

To measure the affects/benefits of the Afterburner might to run a test case with and without it, and compare the two results. However, I suspect this is not a rigorous test procedure.

What I would like is a utility that can collect the work the Afterburner is given and for it to report out some meaningful numbers. If Apple doesn't provide this then maybe some clever 3rd party can pickup the slack so to speak.

My understanding is that the Afterburner should seamlessly pick up, or be given, work to do to relieve the burden on the GPU and CPU.

As an aside... Activity Monitor provides insights on the system's resource use such as CPU use, Memory use, disk reading/writing, network transfers, and File caching. So why not display Afterburner's use ?