Iliah Borg
-
Posts
9 -
Joined
-
Last visited
Posts posted by Iliah Borg
-
-
On 11/20/2022 at 4:09 PM, walt.farrell said:
He has done more than that, because browsing to the full path in 2.0.5 doesn't work. When you get there, it tells you that the file is not accessible.
And browsing to the full path also fails in the 2.0.6 beta. He is recognizing %localappdata% as a trigger for some different processing.
Browsing won't work because the user has no 'read' rights, only 'execute' rights.
-
Dear Sir:
Yes, it's a Beta, which means we are open to adding features before the release.
OM-1 is officially supported in FastRawViewer since February: https://www.fastrawviewer.com/blog/FastRawViewer-2-0-4-Release
-
But we do, even in the public version, since 4 July, 2022:
https://www.libraw.org/news/libraw-0-21
If FastRawViewer / RawDigger display the raw, it is supported in LibRaw.
-
On 7/19/2022 at 6:23 AM, MiPo said:
@Ron.P: I am not sure what the difference is between Camera format support and camera support.
When raw decoder and metadata structure stay the the same as they were with some previous model, we tend to say "camera support"; but when either of those are different, we prefer to say "format support".
-
On 7/17/2022 at 10:20 AM, Ron P. said:
Need to voice your request/demands with LibRAW, as Serif relies on them for these profiles.
Just in case: LibRaw is a free and opensource library. We are not under any contract obligations with Serif/Affinity. We accept requests, but not demands.
On a side note, I don't remember a single request coming from Serif/Affinity themselves.
-
6 minutes ago, Riff said:
I would have presumed that a format is a format is a format
CR3 is a generic name for a bunch of formats, meaning raw data itself can be packed / compressed differently depending on the firmware and camera settings.
-
3 minutes ago, Patrick Connor said:
Welcome to the Serif Affinity forums
I feel honoured and thanks for the clarifications.
We had a camera list for 0.19.0 and see now that is the list for our 1.7.3 release (using 0.19.3 at that point).
Currently 0.19.5 as included in our early 1.8.0 betas. I will see if the developers plan to use 201910 instead, for our 1.8.0 release (depending on whether there is enough time for our processes). If they do our supported cameras would be this newer list.
Can you tell me if you consider the code rearrangement in 201910 should be considered as a beta release?
It's hard to define what a Beta state is. We use this snapshot ourselves, as I mentioned. The "formal cycle" Alpha - Beta - Release results in fixing ABI/API, which in our view is counterproductive for LibRaw development as we deal with "living matter". Since your users are not supposed to compile LibRaw themselves, ABI stability shouldn't be a concern. 201910 offers many improvements apart from support of new cameras. It is quite stable and some developers of commercial software told us they had no problems switching to it.
-
On 11/5/2019 at 7:07 AM, Patrick Connor said:
Welcome to the Serif Affinity forums
LibRaw 201910 is a submission to the Master of Github, and is not on the stable release branch 0.19.x which we rely on (as I understand it).
Affinity Photo 1.8.0 does however include the August LibRaw release 0.19.5 which also adds a number of other cameras (whereas APh 1.7.3 includes Libraw 0.19.3).
The benefits included in 201910 will make it to the stable release branch when checked and tested, and should appear in a future Affinity Photo beta.
Technically, this snapshot is no different from a release - it is tested and is the base for our own FastRawViewer and RawDigger.
No new cameras were added to 0.19.5 compared to 0.19.3 or 0.19.0, please see https://www.libraw.org/news/libraw-0-19-5-release
No new cameras will be added to 0.19 branch.
We have no immediate plans for Release 0.20
--
Best regards,
Iliah Borg
www.libraw.org
I feel honoured and t
FastRawViewer now supports APh
in Affinity on Desktop Questions (macOS and Windows)
Posted
I was explaining why "browsing to the full path also fails in the 2.0.6 beta".