Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upSupport Sigma X3F camera RAW format #76
Comments
This comment has been minimized.
This comment has been minimized.
Hi, |
This comment has been minimized.
This comment has been minimized.
@berndmichaely, thanks for the reference. |
This comment has been minimized.
This comment has been minimized.
The issue you're having is identifying them? Basically need a new It sounds simple enough to pull the last four bytes for the directory location. Any lessons learned here you wanna share before I dive in? |
This comment has been minimized.
This comment has been minimized.
Offset 0 This was sufficient to identify my example image: _root.addPath(FileType.X3f, "FOVb".getBytes()); I'll look at reading a little more tonight. Their spec makes it sound fairly simple. |
This comment has been minimized.
This comment has been minimized.
I have implemented the x3f-raw-format specification in my JX3fExtract library available at
|
This comment has been minimized.
This comment has been minimized.
Thanks for the very detailed reply.
Once again, thanks a lot for this info. It confirms my conclusions from last night, which is very welcome. No longer feel like I'm diving into this with a flashlight. |
This comment has been minimized.
This comment has been minimized.
Ok, I've pulled all the maker notes, I just need to create a directory and int mapping for the string tags. The exif I assume is in the ima2 section, Bernd? |
This comment has been minimized.
This comment has been minimized.
@drewnoakes rcketscientist@d0eace4#diff-c5f93be4e042a2a86706739e098e766a |
This comment has been minimized.
This comment has been minimized.
Hi, |
This comment has been minimized.
This comment has been minimized.
Don't apologize, we're all dong this in our spare moments ;-).
I'm embarrassed to admit I lost an hour using the existing string reader and staring at your code going "Why oh why is he multiplying the offset be twoooooo!!!", lol
I figured it was just piggybacking the thumbs. The info on exactly what (IMAG, IMA2) represent was sorely lacking, especially taking the larger, so thanks for that!
Wow, thanks. I would easily have overlooked that, basing most of this on a single test image and some Phil Harvey notes.
Well, 2.1 and 2.2 mean that the extended header section might exist right? Did they ever use that (my test image is 3.1)?
I saw the recovery parser, I'll leave that for a day when I'm feeling particularly grumpy ;-), or never. For now I'll be satisfied to only handle intact images.
I saw that in the spec. As it stands I was planning on overwriting prior values.
No properties?
Thanks, I'll probably swipe those. I have a workable test setup in my android app, but testing in Android is a nightmare. |
This comment has been minimized.
This comment has been minimized.
Don't worry, the UTF-16 coding was also unusual to me, i was just glad it is supported as a standard charset by JRE ...
Thanks for pointing to this. I just saw there are even a few hints to "SigmaRaw Header4 Tags" unknown to me, i will have a look at this later :-)
Right. (It should even always exist in this case.)
I think i have never seen an older header version than 2.2 (Polaroid X530, Sigma SD9, SD10 used these already), but 2.2 and 2.3 is widely-used (SD14, SD15, first DP generation and Sigma Merrill generation with earlier firmware). Major version switched to 3 with newer Merrill firmware and to 4 with Quattro generation. (So i guess that 2.1 and older was used by Foveon only in times before they built consumer cameras based on that sensor.)
No proprietary properties anymore, only Jpeg+Exif anymore. (SD9, SD10 used Properties only, no Jpeg, instead the propriertary Data Formats 3 and 11, later cameras produce both Properties and Jpeg with Exif, and Quattro dropped Properties (and i think also the processed for preview thumnail size image)) |
This comment has been minimized.
This comment has been minimized.
So quattro only requires an IMAG parse? The image sections have never changed, right? |
This comment has been minimized.
This comment has been minimized.
I haven't seen any (version 2.x) Properties in any Quattro files yet, but that is just a guess (could change with new firmware at any time ...) |
This comment has been minimized.
This comment has been minimized.
@rcketscientist did you end up getting some support for Sigma in your own code? I saw a suggestion that you have in your recent PR here (which was the reason it failed to build). (edit: re-reading the thread I see your comment here) |
This comment has been minimized.
This comment has been minimized.
See #258 |
This comment has been minimized.
This comment has been minimized.
Actually ignore that comment. I removed those changes to from the reader and opted instead to process a byte block. It's more efficient, though we could always consider moving that code in if it's repeated elsewhere. For now there's no need to modify the reader. |
Sigma's X3F files appear to contain Exif data, yet do not start with a regular TIFF preamble.
Also known as the Foveon X3 format or "FOVb".
References: