Very kind, but the result of my request to Microsoft was ' if LibRaw implements this support (FITS files) then automatically in subsequent implementations (automatic update) they (FITS files) would be recognized'
that's why I turned to you.
Microsoft may not be responsible for this library, but they are responsible for their extension realization. The same way that "realization of this package was made possible thanks to ...", you can ask them to also add the cfitsio (or whatever other existing FITS library they might choose) to their extension to make that realization more capable, or ask them to create a new extension.
LibRaw library is targeted for developers, not for end-users.
Any questions related to MS' explorer extension should be asked to MS, we're not responsible for this product and not able to change anything in it. In this case Microsoft is one of our users (developer who use LibRaw).
If your problem is related to LibRaw library itself (you're software developer who uses LibRaw) we'll try to help.
sorry I don't want to question further, but there it says just the opposite: that Microsoft is not responsible for the good or bad functioning of a library (only integrated) and that you must refer to the LibRaw project...so if by chance I had I encountered problems interpreting Sony RAWs, for example, would I have done wrong to contact you here?
then I do not understand at this point; my windows 11, through Microsoft store, downloads libRAW and includes it in the operating system (Explorer).
in the wording of the store is written:
The realization of this package was made possible thanks to the open source project libraw (http://www.libraw.org). See the https://www.libraw.org/supported-cameras page for a list of supported cameras. The Libraw library is licensed under the COMMON DEVELOPMENT AND DISTRIBUTION LICENSE Version 1.0 (CDDL-1.0)
NOTE: The Raw codec provided by this extension requires changes to Windows in order to run. Windows 10 May 2019 Update, version 1903 or later is required. If you can't install the extension, your device is using a version of Windows that doesn't match the minimum number of Windows builds needed to run it. Consider updating your device to the latest version of Windows to install the extension.
NOTE: The extension is NOT an app. Direct interaction is not possible. The extension installs a codec plug-in for the operating system that Windows apps, including File Explorer and Photos, use to decode raw images. Use File Explorer to view thumbnails or the Photos app to view raw images of supported cameras after installing the extension.
Why don't you understand? also my sony camera provides sony software to see previews of RAW so, according to your reasoning, even libRAW does not need to support sony....
explorer simply doesn't show FITS all at once: wouldn't libRAW make this possible?
Sorry, I can not understand how Librav will help in this task. It is a file reading library, similar to (already existing) FITS-support libraries you mentioned above
FITS files are astronomical RAWs; they are used by astronomy camera manufacturers ZWO, QHY etc. to store shooting data and metadata (bayer grid etc.). they are normally treated only by astronomical software and therefore must be opened separately in order to be seen; Generally we astrophotographers produce many dozens of files for a single subject and we usually have to filter the good from the bad. It is really long and annoying to open every single shot to see, for example, if there are trails of satellites, which ruin the shot.
some groups have interpreted this format in preview but you must always have a separate software (example Quicklook with appropriate plugin https://github.com/siyu6974/QuickLook.Plugin.FitsViewer/releases).
it would therefore be interesting to integrate this encoding into LibRaw.
why don't you include the FITS astronomical format in the project, it is really widely used and it would be an excellent support to have a preview.
bye
I'm sorry to bother you, I managed to solve the problem by using the DNG color matrix, thank you.
I assumed that it was necessary to use the matrices built into libraw, after reading the comments above, where people asked to add support for RAW cameras.
And I'm amazed at how fast tech support is, it's amazing, I've never seen anything like this before.
Good luck with the development and improvement of the project!
Dear Sir:
Again, "Could you please tell what libraw command / call you used"?
"color shift occurs" - please use the color matrix the DNG contains. For DNG files, matrices in LibRaw are only fallbacks.
"underestimation of the exposure in shadows and highlights" - LibRaw has nothing to do with that.
AFAIK, Samsung phones records more-or-less (*) normal DNG, so already supported
(*) some DNG files from latest Samsung devices contains incorrect thumnail data (while RAW data is OK)
This file looks damaged: it contents does not pass bounds checks in samsung3_load_raw; disabling this checks not results into correct image.
All other samples from Samsung NX500 camera we have are processed OK.
Use open_file() or open_buffer() and check the return code.
Thanks
LibRaw is dual-licensed (LGPL 2.1 and CDDL-1), I do not see any problems from our side to use LibRaw under the terms of one of these licenses.
Please ask (topaz?) denoiser questions to vendor support, not to LibRaw
Bonjour,
Votre débruiteur pends t'il ma caméra 360 en charge (Theta Z1) ?
No plans for that, sorry
Very kind, but the result of my request to Microsoft was ' if LibRaw implements this support (FITS files) then automatically in subsequent implementations (automatic update) they (FITS files) would be recognized'
that's why I turned to you.
Microsoft may not be responsible for this library, but they are responsible for their extension realization. The same way that "realization of this package was made possible thanks to ...", you can ask them to also add the cfitsio (or whatever other existing FITS library they might choose) to their extension to make that realization more capable, or ask them to create a new extension.
LibRaw library is targeted for developers, not for end-users.
Any questions related to MS' explorer extension should be asked to MS, we're not responsible for this product and not able to change anything in it. In this case Microsoft is one of our users (developer who use LibRaw).
If your problem is related to LibRaw library itself (you're software developer who uses LibRaw) we'll try to help.
sorry I don't want to question further, but there it says just the opposite: that Microsoft is not responsible for the good or bad functioning of a library (only integrated) and that you must refer to the LibRaw project...so if by chance I had I encountered problems interpreting Sony RAWs, for example, would I have done wrong to contact you here?
This is Microsoft product, not ours (Microsoft uses LibRaw library in this product, yes).
Please contact Microsoft with any questions or suggestions related to this explorer extension. We're not responsible for it.
then I do not understand at this point; my windows 11, through Microsoft store, downloads libRAW and includes it in the operating system (Explorer).
in the wording of the store is written:
The realization of this package was made possible thanks to the open source project libraw (http://www.libraw.org). See the https://www.libraw.org/supported-cameras page for a list of supported cameras. The Libraw library is licensed under the COMMON DEVELOPMENT AND DISTRIBUTION LICENSE Version 1.0 (CDDL-1.0)
NOTE: The Raw codec provided by this extension requires changes to Windows in order to run. Windows 10 May 2019 Update, version 1903 or later is required. If you can't install the extension, your device is using a version of Windows that doesn't match the minimum number of Windows builds needed to run it. Consider updating your device to the latest version of Windows to install the extension.
NOTE: The extension is NOT an app. Direct interaction is not possible. The extension installs a codec plug-in for the operating system that Windows apps, including File Explorer and Photos, use to decode raw images. Use File Explorer to view thumbnails or the Photos app to view raw images of supported cameras after installing the extension.
LibRaw library itself provides nothing for explorer. It is just file reading library similar to FITS-reading libraries you mentioned above.
Why don't you understand? also my sony camera provides sony software to see previews of RAW so, according to your reasoning, even libRAW does not need to support sony....
explorer simply doesn't show FITS all at once: wouldn't libRAW make this possible?
Sorry, I can not understand how Librav will help in this task. It is a file reading library, similar to (already existing) FITS-support libraries you mentioned above
No software provides an integrated preview in explorer so it is not possible to see the FITS as jpg or RAW photos all together but only 1 at a time
As you mentioned, there are a lot of software supporting FITS, what can another library add here?
FITS files are astronomical RAWs; they are used by astronomy camera manufacturers ZWO, QHY etc. to store shooting data and metadata (bayer grid etc.). they are normally treated only by astronomical software and therefore must be opened separately in order to be seen; Generally we astrophotographers produce many dozens of files for a single subject and we usually have to filter the good from the bad. It is really long and annoying to open every single shot to see, for example, if there are trails of satellites, which ruin the shot.
some groups have interpreted this format in preview but you must always have a separate software (example Quicklook with appropriate plugin https://github.com/siyu6974/QuickLook.Plugin.FitsViewer/releases).
it would therefore be interesting to integrate this encoding into LibRaw.
Could you please explain your proposal?
why don't you include the FITS astronomical format in the project, it is really widely used and it would be an excellent support to have a preview.
bye
Could you clarify what exactly is your question?
I'm sorry to bother you, I managed to solve the problem by using the DNG color matrix, thank you.
I assumed that it was necessary to use the matrices built into libraw, after reading the comments above, where people asked to add support for RAW cameras.
And I'm amazed at how fast tech support is, it's amazing, I've never seen anything like this before.
Good luck with the development and improvement of the project!
Dear Sir:
Again, "Could you please tell what libraw command / call you used"?
"color shift occurs" - please use the color matrix the DNG contains. For DNG files, matrices in LibRaw are only fallbacks.
"underestimation of the exposure in shadows and highlights" - LibRaw has nothing to do with that.
Where can we see the sample raw files?
Pages