Opening X-S10 files with Capture One v20

[Spencer]

I've just been playing around with raw files of the Fuji X-S10, using Hex Fiend on macOS. If you replace the instances of X-S10 with X-T30, then Capture One will open those files.

You could also replace X-S10 with X-T3 but then you have fiddle a bit because that's one character less and the following bytes will move one position forward.

Warning #1: only do this if you know what you're doing. Make a backup of your raw files first before you start editing them!!

Warning #2: I don't know if the result in Capture One is the same as proper support in C1 v21.

[YOUTA]

On 12/18/2020 at 1:35 AM, Spencer said:

I've just been playing around with raw files of the Fuji X-S10, using Hex Fiend on macOS. If you replace the instances of X-S10 with X-T30, then Capture One will open those files.

You could also replace X-S10 with X-T3 but then you have fiddle a bit because that's one character less and the following bytes will move one position forward.

Warning #1: only do this if you know what you're doing. Make a backup of your raw files first before you start editing them!!

Warning #2: I don't know if the result in Capture One is the same as proper support in C1 v21.

thanks for the information .keep posting whenever you find any information like this , it will be helpful for others .have a nice day ahead

[jerryy]

On 12/17/2020 at 3:05 PM, Spencer said:

I've just been playing around with raw files of the Fuji X-S10, using Hex Fiend on macOS. If you replace the instances of X-S10 with X-T30, then Capture One will open those files.

You could also replace X-S10 with X-T3 but then you have fiddle a bit because that's one character less and the following bytes will move one position forward.

Warning #1: only do this if you know what you're doing. Make a backup of your raw files first before you start editing them!!

Warning #2: I don't know if the result in Capture One is the same as proper support in C1 v21.

You can also do this using exif editors without having to worry about that extra byte in the body name. But hex editors are more fun!

(In general, is you do this make. sure the sensor and bsi type etc. etc. are the same so that the image editor can bring out the most in the file. You might want to change the information after you have imported it.)

[mdm]

4 minutes ago, jerryy said:

You can also do this using exif editors without having to worry about that extra byte in the body name. But hex editors are more fun!

(In general, is you do this make. sure the sensor and bsi type etc. etc. are the same so that the image editor can bring out the most in the file. You might want to change the information after you have imported it.)

Sometimes I substitute X-E2 with  X-T4 and see nothing wrong about image rendering )))