![]() ![]() Load balancing isn’t as even across cores in Premiere as it is for Blender. This is an artifact of how applications are built: Premiere is built, at least with this standard YouTube-ready encoding configuration, to favor frequency heavily, and Threadripper does fall behind in that front. For us, a 27% reduction would add up to several hours of render time per week, but for a hobbyist, it’s better value to buy something like the 9900K or 8700K.Īs for Threadripper, it doesn’t handle our 4K60 clip as competitively as it handles Blender rendering, which we’ll look at next. It’s just going to depend on how much that time is worth to the individual or organization. For most of our normal audience, that’s pretty rough value when considering the already reasonable performance of the 9900K. How meaningful that improvement is will depend upon your use case: For professionals where every minute counts, like we’ll talk about in Blender for Threadripper momentarily, that 27% reduction for $1000 might be great value. The Intel i9-9980XE stock CPU completed the same render in 22% less time than the 9900K with IGP acceleration, with the $3000 Intel Xeon 3175X completing its render in 12 minutes, reducing the time required from the $2000 9980XE by 27%. Note that IGP acceleration helps primarily with our charted reviews, but doesn’t do as much for heavy a-roll and b-roll videos like this one. The Intel i9-9900K stock CPU completed our render in 24 minutes, or 21 minutes when using QuickSync, which isn’t available on the HEDT CPUs. Premiere likes cores more than Photoshop, but is still heavily frequency dependent. #Intel quicksync and blender software#Adobe software in general, including Photoshop, really likes frequency. This workload represents what we go through every day when rendering reviews. Our years of experience with Premiere have taught us that our charts sections are heavily reliant upon the GPU, so those have been removed from CPU tests, and that working with high bitrate, high resolution files will stress the CPU heavily. H.264 is used, as YouTube still isn’t ready for primetime on H.265. We firmly believe this is a real-world scenario, knowing most of the tech YouTubers you all watch, and find this a representative workload for content creators. ![]() The render is CUDA-accelerated, but the majority of the work still bottlenecks on the CPU. We’ll play some of that file back now so you can get an idea for what’s being rendered. The video is an 11-minute truncated GPU review, using only a-roll and b-roll clips at 4K60 and rendered at 45Mbps. Our first test uses Adobe Premiere to encode a real GN clip.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |