Bloom issues

[B.Y.O.B.]

Hi,

there are some things with the "bloom" lens effect that have bugged me for a while.
First, this little bug: http://www.luxrender.net/mantis/view.php?id=1254

Apart from that it's very annoying that the bloom computation cannot be aborted by the user without killing Lux. Would it be hard to add that functionality?
It's really tedious when you have to watch when Lux computes a bloom layer with messed up settings (i.e. much too large radius) and you know you will throw it away afterwards, but the render gets slowed down and it takes 20 minutes or so...

[A-man]

I think the post fx should be openCL accelerated, because calculations like bloom and chiu take a long time, but should be easily parallelised. The bloom one in particular takes realllly long and would benefit greatly from an interactive speed.

+1 for having an abort button It would go well with greycstoration as well.

[B.Y.O.B.]

because calculations like bloom and chiu take a long time, but should be easily parallelised.

AFAIK someone's working on Bloom parallelization.

[spectral fusion]

Yes it feels like its even slower in the new version, and i have to kill the process every time.

update: I managed to get it to finish once i lower the resolution to something like 640x480

[J the Ninja]

Yes it feels like its even slower in the new version, and i have to kill the process every time.

update: I managed to get it to finish once i lower the resolution to something like 640x480

Just FYI, if you import the EXR into Blender's compositor, you can do a much faster bloom effect with either the glare node (switch it to fog-glow mode) or luma key + blur. You can also (if you want) save the light groups separately and only bloom certain light groups. You also get a brightness threshold option that way, which Lux's bloom is sorely missing.

[spectral fusion]

Thanks for these tips, sound like a good alternative for now, how is the intel tbb proceeding for post production ?