I was debayering.What process are you running? If it creates new images (rather than "applying to" and modifying the container images), I don't think the images get output.
not sure I understand you.Images do get output (or they do for me) if the process modifies the input image (rather than generating a new image). So the output can only be (in-place) modified versions of the input images.
ok, I tried this. Thank you.It is not true that the Debayer process does not output the results to a specified output directory. Applying an ImageContainer to the lower gray bar of the Debayer process debayers the frames in the process container, opens views of the results and saves them to the specified output directory.
In order to avoid opening the views, make a process icon of the debayer process, right-click on it, click on 'Edit instance source code' and set "P.showImages = false" and click on the green checkmark icon. Now drag the blue triangle icon of the ImageContainer to the modified debayer process icon.
Bernd
Neither do I. I am having no problem.It's no longer opening views, but neither is is saving the debayered images in the folder I specified.
Not sure what I'm doing wrong here
Ok, yes I see that the debayer process has its own output directory setting. And you can load the files into it directly (which is easier that using an image container). That works fine.Hi,
You can simply set an output folder in Debayer and apply it globally (the blue circle or F6 hot key).
Best regards,
Vicent.
Ok, I tried that and I got a red errorNeither do I. I am having no problem.
Bernd
P.S.:
Sure! You are processing frames in proprietary raw format (CR2)!
In this case you cannot use the output template "&filename;_&datetime;&extension;" because the extension is ".CR2". PixInsight cannot write files in proprietary raw format. Your output template could read: "&filename;_d.xisf". This should work flawlessly.
perfect! Thank youOh boy! Please delete any quotation marks in the output template.
Bernd