![]() For example, I imported HD video from a Nikon D5000, and Premiere required no conversion at all–I just dropped the clips into the source bin, and, from there, immediately into the timeline. Native support for massive R3D files generated by RED Digital Cinema cameras is new, as well as support for XDCAM HD 50, AVC-Intra footage, and HD video from some Canon and Nikon digital SLRs. For example, you’ll see notes like, “additive dissolve not translated cross dissolve used instead.” ![]() If you use only common effects and transitions, you may be able to do so without converting or even rendering–though you will still have to worry about how to share the gargantuan source files.When you import or export a Final Cut Pro project, Premiere will generate a translation report that details how effects, transitions, and other elements got carried over from one platform to the other. Mixing Macs and PCs in the same shop? Premiere Pro can now share projects and assets with Apple’s Final Cut Pro, and with Avid editing applications. Also, the accelerated effects are a bit of a tease–they are available for use only if you have one of the supported graphics cards installed, but they show up whether you have an appropriate card or not. The filtering is particularly useful because if you mix 32-bit effects and 8-bit effects, they’ll all render in 8 bits. Premiere’s Effects Browser now has three buttons at the top of its window–one that filters the list to show only GPU-accelerated 32-bit effects, one that shows only CPU-accelerated 32-bit effects, and one that shows only YUV color-space effects. Unfortunately, while those cards are coming out soon, Premiere won’t gain GPU-acceleration support for the GTX480 until the third quarter of this year, and Adobe hasn’t said anything yet about the GTX 470. Only when I started adding several tracks of HD clips and effects did Premiere start gobbling RAM the highest amount I saw was about 3.5GB.Īdobe says it will also support new cards from nVidia’s Fermi line, such as the GTX 470 and GTX 480, which are supposed to be available this month. However, with only a simple, single-track project open, Premiere used merely 214MB of RAM–it did not take up the entire 6.5GB, and my system ran perfectly well with several other applications open. On my 8GB system, the default setup reserved 6.5GB for Premiere and 1.5GB for everything else. However, I had none of the RAM-related problems I’ve occasionally encountered with Premiere Pro CS4–none of the slow reading and writing of data to the hard drive instead of to RAM, fewer playback and timeline scrubbing hesitations, and generally smoother operation overall.Īs with the 64-bit Photoshop, Premiere Pro requires that you allocate RAM manually–up to a maximum of 128GB. Relying on CPU power, Premiere Pro CS5 didn’t render any more quickly than Premiere Pro CS4 did. ![]() When I installed a beta version of Creative Suite 5 on my test system, a dual-Xeon workstation running Windows 7 64-bit with 8GB of RAM, I did not notice a substantial improvement in rendering speed–but then, my workstation doesn’t have one of the approved graphics cards.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |