fredvanner
Well-known member
If you upload one of your .CR2 files we could test that.
This image opens for me debayered, but is part of a set I ran through WBPP without any problems, with debayering showing in the process window. https://cloudbait.com/refs/E7_44126.CR2If you upload one of your .CR2 files we could test that.
Interesting. Don't know what to say. It's not an issue for me (in fact, it's nice to have individual images open already debayered). These are my raw preferences. When I push "Pure Raw" nothing seems to change, which I push "Demosaiced RGB" the whole setup changes. Neither preset seems to change how my CR2 files open outside of a process or script.Chris, I dragged your CR2 file onto PixInsight with 'RAW Format Preference' set to 'Pure Raw' -> CFA data, and to ''Demosaced RGB' -> RGB image - just as expected.
Bernd
Interesting. Don't know what to say. It's not an issue for me (in fact, it's nice to have individual images open already debayered). These are my raw preferences. When I push "Pure Raw" nothing seems to change, which I push "Demosaiced RGB" the whole setup changes. Neither preset seems to change how my CR2 files open outside of a process or script.
View attachment 22420
<v k="RawPreferences_outputCFA" t="b" v="true"/>
Same as yours. In any case, I believe this behavior predates the existence of the .settings file completely.I think something must be broken in your core-001-pxi.settings file
Do you see this line?
Code:<v k="RawPreferences_outputCFA" t="b" v="true"/>
Something very odd must be going on if the values in the .settings file don't match the displayed values in the Format Explorer preferences.I think something must be broken in your core-001-pxi.settings file
Do you see this line?
Hmm... In that case I really don't see why your system loads debayered RGB - these settings are telling it not to. It is as though your file open command is accessing some hidden format preferences. Do you consistently get this behaviour when:Same as yours.
Yes, I tried it all three ways. And double-clicking the desktop to access a file dialog. And also if I open multiple files.Hmm... In that case I really don't see why your system loads debayered RGB - these settings are telling it not to. It is as though your file open command is accessing some hidden format preferences. Do you consistently get this behaviour when:
- opening a file using the "FILE" menu "OPEN" command (or Ctrl+O)?
- selecting a raw file in the OS file explorer / finder (Windows File Explorer on my system)?
- dragging from the OS file explorer / finder onto the PI desktop?