View Bug Details

IDProjectCategoryView StatusLast Update
0000328DCP-o-matic[All Projects] Featurespublic2019-02-13 23:46
ReporterTheo KooijmansAssigned To 
PrioritynormalSeverityfeatureReproducibilityhave not tried
Status acknowledgedResolutionopen 
Platform64 bitOSWindowsOS Version7
Product Version 
Target VersionFixed in Version 
Summary0000328: Use Nvidia CUDA to speedup render times

Is it possible to use the Nvidia CUDA technology to speedup render times?
Adobe Creative Cloud and others used this technology very succesfull to dramaticly increase rendertimes.

Now rendering takes place on the CPU core, the NVidia GTX card has hunderds of cores to do this...

TagsNo tags attached.
Estimated work requiredMajor



2014-03-31 11:12

administrator   ~0000313

There is some work being done by a guy on the openjpeg mailing list to accelerate that library with CUDA. If he succeeds it will work in DCP-o-matic too...

2017-02-18 12:49

reporter   ~0001616

Hm, it seems it is not happening as open source in the end: and

Any possibility of using this: ? Thye claim they are much faster then OpenJPEG.

Also, at the announcement of the latest OpenJPEG version ( ), they claim some performance improvemets are around hte corner: "Note that meanwhile, in the master branch, an important improvement has been merged, namely T1 optimizations and multithreading support (contribution from Even Rouault … Thanks a lot !). A (much) faster OpenJPEG is on track … Stay tuned for v2.2.0." - Would that be relevant for performance of DOM? It already uses my four cores 100 %.


2017-02-21 13:23

manager   ~0001617

DOM already contains some optimizations that are not part of the official OpenJPEG line.

Technically, it would be no problem to add GPU support to DOM. However, Carl doesn't want to add proprietary or commercial code to the project. Also, GPU support should be compatible with the multi-platform development approach of DCP-o-matic.

Keep in mind, Cinema servers do not play 'any' JPEG2000 codestream, but only a special restricted subtype. Not every highspeed J2C codec is able to keep the codestream within these limits. To deviate from this route means a risc of crashing servers.

So, Carl is definitely keeping an eye on GPU support, but he is for good reasons also careful about it. DOMs J2C codestream robustness has never been questioned as long as I remember following this project, and that is a very valuable asset for a free/open source software project.

  • Carsten


2017-02-22 13:48

administrator   ~0001620

As far as I know the stuff that OpenJPEG are now including is basically already in DoM. DoM multi-threads encoding itself, and it has a set of similar T1 optimizations that I offered to the project years ago.

I am not an expert on the innards of J2K nor CUDA, so this is a difficult task. I have done some work on the code but it is not, so far as I can see, suitable for cinema work out of the box, so it needs some modifications.


2019-02-13 21:31

administrator   ~0003083

Last edited: 2019-02-13 23:46

View 2 revisions

@carl: poznan-jpeg2k test script is run/test. dumpj2k shows numerous differences.

Bug History

Date Modified Username Field Change
2014-03-30 11:45 Theo Kooijmans New Bug
2014-03-31 11:12 carl Note Added: 0000313
2014-03-31 11:12 carl Status new => acknowledged
2015-06-12 10:49 carl Summary Use Nvidia CUDA to speedup rendertimes => Use Nvidia CUDA to speedup render times
2015-06-12 10:51 carl Target Version => 2.x
2015-06-12 11:19 carl Estimated work required => Major
2015-06-12 11:20 carl Severity major => feature
2017-02-18 12:49 Note Added: 0001616
2017-02-21 13:23 Carsten Note Added: 0001617
2017-02-22 13:48 carl Note Added: 0001620
2019-02-13 21:31 carl Note Added: 0003083
2019-02-13 23:46 carl Note Edited: 0003083 View Revisions