Open GoogleCodeExporter opened 9 years ago
I would strongly support this wish! Photivo is great software, but a
raw-workflow without exporting every manipulated image to tif or jpeg is
difficult as long as one has to load the previously made settings manually
every time a photo is opened.
Matthias
Original comment by hicnun...@gmail.com
on 11 Oct 2012 at 9:26
I’ll mark this postponed for the moment. The whole preset handling stuff is
the Next Big Thing I plan to work on but unfortunately time is limited and
there are a couple of things that need to be finished first (say the local spot
filter ...)
What I imagine for the “presets project” is a) a better way for presest
management than the standard file dialogs we have now and b) attach specific
presets to specific files; and that includes some kind of auto preset
loading/saving as well. For (b) we already have a good part of the code to
switch to XMP based presets from domlyons’ GSOC project that needs to be
integrated into the “production ready” Photivo code anyway.
So in a nutshell: Don’t expect anything in the immediate future, but
”Preset 2.0” ;) will happen. As an immediate workaround you can save your
current pipe config at any time with a right click on the Save button.
Original comment by brother.john.gm@googlemail.com
on 12 Oct 2012 at 9:28
[deleted comment]
[deleted comment]
Thank you for the reply.
As a workaround one can use the following script in Windows that loads the
settings file with the image:
@echo off
set IMAGE=%1
for %%i in (%IMAGE%) DO set PATH=%%~dpni.pts
if exist %PATH% (
"C:\Program Files\Photivo\photivo.exe" --pts %PATH% -i %IMAGE%
exit
)
"C:\Program Files\Photivo\photivo.exe" -i %IMAGE%
exit
Original comment by hicnun...@gmail.com
on 14 Oct 2012 at 7:00
Original issue reported on code.google.com by
maino.an...@gmail.com
on 4 Sep 2012 at 6:51