The most significant change in v3.4 is support for incremental code-stream flushing. This long overdue feature enables compressed data to be flushed periodically to the final code-stream so that it does not need to be stored in memory. Previous versions required all compressed data to be stored in memory until the image was completely processed. The kdu_codestream::flush function may now be called as frequently as required, while the image is being compressed. Of course, for this to be of any benefit, you must select a code-stream progression order which is consistent with incremental flushing. The new feature is extensively documented in the description of the `kdu_codestream::flush' function.
GCC builds now offer the same support as MSVC builds for huge files, having compressed sizes ranging into the Terabytes.