YOUR ACCOUNT

Login or Register to post new topics or replies
Bob Nolin
bnolin
Posts: 7
I've downloaded the demo of 2.0, and sure enough, it seems just as slow as v1. Click on a "preset" and it can take 5 minutes for the preview to finish rendering. Why this isn't stored as a JPEG that loads instantly is a mystery to me. I see it's using 3 or 4 CPUs in my Mac Pro 8 core tower. Just rendering a preset raises the CPU temperature 10 degrees Fahrenheit, to 97F. Just to look at a preset. (My machine usually operates on most tasks at about 85 degrees.)

Beyond the resource issues, this is a tool that takes a lot of playing and experimentation to learn and use effectively. Problem is, every little tweak takes minutes to run. If there were some way to get quick feedback (a sort of preview render, as in Vue or other 3D packages), it might be more usable. Not to mention a lot more fun.

You might want to take a look at PhotoworkShop by Xycod. It runs very quickly, and has options for controlling the level of rendering, to speed things up during the creation phase. It also includes a node-based editor. It's not nearly as powerful or full-featured as FF, but the implementation, I feel, is much better than FF's.
  Details E-Mail
Betis
The Blacksmith

Posts: 1207
Filters: 76
The efficiency and options for previewing and render levels are entirely dependent on the filter creator. In fact in my latest filter I have a few checkboxes that really address this issue because I know what it's like to want fast results and then get a quality rendering.
Roses are #FF0000
Violets are #0000FF
All my base are belong to you.
  Details E-Mail

Join Our Community!

Filter Forge has a thriving, vibrant, knowledgeable user community. Feel free to join us and have fun!

33,711 Registered Users
+18 new in 30 days!

153,533 Posts
+38 new in 30 days!

15,348 Topics
+73 new in year!

Create an Account

Online Users Last minute:

20 unregistered users.