One of my first feedback was about this. I prefer to import first, then adjust. Import is possible but moving layers on canvas, cropping, tiling, resizing and defining borders aren’t available or unstable.
Exactly!
It can be done elsewhere in a rather complex way but in current Photoflow, this may become second nature (as playing with tansparency and selecting various overlays are already there).
1 Like
After quite some time of silent programming, here is an update of PhotoFlow’s features:
-
I have finally fixed a long-standing issue with EXIF data in exported TIFF files, which were for example seen as multi-page TIFFs by GIMP. Now EXIF data in TIFF files is saved correctly, apart from a small remaining issue with the copyright string being null that I am going to fix soon.
-
the stable branch now offers the possibility to save 16-bit or 32-bit EXR files. The ICC primaries are stored in the EXR file so that colors can be interpreted correctly, and EXIF data is also stored in a way that is recognized by at least GIMP and Darktable. The image data is automatically linearized upon saving if it is not already in a linear colorspace.
5 Likes
@Carmelo_DrRaw This is a gentle reminder to place the continuous releases to a more prominent position on GitHub. I use a bookmark but it shouldn’t be difficult for others to find.
This is what visitors see:
README.md also links to this ancient version.
PS Old typo (missing “)”).
1 Like
Thanks for the reminder! I have finally managed to find out how to refresh a git tag, so that the continuous release gets moved to the top of the list. Now it’s done:
The typo will be fixed in the next packages…
It should be possible to open the file with the latest package from 2020-08-04, which includes an update of the raw decoding engine. Could you please check?
Thanks!
stable, rc1 or either are fine? Where there is choice there can be confusion.
@afre only stable for the moment. I will back-port the updated raw engine once I am sure there are no side-effects…
As usual, decompression takes a long time. 
Will find out later in the afternoon.
decompression or demosaic?
@heckflosse The day a raw processor can pwn a rival by demosaicing its package would be glorious indeed. Demosaicing itself while in a archive is something else entirely.
@Carmelo_DrRaw Works now. Thanks.
@heckflosse The unzipping of the archive is slow. Used the term decompression instead because it is more polite. BTW, this is also the case with @Carmelo_DrRaw’s build-archives of RT. I make these observations from time to time but I don’t know the cause of this problem. Could be the number of small files, archival settings or even how the app is assembled.
@Carmelo_DrRaw I just noticed that the camera and lens are unknown under lens corrections.
1 Like
Yes, it looks like the automatic detection does not work due to the camera/lens name formatting in the EXIF data. However, I was able to manually select the good camera/lens combo. Could you check if they are available also in your windows version?
Thanks!
As said twice before, the selection boxes won’t open. Actually, this time around, something does happen. I see a short horizontal line appear when I click to the left of Unknown camera.
There was indeed a problem with the update of the LensFun database during the package creation, so the LF DB was actually empty. The Win64 package from today should finally fix this issue. Could you please confirm that it works for you as well?
Thanks! And sorry for the delay in fixing this. I am catching up with the pending issues after a quite heavy period at work…
1 Like
No problem. I didn’t know if you got the message because you didn’t address it.
The entries take a long time to sift through because the names don’t match and there are multiple sub-selection menus per manufacturer. Please consider a Boolean partial word filter / search box, Same request I have had for the new layer menu.
Another feature (that I have mentioned but am not holding my breath on) is the ability for the user to specify the installation of gmic. I think this would simply things.
1 The pace of development is fast, I usually have the latest version on my system. People interested in gmic would already have the package installed through their package manager or manually.
2 You won’t have to package an obsolete version.
20XX Include the G’MIC plugin but use PhotoFlow preview instead of the plugin’s, which is inaccurate.
2 Likes
Hi, I am a bit confused.
Photoflow 2.8 is included in the Debian testing repo. However, there are serveral issues: 1. I cannot open raws from my OM-D E-M 5 Mark III - it’s a relatively new camera that is available since about 18 months; 2. If I use a light gtk theme, the icons are invisible; 3. If I open a file and create layers, apparently the options for merge (blend) mode and the opacity slider are missing, also in the mask settings there is no mix button.
I tried several other AppImages. PhotoFlow_git_v0.3.0-rc1_linux_20200613_1458_b7b4d.AppImage cannot open the raws form my e-m5 mark III and in PhotoFlow_git_stable_linux_20200804_2036_00b2c.AppImage merge mode options, opacity slider and the mix button are missing.
I would really like to have a closer look at this program. Should I compile it or are there usable AppImages?
Thanks Anna
1 Like
I use PhotoFlow in a minimalist way in win10, so I haven’t verified whether the bugs have been fixed (in Windows or Linux). I have reported so many that I don’t want to apply too much pressure on @Carmelo_DrRaw who is the sole dev. 
I have seen yours, so you aren’t crazy.
A workaround to your present problem may be to change the way modules are displayed. Since my screen is relatively small, I set my modules to appear in windowed form by default.
Lastly, the best way to access builds is from Release Continuous build · aferrero2707/PhotoFlow · GitHub, but I see you have tried the latest builds, at least in name. If you haven’t already, download from the aforementioned link and try again.
3 Likes