Duplicated comments will be void.ĭon’t forget to invite your friends to enter! Update: The contest is closed and the winners are:Ĭongrats to the winners and thank you for your participation. One comment per person (submit once only and do not reply any comment here).Add a comment to this post, simply say something or "I want photoFlow".The winners will be announced on September 1, 2007. Each winner will win a copy of photoFlow component. We will randomly generate three winning numbers from the comment list. How does this work?Ĭomment entries will be accepted until Augat 12am (GMT -5 hrs). All comments must be submitted before Augat 12am. Just add a comment in this post and you could win one of the three photoFlow component giveaways (value $59.95). In addition, we are giving out 3 licensed copies of photoFlow. Is the current behaviour is to show a histogram with bins evently distributed between between 0 and 1 in the current colour space (so you get a linear histogram unless you change the colour space to e.g.First of all, we would like to thank Flashloaded, who provided us with the photoFlow component to complete the PhotoFlip Gallery tutorial. (the associated raw file is the one from the recent Rice Field Play Raw).Īdd some Samplers (I used 4), and then try turning the layer named “TOGGLE ME” on and off. Adjusting the settings on a layer does not have this problem.
If you have Samplers active then the UI thread is blocked when you make changes to layer visiblility (you click a checkbox and nothing happens for a few seconds - it looks like the interface is frozen). There is a performance issue with Samplers though (I did some testing and its in the previous version as well, so not to do with the Histogram changes). It seems this has nothing to do with the new caching mechanism, right?ĮDIT 3: +1 on suggestion to scale the histogramħadc6 seems to be working fine after some brief testing - the histogram is certainly responding well. I opened the last pfi I had, deactivated all layers, added a channel mixer layer then set reds as zero and it crashed. Maybe it didn’t liked getting a pure black image (when I set the red channel down to zero), but this is just a thought.ĮDIT2: Please disregard my previous comment. Index=-nan(0x400000), this=0x555559117000)Īt /home/gustavo/PhotoFlow/src/base/./rt/rtengine/LUT.h:449Ĥ49 int idx = (int)index // don't use floor! The difference in negative space is no problems hereġ Thread 0x7ffff7fada00 (LWP 4368) "photoflow" 0x00007ffff2f199e2 in mallocĮDIT: Forgot to mention that soon after adding the channel mixer layer, I activated a relight layer that was already there in the pipe, to help me “see” better the noise. Thread 16548 "worker" received signal SIGSEGV, Segmentation fault. OperationConfigGUI::disable_editing(): setting editing flag to false OpParBase::build_many_internal(): added tilecache for output image #0, padding=0 OpParBase::build_many_internal(): adding tilecache for output image #0, padding=0 layer relight finished Building layer channel mixer. PF::Image::do_update(): pipeline #2 updated. The image caching logic implemented so far in PhotoFlow was rather slow and. PF::Image::do_update(): updating pipeline #2 PF::Image::do_update(): preparing pipeline #2 PF::Image::do_update(): pipeline #1 updated. PF::Image::do_update(): updating pipeline #1 PF::Image::do_update(): preparing pipeline #1 PF::Image::do_update(): pipeline #0 updated. PF::new_operation: creating operation of type "blender" PF::Image::do_update(): updating pipeline #0
PF::Image::do_update(): preparing pipeline #0
PF::new_operation: creating operation of type "uniform" PF::new_operation: creating operation of type "channel_mixer"
PF::new_operation_with_gui: creating operation of type "channel_mixer" OperationsTreeDialog::add_layer(): layer=0x555560c48f00Īdding layer of type "Channel Mixer" (channel_mixer) OperationsTreeDialog::add_layer(): page=1 OperationsTreeDialog::on_button_clicked: id=1 Image 1366×768 407 KB IMAGE_REBUILD finished
0 kommentar(er)
