×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

dslr - image info

  • Posts: 21
  • Thank you received: 0

Replied by Richard Konrad on topic dslr - image info

Hi,

Just a few issues still....I can't seem to enter any information in the image_info tab - I'm not sure why. Also I don't seem to have the auto-focus function working on the focus model. I have enable this in indi without any warning messages. I've attached a couple of screen shots for you to browse. Thanks!
7 years 1 month ago #14243
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 1309
  • Thank you received: 226

Replied by Andrew on topic dslr - image info

If you scroll or expand the window horizontally you should see a second field you can type into and a set button on most fields.
7 years 1 month ago #14244

Please Log in or Create an account to join the conversation.

  • Posts: 21
  • Thank you received: 0

Replied by Richard Konrad on topic dslr - image info

Thanks. I missed that.

I have filled in 4.3 under x, y, and pixel size um. I just read online that the three should be the same value unless my pixel isn't square. I'm getting an error message saying
Thanks.
7 years 1 month ago #14245

Please Log in or Create an account to join the conversation.

  • Posts: 1309
  • Thank you received: 226

Replied by Andrew on topic dslr - image info

You need to put in valid values in all fields updated by that set button. This includes the resolution and bit depth, even if they had already been entered.
7 years 1 month ago #14251

Please Log in or Create an account to join the conversation.

Replied by Jasem Mutlaq on topic dslr - image info

I also updated GPhoto driver documentation to include these steps. Furthermore, Ekos will warn you if the values are not set when you first use the driver.
Last edit: 7 years 1 month ago by Jasem Mutlaq.
7 years 1 month ago #14252

Please Log in or Create an account to join the conversation.

  • Posts: 1309
  • Thank you received: 226

Replied by Andrew on topic dslr - image info

Krno, have you noticed that with the Canon 600d, when values are set by taking a preview fits image, the resolution is larger than that of a typical raw frame?
With that camera, a raw frame should be 5184x3456. But the automatically entered values are 5202x3465.
Why is that?
7 years 1 month ago #14264

Please Log in or Create an account to join the conversation.

Replied by Jasem Mutlaq on topic dslr - image info

The driver updates whatever dimensions reported back by libgphoto2. Maybe there is some padding added? I'm not sure. I can check today the size of RAW vs. FITS of the same frame.
7 years 1 month ago #14288

Please Log in or Create an account to join the conversation.

  • Posts: 56
  • Thank you received: 6

Replied by Andrew on topic dslr - image info

hi jasem, did you ever have luck checking this?

I had similar experience with 60Da. I use SIRIL to process images, it accepts .fits directly but I've always converted from .cr2.
A couple of weeks ago, in an effort to streamline workflow I tried to save some lights and darks directly as .fits which worked fine. However when I came to processing, I found my SIRIL library bias and flats (taken another day as cr2 converted in SIRIL to fits) had different sizes as reported by lhoujin.

I assumed I'd made an error when setting the image frame or it had changed between sessions, normally I just load a saved profile and it works fine for .cr2. since I don't use any EKOS functions to focus or guide with the 60Da .

I tried cropping the files using PyFits to same size but in the end had to scrap this session and decided to return to saving as .cr2 but I'd like to try .fits only workflow again!
6 years 11 months ago #16119

Please Log in or Create an account to join the conversation.

  • Posts: 1309
  • Thank you received: 226

Replied by Andrew on topic dslr - image info

I also went back to strictly taking cr2. Which is a bit of a hassle right now as sequence maker defaults to FITS. As for Canon 600d, the sensor specs are 5184x3456, as are the raw files it saves. But the FITS files come out 5202x3465, otherwise they are clear images.
6 years 11 months ago #16147

Please Log in or Create an account to join the conversation.

Replied by Jasem Mutlaq on topic dslr - image info

Ok I have the same camera (600D), I will check this issue later today.
6 years 11 months ago #16150

Please Log in or Create an account to join the conversation.

Replied by Jasem Mutlaq on topic dslr - image info

So libraw always return the usable image size to be 5202x3465 for 600D. While CR2 is, as expected, 5184x3456. I do not understand the discrepancy, but this is an old issue (from ~2014). It even reports the "raw" width to be a higher value:
DEBUG	118.322965 sec	: read_libraw: raw_width: 5344 top_margin 51 left_margin 142 first_visible_pixel 272686
DEBUG	118.323072 sec	: read_libraw: rawdata.sizes.width: 5202 rawdata.sizes.height 3465 memsize 36049860 bayer_pattern RGGB
DEBUG	118.328976 sec	: read_libraw: memsize (36049860) naxis (2) w (5202) h (3465) bpp (16) pattern (RGGB)

So if someone knows a clear consistent way around this, let me know. The current solution is to specify the X&Y offset + widthxheight to 5184x3456. The offsets should just be diff between the two resolutions.
6 years 11 months ago #16190

Please Log in or Create an account to join the conversation.

  • Posts: 56
  • Thank you received: 6

Replied by Andrew on topic dslr - image info

I tried another .fits only session last night it made 20+ images overnight Lights + Darks in .fits with 5184x3456, I didn't really touch anything - strange.
This morning I tried some bias frames and saw immediately EKOS fields change to 5202x3456, then no matter what I did in either INDI or EKOS it retained this, I tried setting each image size in INDI to the smaller frame, I tried setting offsets in both INDI and EKOS which didn't work as expected, each time the exposure would reset to the larger frame size.I even tried setting Native transport in INDI and left is FITs in EKOS.

In my workflow, and when I first noticed this issue, the Lights and Darks were OK just like this session (5184x3456) but bias and flats effected by larger frame size. so it seems it is capable of retaining the smaller frames! I start every session with INDI Capture Format to 'normal JPEG' since it speeds downloads for framing (set EKOS Format to Native. The result is a 5184x3456 image Preview, then by switching in INDI to RAW capture and in EKOS to FITS it retains a 5184x3456 FITs image.

It's an ugly workaround and when I tried to repeat it this morning it failed so I'll move back to Native CR2 since this is not a big issue really, but more importantly I think for DSLR workflow are the following issues which I notice every session:-
a. Bias setting min 0.001 : cannot set it lower i.e to 1/8000 (0.000125)
b. File name suffix for exposure is always '_0_' for sub-second frames (Flats and Bias) : is useful to see file list with exposures i.e. target_000125s_
c. Temperature in filename - from exif data, I mentioned this in wishlist for 2017 but thought it fits well here too but I recognise it is probably I much larger edit than the other 2 items.

thanks, Andrew.
The following user(s) said Thank You: Jasem Mutlaq, Acapulco Rolf
6 years 11 months ago #16275

Please Log in or Create an account to join the conversation.

Time to create page: 0.700 seconds