Saving takes as long as rendering ?
Author: Kraellin. ok, so as long as you're under your limit of memory, like i was with the 1200 x 1200 image, the rendering on a save wont show. but, if you've exceeded your memory limit and are using the swap, then things may slow down during the save due to what you said. cool. thanks, onyx :)
Simple question: Picking a color
...
because with maxed opacity on normal it's not using a blend function"
----Ha-ha, you win the splitting hairs of the week award with that logic, good one. :D I really don't think any of the methods described are taking even 1/2 of 1% of the render time though, there are 100 worse things that people do that slow filters down. :P
jffe
What would be good way to test the FF render speed between computers?
... images for the test purpose?
I can make images of fixed resolution sizes in the same way as I could make with the first FF generated graphics so they could be compared.
Please can you suggest what filters that you know I could use to test the render speed in the best way ?
It should be some fast filters, some medium speed filter, and some slow filters.
Workspace Rendering Times
... at each component isn't always the same-for-the-same-component, it can depend on other factors like what's plugged into it, and how many blur/noise components are chained behind it etc. So there's some cpu wasted there just calculating your wasted render time if you want a read out of it on the screen. Plus for each change then, it has to recalculate those times, wasting more time, granted not much time, maybe 1 or 2 seconds or something but it just slows things back down and is kind of counter-productive really.
jffe
Hints, tips and undocumented features
... filter in the Filter Editor for the first time, the Result Component is selected by default. Quickly deselect it and watch all the greyed out thumbnails getting rendered blazingly fast. Now be adventurous, re-select any component and watch the thumbnails rendering slowly again. (This is best observed with complex filters of course.) :eek:
I noticed this on my slow 1 GHz AMD win2K home machine, where it can become quite painful to wait for a whole node tree to update its thumbnails, so I can get a quick overview of what's going on inside the filter... :D
Slow preview when Before/After split is active
Author: Davide Barranca. Hello,
when the "Show Original" checkbox is active (and the preview window is split in two) apparently FF takes a lot more to render a filter (about 8x the time) compared to the speed of the "Show Original" unchecked. Is this a known issue?
OSX 10.8.2, FF 4.002.26192.3346.
Davide
New Processing Components: Illumination, Shadow, Reflect
Author: uberzev. I pretty much nailed the illumination effect in FF. Unfortunatly its pretty slow and there's a serious bug that will delay its release for a while. Anyway here's a preview...
Controls...
http://img245.imageshack.us/img245/4645/3ol6.gif
Height Map...
http://img245.imageshack.us/img245/4190/1xn1.jpg
Rendered Effect...
http://img224.imageshack.us/img224/6766/2em8.jpg
Ideas for Filter Forge
... moment.
On a tactical level, one of the biggest problems is the rendering bandwidth (we need to render all preview images before we can upload the filter to the Library and on the web). Even now people submit 40-50 filters a day, many of them very slow, and our rendering horsepower is limited at the moment (and it's scalability is limited as well). And this is beta! You can imagine what will happen when we release the final version, which will attract a lot more people.
We've implemented a background renderer ...
Comparison between FF2 and FF3 render speed test
... time depends VERY MUCH on the filter construction, and what the filter does, and how much CPU intensive is the filter, for example Photo effect filter are really very fast, but others that modify and distort and change very much the image are really slow because must make a huge amount of calculations to get the result.
I choosed to make the test with Crysta and Creepy because:
They are very CPU intensive and is good to test the rendering speed.
These filters do not depend on any image that must be loaded to work
These have been created by Vladimir Golovin so is supossed that as he is the creator of FF he should have optimized these filters to work in the best way and get ...
Huge time variance in rendering
... somewh ere in the neighborhood of 4x the rendering time? 26 minutes to 10080+ minutes is ridiculous.
I should mention that the machine I did this test on is a Windows XP box with 3GB memory, so is this a problem of memory being "filled" and slowing down the process? What approaches would help reduce rendering time? If I were to do this test on a Windows 7 x64 machine with 16GB RAM would the time likely drop? What about the same processor but with 32GB RAM? Would that also help?
Any insights are welcome. I'd also like to hear from anyone who is ...
Slow.. slow... slow...
Author: SpaceRay. By the way the Mystery of why Vincs got this very slowrender times is STILL unsolved so please GMM or any other, help him be able to solve this problem, thanks
" Vincs wrote
My time render is :
Last macbook Air (i5 2x1.8ghz - Ram 4go) : up to 1h
MacPro C2D 2,5ghz : up to 2h
And the best, in ...
Suggestion to give to new filters a Speed render level rating or mark
Author: SpaceRay. THERE IS ALSO A VERY BIG MISSING POINT HERE THAT IS NOT BEING TALKED ABOUT
This missing point is something called RENDER RESOLUTION !!!
The same filter does NOT take the same time to render a 600x600, a 1500x1500 or a 3000x3000 image, and the increases much with resolution.
It could be FAST for this same filter for 600x600 BUT could be probably SLOW for 1500x1500 and much slower in 3000x3000
I have made some time ago this measurements that are in the list below, so you can that what could be fast in 1000x1000 in just more that minute, it will increase to 23 MINUTES by increasing the resolution ...
Making trees -- any ideas?
Author: Kraellin. thanks, threedee. looking at it now. the first thing i can tell you is, turn off anti-aliasing :) that thing is just a weeeeee bit slow ;)
i'd leave the noise for leaves right now.
i'm running a single core, 3.5 ghz machine and timing the render................ i'll get back to you in an hour or so ;)
ok, with anti-aliasing turned off, 3 min, 27 seconds on my rig.
speed issue on user side
Author: Kraellin. vladimir,
i'll check these again today. but last night, all the texture filters were very slow in rendering. in fact, i quit even testing them because i was getting annoyed with having to wait.
i think i'll also remove the file i created and renamed and do that again just to make sure i did copy and rename the wrong file.
craig
Fimbulwinter by Burt
... corner of a post. " Gosh right in front of me. I was expecting an inbox of some sort. Thanks.
Ah, ok. The filter is a bit slow. I actually saw I left some dead ends and will have to fix or remove them - I had created a different but very nice ice effect ... ... then couldn't get the effect back - lesson learned and now I save a backup before I make changes.
As for the difference in renderings it almost looks to me like the transparency and the edge filter in particular (or the layer mode it is applied with) ...
Belgium Ripple filter render size
Author: Indigo Ray. A lot of the "slowness" in this filter comes from the highpass / blur that goes into the heightmap.
Here's what I did instead (it looks pretty similar). Rendering time for the a 600x600 image of the default preset cut by ~40% on my PC. :) I haven't tested large images or higher AA.
*for FF team: Both the original filter and my mod run slower in the FF4 Beta! :?:
FF3.0 Q&A: Progressive Preview
Author: Vladimir Golovin. 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:
Crackles by Apple
Author: Crapadilla. This is looking good! Checking it out... :)
... it is beautiful, but very slow! :) :(
You've got many many noises in there with Details values of 100. Noise Detail should be equal to or less than the value of the Roughness parameter for rendering efficiency. Also note that Blur components are generally bad, especially when they are blurring away all the detail of high-detail noises...
Saving takes as long as rendering ?
Author: onyXMaster. jffe: your settings are okay, maybe your hard drive is slow, needs defragmentation or so? Also I see that you have only 2.6Gb free space -- that may be too low for some large renders. Also, Windows disk performance suffers when there is less than 20% disk space left if you're using NTFS.
FFEasyRender 2.0 - GUI based batch renderer for Windows for FF 9.0
....0 and also with other previous versions. It works with Windows OS Based computers.
Is really very needed for batch rendering images automatically with your custom selection of filter, presets and source images.
it also helps very much with FF slowness that may take much time to render high resolution results, because with this tool, you can put it to work and leave it working and you can go away and do other things, or put it during the night, and when you come back, it is already finished all the work you wanted without having ...
