×

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

Bi-monthly release with minor bug fixes and improvements

dslr: wrong sensor dimensions

  • Posts: 969
  • Thank you received: 94
Hi everyone
I'm trying to test the latest source but my camera sensor dimensions are recorded incorrectly so I cannot continue.
They should be 0 0 5208 3476
but after a restart are recorded as 5208 3476 4 4 or just 0 0 0 0, all zero values.
I have tried purging the dslr configuration, removing the entries in userdb.sqlite and removing userdb.sqlite altogether, but the problem persists.

It maybe related to this
Trying to avoid the problem being carried to the stable version.;)The same dslr works fine with the current stable version.

Can anyone help?
Logs and screenshots here
TIA and clear skies,
Steve
4 years 2 months ago #48103

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

  • Posts: 985
  • Thank you received: 161
Steve, I don't own a 700D but tested latest nightlies with my 5DMk2. Image settings were correct and no crash occurred so I cannot replicate the issue.
The following user(s) said Thank You: alacant
Last edit: 4 years 2 months ago by Alfred.
4 years 2 months ago #48108

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

  • Posts: 969
  • Thank you received: 94
Hi and thanks for testing
I installed the nightly but with the same results:(
logs attached

File Attachment:

File Name: log_12-35-44.txt
File Size:483 KB
4 years 2 months ago #48110
Attachments:

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

  • Posts: 985
  • Thank you received: 161
Ok, here is my logfile. Maybe there is a difference between the two that could provide a hint as to what is going wrong.
4 years 2 months ago #48112
Attachments:

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

  • Posts: 111
  • Thank you received: 41
Another approach is to edit <code>$HOME/.indi/<DSLR_MODEL>_config.xml</code> and adjust the proper settings.
Then re-load in INDI property window the settings and it should work
The following user(s) said Thank You: Alfred, alacant
Last edit: 4 years 2 months ago by Thomas Stibor.
4 years 2 months ago #48113

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

  • Posts: 969
  • Thank you received: 94
Hi
Thanks
Yes, I tried that but it always resets to this upon restarting indi:
<INDIDriver>
<newTextVector device='Canon DSLR EOS 700D' name='DEVICE_PORT'>
<oneText name='PORT'>

</oneText>
</newTextVector>
<newNumberVector device='Canon DSLR EOS 700D' name='CCD_INFO'>
<oneNumber name='CCD_MAX_X'>
0
</oneNumber>
<oneNumber name='CCD_MAX_Y'>
0
</oneNumber>
<oneNumber name='CCD_PIXEL_SIZE'>
4.3000001907348632812
</oneNumber>
<oneNumber name='CCD_PIXEL_SIZE_X'>
4.3000001907348632812
</oneNumber>
<oneNumber name='CCD_PIXEL_SIZE_Y'>
4.3000001907348632812
</oneNumber>
<oneNumber name='CCD_BITSPERPIXEL'>
0
</oneNumber>
4 years 2 months ago #48115

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

  • Posts: 111
  • Thank you received: 41
Then it looks like the problem could be introduced with e.g. commit Make sure when subframing that we are still within range of the actual image resolution
How about git checkout one commit before, compile and see what happens?
The following user(s) said Thank You: alacant
4 years 2 months ago #48116

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

  • Posts: 969
  • Thank you received: 94
Hi. I'm not getting the errors in that commit; the stable version from earlier this month works.
The workaround ATM seems to be to edit the xml file with the correct sensor dimensions and make it read only. I then have to remember to load it each time from the indi control panel, otherwise each new session reverts to 0 0 0 0.
Thanks again.
4 years 2 months ago #48118

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

  • Posts: 969
  • Thank you received: 94
Tested also with eos450d. Same: the sensor dimensions are reset to 0 0 0 0.
4 years 2 months ago #48121

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

I just purged all configuration for my 600D and started from scratch. Entered the values initial and that was pretty much it. No issues after multiple connects/disconnects. Is there _any_ permission issue for ~/.local/share/kstars ? or ~/.indi ? are they both owned by your user? That's the only thing I can think of. At a last resort, you can email me your TeamViewer credentials and I can login in to diagnose it live.
4 years 2 months ago #48144

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

  • Posts: 969
  • Thank you received: 94
OK. I went through the permissions again. They're all OK. I noticed that the issue occurs after switching profiles. If you keep the same profile and restart, it's OK but then starting with the same camera in another profile, the config resets to 0 0 0 0. then upon purging and reentering the correct coordinates, it is recorded by indi as 5208 3476 4 4 instead of 0 0 5280 3476. It restored to 0 0 5208 3476 upon taking a frame but then fitsviewer crashes:
(gdb) bt
#0 0x00007ffff0184e97 in __GI_raise (sig=sig@entry=6)
at ../sysdeps/unix/sysv/linux/raise.c:51
#1 0x00007ffff0186801 in __GI_abort () at abort.c:79
#2 0x00007ffff21c9fb7 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3 0x00007ffff21c5486 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4 0x00005555559fd650 in Stretch::run(unsigned char*, QImage*, int) (this=0x7fffffffcb10, input=0x7fff730d2010 "\361\a\030\b\030\b\376\a\376\a\375\a\375\a\354\a\354\a", outputImage=0x555559a4a130, sampling=4)
at /home/steve/Projects/kstars/kstars/fitsviewer/stretch.cpp:321
#5 0x0000555555849199 in FITSView::doStretch(FITSData*, QImage*) (this=
0x555559a4a050, data=0x55555c7c0960, outputImage=0x555559a4a130)
at /home/steve/Projects/kstars/kstars/fitsviewer/fitsview.cpp:100
#6 0x000055555585537b in FITSView::rescale<unsigned short>(FITSZoom) (this=0x555559a4a050, type=ZOOM_KEEP_LEVEL)
at /home/steve/Projects/kstars/kstars/fitsviewer/fitsview.cpp:554
#7 0x000055555584b3a5 in FITSView::rescale(FITSZoom) (this=0x555559a4a050, type=ZOOM_KEEP_LEVEL)
at /home/steve/Projects/kstars/kstars/fitsviewer/fitsview.cpp:427
#8 0x0000555555849355 in FITSView::setStretchParams(StretchParams const&) (this=0x555559a4a050, params=...)
at /home/steve/Projects/kstars/kstars/fitsviewer/fitsview.cpp:117
#9 0x0000555555a1e4e7 in FITSTab::<lambda(int)>::operator()(int) const (__closure=0x55555ca5e600, value=5333)
---Type <return> to continue, or q <return> to quit---
at /home/steve/Projects/kstars/kstars/fitsviewer/fitstab.cpp:281
#10 0x0000555555a26e69 in QtPrivate::FunctorCall<QtPrivate::IndexesList<0>, QtPrivate::List<int>, void, FITSTab::setupStretchBar()::<lambda(int)> >::call(FITSTab::<lambda(int)> &, void **) (f=..., arg=0x7fffffffcf20)
at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:130
#11 0x0000555555a26727 in QtPrivate::Functor<FITSTab::setupStretchBar()::<lambda(int)>, 1>::call<QtPrivate::List<int>, void>(FITSTab::<lambda(int)> &, void *, void **) (f=..., arg=0x7fffffffcf20)
at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:240
#12 0x0000555555a25cdf in QtPrivate::QFunctorSlotObject<FITSTab::setupStretchBar()::<lambda(int)>, 1, QtPrivate::List<int>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=1, this_=0x55555ca5e5f0, r=0x55555ca5c270, a=0x7fffffffcf20, ret=0x0)
at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject_impl.h:168
#13 0x00007ffff23ec75f in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00007ffff3936c81 in QAbstractSlider::sliderMoved(int) ()
at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x00007ffff39376f6 in QAbstractSlider::setSliderPosition(int) ()
at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x00007ffff39dca1b in QSlider::mouseMoveEvent(QMouseEvent*) ()
at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#17 0x00007ffff3881048 in QWidget::event(QEvent*) ()
---Type <return> to continue, or q <return> to quit---
at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#18 0x00007ffff39dd04a in QSlider::event(QEvent*) ()
at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#19 0x00007ffff384283c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#20 0x00007ffff384a65f in QApplication::notify(QObject*, QEvent*) ()
at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#21 0x00007ffff23bd9c8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x00007ffff3849632 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) ()
at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#23 0x00007ffff389c16b in () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#24 0x00007ffff389e7da in () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#25 0x00007ffff384283c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#26 0x00007ffff384a104 in QApplication::notify(QObject*, QEvent*) ()
at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#27 0x00007ffff23bd9c8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#28 0x00007ffff2e64583 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#29 0x00007ffff2e66055 in QGuiApplicationPrivate::processWindowSystemEvent(QWind---Type <return> to continue, or q <return> to quit---
owSystemInterfacePrivate::WindowSystemEvent*) ()
at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#30 0x00007ffff2e3d2eb in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#31 0x00007fffdedd0260 in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#32 0x00007fffed8f3417 in g_main_context_dispatch ()
at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#33 0x00007fffed8f3650 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#34 0x00007fffed8f36dc in g_main_context_iteration ()
at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#35 0x00007ffff241697f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#36 0x00007ffff23bb9fa in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#37 0x00007ffff23c4aa4 in QCoreApplication::exec() ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#38 0x000055555562e23b in main(int, char**) (argc=1, argv=0x7fffffffdf88)
at /home/steve/Projects/kstars/kstars/main.cpp:332
(gdb)

I'll check one more time but if you could TeamViewer in that would be great.
TIA,
Steve
The following user(s) said Thank You: Jasem Mutlaq
4 years 2 months ago #48146

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

I actually tried now with multiple profile but couldn't get the crash.. teamviewer would be next.
4 years 2 months ago #48150

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

Time to create page: 0.933 seconds