PhotoFlow News and Updates

photoflow
news

(Gustavo Adolfo) #350

@chroma_ghost You’re probably aware of this but It happened frequently with me until I sorted out that I had deleted a layer that was referenced above by a mask. When I cleaned the mask’s reference, it stopped crashing.


(Gustavo Adolfo) #351

Sure.
CRW_4001.DNG (17.8 MB)


#352

Yeah I had that with buffer layers… don’t think is the case here; thanks though.
I’ll have to collect more cases, right now I just want to edit so I’ll leave this for a bit


(Carmelo Dr Raw) #353

Does it crash when you try to restored the crashed edit, or when loading the original .pfi?

You could try to send me the most recent files in your ~/.photoflow/cache/ folder, so that I can try to have a look into the failing backup file…


#354

Does it crash when you try to restored the crashed edit, or when loading the original .pfi?

Don’t think I follow Andrea. There’s a raw and then when I save the edit there’s a raw.pfi
If by any reason photoflow had to be forced quit / kill; when I try ro reload the raw.pfi with the edit it crashes immediately. This didn’t happen before.

cache folder
cache.zip (2.9 KB)


(Carmelo Dr Raw) #355

Th is how it works: each time the processing pipeline is successfully built after a modification of some parameter, the software saves it as a temporary .pfi file in the cache folder, and associates this temporary file with the name of the file being processed. So if you have a crash you should be able to re-load the last non-corrupted editing status.

Now it seems that in your case the backup is corrupted as well, but I do not yet know why. So what I would need from you is to send me the contents of the cache folder after a crash that you know will likely not be recoverable, and you tell me the name of the file you were editing.
Then I can have a look at the corrupted backup file…


#356

Th is how it works: each time the processing pipeline is successfully built after a modification of some parameter, the software saves it as a temporary .pfi file in the cache folder, and associates this temporary file with the name of the file being processed. So if you have a crash you should be able to re-load the last non-corrupted editing status

pfi file was not created after cache was “ready”

contents of the cache folder after a crash that you know will likely not be recoverable, and you tell me the name of the file you were editing.

cache_and_pfi.zip (11.8 KB)

file being edited is _DSC0438.NEF

Just to be clear I forced the crash (after cache was “ready”)


(Gustavo Adolfo) #357

Hi.

I’m still unable to manually select a camera model in the RAW developer layer.

While executing PF, I noticed that the following file shows up:

image

It contains the similar model that i use to make geometric corrections:

However, even when I uncheck auto matching and/or match camera, nothing happens when I click both Unknown camera and Unknown lens.

image

I found a line in the log file that I thought might be a clue (there are two backslashes instead of one):

Can this be the reason why the camera/lens dialog doesn’t open?

anyway, here’s the full logfile

log1.txt (41.3 KB)


#358

I don’t know but it seems that there is something broken in lens corrections.

– If I understand you correctly, you cannot open the context menu when you click on the boxes, as I have suggested previously.
– And I have opened many PlayRaws with known camera and lens but all corrections doesn’t do a thing, except for the a little budging of the preview image and it returning to the same state. (I know I am bad at keeping track and reporting; sorry.)


(Carmelo Dr Raw) #359

The suspicious line in the log file is for the RawSpeed camera DB, and is harmless (two slashes under Unix are OK, and equivalent to one).

I have just tried the RAW sample file that you send me a while ago, and it works for me. This is what I get when I click on “Unknown camera”:

Is is really strange… you are under Ubuntu 18.04, right? I will try to reproduce on the same system…


#360

Okay, I will give you an example: [PlayRaw] Long exposure of waterflow, to process or not to process. This one does have changes but is just not very noticeable until I flip it back and forth outside of PhotoFlow. I think it has to do with the rocking and redrawing of the preview image that confuses the eye.
– The distortion adjustment for this particular image is also small.
– The vignetting adjustment seems to be non-existent, at least the samplers don’t change.
– This is the most noticeable when I difference the output images, so I will likely use this one only.

PS I mentioned this before. The sampler visible space is very small on my screen. Could you please make it adjustable vertically or provide an option to make it a floating window? It would be great if I could at least see the info of two samplers.

image

PPS After doing the the PF only PlayRaw entry, I noticed that the export image dialogue settings isn’t saved in the PFI. I am pretty sure it isn’t saved in other raw processors either. So I had to point out that I didn’t use post-resize sharpening because anyone looking at the PFI wouldn’t know. This is just a discussion point. I wonder whether that info should be included.

Also, I don’t remember whether you fixed the path issue. When I share the PFI, the path would inevitably be different on another user’s computer: is there a prompt to ask the user to select the path of the raw?


(Carmelo Dr Raw) #361

The problems when deleting a layer that is cloned somewhere in the pipeline should be fixed by this commit. Could you please check if this works for you as well?

Thanks!


(Carmelo Dr Raw) #362

I have just tried one on those RAWs. I was able to manually select the right lens by de-selecting “match camera” and “auto matching”, but the changes are quite subtle (I guess this is due to the good quality of the lens itself):

I have modified the code so that the samplers widget is now detachable. If you double-click on the tab widget label (“samplers”) the tab disappears and the samplers are moved into a separate dialog. Closing the dialog brings the samples back into the tab widget…

I am still fighting with the missing “close” buttons for dialogs, I hope to find an explanation soon…

Yes, this is currently the case. I am thinking about the best way to incorporate this information on a per-image basis… currently my idea would be to write the information into the sidecar .pfi files that can be created when exporting an image. Does this make sense?

This works already correctly when exchanging files between windows systems or between Linux/OSX ones, but not yet when going for Win to Linux/OSX or vice-versa. I am also trying to get this fixed…


#363

Do you mean it works if they are in the same folder but different than when saved? I haven’t tested that but I will take your word for it. What I have tried is to move or change the name of the raw file and then try opening the PFI. In this case, it seems that PF ends up constantly searching but not finding. Ideally, there should be an alert that says the raw couldn’t be found and even better present an open dialogue for the user to link the file.