PixInsight made the idiotic update in 1.9 to not allow .FITS as Master Flats, and Master Darks.
"This is because PI stores important metadata in XISF that FITS can’t reliably hold, and the calibration process relies on it.Pixinsight"
If SharpCap won't / can't add that ability, I may just stop updating PixInsight. I don't use much that's been added in the last couple years.
If you plan to this the future, I will stop updating PixInsight until then. I turned off updates on it today.
Ability to output .XIFS
Forum rules
'+1' posts are welcome in this area of the forums to indicate your support for a particular feature suggestion. Suggestions that get the most +1's will be seriously considered for inclusion in future versions of SharpCap.
'+1' posts are welcome in this area of the forums to indicate your support for a particular feature suggestion. Suggestions that get the most +1's will be seriously considered for inclusion in future versions of SharpCap.
Re: Ability to output .XIFS
Move over to seti astro suite pro
-
admin
- Site Admin
- Posts: 17457
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: Ability to output .XIFS
Hi,
it looks like there is no suitable file format support library to read/write XISF that SharpCap could use (all the options are either read-only, have licenses that are incompatible with commercial software or are in languages that are no help as far as SharpCap is concerned). That puts a practical level block on doing this.
Additionally, while it can be productive, we don't recommend the approach of partially processing (like making master darks/flats) in SharpCap and completing the processing in other applications. There are lots of pitfalls around this approach - cases where the hidden assumptions in how processing in one application works are in conflict with different hidden assumptions in the other application.
cheers,
Robin
it looks like there is no suitable file format support library to read/write XISF that SharpCap could use (all the options are either read-only, have licenses that are incompatible with commercial software or are in languages that are no help as far as SharpCap is concerned). That puts a practical level block on doing this.
Additionally, while it can be productive, we don't recommend the approach of partially processing (like making master darks/flats) in SharpCap and completing the processing in other applications. There are lots of pitfalls around this approach - cases where the hidden assumptions in how processing in one application works are in conflict with different hidden assumptions in the other application.
cheers,
Robin
Re: Ability to output .XIFS
Thanks.
And as I learn more about this (from the Pixinsight Facebook group, which has most of the devs), they don't trust any other program to "get it right" anyway.
I like that you allow the ability to make Master Flats and Darks even though you say it's not the best way.
I don't like when software removes an existing feature like they're doing, in a program that costs more than nothing and more than the pittance you charge.
I ranted in depth on that group about it. Can link if you want, but maybe part of it was I was just having a difficult day. lol. But I really don't like when programs do that.
Microsoft does it all day every day because "they know better than us" or something.
The music DAW Reaper does it right. They don't remove old features when they add new ones. In fact, they're the only DAW that still supports VST2, which is cool since there are a lot of free old unique VST2 soft synths around. Everyone else deprecated at the suggestion of Steinberg (makers of VST format) was very pushy about "This is the old way, get rid of it."
And as I learn more about this (from the Pixinsight Facebook group, which has most of the devs), they don't trust any other program to "get it right" anyway.
I like that you allow the ability to make Master Flats and Darks even though you say it's not the best way.
I don't like when software removes an existing feature like they're doing, in a program that costs more than nothing and more than the pittance you charge.
I ranted in depth on that group about it. Can link if you want, but maybe part of it was I was just having a difficult day. lol. But I really don't like when programs do that.
Microsoft does it all day every day because "they know better than us" or something.
The music DAW Reaper does it right. They don't remove old features when they add new ones. In fact, they're the only DAW that still supports VST2, which is cool since there are a lot of free old unique VST2 soft synths around. Everyone else deprecated at the suggestion of Steinberg (makers of VST format) was very pushy about "This is the old way, get rid of it."