When do you/will you add new camera support to the stable branch? When do you expect to add the support for the X-T100, as at least some of my user base made the same incorrect assumption that 0.19.3 included the 201903 support.
As you can see in 0.19-branch changelog: https://www.libraw.org/download#changelog
there is no new camera support added.
Only security fixes/severe bug fixes are added within stable branch.
I had assumed (apparently incorrectly) that as 0.19.3 was months after the snapsot that it included the snapshot code. When will the X-t100 be supported please?
I had all kinds of trouble with Visual Studio
More than one version
My problem was related to permissions and paths
I was too lazy to find it
and
Switched to Mingw
The mingw is pretty bare bones but at elast it seems to work
Compiled by me - I use make -f makefile.mingw
I make all samples work - no problems - just the tiff
I use windows
make -f makefile.mingw
Like i say the ppm and the thumb work perfect
While I have your attention could you please tell me
on the -Z option to stdout
What is the output - does it have a header - is it tiff or ppm
A C programmer would find this instantly - but not me
I no C programmer but last year i got a stdout pgm working
that outputs to Windows using stdout - i get thumbs and exit
etc and all works great and fast
Thanks for you help
'
Dear Sir:
If it is just one file, you can try to open it with a free trial of our RawDigger (if it opens it, libraw will sure do too), or upload it to some place and send us the link to info@libraw.org
Hello !
I have a file whose format is simply ".raw", and I have no idea what camera it comes from.
I do not understand a lot about RAW files, and I was wondering if :
- LibRaw would be able to decode it ?
- Once decoded, will I be able to read the file (I mean, is the information obtained understandable without furter encoding ? For example, will I have access to the value of each pixel of the image ?)
I installed the Raw Image Extension from the Microsoft Store in the hopes that I could view the raw images I took on my Canon EOS M50 natively on the Photos app. I found in another online forum that the .CR3 file is still currently unsupported yet it seems like the older .CR file types are supported. I was wondering when you intend to finally provide support for this raw file format?
I've recently faced the same problem and the reason was the following:
VS2017's option "Treat WChar_t As Built-in Type" was "No" (/Zc:wchar_t-)
By default, it's usually On.
But maybe, when I generated configurations for Target Machine: X64 from x86 by copying, it's got off? I don't know. If the settings are copied, the Zc has been Off even for X86?
Anyway, being Off, the function signatures got generated as unsigned short const * i.e. @@@UEAAHPEBG@Z instead of wchar_t const * which is @@UEAAHPEB_W@Z and the linker can't find them.
Hey there! Thanks for your work! Will you add CR3 support to LibRaw?
OK understood, thanks
X-T100 is supported in current public snapshot.
There is no plans for LibRaw 0.20 this year.
When do you/will you add new camera support to the stable branch? When do you expect to add the support for the X-T100, as at least some of my user base made the same incorrect assumption that 0.19.3 included the 201903 support.
As you can see in 0.19-branch changelog: https://www.libraw.org/download#changelog
there is no new camera support added.
Only security fixes/severe bug fixes are added within stable branch.
I had assumed (apparently incorrectly) that as 0.19.3 was months after the snapsot that it included the snapshot code. When will the X-t100 be supported please?
0.19.3 and 'snapshot 201903' are different versions.
I already said the embedded list doesn't contain this camera but you claimed support here:
https://www.libraw.org/supported-cameras-snapshot-201903
so it should be in 0.19.3 shouldn't it?
Look into LibRaw[-version]/samples folder for LibRaw usage sample code.
You can get actual list for the version you use by using https://www.libraw.org/docs/API-CXX.html#cameraList
No, the X-T100 isn't in the list of cameras embedded in the code, but then neither is the X-T3 which you do support ...
But on the other hand it was in the list of supported cameras for the 1903 snapshot, so *should* be in 0.19.3 ???
David
So I came to the wrong place...
1) We do not change your password (AFAIK)
2) Is there X-T100 in 0.19 supported camera list?
Dear Sir:
LibRaw is able to extract both sub-frames via params.shot_select (=0,=1) option.
LibRaw's postprocessing do not merge two frames, you'll need to implement this in your code.
It happens some time, especially while raw to tiff conversation,left and top gets some dead pixel values.
I had all kinds of trouble with Visual Studio
More than one version
My problem was related to permissions and paths
I was too lazy to find it
and
Switched to Mingw
The mingw is pretty bare bones but at elast it seems to work
18.2 and 18.3 so it is no my end
Compiled by me - I use make -f makefile.mingw
I make all samples work - no problems - just the tiff
I use windows
make -f makefile.mingw
Like i say the ppm and the thumb work perfect
While I have your attention could you please tell me
on the -Z option to stdout
What is the output - does it have a header - is it tiff or ppm
A C programmer would find this instantly - but not me
I no C programmer but last year i got a stdout pgm working
that outputs to Windows using stdout - i get thumbs and exit
etc and all works great and fast
Thanks for you help
'
what version do you use (precompiled one, or compiled by you?)
Dear Sir:
sorry, missed your submission (caught by spam filter?)
Could you please resend links to files to info@libraw.org
Dear Sir:
If it is just one file, you can try to open it with a free trial of our RawDigger (if it opens it, libraw will sure do too), or upload it to some place and send us the link to info@libraw.org
Hello !
I have a file whose format is simply ".raw", and I have no idea what camera it comes from.
I do not understand a lot about RAW files, and I was wondering if :
- LibRaw would be able to decode it ?
- Once decoded, will I be able to read the file (I mean, is the information obtained understandable without furter encoding ? For example, will I have access to the value of each pixel of the image ?)
Thanks !
Sincerely,
Nath
Dear Sir:
Our plans haven't change, it is scheduled for this Fall.
Hi there,
I installed the Raw Image Extension from the Microsoft Store in the hopes that I could view the raw images I took on my Canon EOS M50 natively on the Photos app. I found in another online forum that the .CR3 file is still currently unsupported yet it seems like the older .CR file types are supported. I was wondering when you intend to finally provide support for this raw file format?
Sincerely,
Joseph
I've recently faced the same problem and the reason was the following:
VS2017's option "Treat WChar_t As Built-in Type" was "No" (/Zc:wchar_t-)
By default, it's usually On.
But maybe, when I generated configurations for Target Machine: X64 from x86 by copying, it's got off? I don't know. If the settings are copied, the Zc has been Off even for X86?
Anyway, being Off, the function signatures got generated as unsigned short const * i.e. @@@UEAAHPEBG@Z instead of wchar_t const * which is @@UEAAHPEB_W@Z and the linker can't find them.
Pages