It should, the executable name is just a bit different (should be photoflow.bin
or photoflow.real
, if I remember correctly).
The appimage is really just a package that runs the executable in a custom environment.
It should, the executable name is just a bit different (should be photoflow.bin
or photoflow.real
, if I remember correctly).
The appimage is really just a package that runs the executable in a custom environment.
There is photoflow.bin and PhotoFlow.AppIm.
The first one?
photoflow.bin
for sure. You should see it in the list when running top (or htop) without parameters.
Which branch is it? I just tested the new-caching
appimage, and processing a Nikon 810 RAW with spot WB and exposure correction required about 600MB on my Linux system.
Humm, I think I was running an older version, Iâm really sorry.
You know what may have caused this? The desktop integration thing.
When I hit the Super key and type photoflow, I see this:
The one with the nice icon (â1â) is the one I was using. The one with the ugly icon(â2â) is the one that corresponds to the latest stable version.
Really sorry to have wasted your time on this.
No problem! I will check what is going on with the desktop integration⌠I must admit I am not really using it myself.
I wouldnât bother with that if I were you. This older version but nicer icon must be a left over from some manual tweak I did in Ubuntu in the past. Let it be. Just double check the program version on the next print screens users like me post around.
Latest stable doesnât run because
Thatâs strange⌠I will have a look tomorrow.
@afre The problem with the missing dll should be fixed now, could you please check?
@paulmiller @gadolf I have also fixed the âassign profileâ bug in the new-caching branch, and prepared new packages. There is still something wrong with the Spot WB that I am trying to fixâŚ
It opens properly now. I noticed an unrelated problem. I may have reported this before. When I open the app, there is an open dialog. If I close it without opening a file, I am left with an empty window without any GUI. I cannot do anything besides close the app. Same as when I open a PFI of which the original file no longer exists. The app just continues to load without error and without a way to reenter the open dialog.
Yes, I am aware of this⌠however, one of the next steps in the UI development will be to replace most of the buttons with menu items. At that point, the problems you describe will be solved, and we will gain a bit more of space for the preview and the layers list.
I will start working on this as soon as the recent improvements in the processing pipeline will be merges into the stable branch.
Great! If one closes the open window or opens a malformed PFI or one that goes nowhere, the user has no choice but to quit the app. Not a good experience for a first time user or a non-techie.
@gadolf @paulmiller @afre
New update:
Packages are available for download in the usual place.
When I check the settings, the tile cache size is set to 10,000 not 1,000.
I just fixed this as well. Thanks for checking!
Next step is to re-introduce the histogram visualization, after which I think the code might be good to be committed into the stable branch.
(To avoid the same mistake as before, Iâm running new-caching-24343 from 2019/10/08)
Crash when trying to open the country sunset play raw:
Some notes:
RawImage::RawImage() finished
⌠layer âRAW loaderâ finished
Building layer âRAW developerââŚ
RawPreprocessorPar::init_wb_coefficients() called
⌠layer âRAW developerâ finished
PF::Image::do_update(): pipeline #0 updated.
PF::Image::do_update(): preparing pipeline #1
PF::Image::do_update(): updating pipeline #1
PF::new_operation: creating operation of type âraw_loaderâ
PF::new_operation: creating operation of type âblenderâ
PF::new_operation: creating operation of type âuniformâ
PF::new_operation: creating operation of type âraw_developer_v2â
PF::new_operation: creating operation of type âblenderâ
PF::new_operation: creating operation of type âuniformâ
Building layer âRAW loaderââŚ
⌠layer âRAW loaderâ finished
Building layer âRAW developerââŚ
RawPreprocessorPar::init_wb_coefficients() called
OpParBase::build_many_internal(): adding tilecache for output image #0, padding=0
phf_tile_pool_init(): called
OpParBase::build_many_internal(): added tilecache for output image #0, padding=0
⌠layer âRAW developerâ finished
[New Thread 0x7fffda7fc700 (LWP 13340)]
PF::Image::do_update(): pipeline #1 updated.
PF::Image::do_update(): preparing pipeline #2
Pipeline: force_rebuild set to true
PF::Image::do_update(): updating pipeline #2
PF::new_operation: creating operation of type âraw_loaderâ
PF::new_operation: creating operation of type âblenderâ
PF::new_operation: creating operation of type âuniformâ
PF::new_operation: creating operation of type âraw_developer_v2â
PF::new_operation: creating operation of type âblenderâ
PF::new_operation: creating operation of type âuniformâ
Building layer âRAW loaderââŚ
⌠layer âRAW loaderâ finished
Building layer âRAW developerââŚ
RawPreprocessorPar::init_wb_coefficients() called
⌠layer âRAW developerâ finished
PF::Image::do_update(): pipeline #2 updated.
IMAGE_REBUILD finished
Pipeline: force_rebuild set to true
IMAGE_REBUILD started
PF::Image::do_update(): preparing pipeline #0
PF::Image::do_update(): updating pipeline #0
PF::Image::do_update(): pipeline #0 updated.
PF::Image::do_update(): preparing pipeline #1
PF::Image::do_update(): updating pipeline #1
Building layer âRAW loaderââŚ
⌠layer âRAW loaderâ finished
Building layer âRAW developerââŚ
RawPreprocessorPar::init_wb_coefficients() called
OpParBase::build_many_internal(): adding tilecache for output image #0, padding=0
phf_tile_pool_init(): called
OpParBase::build_many_internal(): added tilecache for output image #0, padding=0
⌠layer âRAW developerâ finished
PF::Image::do_update(): pipeline #1 updated.
PF::Image::do_update(): preparing pipeline #2
PF::Image::do_update(): updating pipeline #2
PF::Image::do_update(): pipeline #2 updated.
IMAGE_REBUILD finished
IMAGE_REDRAW_START started
IMAGE_REDRAW_START finished
IMAGE_REDRAW started
[New Thread 0x7fffdb7fe700 (LWP 13341)]
[New Thread 0x7fffdbfff700 (LWP 13342)]
[Thread 0x7fffdb7fe700 (LWP 13341) exited]
[Thread 0x7fffdbfff700 (LWP 13342) exited]
[New Thread 0x7fffd9ffb700 (LWP 13343)]
[Thread 0x7fffd9ffb700 (LWP 13343) exited]
[New Thread 0x7fffbffff700 (LWP 13344)]
[Thread 0x7fffbffff700 (LWP 13344) exited]
[New Thread 0x7fffbffff700 (LWP 13345)]
[New Thread 0x7fffd9ffb700 (LWP 13346)]
[New Thread 0x7fffdbfff700 (LWP 13347)]
[New Thread 0x7fffdb7fe700 (LWP 13348)]
Thread 29 âworkerâ received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffbffff700 (LWP 13345)]
0x00007ffff697f645 in g_mutex_lock ()
from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
(gdb) set pagination off
(gdb) set logging file log.txt
(gdb) set logging on
Copying output to log.txt.
(gdb) info threads
log.txt (46.9 KB)
There is a problem with the tile allocation. In the log I only see
phf_tile_pool_init(): called
without any further message afterwards. What is the tile cache size in your settings?
This means I need to better handle the errors in the tile cache initializationâŚ
Meanwhile I have added some more messages to better understand the source of the problem.
Iâve built it and this time I didnât have any issues and could complete an edit until the end.
It was 1 GB and I changed it to 2 GB before starting this edit.