NVIDIA CUDA technology in Adobe Premiere Pro & Mercury playback engine

Started by Stefan, July 22, 2010, 05:29:09 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.


QuoteProfessional video editing demands enormous computational power, especially when
you have HD video firmly established as the de facto standard and the increasing
popularity of 4K and other higher-resolution formats. Simply manipulating high
resolution footage is a laborious task, even with the most powerful workstations; editors
apply changes and then wait patiently for renders to complete. Full quality previews of
complicated timelines are only possibly after a lengthy export and encode process. In the
past, users demanding more interactive control or those with high productivity
requirements had no choice but to spend tens of thousands of dollars on custom
hardware solutions.  
Adobe Premiere Pro CS5 takes a bold step forward with its new Mercury Playback
Engine by leveraging the massive parallel computational power of a Graphics Processor
unit (GPU). With a quantum leap in performance afforded by the GPU, HD video
editing of complex projects suddenly becomes interactive. Most high-end workstations
today feature powerful GPUs, brining to all Premiere users an editing experience
previously available only to professionals with the highest production budgets.
The Mercury Playback Engine was an ambitious project and required close collaboration
between Adobe and NVIDIA®, the GPU manufacturer. This whitepaper is intended for
those readers interested in the technical background of GPU computing, and specifically
how the parallel processing capability of NVIDIA GPUs provides such a remarkable
advancement for video processing. Although the technical detail presented herein is
certainly not required for effective use of the Mercury Playback Engine, it can serve to
better educate hardware configuration and purchasing decision and to satisfy the
technical curiosity of those hardware-savvy users.

Get whitepaper here

Read more at Icrontic