Tag: Performance easyDCP Creator
Found 2 FAQs and 1 videos.
This FAQ is valid for
easyDCP Creator+   all versions
IMF Creator   from Version 4.0.X

 

easyDCP Creator+, easyDCP JPEG 2000 Transcoder are highly optimized for running on multi-processor/multi-core machines. On Windows and from easyDCP Creator(+) 3.3.X can also use one or more CUDA® enabled graphics devices.

We recommend the following minimal system configuration:

  • Windows PC (Windows 64 bit, Version 7 or higher) or Intel Mac (Mac OS X 64 bit, Version 10.7 or higher)
  • You also need a minimum of 2 GB RAM
  • Installation occupies 200 MB free disc space
  • Fast hard disk is also recommended

For best performance, opt for the following specifications:

  • CPU with 6 cores or more
  • 8 GB RAM
  • Fast SSD
  • A CUDA-enabled graphics device for encoding with the following specifications:
    • Compute Capability 2.0 or higher
    • Minimum of 1 GB memory, better 4 GB of memory
    • Preferably connected with 16 PCI Express lanes
    • The more cores, the better
    • E.g. NVIDIA GeForce 980 Ti
This FAQ is valid for
easyDCP Creator+   all versions
IMF Creator   from Version 4.0.X

 

With the new version easyDCP Creator+ 3.7.3 or higher, a significant increase in performance for Windows systems in GPU mode could be achieved with maximum values of up to 125fps.

System 1:

  • Intel Core i9-9900K @ 3.60GHz 8 Cores
  • 16 GB RAM
  • Samsung SSD 970 EVO 1TB (NVMe M.2 SSD)
  • NVIDIA GeForce GTX 1060 6GB 

System 2:

  • AMD Ryzen Threadripper 2950X
  • 64 GB RAM
  • Samsung SSD 860 EVO 1TB
  • NVIDIA GeForce RTX 2080 

System 3:

  • AMD Ryzen 9 3900X 12-Core
  • 32 GB RAM
  • Samsung SSD 970 Pro 1TB (NVMe M.2 SSD)
  • NVIDIA GeForce RTX 2080 Ti

Test results

System TIFF
2623 frames, 2K, 16-bit
ProRes
2400 frames, 2K, 12-bit
System 1 77.15 fps 66.67 fps
System 2 109.29 fps 96.00 fps
System 3 124.90 fps 96.00 fps

The following settings were used in easyDCP Creator+ 3.7.3:

  • Color Transform: RGB BT.709 nach XYZ (DCI)
  • Maximum Bitrate: 250 Mbit/s

The source image material and the destination folder were in all cases on an SSD, if possible on an NVMe SSD.