Jump to content
You must now use your email address to sign in [click for more info] ×

Search the Community

Showing results for tags 'wavelets'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Affinity Support
    • News and Information
    • Frequently Asked Questions
    • Affinity Support & Questions
    • Feedback & Suggestions
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • V2 Bugs found on macOS
    • V2 Bugs found on Windows
    • V2 Bugs found on iPad
    • Reports of Bugs in Affinity Version 1 applications
  • Beta Software Forums
    • 2.2 New Features and Improvements
    • Other New Bugs and Issues in the Betas
    • Beta Software Program Members Area
    • [ARCHIVE] Reports from earlier Affinity betas

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



Website URL



Member Title

Found 1 result

  1. In a recent post, the OP was asking about wavelets. I was aware that FilterForge did offer wavelet filter and that FF 6 was compatible with Affinity Photo. Some time ago I bought FF6 on a special offer, but I had not really explored it. So I downloaded the wavelet filter for FF. I needed to upgrade to the latest version of FF6 first (not FF7), and it loaded into Affinity. I had loaded and developed a raw image of a prickly shrub first as a suitable subject. After a while it showed a set of images of the various decompositions squashed side-by-side. The rather limited filter documentation tells me to load the six output images into a stack above the residual image. I can work out which these are in the composite image above, but I have no idea what happened to the individual, properly-scaled output images. Does anyone have any experience of this? The FF filter is said to emulate the wavelet filter in GIMP. I saved the composite image from within the FF filter, but I found that it had frozen Affinity. I had to use the Task Manager to close it. I also noticed that Affinity was using over 5Gb of memory as opposed to a more usual 400Mb. I was later able to run FilterForge as a standalone with no problems. I have posed a comment on the Filter Forge Forum, but the link to email the author does not function. John
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.