Replies: 7 comments
-
I suggest testing with R0000349.JPG. Upload that file to your camera, with a different name. Can the camera still read it? If you change something trivial in the file, can the camera still read it? Look at the problem from another angle. Take a bunch of JPG files from the camera. What do they all have in common? Perhaps the ThumbnailOffset is constant, and this is what you need to make your file readable. I suggest you ask the question on the https://discuss.pixls.us/ forum. |
Beta Was this translation helpful? Give feedback.
-
There is a lot that can be changed, and the camera can still read the file. A name change is no problem. Note what I wrote about Imaging Edge Desktop. I can even make the generated file readable, but I want to be able to do that on the Linux command line.
Thanks for the suggestion!
Not sure I want to post in yet another place, unless there is more technical expertise than here. (which I doubt) |
Beta Was this translation helpful? Give feedback.
-
I notice that "exiftool R0000349.JPG" has:
IM won't create files with old-style compression. You have a process of elimination. You know your camera can read some files but not others. You can slowly step through all the variables to find which makes it unreadable. |
Beta Was this translation helpful? Give feedback.
-
Right, I found that too. How is old-style JPEG different from just JPEG? |
Beta Was this translation helpful? Give feedback.
-
As far as I know, exiftool reporting "-Compression=JPEG (old-style)" in a JPG file just means that tag is present and has the value 6. Just for fun, we can change it to other values, such as 4, which is "T6/Group 4 Fax". This doesn't seem to prevent any software from correctly reading the file. But there is a chance that your camera reads that tag and, if it isn't present or is not 6, the camera refuses to read the image. To set the tag:
Verify this:
See also https://en.wikipedia.org/wiki/TIFF#TIFF_Compression_Tag and the Exif standard at http://cipa.jp/std/documents/download_e.html?DC-008-Translation-2019-E |
Beta Was this translation helpful? Give feedback.
-
Thanks, but the tag is set, as can be seen in the |
Beta Was this translation helpful? Give feedback.
-
In the end, aside from changing chrome subsampling with ImageMagick, it is a job for ExifTool. First create a test image:
Then process the test image, which includes copying Exif data from a picture R0000349.JPG, which was taken with the camera:
The output needs to be placed in a DCF compatible path on the camera. Make sure that the number in the file name is unique on the card, or else the camera may be confused. For example, if there is |
Beta Was this translation helpful? Give feedback.
-
The plan is to convert maps to JPEG images that I can view inside of my Ricoh GR III digicam. This is useful when I don’t have my phone with me.
For now, I create a test image in ImageMagick and try to make it viewable in the phone. So far I have not succeeded, although the Exif data looks very similar. The image R0000349.JPG was shot with the camera. Here is what I tried:
The camera cannot display
S0000422.JPG
.As a workaround, I found I can open and save
S0000422.JPG
using Sony’s Imaging Edge Desktop. Optionally, if I copy the Exif data using ExifTool as above, the image will still display in the camera. However, Imaging Edge Desktop does not run on Linux, and as far as I can tell, there is no batch processing option.PS: I may crosspost this to the ExifTool forum. Interesting is the archived thread Make JPEG file DCF compatible, but with no solution.
Beta Was this translation helpful? Give feedback.
All reactions