ShopDreamUp AI ArtDreamUp
Deviation Actions
Download here
This is a medium-sized release that fixes some bugs and adds a couple of new features.
Key features with explanations:
Full list:
--User changes
-Add support for Exr files which use 32-bit floats for each RGBA channel.
-Allow for clearing an individual color curve.
-Allow for saving multiple image types in EmberRender and EmberAnimate. All writes are threaded.
-Remove --bpc command line argument. Add format --png16 as a replacement.
-Remove --enable_jpg_comments and --enable_png_comments command line arguments, and replace them with --enable_comments which applies to jpg, png and exr.
-Add menu items to variations and affine spinners which allow for easy entry of specific numeric values like pi.
-Make final render dialog be wider rather than being so tall.
-Added panorama1 and panorama2 variations.
--Bug fixes
-Fix several OpenCL build errors that were occurring on Mac. Some still remain.
-Remove ability to save bitmap files on all platforms but Windows.
-Fix bug where clearing the final xform, but leaving it present, then editing it would crash the program.
-Disallow the use of synth when randomly generating xforms if the user has an Nvidia device present on their system.
-crackle had a bug with Nvidia GPUs.
-Only allow crackle_cellsize to be greater than 0.
-Typing in the xform color index spinner produced strange results.
-Returning from palette editor did not always update xform color indices.
-Cleaner exit on some failures.
-Better reporting of OpenCL errors.
This is a medium-sized release that fixes some bugs and adds a couple of new features.
Key features with explanations:
- EXR is an image format developed by the movie industry to store extremely high precision color channel information, rather than the usual 8 bits per channel. It does this by using a 32-bit float for each RGBA channel. Some people call this High Dynamic Range (sometimes implemented as 10 bits per channel). In order to do this, I reworked much of the internal coloring code for the final color correction phase of the algorithm. This means I have finally removed all of the last remnants of strange flam3 code that converts between normalized and non-normalized color range values. The downside is that this requires more memory, but it shouldn't be too big of a deal. Using EXR is available in the final render dialog, as well as on the command line with --format=exr. Note that if you want high precision, but are not a fan of EXR, you can always use 16-bits per channel PNG files as the output on the command line via --formatng16.
- Reworking this code led me to remove the --bpc command line option as well as some others. The image format implicitly specifies what the pixel type is.
- When rendering on the command line, you were only able to specify one image output type. This could be a real pain if you were trying to see which file type was best for your images. Now, you can specify one or more types all at once with the --format option like so: --format=bmppngjpgpng16exr
- The panorama 1 and 2 variations are interesting new developments from tatasz. I've ported them to Fractorium, so a big thanks to her!
- Note that despite fixing some OpenCL compiler errors for Mac, a recent update of the Nvidia drivers broke compilation for some variations when using double precision. So if you're running this on a Mac and run into that problem, switch back to single precision. Remember, most flames are fine with single precision and it's much faster (2-32x) on the GPU. Future driver updates from Nvidia may fix this problem.
Full list:
--User changes
-Add support for Exr files which use 32-bit floats for each RGBA channel.
-Allow for clearing an individual color curve.
-Allow for saving multiple image types in EmberRender and EmberAnimate. All writes are threaded.
-Remove --bpc command line argument. Add format --png16 as a replacement.
-Remove --enable_jpg_comments and --enable_png_comments command line arguments, and replace them with --enable_comments which applies to jpg, png and exr.
-Add menu items to variations and affine spinners which allow for easy entry of specific numeric values like pi.
-Make final render dialog be wider rather than being so tall.
-Added panorama1 and panorama2 variations.
--Bug fixes
-Fix several OpenCL build errors that were occurring on Mac. Some still remain.
-Remove ability to save bitmap files on all platforms but Windows.
-Fix bug where clearing the final xform, but leaving it present, then editing it would crash the program.
-Disallow the use of synth when randomly generating xforms if the user has an Nvidia device present on their system.
-crackle had a bug with Nvidia GPUs.
-Only allow crackle_cellsize to be greater than 0.
-Typing in the xform color index spinner produced strange results.
-Returning from palette editor did not always update xform color indices.
-Cleaner exit on some failures.
-Better reporting of OpenCL errors.
Fractorium 23.23.8.1 Released
This release is the first in two years and adds a few small features and fixes some bugs. In addition to that, we've upgraded to Qt 6.5.1 which means you need to reload your stylesheets for things to look correct. As always, a big thanks to Michel Mastriani (@triptychaos) of Brazil for helping with the Mac and Linux installers. Also, thanks to the various contributors on Bitbucket who submitted pull requests. --User changes -Add Clear Sequence button to the Sequence Panel. -Add animation preview in the sequence generator output pane. -Add two new options --width and --height to EmberRender and EmberAnimate to allow the user to specify absolute dimensions to render the image at. -Add a new option to EmberAnimate --ignore-existing which makes it skip rendering a frame if the files from all of the requested extensions for that frame already exist. -Add new preset dimensions to the right click menu of the width and height fields in the editor. -Make various fields in the Options
Fractorium 22.21.4.2 Released
The last release had a severe animation bug in it that has apparently been present for quite some time. Thanks to @gameryamen for reporting it. Please update at fractorium.com --User changes -Allow users to set the Exp value when using the Exp temporal filter type. -Set the default temporal filter type to be Box, which does not alter the palette values at all during animation. This is done to avoid confusion when using Gaussian or Exp which can produce darkened images. -Clarify what the temporal filters are doing in their tool tips. --Bug fixes -Sending a sequence to the final render dialog when the keyframes had non zero rotate and center Y values would produce off center animations when rendered. -Temporal filters were being unnecessarily recreated many times when rendering or generating sequences. -Exp filter was always treated like a Box filter.
Fractorium 21.21.4.1 Released
It's been about a year since the last release, and what a year it's been. @triptychaos is the only other contributing developer on this project, and is the person who makes the MacOS installer for every release. He recently said his final goodbye to his mother, so this release is dedicated to him. At the bottom are the changes, with important ones in bold. I'd like to clarify the important ones as usual. Features: Two of the 3D fields, Pitch and Yaw, were only adjustable via the spinners like most fields in the program. This release allows you to change them while dragging with the mouse which gives intuitive user feedback and is much easier than adjusting with the spinners. A big thanks to @triptychaos for implementing this entire feature. Xform opacity has always had a range of 0-1. I got creative and started wondering what would happen if we used a value greater than 1? It turns out that it's a nice way to highlight a specific xform in your final image. It can also help you with
Fractorium 1.0.0.20 Released
This release is only contains bug fixes, no new features have been added.
Despite the number of fixes only being two, I decided to release because triptychaos (https://www.deviantart.com/triptychaos) was able to track down a rather severe bug that was crashing the entire program on AMD cards when using cubic3D and cubicLattice_3D. I had known about it for quite a while as a result of a report from b33rheart (https://www.deviantart.com/b33rheart) but was never able to reproduce it on my machine. After triptychaos (https://www.deviantart.com/triptychaos) told me he was able to reproduce it, he went to work solving it. The solution was embarrassingly simple: the OpenCL code for those two variations contained a switch statement without a default case. Once we a
© 2017 - 2024 mfeemster
Comments3
Join the community to add your comment. Already a deviant? Log In
Thank you, awesome job!