Geometric Filter turns an image into a geometric approximation. It does so by using our custom proximity matching algorithm, which gives it a bit of a human touch, as it can trace contours and similar regions. The results are somewhat similar to what you get by using the so-called "style transfer" machine learning algorithms, but with much finer control over the result. The plugin will be aimed at artistic audiences who wish to simulate hand-drawn styles and will likely see most use in music videos, visualizations and with VJs.
https://aescripts.com/geometric-filter/
For now, please fix the problem with selecting 8 bits per channel in your project setting (menu File > Project Settings > Color > Depth: 8 bits per channel).
Sorry for the inconvenience. We will fix this problem as soon as possible and support the remaining color's depths.
OSX 10.13
PP And AE are CC2019.
I want to ask you few questions to confirm conditions when the problem occurs:
1) Resolution you work with is precisely 3840 x 2160 ?
2) Can you run the rendering in 8/16 bpc and confirm, it's happening only in 32 bpc cases?
3) Is this problem occurring for all 4k projects in 32 bpc using GF, or only with a specific set of parameters? If in a particular set, it would help us write them down exactly or provide a screenshot from the UI.
4) Exact version of AE and macOS is always helpful to mention.
Thank you for the additional information.
cheers
Best regards, Zden
Video codecs aren't optimized to store geometric shapes efficiently. Using the GF plugin, the image's complexity is higher than regular video footage, with a lot of gradients and noise to remove, and there isn't much to do. I think reducing the number of geometric shapes, larger line widths, and perhaps application of opacity or blur might help. But you need to experiment and see what works best. The export file size was never a concern to someone, and it's really out of our hands (as plugins devs) about which video codec you will use during export and how its compressing algorithm works. Generally speaking, the more you encode computer-generated graphics with sharp edges, the higher bitrate you need to maintain original visual quality.
All the best, Zden
Ask more about the plugin or report problems. If you suspect a bug in the plugin, it's preferred to open an internal ticket. If you want to know more about some specifics of the plugin, a public forum is good, as it might serve as the answer to others with similar question. Your question about file size is an excellent addition to "Knowledge Base," as it's a side-effect of the plugin's jitter if you apply GF on actual footage and for every frame. Besides previously mentioned options, try to play around with "Matching Accuracy." The lower the value, the less sensitivity to noise, leading to a more stable output but lower accuracy.
In GF, I expect the best results with the right combination of
"Skip Frame(s)" = values 2-4,
"Starting Pos. Strategy" = Stable Random or Grid,
and "Matching Accuracy" = values 55-85.
Also worth trying, applying a bit of gaussian blur or denoise before GF's processing.
The less shivery the output while compositing, the better it will compress.
I'm looking forward to your results and how it went.