×

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

Bi-monthly release with minor bug fixes and improvements

canon dslr banding artefact after upgrade to the stable version

  • Posts: 969
  • Thank you received: 94
Hi everyone
I took the update and now there is an artefact across the top of the downloaded image. If I reset the frame values in the indi control panel, the artefact disappears and all is normal but the setting does not stick and the artefact reappears upon the next download.

Tried also with the gphoto driver: same, but the artefact remains despite resetting the frame sizes.

Is there any way I can revert to where I was before the update or any fix available for this?
TIA

logs: drive.google.com/open?id=1Y2_pUY-rrDhAT1kn3HKOyz53VG1Cv6oy
5 years 2 weeks ago #36194
Attachments:

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

  • Posts: 985
  • Thank you received: 161
I have seen the exact same artefact in my pictures, too.
5 years 2 weeks ago #36199

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

  • Posts: 969
  • Thank you received: 94
Hi. OK and thanks fr the confirmation.
1. Is there a fix available? Or...
2. Is there a way I can revert to the pre-bug version?
TIA

EDIT
Tried wih a different camera; the same...
Last edit: 5 years 2 weeks ago by alacant.
5 years 2 weeks ago #36207
Attachments:

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

Can you clear the DSLR config and then when you enter the value again, you enter the 5208x3476

What appears to be happening is when the DSLR was first detected, you entered 5184x3456, so the driver always crops to this value. If you clear the config and enter the value above, the value should stick.
The following user(s) said Thank You: alacant
5 years 2 weeks ago #36211

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

  • Posts: 969
  • Thank you received: 94
Hi
Still unreliable...

I cleared the dslr config and entered the new values of 5208x3476 with 4.30x4.30 for the pixel size. It starts correctly without the artefact for a few exposures at 5208x3476 but the artefact returns as it reverts to 5184x3456.

My database is owned by me:
-rw-rw-r-- 1 steve steve 98304 Mar 9 23:33 userdb.sqlite
and I start indi via ekos as the same user.

logs: drive.google.com/open?id=1TFSYd9DSTgEyy7dDGSLzvIL4st1kXNG2

The file sizes
without artefact 5208x3476:
-rw-rw-r-- 1 steve steve 36213120 Mar 9 20:53 Light_003.fits
with artefact 5184x3456:
-rw-rw-r-- 1 steve steve 35838720 Mar 9 23:20 Light_036.fits

I believe 5184x3456 is correct for the imaging area of the canon 700d with 5208x3476 the whole chip including non imaging pixels. Did this change with the upgrade? We have always dealt with te smller size before without problem.

How can I make the new value stick?
Thanks.


EDIT:
Jasem, could this be the reason? There are 4 entries for dslr:


Cheers
Last edit: 5 years 2 weeks ago by alacant.
5 years 2 weeks ago #36249
Attachments:

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

Ok time to look at the logs to see what's going on.
5 years 2 weeks ago #36254

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

  • Posts: 969
  • Thank you received: 94
Hi
I think I found the problem; at least the values are sticking now.
Clearing the dslr configuration does not clear other values from the database. Instead, it adds another record to those already existing.
Please see the edit to the post above; I cleared the first 3 entries, leaving only the 5208x3476. Now the values stick.
What I'm not sure about is the entry '9' for the field 'Filter' in record number 4. Should I leave this at 9?
TIA,
Steve
Last edit: 5 years 2 weeks ago by alacant.
5 years 2 weeks ago #36256

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

  • Posts: 969
  • Thank you received: 94
Ahggh, another gotcha. It's also in the .esl files, so the <Frame> section needs changing too:
<Frame>
<X>0</X>
<Y>0</Y>
<W>5208</W>
<H>3476</H>
</Frame>
Slowly getting there:)
Last edit: 5 years 2 weeks ago by alacant.
5 years 2 weeks ago #36334

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

Time to create page: 0.452 seconds