Vladimir Golovin
Administrator
|
In this thread I'll answer questions about progressive previews introduced in FF3.0.
|
| Posted: April 29, 2011 3:39 am |
Details
E-Mail
|
Vladimir Golovin
Administrator
|
| Quote |
|---|
SpaceRay wrote:
Will it be able to use graphic card accelleration by using Open Gl, Open CL, or Nvidia Cuda ? |
Unfortunately, no. We spent at least a year trying to port FF to graphic hardware, but no luck so far -- the current FF rendering architecture and multithreading werebuilt for X86, so it doesn't lend itself well to GPU porting.
|
| Posted: April 29, 2011 3:46 am |
Details
E-Mail
|
Vladimir Golovin
Administrator
|
Attention everyone! If you're using Progressive Preview, make sure you uncheck the "Use cache preservation for previews" checkbox in Tools > Options > Interface. If you leave it checked, progressive previews will slow down the rendering.
This especially applies to users of FF2.0 who imported settings into FF3.0 during installation.
Here's how to do it: 
|
| Posted: April 29, 2011 4:45 am |
Details
E-Mail
|
|
StevieJ
Designer/Artist
Posts: 11264
Filters: 163
|
Suggest automatically unchecking and ghosting Cache Preservation option when Progressive Previews are selected...many aren't going to catch this... Steve
"Buzzards gotta eat...same as worms..." - Clint :) |
| Posted: April 29, 2011 6:41 am |
Details
E-Mail
|
Vladimir Golovin
Administrator
|
Steve, yes, most likely we'll rework these into mutually exclusive options.
|
| Posted: April 29, 2011 9:37 am |
Details
E-Mail
|
|
Indigo Ray
Adam
|
Does the progressive preview actually decrease the total rendering time, or is it just an aesthetic?
|
| Posted: May 1, 2011 1:54 pm |
Details
E-Mail
|
GMM
Moderator
Filter Forge, Inc
Posts: 3491
|
| Quote |
|---|
Indigo Ray wrote:
actually decrease the total rendering time |
No. It just allows you to see a rough version of the result faster.
|
| Posted: May 2, 2011 2:46 am |
Details
E-Mail
|
|
Sphinx.
Filter Optimizer
|
Can you explain the Degradation option? |
| Posted: May 3, 2011 5:33 am |
Details
E-Mail
|
Vladimir Golovin
Administrator
|
| Quote |
|---|
Indigo Ray wrote:
Does the progressive preview actually decrease the total rendering time, or is it just an aesthetic? |
As GMM said above, it doesn't. The actual rendering time will be roughly 2 to 5% longer than without the progressive preview.
|
| Posted: May 3, 2011 12:37 pm |
Details
E-Mail
|
Vladimir Golovin
Administrator
|
| Quote |
|---|
Sphinx. wrote:
Can you explain the Degradation option? |
The Degradation option postpones the rendering of low-contrast areas of the image to the last rendering pass (the one before the anti-aliasing pass).
Essentially, this slider specifies the threshold level of RGB contrast. During the first sparse pass, the renderer examines the channelwise variance between RGB values of pixels at the corners of each square 'patch' of the sparse image, and if this variance is below the threshold set by Degradation, this 'patch' will not receive any further refinement (i.e. samples) until the last rendering pass.
|
| Posted: May 3, 2011 12:49 pm |
Details
E-Mail
|
|
Sphinx.
Filter Optimizer
|
Alright, so the degradation option is only related to temporary quality, i.e. the final rendering is not related to the degradation setting, correct?
Btw. the progressive preview is a very nice addition. Sometimes though I wish I could temporary disable it, in particular during filter construction. It would be great if you could add a toggle option (w. shortcut) in the View menu. Currently I have to save the filter, close the editor, go to options and change this (btw. having access to Options from filter editor would be a great help in general) |
| Posted: May 4, 2011 5:04 am |
Details
E-Mail
|
Vladimir Golovin
Administrator
|
| Quote |
|---|
Sphinx. wrote:
Alright, so the degradation option is only related to temporary quality, i.e. the final rendering is not related to the degradation setting, correct? |
Exactly. The Degradation option does not affect the final quality in any way.
|
| Posted: May 4, 2011 7:47 am |
Details
E-Mail
|
|
betatester65
Posts: 10
|
Hello, i download yesterday FF3 beta, and i do a Filter that use some blur / subtract /add/ gamma and 5 controls.The filter i create need with 4 pass 43 sec and with no pass 5.5 sec.So i use always nopass.And peview size is always actual.
Is it possible that FF can support 4 cores for the effect ?
On my I5 760 the default setting with multipass preview is very slow.
when i show the whole picuture with zoom to fit, always need 5.5 sec, because the full image is render.the 4 pass effect is not better, can it here it render only the visible pixel in preview and later it can render the rest.
because visible pixel on preview are in the preview area only 700*540.so a preview can faster be here.is there a better setting for my system ?
If you like you can tell me what filter i should compare for speed (i use the time output option of FF)
EDIT: I use zoom to fit and 1 zoom with wheel in, because with zoom to fit, image is too small.
|
| Posted: May 24, 2011 2:06 pm |
Details
E-Mail
|
