coriander-user Mailing List for Coriander

Damien,

Thanks for your response…it appears the Micromanager package for microscopes does indeed have a driver for the Micropublisher, but it appears to be quite old and only for black and white.

Venkat


> On Mar 31, 2020, at 8:01 AM, Damien Douxchamps <dd...@do...> wrote:
> 
> Hello Venkat,
> 
> On Tue, 2020-03-31 at 01:00 +0000, Venkat Chandrasekhar wrote:
>> I was able to get coriander to compile from source on a Ubuntu based
>> distro (elementary os, vs 5.1), which runs kernel 5.3.0 by running the
>> configure script and installing all the packages required.  (the SDL
>> library used should be downgraded to version 1, as version 2 is
>> installed by default).  Using chmod 666 on /dev/fw*, I was able to
>> view the image from an old Apple iSight camera.
> 
> Great news! I'm running a much older distro so I don't know if Coriander
> can be build on recent systems.
> 
>> Unfortunately, the camera I actually would like to use for  a
>> microscopy application, a QImaging Micropublisher 3.3., was not
>> recognized by coriander.  A closer look at the excellent camera
>> listing by Damien Douxchamps showed me
> 
> (thanks!)
> 
>> that although the camera was listed, it does not support the IIDC
>> standard, and hence would not be recognized by libdc1394.  My mistake:
>> I should have looked at the documentation more closely before
>> starting.  I am now back to using the QImaging legacy software on
>> Windows, but Coriander does compile and work on a relatively recent
>> Ubuntu based distribution.
> 
> Yeah, not all cameras are compatible with IIDC. I think some QImaging
> cameras were compatible but I'm not sure any more. It was all a little
> bit messy. And with recent standards that have put the deeper
> capture/control layers entirely in the hands of manufacturers I don't
> know when we'll see another standard like IIDC :(
> 
> -- 
> Damien 高原 Douxchamps    https://urldefense.com/v3/__http://damien.douxchamps.net/__;!!Dq0X2DkFhyF93HkjWTBQKhk!HwubD42ADvUq040Cysyav_QXl3ZTjN716aRf2Ne6la1v3Gv-PpaS0gwSYPg8wd-eyCK5uxgp7UqK$ 
> 
> 
> 
> _______________________________________________
> Coriander-user mailing list
> Cor...@li...
> https://urldefense.com/v3/__https://lists.sourceforge.net/lists/listinfo/coriander-user__;!!Dq0X2DkFhyF93HkjWTBQKhk!HwubD42ADvUq040Cysyav_QXl3ZTjN716aRf2Ne6la1v3Gv-PpaS0gwSYPg8wd-eyCK5u8xKnSPA$ 

Hello Venkat,

On Tue, 2020-03-31 at 01:00 +0000, Venkat Chandrasekhar wrote:
> I was able to get coriander to compile from source on a Ubuntu based
> distro (elementary os, vs 5.1), which runs kernel 5.3.0 by running the
> configure script and installing all the packages required.  (the SDL
> library used should be downgraded to version 1, as version 2 is
> installed by default).  Using chmod 666 on /dev/fw*, I was able to
> view the image from an old Apple iSight camera.

Great news! I'm running a much older distro so I don't know if Coriander
can be build on recent systems.

> Unfortunately, the camera I actually would like to use for  a
> microscopy application, a QImaging Micropublisher 3.3., was not
> recognized by coriander.  A closer look at the excellent camera
> listing by Damien Douxchamps showed me

(thanks!)

>  that although the camera was listed, it does not support the IIDC
> standard, and hence would not be recognized by libdc1394.  My mistake:
> I should have looked at the documentation more closely before
> starting.  I am now back to using the QImaging legacy software on
> Windows, but Coriander does compile and work on a relatively recent
> Ubuntu based distribution.

Yeah, not all cameras are compatible with IIDC. I think some QImaging
cameras were compatible but I'm not sure any more. It was all a little
bit messy. And with recent standards that have put the deeper
capture/control layers entirely in the hands of manufacturers I don't
know when we'll see another standard like IIDC :(

-- 
Damien 高原 Douxchamps    http://damien.douxchamps.net/

I was able to get coriander to compile from source on a Ubuntu based distro (elementary os, vs 5.1), which runs kernel 5.3.0 by running the configure script and installing all the packages required.  (the SDL library used should be downgraded to version 1, as version 2 is installed by default).  Using chmod 666 on /dev/fw*, I was able to view the image from an old Apple iSight camera.  Unfortunately, the camera I actually would like to use for  a microscopy application, a QImaging Micropublisher 3.3., was not recognized by coriander.  A closer look at the excellent camera listing by Damien Douxchamps showed me that although the camera was listed, it does not support the IIDC standard, and hence would not be recognized by libdc1394.  My mistake: I should have looked at the documentation more closely before starting.  I am now back to using the QImaging legacy software on Windows, but Coriander does compile and work on a relatively recent Ubuntu based distribution.

Venkat Chandrasekhar

I have been trying to install and run Coriander on both an Ubuntu 19.10 distribution as well as on OpenSuse Leap 15.1 distribution.

I am trying to control a QImaging Micropublisher 3.3 camera through a PCI firewire card.  The card and camera were detected and work on the same machine using Windows 10 and QImaging’s own software, so there appear to be no problems with the card or camera.  On both Ubuntu and OpenSuse, the card is detected and is tied to the firewire-ohci module, and /dev/fw0 and /dev/fw1 show up on the device list (the card has two ports).

On Ubuntu, there are no deb packages to install coriander as apparently coriander requires Gnome 2, and current Ubuntu distributions are based on Gnome3.  Attempting to install coriander from source gives the error that libgnomeui-2.0 is not installed, but this package is no longer available from the 19.10 Ubuntu distributions.

I was able to install coriander on OpenSuse Leap 15.1, but the program quits immediately saying that no camera was found, with no other error message.  I think the problem is associated with permissions for the device files (/dev/fw*).  I found some howtos from 2008, but none of these seem to apply as they all discuss pre-Juju stack configurations (they discuss /dev/raw1394 and /dev/video1394).   I have tried the usual tricks of adding the current user to the video group, changing permission to /dev/fw*, but none of them seem to help.  So my question is, are there more up-to-date instructions on setting up coriander and libdc1394 with the new juju stacks?

Thanks for any help in advance.

Venkat Chandrasekhar
      

  I've been very busy with other tasks for some weeks now, so have had
little time to pursue this challenge.

On 07/19/16 01:35, Damien Douxchamps wrote:

> Then it seems to be related to lower level stuff, maybe a USB chipset
> quirk of some sort...? Could you dump the result of "lspci" on both
> machines? Also check the various logs (dmesg?) for related errors. There
> may also be issues with USB3 ports compared to USB2 ports. Maybe the
> working machine is USB2 only?

  lspci output from three different machines appended below. Coriander
works on both simak and asimov without any identifiable difficulties;
the program runs on harrison but exhibits substantial lag when dialog
buttons are activated and I've been unable to obtain color images. Also
appended is an excerpt from "/var/log/syslog" showing all messages from
the time the camera is connected until coriander is terminated. Nothing
looks out of place and no messages were logged as coriander ran.

  Given that I have only one system which doesn't work correctly, I
would suggest that this issue doesn't warrant a lot of attention. If you
see something obvious which might correct the problem, please pass the
word along but otherwise I wouldn't worry about it. I've also tried
using this camera under coriander on a Raspberry Pi 2 with mixed
results. I'll post a separate report on that effort if I can't resolve
the issues I was seeing there.

				-- Mike --
-- 
f7j...@co...

On Sat, 2016-07-16 at 10:30 -0700, MC wrote:
>   A further update on this topic. I had the chance to boot Ubuntu 14.04
> on one of my other computers from the same flash drive used for the
> primary computer. After again installing coriander-2.0.2 from the
> repositories, it appears to work without any significant errors on that
> machine. There is no appreciable lag when selecting dialog items, I can
> configure the display to any of the available choices, and both color
> and monochrome images render well. Debian wheezy is normally runs on the
> alternate machine. Installing coriander-2.0.1 under wheezy from the
> repositories results in pretty much the same outcome -- everything seems
> to be working as intended.
> 
>  Whatever the problem may be, it's certainly related to the difference
> in hardware or hardware configuration between the two machines. I tried
> connecting the camera to the Dell machine using an ExpressCard USB 3.0
> adapter in case the behavior I'm seeing is related to integrated USB
> support, however results were identical.
> 
>   High-level details for each are listed below. If you have any ideas as
> to why the camera works well with one but not the other, or suggestions
> for alternate configuration options which may be applied, please pass
> them along.

Then it seems to be related to lower level stuff, maybe a USB chipset
quirk of some sort...? Could you dump the result of "lspci" on both
machines? Also check the various logs (dmesg?) for related errors. There
may also be issues with USB3 ports compared to USB2 ports. Maybe the
working machine is USB2 only?

Damien

> 				-- Mike --
> 
> Fully functional
> ----------------
> Fujitsu LifeBook AH550
> Intel Core i3-330M 2.13 GHz, 3 MB L3 cache, 1066 MHz FSB
> Intel HM55 Express Chipset
> 
> Minimally functional
> --------------------
> Dell Latitude E6520
> Intel Core i5-2430M, 2.40 GHz, 3 MB cache
> Intel QM67 Express Chipset
> nVidia NVS 4200M 512 MB discrete graphics[see note below]
> 
>   According to Dell, this machine shipped with a discrete graphics
> module in place of Intel HD Graphics 3000 integrated graphics support.
> I've not confirmed this claim.

-- 
Damien 高原 Douxchamps    http://damien.douxchamps.net/

  A further update on this topic. I had the chance to boot Ubuntu 14.04
on one of my other computers from the same flash drive used for the
primary computer. After again installing coriander-2.0.2 from the
repositories, it appears to work without any significant errors on that
machine. There is no appreciable lag when selecting dialog items, I can
configure the display to any of the available choices, and both color
and monochrome images render well. Debian wheezy is normally runs on the
alternate machine. Installing coriander-2.0.1 under wheezy from the
repositories results in pretty much the same outcome -- everything seems
to be working as intended.

 Whatever the problem may be, it's certainly related to the difference
in hardware or hardware configuration between the two machines. I tried
connecting the camera to the Dell machine using an ExpressCard USB 3.0
adapter in case the behavior I'm seeing is related to integrated USB
support, however results were identical.

  High-level details for each are listed below. If you have any ideas as
to why the camera works well with one but not the other, or suggestions
for alternate configuration options which may be applied, please pass
them along.

				-- Mike --

Fully functional
----------------
Fujitsu LifeBook AH550
Intel Core i3-330M 2.13 GHz, 3 MB L3 cache, 1066 MHz FSB
Intel HM55 Express Chipset

Minimally functional
--------------------
Dell Latitude E6520
Intel Core i5-2430M, 2.40 GHz, 3 MB cache
Intel QM67 Express Chipset
nVidia NVS 4200M 512 MB discrete graphics[see note below]

  According to Dell, this machine shipped with a discrete graphics
module in place of Intel HD Graphics 3000 integrated graphics support.
I've not confirmed this claim.
-- 
f7j...@co...

On 07/06/16 05:55, Damien Douxchamps wrote:

> I didn't spot anything wrong with the linked libraries. Any luck with
> 14.04?

  Results are much the same as I found using Mint 17.3. I changed the
BIOS setting as recommended to ensure that sleep states were disabled,
though this didn't appear to have any significant effect. There is
perhaps slightly less lag when selecting dialog buttons. The problems
reported in my initial message regarding inability to access certain
dialogs or obtain color images from the camera persist.

  Do you by any chance have access to this camera model? If you're able
to make it work while I'm not, some procedural error on my part may be
indicated. It also occurs to me that I can try the same tests using a
different computer, in case there is something unique to the USB
subsystem on my Dell which is causing problems.

  Thanks for the information and suggestions provided so far.

				-- Mike --
-- 
f7j...@co...

Hi Mike,

On Tue, 2016-06-28 at 23:23 -0700, MC wrote:
> On 06/27/16 22:13, Damien Douxchamps wrote:
> 
> > The biggest problem is the foobar'ed UI. I've never experienced this
> > kind of major issue so I'm a bit clueless but I think this points to
> > some deeper problem, maybe GNOME subsystem related. Coriander was
> > designed a long time ago (15+ years!) and there may be compatibility
> > issues with more recent GNOME releases. I'm currently using ubuntu
> > 14.04; could you make a quick install of that distro and try it? (it may
> > even be possible from the live CD...)
> 
>   I've downloaded the ISO image and transferred it to a USB flash
> module. It will be ready to go as soon as I can find an hour or two.
> 
> > Also please share the output of "ldd coriander" (or
> > "ldd /usr/loca/bin/coriander",...)
> 
>   See below. Don't know if the list server allows attachments, so I
> simply appended the output from ldd. Apologies for the line wrap.
> 
>   Thanks for the detailed reply. I'll report more in a day or two after
> I've had the chance to try using the camera under Ubuntu 14.04.

I didn't spot anything wrong with the linked libraries. Any luck with
14.04?

-- 
Damien 高原 Douxchamps    http://damien.douxchamps.net/

On 06/27/16 22:13, Damien Douxchamps wrote:

> The biggest problem is the foobar'ed UI. I've never experienced this
> kind of major issue so I'm a bit clueless but I think this points to
> some deeper problem, maybe GNOME subsystem related. Coriander was
> designed a long time ago (15+ years!) and there may be compatibility
> issues with more recent GNOME releases. I'm currently using ubuntu
> 14.04; could you make a quick install of that distro and try it? (it may
> even be possible from the live CD...)

  I've downloaded the ISO image and transferred it to a USB flash
module. It will be ready to go as soon as I can find an hour or two.

> Also please share the output of "ldd coriander" (or
> "ldd /usr/loca/bin/coriander",...)

  See below. Don't know if the list server allows attachments, so I
simply appended the output from ldd. Apologies for the line wrap.

  Thanks for the detailed reply. I'll report more in a day or two after
I've had the chance to try using the camera under Ubuntu 14.04.

				-- Mike --

harrison :: less /tmp/coriander.ldd
        linux-vdso.so.1 =>  (0x00007ffd760f1000)
        libgnomeui-2.so.0 => /usr/lib/x86_64-linux-gnu/libgnomeui-2.so.0
(0x00007efd71ef8000)
        libgnome-2.so.0 => /usr/lib/x86_64-linux-gnu/libgnome-2.so.0
(0x00007efd71ce1000)
        libgtk-x11-2.0.so.0 =>
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 (0x00007efd716a4000)
        libatk-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libatk-1.0.so.0
(0x00007efd71482000)
        libgdk_pixbuf-2.0.so.0 =>
/usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x00007efd71261000)
        libgobject-2.0.so.0 =>
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 (0x00007efd71010000)
        libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0
(0x00007efd70d08000)
        libtiff.so.5 => /usr/lib/x86_64-linux-gnu/libtiff.so.5
(0x00007efd70a96000)
        libftp.so.3 => /usr/lib/x86_64-linux-gnu/libftp.so.3
(0x00007efd7088f000)
        libSDL-1.2.so.0 => /usr/lib/x86_64-linux-gnu/libSDL-1.2.so.0
(0x00007efd705f9000)
        libdc1394.so.22 => /usr/local/lib/libdc1394.so.22
(0x00007efd70382000)
        libraw1394.so.11 => /usr/local/lib/libraw1394.so.11
(0x00007efd70174000)
        libXv.so.1 => /usr/lib/x86_64-linux-gnu/libXv.so.1
(0x00007efd6ff6f000)
        libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6
(0x00007efd6fc3a000)
        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x00007efd6fa1c000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007efd6f657000)
        libbonoboui-2.so.0 =>
/usr/lib/x86_64-linux-gnu/libbonoboui-2.so.0 (0x00007efd6f3ea000)
        libgnomecanvas-2.so.0 =>
/usr/lib/x86_64-linux-gnu/libgnomecanvas-2.so.0 (0x00007efd6f1b5000)
        libart_lgpl_2.so.2 =>
/usr/lib/x86_64-linux-gnu/libart_lgpl_2.so.2 (0x00007efd6ef9c000)
        libgdk-x11-2.0.so.0 =>
/usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 (0x00007efd6ece9000)
        libpango-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0
(0x00007efd6ea9c000)
        libgio-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
(0x00007efd6e729000)
        libgnomevfs-2.so.0 =>
/usr/lib/x86_64-linux-gnu/libgnomevfs-2.so.0 (0x00007efd6e4c1000)
        libgconf-2.so.4 => /usr/lib/x86_64-linux-gnu/libgconf-2.so.4
(0x00007efd6e292000)
        libgnome-keyring.so.0 =>
/usr/lib/x86_64-linux-gnu/libgnome-keyring.so.0 (0x00007efd6e06d000)
        libSM.so.6 => /usr/lib/x86_64-linux-gnu/libSM.so.6
(0x00007efd6de65000)
        libICE.so.6 => /usr/lib/x86_64-linux-gnu/libICE.so.6
(0x00007efd6dc49000)
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007efd6d943000)
        libbonobo-2.so.0 => /usr/lib/x86_64-linux-gnu/libbonobo-2.so.0
(0x00007efd6d6d3000)
        libbonobo-activation.so.4 =>
/usr/lib/x86_64-linux-gnu/libbonobo-activation.so.4 (0x00007efd6d4b9000)
        libgmodule-2.0.so.0 =>
/usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0 (0x00007efd6d2b5000)
        libgthread-2.0.so.0 =>
/usr/lib/x86_64-linux-gnu/libgthread-2.0.so.0 (0x00007efd6d0b3000)
        libcanberra.so.0 => /usr/lib/x86_64-linux-gnu/libcanberra.so.0
(0x00007efd6cea3000)
        libpopt.so.0 => /lib/x86_64-linux-gnu/libpopt.so.0
(0x00007efd6cc97000)
        libpangocairo-1.0.so.0 =>
/usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0 (0x00007efd6ca8a000)
        libXfixes.so.3 => /usr/lib/x86_64-linux-gnu/libXfixes.so.3
(0x00007efd6c884000)
        libcairo.so.2 => /usr/lib/x86_64-linux-gnu/libcairo.so.2
(0x00007efd6c579000)
        libpangoft2-1.0.so.0 =>
/usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0 (0x00007efd6c364000)
        libfontconfig.so.1 =>
/usr/lib/x86_64-linux-gnu/libfontconfig.so.1 (0x00007efd6c128000)
        libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6
(0x00007efd6bf20000)
        libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3
(0x00007efd6bce2000)
        liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5
(0x00007efd6bac0000)
        libjbig.so.0 => /usr/lib/x86_64-linux-gnu/libjbig.so.0
(0x00007efd6b8b2000)
        libjpeg.so.8 => /usr/lib/x86_64-linux-gnu/libjpeg.so.8
(0x00007efd6b65d000)
        libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007efd6b444000)
        libasound.so.2 => /usr/lib/x86_64-linux-gnu/libasound.so.2
(0x00007efd6b154000)
        libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007efd6af50000)
        libpulse-simple.so.0 =>
/usr/lib/x86_64-linux-gnu/libpulse-simple.so.0 (0x00007efd6ad4c000)
        libpulse.so.0 => /usr/lib/x86_64-linux-gnu/libpulse.so.0
(0x00007efd6ab03000)
        libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6
(0x00007efd6a8f1000)
        libcaca.so.0 => /usr/lib/x86_64-linux-gnu/libcaca.so.0
(0x00007efd6a624000)
        libusb-1.0.so.0 => /usr/local/lib/libusb-1.0.so.0
(0x00007efd6a414000)
        libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1
(0x00007efd6a1f5000)
        /lib64/ld-linux-x86-64.so.2 (0x00007efd72193000)
        linux-vdso.so.1 =>  (0x00007ffd760f1000)
        libgnomeui-2.so.0 => /usr/lib/x86_64-linux-gnu/libgnomeui-2.so.0
(0x00007efd71ef8000)
        libgnome-2.so.0 => /usr/lib/x86_64-linux-gnu/libgnome-2.so.0
(0x00007efd71ce1000)
        libgtk-x11-2.0.so.0 =>
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 (0x00007efd716a4000)
        libatk-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libatk-1.0.so.0
(0x00007efd71482000)
        libgdk_pixbuf-2.0.so.0 =>
/usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x00007efd71261000)
        libgobject-2.0.so.0 =>
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 (0x00007efd71010000)
        libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0
(0x00007efd70d08000)
        libtiff.so.5 => /usr/lib/x86_64-linux-gnu/libtiff.so.5
(0x00007efd70a96000)
        libftp.so.3 => /usr/lib/x86_64-linux-gnu/libftp.so.3
(0x00007efd7088f000)
        libSDL-1.2.so.0 => /usr/lib/x86_64-linux-gnu/libSDL-1.2.so.0
(0x00007efd705f9000)
        libdc1394.so.22 => /usr/local/lib/libdc1394.so.22
(0x00007efd70382000)
        libraw1394.so.11 => /usr/local/lib/libraw1394.so.11
(0x00007efd70174000)
        libXv.so.1 => /usr/lib/x86_64-linux-gnu/libXv.so.1
(0x00007efd6ff6f000)
        libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6
(0x00007efd6fc3a000)
        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x00007efd6fa1c000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007efd6f657000)
        libbonoboui-2.so.0 =>
/usr/lib/x86_64-linux-gnu/libbonoboui-2.so.0 (0x00007efd6f3ea000)
        libgnomecanvas-2.so.0 =>
/usr/lib/x86_64-linux-gnu/libgnomecanvas-2.so.0 (0x00007efd6f1b5000)
        libart_lgpl_2.so.2 =>
/usr/lib/x86_64-linux-gnu/libart_lgpl_2.so.2 (0x00007efd6ef9c000)
        libgdk-x11-2.0.so.0 =>
/usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 (0x00007efd6ece9000)
        libpango-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0
(0x00007efd6ea9c000)
        libgio-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
(0x00007efd6e729000)
        libgnomevfs-2.so.0 =>
/usr/lib/x86_64-linux-gnu/libgnomevfs-2.so.0 (0x00007efd6e4c1000)
        libgconf-2.so.4 => /usr/lib/x86_64-linux-gnu/libgconf-2.so.4
(0x00007efd6e292000)
        libgnome-keyring.so.0 =>
/usr/lib/x86_64-linux-gnu/libgnome-keyring.so.0 (0x00007efd6e06d000)
        libSM.so.6 => /usr/lib/x86_64-linux-gnu/libSM.so.6
(0x00007efd6de65000)
        libICE.so.6 => /usr/lib/x86_64-linux-gnu/libICE.so.6
(0x00007efd6dc49000)
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007efd6d943000)
        libbonobo-2.so.0 => /usr/lib/x86_64-linux-gnu/libbonobo-2.so.0
(0x00007efd6d6d3000)
        libbonobo-activation.so.4 =>
/usr/lib/x86_64-linux-gnu/libbonobo-activation.so.4 (0x00007efd6d4b9000)
        libgmodule-2.0.so.0 =>
/usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0 (0x00007efd6d2b5000)
        libgthread-2.0.so.0 =>
/usr/lib/x86_64-linux-gnu/libgthread-2.0.so.0 (0x00007efd6d0b3000)
        libcanberra.so.0 => /usr/lib/x86_64-linux-gnu/libcanberra.so.0
(0x00007efd6cea3000)
        libpopt.so.0 => /lib/x86_64-linux-gnu/libpopt.so.0
(0x00007efd6cc97000)
        libpangocairo-1.0.so.0 =>
/usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0 (0x00007efd6ca8a000)
        libXfixes.so.3 => /usr/lib/x86_64-linux-gnu/libXfixes.so.3
(0x00007efd6c884000)
        libcairo.so.2 => /usr/lib/x86_64-linux-gnu/libcairo.so.2
(0x00007efd6c579000)
        libpangoft2-1.0.so.0 =>
/usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0 (0x00007efd6c364000)
        libfontconfig.so.1 =>
/usr/lib/x86_64-linux-gnu/libfontconfig.so.1 (0x00007efd6c128000)
        libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6
(0x00007efd6bf20000)
        libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3
(0x00007efd6bce2000)
        liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5
(0x00007efd6bac0000)
        libjbig.so.0 => /usr/lib/x86_64-linux-gnu/libjbig.so.0
(0x00007efd6b8b2000)
        libjpeg.so.8 => /usr/lib/x86_64-linux-gnu/libjpeg.so.8
(0x00007efd6b65d000)
        libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007efd6b444000)
        libasound.so.2 => /usr/lib/x86_64-linux-gnu/libasound.so.2
(0x00007efd6b154000)
        libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007efd6af50000)
        libpulse-simple.so.0 =>
/usr/lib/x86_64-linux-gnu/libpulse-simple.so.0 (0x00007efd6ad4c000)
        libpulse.so.0 => /usr/lib/x86_64-linux-gnu/libpulse.so.0
(0x00007efd6ab03000)
        libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6
(0x00007efd6a8f1000)
        libcaca.so.0 => /usr/lib/x86_64-linux-gnu/libcaca.so.0
(0x00007efd6a624000)
        libusb-1.0.so.0 => /usr/local/lib/libusb-1.0.so.0
(0x00007efd6a414000)
        libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1
(0x00007efd6a1f5000)
-- 
f7j...@co...

Hi Mike,

On Sun, 2016-06-26 at 11:08 -0700, MC wrote:
>   I recently obtained a used Point Grey Research Chameleon CMLN-13S2C
> USB-2.0 camera which I'd like to use for some time lapse work. Prior to
> buying the camera, I found several postings on the Internet indicating
> that this model should work under Linux with Coriander, including one in
> a Point Grey Knowledge Base article (KB 10103). The camera was initially

Yes it should work.

> tested using PGR's FlyCapture utility to confirm that it was fully
> functional. While the FlyCapture GUI under Linux has its peculiarities,
> I encountered no difficulties with configuration of the camera and was
> able to view good quality images in both color and monochrome modes at
> all supported resolutions.
> 
>   My computer is a Dell Core i5-based model running Linux Mint 17.3.
> Coriander-2.02 is one of the packages available through the Ubuntu
> repositories, so after initial check-out I attempted to use the camera
> with the package maintainers' version of Coriander.
> 
>   The camera is reliably detected by Coriander and some operations work
> as expected. Camera information is reported correctly, all of the
> primary tabs except ROI on can be selected, most of the configuration
> options under all tabs can be selected, and Services -> Display opens a
> window which displays camera images with an occasional dropped frame.

Dropped frames can happen depending on the host computer performance.
Also verify that you don't have the sleep states enabled in your BIOS:
they can seriously degrade real-time video performance.

The ROI tab may not be accessible if the camera (or currently selected
video mode) doesn't support ROI. But since the camera does have some ROI
capabilities this looks like yet another UI problem.

>   I've noted a number of issues, however. These may well result from
> configuration errors or other problems which I've introduced, however
> I've not found resolution in the available documentation. Perhaps
> someone with more experience using Coriander could provide some
> guidance. I'd be particularly interested in first hand success using
> this particular camera model. What I've noted is listed below. Beside
> using the version of Coriander from the Ubuntu repositories, I've also
> built the program from source in case there were dependencies upon the
> FlyCapture libraries.

Coriander or libdc1394 have no dependencies with PGR libraries or
software.

> As a registered Point Grey customer, I have their
> SDK (flycapture2-2.8.3.1-amd64) installed on my system. In order to
> build Coriander-2.0.2, I also had to build libusb-1.0.9, libdc1394-2.2.4
> and libraw1394-2.0.5. Log files were generated from configure and make
> operations and show no obvious errors or missing packages. No obvious
> differences in behavior between the pre-packaged and source-built
> Coriander binaries have been noted.
> 
> Issues and observations
> -----------------------
> 
> There is substantial (>4 second) lag between selection of most dialog
> buttons and response from the program.

If the lag happens even when you don't change a camera parameter (e.g.
changing something in the "display" or "save" service tabs) then there
may be an issue with GNOME or some lower level component of your system.

If the lag only happens when you change a camera parameter (e.g. setting
something in the controls tab) then the USB on your machine may have an
issue (lag talking to the camera).

It looks like a fairly large issue; other problems may be linked to
this.

> Services -> Receive tab -> Format lists six configuration options,
> however only the default (Format 2, Mode 2, 1280x960 8bpp) can be
> selected. The Format selection list cannot reliably be opened. Most
> attempts at clicking on the selection list have no effect.

This looks like some UI/system issue, not related to the camera, 1394 or
USB. 

> Services -> Display button opens a display window which shows video from
> the camera, however only as monochrome images. I presume this is related
> to camera format selection as described above.

Yes, if the format is monochrome then it will render in grayscale. Some
color cameras support monochrome modes but send raw bayer images instead
of truly grayscale data. You can spot that by looking for a
lattice-looking texture on strongly red, green or blue objects. 

> Controls -> White balance
>   None of the three controls respond.

Not surprising given the big UI issue you experience...

> Services -> Receive tab -> Options
>   First list select button does not respond. No Bayer selection is fixed
> (again, presumably related to camera format selection).

Bayer is selectable for monochrome images given some monochrome images
are actually bayer (see above). If it's not -> another UI issue.

>   Second list select button provides the four de-mosaic options, any of
> which can be selected.

That looks OK.

> Services -> Save tab -> Format list selection button does not respond.
> Selection fixed at "Raw (still)".

OK that's another weird UI thing.

>   The camera was received with an older firmware load. This has been
> updated to 1.17.3.0, though not to any obvious effect.

The firmware should not matter too much. PGR has very good IIDC
firmwares, including in their USB cameras.

>   Any assistance or suggestions which might be offered would be most
> appreciated.

The biggest problem is the foobar'ed UI. I've never experienced this
kind of major issue so I'm a bit clueless but I think this points to
some deeper problem, maybe GNOME subsystem related. Coriander was
designed a long time ago (15+ years!) and there may be compatibility
issues with more recent GNOME releases. I'm currently using ubuntu
14.04; could you make a quick install of that distro and try it? (it may
even be possible from the live CD...)

Also please share the output of "ldd coriander" (or
"ldd /usr/loca/bin/coriander",...)

Damien

-- 
Damien 高原 Douxchamps    http://damien.douxchamps.net/

  I recently obtained a used Point Grey Research Chameleon CMLN-13S2C
USB-2.0 camera which I'd like to use for some time lapse work. Prior to
buying the camera, I found several postings on the Internet indicating
that this model should work under Linux with Coriander, including one in
a Point Grey Knowledge Base article (KB 10103). The camera was initially
tested using PGR's FlyCapture utility to confirm that it was fully
functional. While the FlyCapture GUI under Linux has its peculiarities,
I encountered no difficulties with configuration of the camera and was
able to view good quality images in both color and monochrome modes at
all supported resolutions.

  My computer is a Dell Core i5-based model running Linux Mint 17.3.
Coriander-2.02 is one of the packages available through the Ubuntu
repositories, so after initial check-out I attempted to use the camera
with the package maintainers' version of Coriander.

  The camera is reliably detected by Coriander and some operations work
as expected. Camera information is reported correctly, all of the
primary tabs except ROI on can be selected, most of the configuration
options under all tabs can be selected, and Services -> Display opens a
window which displays camera images with an occasional dropped frame.

  I've noted a number of issues, however. These may well result from
configuration errors or other problems which I've introduced, however
I've not found resolution in the available documentation. Perhaps
someone with more experience using Coriander could provide some
guidance. I'd be particularly interested in first hand success using
this particular camera model. What I've noted is listed below. Beside
using the version of Coriander from the Ubuntu repositories, I've also
built the program from source in case there were dependencies upon the
FlyCapture libraries. As a registered Point Grey customer, I have their
SDK (flycapture2-2.8.3.1-amd64) installed on my system. In order to
build Coriander-2.0.2, I also had to build libusb-1.0.9, libdc1394-2.2.4
and libraw1394-2.0.5. Log files were generated from configure and make
operations and show no obvious errors or missing packages. No obvious
differences in behavior between the pre-packaged and source-built
Coriander binaries have been noted.

Issues and observations
-----------------------

There is substantial (>4 second) lag between selection of most dialog
buttons and response from the program.

Services -> Receive tab -> Format lists six configuration options,
however only the default (Format 2, Mode 2, 1280x960 8bpp) can be
selected. The Format selection list cannot reliably be opened. Most
attempts at clicking on the selection list have no effect.

Services -> Display button opens a display window which shows video from
the camera, however only as monochrome images. I presume this is related
to camera format selection as described above.

Controls -> White balance
  None of the three controls respond.

Services -> Receive tab -> Options
  First list select button does not respond. No Bayer selection is fixed
(again, presumably related to camera format selection).

  Second list select button provides the four de-mosaic options, any of
which can be selected.

Services -> Save tab -> Format list selection button does not respond.
Selection fixed at "Raw (still)".

  The camera was received with an older firmware load. This has been
updated to 1.17.3.0, though not to any obvious effect.

  Any assistance or suggestions which might be offered would be most
appreciated.
				-- Mike --
-- 
f7j...@co...

Hi Tim,

On Thu, 2016-03-24 at 17:11 -0700, CF Mineral Research Ltd wrote:
> Hello,
> 
> first of all, I have read through the manual and the posts.
> 
> What we have: 
> 
> Coriander 2.0.2
> Ubuntu 14.04 LTS, 64 bit
> Allied Vision Stingray F-046B/C camera
> Allied Vision firewire card FWB-PCIe1x20
> IEEE 1394b firewire cable
> 
> The video works great but we constantly get errors popping up over
> top. If we could just make the errors pop up to the side, out of the
> way of the video, we'd be much happier. The errors do not affect the
> quality of the video, except that they pop up right in the bulls eye
> of the video. We don't need to solve the errors unless that's the only
> way to get the error windows out of the way. Otherwise, it is really a
> great program.
> 
> The two errors are:
> 
> Error 1. "Could not get a camera bandwidth usage. Bus usage might be
> inaccurate."
> Error 2. "Could not get ISO status."

Go in File->Preferences. There is an option to show (or hide) the
warning/error popups. If it still doesn;t work after that I'll have to
fix something...

Damien

-- 
Damien 高原 Douxchamps    http://damien.douxchamps.net/

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000000">
Hello,<br>
<br>
first of all, I have read through the manual and the posts.<br>
<br>
What we have: <br>
<br>
Coriander 2.0.2<br>
Ubuntu 14.04 LTS, 64 bit<br>
Allied Vision Stingray F-046B/C camera<br>
Allied Vision firewire card FWB-PCIe1x20<br>
IEEE 1394b firewire cable<br>
<br>
The video works great but we constantly get errors popping up over top.
If we could just make the errors pop up to the side, out of the way of
the video, we'd be much happier. The errors do not affect the quality
of the video, except that they pop up right in the bulls eye of the
video. We don't need to solve the errors unless that's the only way to
get the error windows out of the way. Otherwise, it is really a great
program.<br>
<br>
The two errors are:<br>
<br>
Error 1. "Could not get a camera bandwidth usage. Bus usage might be
inaccurate."<br>
Error 2. "Could not get ISO status."<br>
<br>
Please help us, (we are not programmers)<br>
<br>
thankyou,<br>
<br>
Tim<br>
<br>
<br>
<br>
<br>
<br>
<br>
<div class="moz-signature">-- <br>
<meta http-equiv="CONTENT-TYPE" content="text/html; ">
<title></title>
<meta name="GENERATOR" content="OpenOffice.org 3.2  (Linux)">
<meta name="CREATED" content="0;0">
<meta name="CHANGED" content="20140124;12015900">
<p>Please forward or distribute in confidence for attention of the
following:</p>
<p><br>
<br>
</p>
<p><br>
<br>
</p>
<p style="margin-bottom: 0.25cm;">Privileged Information</p>
<p style="margin-bottom: 0cm;" align="justify">This Transmission
contains privileged information for the intended recipient which
maybe of a confidential or sensitive nature. If you have received
this email in error, please reply to that effect with subject line
&lt;&lt;Attn: Supervisor&gt;&gt; to <a
 href="mailto:la...@cf...">in...@cf...</a>
and then delete the message. Thank you.</p>
<hr>
<p style="margin-bottom: 0cm;">C.F. Mineral Research Ltd.<br>
1677
Powick Rd. Kelowna, B.C., <br>
Canada V1X 4L1 <br>
Tel: (250) 860-8525
<br>
Fax: (250) 862-9435 </p>
<hr>
</div>
</body>
</html>

Hello everyone,

this is my first message to this list.

For anyone interested, I packaged Coriander 2.0.2 for Slackware Linux 
(14.1 stable release). You can find the package at the SlackBuilds.org 
project's offical website:

http://slackbuilds.org/repository/14.1/multimedia/coriander/

This is not a binary package: it includes a build script that allows you 
to build your own package from the official Coriander source release 
(vanilla!), which is linked on the above page. All required and optional 
dependencies are already available from the SlackBuilds.org project. 
Below you can see the dependency tree: make sure that you build and 
install the packages in the correct order (of course Coriander will be 
the last one).

coriander
|-- ftplib (optional)
|-- libdc1394
|-- libgnomeui
     |-- libbonoboui
         |-- libgnomecanvas
         |-- libgnome
             |-- gnome-vfs
                 |-- gnome-mime-data
                 |-- libbonobo
                     |-- ORBit2

Feel free to drop me a line if you have any comments or suggestions 
regarding this package.

Best wishes,
Philip Lacroix

Hi Jerry,

On Thu, 2013-09-26 at 10:09 -0700, Jerry Biehler wrote: 
> I am trying use Coriander with one of my Point Grey Scorpion cameras.
> It fails on one of two ways. IU am using Ubuntu 10.04 under a P3 with
> 512m ram.
> 
> 
> First is I can start the camera and see the frame rate display show I
> am getting images from the camera. If I open the display window I get
> just a black screen. When I close the window coriander crashes.
> Sometimes it just crashes when I try to open the window.
> 
> 
> I get this in the console when it does. 
> 
> 
> The program 'coriander' received an X Window System error.
> This probably reflects a bug in the program.
> The error was 'BadAlloc (insufficient resources for operation)'.
>   (Details: serial 26 error_code 11 request_code 132 minor_code 19)
>   (Note to programmers: normally, X errors are reported
> asynchronously;
>    that is, you will receive the error a while after causing it.
>    To debug your program, run it with the --sync command line
>    option to change this behavior. You can then get a meaningful
>    backtrace from your debugger if you break on the gdk_x_error()
> function.)
> 
> 
> I dont think it is a camera specific issue. I tried with another
> camera, an ESI CorrectCam, and it does the exact same thing. Mode
> settings have no effect. I tried saving the images coming through the
> stream and it looks like there are good images coming though.

This is indeed not a camera problem. My guess would be some allocation
error of an image field, possibly due to limited system resources. Very
wild guess though. What kind of (video) memory do you have?

Could you run the program in gdb or valgrind to locate the bug with a
better accuracy?

Damien


-- 
Damien 高原 Douxchamps   http://damien.douxchamps.net/

Can youplease remove this e-mail address from the Coriander mailing 
list. Thank you
On 9/26/2013 10:09 AM, Jerry Biehler wrote:
> I am trying use Coriander with one of my Point Grey Scorpion cameras. 
> It fails on one of two ways. IU am using Ubuntu 10.04 under a P3 with 
> 512m ram.
>
> First is I can start the camera and see the frame rate display show I 
> am getting images from the camera. If I open the display window I get 
> just a black screen. When I close the window coriander crashes. 
> Sometimes it just crashes when I try to open the window.
>
> I get this in the console when it does.
>
>
> The program 'coriander' received an X Window System error.
> This probably reflects a bug in the program.
> The error was 'BadAlloc (insufficient resources for operation)'.
>   (Details: serial 26 error_code 11 request_code 132 minor_code 19)
>   (Note to programmers: normally, X errors are reported asynchronously;
>    that is, you will receive the error a while after causing it.
>    To debug your program, run it with the --sync command line
>    option to change this behavior. You can then get a meaningful
>    backtrace from your debugger if you break on the gdk_x_error() 
> function.)
>
> I dont think it is a camera specific issue. I tried with another 
> camera, an ESI CorrectCam, and it does the exact same thing. Mode 
> settings have no effect. I tried saving the images coming through the 
> stream and it looks like there are good images coming though.
>
> -Jerry
>
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
>
>
> _______________________________________________
> Coriander-user mailing list
> Cor...@li...
> https://lists.sourceforge.net/lists/listinfo/coriander-user

I am trying use Coriander with one of my Point Grey Scorpion cameras. It
fails on one of two ways. IU am using Ubuntu 10.04 under a P3 with 512m ram.

First is I can start the camera and see the frame rate display show I am
getting images from the camera. If I open the display window I get just a
black screen. When I close the window coriander crashes. Sometimes it just
crashes when I try to open the window.

I get this in the console when it does.


The program 'coriander' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 26 error_code 11 request_code 132 minor_code 19)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

I dont think it is a camera specific issue. I tried with another camera, an
ESI CorrectCam, and it does the exact same thing. Mode settings have no
effect. I tried saving the images coming through the stream and it looks
like there are good images coming though.

-Jerry

Hi Damien,

Thanks for the quick reply! What I meant was to change the fps on the
settings. I would like to take long exposure(shutter time?) photos with
coriander. And would like to change the display time so that I could
hopefully reach more than 10 seconds...

thanks!

Katherine

Hi Users,

I have a ARM7 processor(cubieboard). I have gotten the binaries from
apt-get and I am trying to stream live coriander images from a point-grey
Chameleon using ssh-X. Even at the 640x480 setting it was still laggy. I
was wondering if there was a good way to compress the images live and send
them? I don't need full resolution for streaming.

Another question is about saving. Is there a recommended application(I'm
running a Mac OS)to view the saved images (saved as still raw image)? I've
tried imageJ and it could not open it...

Thank you!
Katherine

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <font size="+1"><font face="Console">Please unsubscribe me as I
        never <font size="+1">subscribed to this list.<br>
          <font size="+1">I know n<font size="+1">o</font>thing about
            corriander at all<font size="+1">, nor do I use it.<br>
              <font size="+1">I h ave no idea why I am getting emails
                from this list.<br>
                <font size="+1">I tried to unsubscribe, <font size="+1">nut
                    it is asking <font size="+1">me for <font
                        size="+1">a password.<br>
                        <font size="+1">I have no idea what it is since
                          <font size="+1">I never su<font size="+1">bscribed!!!<br>
                              <br>
                              <font size="+1">Thanx.</font><br>
                            </font></font></font></font></font></font></font></font></font></font></font></font></font>
  </body>
</html>

jd...@gm..., you can unsubscribe by visiting the links in the bottom
of the email.

https://lists.sourceforge.net/lists/listinfo/coriander-user

Damien, thanks for awesome software - really helped me on numerous projects
2007-2009.

i've since moved on from computer vision, but at the time coriander was the
primary tool for getting point grey cameras online & functional.

cheers




On Thu, Jul 18, 2013 at 3:42 PM, JD <jd...@gm...> wrote:

>  I am  not a subscriber to this list.
> Why am I getting these emails?
> Would list admin please take me off the
> mailing list as I am unable to do so, since
> I have no idea who subscribed me and with
> what password.
>
> Thanx.
>
>  On 07/18/2013 08:28 AM, Damien Douxchamps wrote:
>
> Hello Katherine,
>
> On Thu, 2013-07-18 at 03:00 -0700, Katherine Yang wrote:
>
>  Hi coriander users,
>
>
> I was wondering if there was an easy way to extend the exposure time
> to much longer(more than 5 seconds)? I will be operating the camera in
> a very dark room. Please help!
>
>  Coriander cannot change the limitations of your camera. However, getting
> longer exposures can also be achieved by taking many shorter exposures.
> There's some limitations of course, but if your camera has a high bit
> depth (12 bits?) then it may be reasonable to take, say, 100~1000 images
> and then "add" the images together.
>
> This will fail if the room is so dark that the LSB does not change. Or
> that the LSB is completely lost in noise.
>
> But remember also that very long exposures on digital cameras lead to
> other forms of noise (typically similar to hot pixels). For that you may
> have to take a identical exposure with the lens cap on (no light) and
> subtract this 'dark frame reference' from your long exposure.
>
> Damien
>
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> _______________________________________________
> Coriander-user mailing list
> Cor...@li...
> https://lists.sourceforge.net/lists/listinfo/coriander-user
>
>

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <font size="+1"><font face="Console">I am  not a subscriber to this
        list.<br>
        <font size="+1">Why am<font size="+1"> I</font> getting these
          emails<font size="+1">?<br>
            <font size="+1">Would list admin please take me off the<br>
              mailing list as I am unable to do so<font size="+1"><font
                  size="+1">, </font>since<br>
                I have no idea who subscribed me and with<br>
                what password.<br>
                <br>
                <font size="+1">Thanx.<br>
                  <br>
                </font></font></font></font></font></font></font>
    <div class="moz-cite-prefix">On 07/18/2013 08:28 AM, Damien
      Douxchamps wrote:<br>
    </div>
    <blockquote cite="mid:1374157692.2308.81.camel@moe" type="cite">
      <pre wrap="">Hello Katherine,

On Thu, 2013-07-18 at 03:00 -0700, Katherine Yang wrote: 
</pre>
      <blockquote type="cite">
        <pre wrap="">Hi coriander users,


I was wondering if there was an easy way to extend the exposure time
to much longer(more than 5 seconds)? I will be operating the camera in
a very dark room. Please help!
</pre>
      </blockquote>
      <pre wrap="">
Coriander cannot change the limitations of your camera. However, getting
longer exposures can also be achieved by taking many shorter exposures.
There's some limitations of course, but if your camera has a high bit
depth (12 bits?) then it may be reasonable to take, say, 100~1000 images
and then "add" the images together.

This will fail if the room is so dark that the LSB does not change. Or
that the LSB is completely lost in noise.

But remember also that very long exposures on digital cameras lead to
other forms of noise (typically similar to hot pixels). For that you may
have to take a identical exposure with the lens cap on (no light) and
subtract this 'dark frame reference' from your long exposure.

Damien



</pre>
    </blockquote>
    <br>
  </body>
</html>

Hello Katherine,

On Thu, 2013-07-18 at 03:00 -0700, Katherine Yang wrote: 
> Hi coriander users,
> 
> 
> I was wondering if there was an easy way to extend the exposure time
> to much longer(more than 5 seconds)? I will be operating the camera in
> a very dark room. Please help!

Coriander cannot change the limitations of your camera. However, getting
longer exposures can also be achieved by taking many shorter exposures.
There's some limitations of course, but if your camera has a high bit
depth (12 bits?) then it may be reasonable to take, say, 100~1000 images
and then "add" the images together.

This will fail if the room is so dark that the LSB does not change. Or
that the LSB is completely lost in noise.

But remember also that very long exposures on digital cameras lead to
other forms of noise (typically similar to hot pixels). For that you may
have to take a identical exposure with the lens cap on (no light) and
subtract this 'dark frame reference' from your long exposure.

Damien



-- 
Damien 高原 Douxchamps   http://damien.douxchamps.net/

Hi coriander users,

I was wondering if there was an easy way to extend the exposure time to
much longer(more than 5 seconds)? I will be operating the camera in a very
dark room. Please help!

thanks