jvansyckle
![]()
Posts: 9 |
Does anyone other than me find many of the filters render unbearably slowly on Mac? I'm using the latest version of FF5, but this has been true for awhile through several versions. I guess I could name the ones that run reeeeeaaaly slowly, but just in general I find all but the most basic filters pretty slow. I'm not running slow hardware by any means - Mac (Retina 5K, 27-inch, Late 2014); 4 GHz Intel Core i7; 24 GB 1600 MHz DDR3; AMD Radeon R9 M290X 2048 MB.
I know it's not the fastest but it's no turtle either. Does anyone have any suggestions. I guess I'm just frustrated because I love this pgm but use it less and less becasue of its (non)speed. Or, maybe I'm just underestimating how long it should take to render. I do pretty complex graphics, I guess. Could folks give me an idea of what they see as "average" rendering speed for a particular filter and whatever size file you want so I could compare my speed? I'd appreciate it Jeff |
|||
Posted: January 13, 2016 8:39 am | ||||
Skybase
![]() |
What's the filter you're rendering? Some of the filters here are extremely computationally heavy to begin with. Also given the variety of user submissions some filters may be poorly optimized, although it's highly dependent on various factors.
As a very very quick remedy, if the image quality permits, try disabling anti-alias. This will usually cut render times significantly. If you're advanced enough; understand enough about both FilterForge and Photoshop, there may be a chance of recombining the filter's output manually using Photoshop. This will obviously take skill, but it cuts back render time since you're only rendering the necessary portions to reconstruct the final result. |
|||
Posted: January 13, 2016 9:04 am | ||||
GMM
Moderator
Posts: 3491 |
Jeff, please take a look at the relevant forum thread:
https://filterforge.com/forum/read.php?FID=5&TID=11020 The most significant speed factor is suboptimal filter design. For common effects, you may be able to find filters that produce similar results but greatly varying render times. |
|||
Posted: January 13, 2016 10:05 am | ||||
jvansyckle
![]()
Posts: 9 |
Thanks to both! Although I was a little put off by the "Refrain from bitching on the forums" comment, I will try the suggestions in the rest of the post.
I don't really understand the idea of "recombining the filter's output manually using Photoshop" unless you mean applying filter(s) to different parts of the image and then layering them in PS. This is obviously a questions from a person (me) who doesn't build filters - at least up to now - but is it possible to "redesign" filters in a more optimal way, or is it that some filters that are poorly designed are just a result of the effect they're trying to achieve? Again, I don't know a whole lot about render speeds, so with a filter I was playing with recently, e.g., "Artistic:Deep Cube 4," I'm not sure what an acceptable render speed should be. I know there are a lot of variables to this question, but should I be looking at 5, 10, 45 mins. I really don't know so I'm asking. Thanks again for the help, Jeff |
|||
Posted: January 13, 2016 1:00 pm | ||||
Skybase
![]() |
haha. That doesn't apply here. There were really obnoxious people back then that would just write irritated responses and nothing could help them despite the best efforts. The "combine in photoshop" technique is a very advanced technique which purposely pushes you to do part of what FilterForge may be too slow at. For example, in some of my filters (see example image below), I apply a curves adjustment before outputting the result. This gives the filter a nice special touch of color. However, the truth is, it's absolutely unnecessary if you understand that you can do this in Photoshop alone. The point is, the basis of this entire filter is much complete at some stage, just enough so that I can ignore the rest of the filter and reapply the effects myself. Ultimately, this method lacks convenience, and it does take significant level of skill to understand what's happening... it may be hardly recommended for everybody. I'm just putting it down as an idea that can be explored regardless. In the case with Artistic:Deep Cube 4, there are significant number of image processes going on. It isn't my filter, but as far as I've looked there are 4 particle bombers, a lot of bit-map based components (which tend to be slow), and some post processing via more bitmap components. The output is fantastic, but the overall filter will be slow. *Personal note: it seems like Ramyln (author) should add a bypass node somewh ere to help with the render times. I think some of the post-bomber phase can be done in Photoshop as well.* Render times are relative to each system. However, I think the FilterForge library has a threshold render time for submissions. If it takes too long to render on the default 600x600, I think it bounces you back that it can't be submitted. It's been a while since my last filter upload... so I can't tell what the numbers were. Personally, I never submit filters that take longer than 40 seconds to render on a default 600x600 machine. So that's been my benchmark that I think helps most people actually finish rendering even on a relatively large image. Then again, everybody else seems to have their own idea of how fast a filter should be. Part of it can't be controlled anyway due tot he software. ![]() |
|||
Posted: January 13, 2016 11:10 pm | ||||
SpaceRay
![]() |
I know and agree with you on the slow speed on many filters, and feel surely your frustration to be waiting much time for rendering, specially above 2000 pixels size
This has been a huge topic through all these years, but regretably nothing has been done yet to make the render engine faster than it is, and the possible solution to use GPU acceleration as many other Graphics software do is not possible with FF because how it was built, and it can not be used So regretably you have to have a huge patience with FF with the filters that are more slow, and is not only to render the final image, also happens the same many times just for the 600x600 preview while experimenting with the settings After 7 years I lost the hope that FF team will make anything to make it faster You can find lots of threads about this in the forum if you search for Render speed Slow render Slow remder speed FIlter Forge slow FF Slow |
|||
Posted: January 14, 2016 1:16 am | ||||
Skybase
![]() |
I feel like part of the "slow" issue is the way you use FilterForge. A lot of times, it becomes this one-stop-shop for effects and textures when it should be part of your workflow. It's not the end-all solution to your needs and wants. I argue that FilterForge is just part of the creative workflow. Although either way it's sometimes a sluggish program. The ultra tip is: if you can do it manually, do it manually. Don't wait on things that you don't need to. |
|||
Posted: January 14, 2016 1:31 am |
Filter Forge has a thriving, vibrant, knowledgeable user community. Feel free to join us and have fun!
33,712 Registered Users
+19 new in 30 days!
153,534 Posts
+31 new in 30 days!
15,348 Topics
+72 new in year!
30 unregistered users.