New version of Raspistill

[karlkiste]

So in the control shot when you have pixel that should be gray (127,127,127) but has the values 127,157,127 you enter into the table a value of 0,-30,0 ?

My first idea wouldn't be 0,-30,0 but 1,0.8,1 . Anyone know if it really must be added, not multiplied?

[gordon77]

Thanks Jamesh,

After doing update, upgrade, rpi-update and built the latest raspistill it seems to be working and I can set the exposure time

It's all been a great learning exercise as well.

Gordon77

[jamesh]

So in the control shot when you have pixel that should be gray (127,127,127) but has the values 127,157,127 you enter into the table a value of 0,-30,0 ?

My first idea wouldn't be 0,-30,0 but 1,0.8,1 . Anyone know if it really must be added, not multiplied?

Correct, it's a scale factor not an offset that is required.

[jamesh]

Just pushed a bug fix release to my github in the bug_fixes branch if people want to give it a go.

[SnowLeopard]

(Same reply about bugfixes as I put in the timeout 0 thread).

• 25 mbit/s fix: works. Using a higher value lowers it to 25mbit. Although I would have expected exiting with an error about using a value out of range (or at least a stderr warning). I fully expect someone to get confused by requesting >25mbit and not being warned the value is out of range, and not understanding why videos never have higher bw. The only way you see the value is overridden is running with '-v'
• shutter speed: works. raspistill -n -v -tl 500 -ex sports -ss 1000 -o shut1000-%d.jpg gave 6 images with same exif exposure time and look all the same to the eye
• timeout: does not work. raspivid exits gracefully after 10 seconds when "-t 0" is used. Changing the vcos_sleep(10000) to 5000 at line 1156 makes it exit after 5 seconds. Not sure what the fix is.

[jamesh]

Sorry. I'll quickly fix that one. My test must have been less than 10s so I didn't see it drop out by itself, although I thought I left it longer than that

As for clipping parameters - I made a conscious decision to force parameters to be in range rather than exit or display an error. Whether that's right or not, I don't know, but that's the current status.

[jamesh]

OK, can you try that again - I think the -t option should work OK now.

I also noticed some print's that were being done outside of verbose mode so also fixed those.

[SnowLeopard]

As for clipping parameters - I made a conscious decision to force parameters to be in range rather than exit or display an error. Whether that's right or not, I don't know, but that's the current status.

Fair enough. Maybe make a note of this in the README?
Does this explain why using -ISO won't set any value beyond 100-800, but using -ex sports can result in the exif data showing ISO as high as 1600?

[jamesh]

As for clipping parameters - I made a conscious decision to force parameters to be in range rather than exit or display an error. Whether that's right or not, I don't know, but that's the current status.

Fair enough. Maybe make a note of this in the README?
Does this explain why using -ISO won't set any value beyond 100-800, but using -ex sports can result in the exif data showing ISO as high as 1600?

Well, you are the only person to comment on it so far... so not sure it's that in need of documentation!

Actually the ISO thing is different. And tbh I'm not sure what's going on there. Anything over 800 is rejected, but internally, the algorithms used in working out gains, shutter times etc obviously don't have the same limitation, but I don;t know why. Although 1600 ISO will be pushing the gain up so high the noise will be pretty bad.

If I have time, I see if I can see why we limit to 800 for external setting (although I think the Nokia 808 allowed 1600, but that is a much better sensor)

[jbeale]

Well, you are the only person to comment on it so far... so not sure it's that in need of documentation!

If we're taking a vote... silent clamping to 25 Mbps is understandable although a warning would be nice. I appreciate hardware encoders always have some maximum supported parameter values, like bitrate, but I would expect the limits to be written down somewhere.

Seems like '-ex sports' is what you want for security applications no matter how bad the noise. The long shutter speeds of '-ex night' make the fixed background look nice, bright and clean but the moving objects pretty shadowy! For example http://www.raspberrypi.org/phpBB3/viewt ... 43&t=58999

[jamesh]

OK, I succumb, I'll update the docs with the parameter ranges!

[mrtamer]

Instead of cloning my repo, clone the raspberry pi one, then checkout the master branch.

Code: Select all

git clone https://github.com/raspberrypi/userland.git
cd userland
git checkout master
./buildme

I did this yesterday to try out the -ss option, and it works as described but unfortunately noticed that the -ex verylong parameter to raspistill now seems to crash the raspistill. If aborting with ctrl+c a reboot is required to have any output from the camera with raspistill after the crash. I used the below code to produce this issue.

Code: Select all

raspistill -w 1024 -h 724 -o pic.jpg -ex verylong

[poing]

That's only if the shutterspeed is longer than 1/3s. Jamesh knows this and it's on the list.

[uherm]

special thanks to jamesh,
the -ss option is so useful!
Keep going.

[nrother]

Just noticed, that you included a mode to wait for a USR1 signal great! Maybe there comes a little inspiration from my

Code: Select all

raspifastcamd

? (From this thread: http://www.raspberrypi.org/phpBB3/viewt ... 43&t=50075)

While reading through your code, I noticed, that you use sigwait to wait for a signal. This only accepts signal, when waiting explicitly for them, if I understand it correctly. I used a semaphore that is posted when a SIGUSR1 arrives, this allows signals to arrive, even when a picture this taken. But this period is really short, so not a big deal (And I just didn't knew about sigwait, when I wrote my code...)

The GPIO-mode in the code sound like a cool idea, too!

[jamesh]

Just noticed, that you included a mode to wait for a USR1 signal great! Maybe there comes a little inspiration from my

Code: Select all

raspifastcamd

? (From this thread: http://www.raspberrypi.org/phpBB3/viewt ... 43&t=50075)

While reading through your code, I noticed, that you use sigwait to wait for a signal. This only accepts signal, when waiting explicitly for them, if I understand it correctly. I used a semaphore that is posted when a SIGUSR1 arrives, this allows signals to arrive, even when a picture this taken. But this period is really short, so not a big deal (And I just didn't knew about sigwait, when I wrote my code...)

The GPIO-mode in the code sound like a cool idea, too!

This was the first code I've used signals in - so I could equally be wrong in my usage.

[rmsalinas]

Hi,

I am trying to set shutter speed in video, but it does not work. Does anyone has any idea how to do it?

Regards

[jamesh]

Hi,

I am trying to set shutter speed in video, but it does not work. Does anyone has any idea how to do it?

Regards

Video puts limits on shutter speed depending on requested frame rate. For examples, 30fps you cannot have a shutter longer than 33ms, otherwise you cannot get to 30fps.

[rmsalinas]

Yes, well... the problem is that the option shutter speed is not even working at all with raspivid

[Ercdraper]

I am building a cosmic ray detector using the camera. These needs exposure times as longs as possible. I've got the -ss to run with raspistill at about 1/3 second any longer than that and the system hangs
I need to get exposure times out to several seconds or even minutes. I know from previous work that 20 minutes would be great
Any suggestions how I can get out to those slow shutter speeds?

[gordon77]

I am building a cosmic ray detector using the camera. These needs exposure times as longs as possible. I've got the -ss to run with raspistill at about 1/3 second any longer than that and the system hangs
I need to get exposure times out to several seconds or even minutes. I know from previous work that 20 minutes would be great
Any suggestions how I can get out to those slow shutter speeds?

At the moment l dont think you can, the 1/3 sec limit is a known issue/bug.

[pelrun]

Take multiple short-exposure images in raw mode and then stack them?

[jbeale]

I need to get exposure times out to several seconds or even minutes. I know from previous work that 20 minutes would be great

Was your previous work with this particular sensor chip? the optimum time is sensor-dependent... on this sensor (not designed for long exposures) I suspect 20 minutes would always give you full-white due to accumulated dark current. At any rate the existing firmware control is limited to 1/3 sec.

[Amarand]

Hope it's not bad form to post/query in an older post however, I've noticed that the version of raspistill I have lacks the -tl option:

Code: Select all

/opt/vc/bin/raspistill
raspistill Camera App v1.3.8

sudo /opt/vc/bin/raspistill --timelapse 30 -o file%d.jpg
Invalid command line option (--timelapse)

sudo /usr/bin/raspistill  -tl 30 -o file%d.jpg
Invalid command line option (-tl)

I would have imagined that this feature would have been wrapped up in the latest distribution by now, a year and a half later?

I've run:

• apt-get update
  apt-get upgrade -y
  apt-get install git-core -y
  wget http://goo.gl/1BOfJ -O /usr/bin/rpi-update
  chmod +x /usr/bin/rpi-update
  rpi-update
  raspi-config to enable camera, and set the graphics split to 128
  rebooted numerous times

Am I missing something?

I installed Raspbian from the latest NOOBS to get the latest clean distribution.

Thanks!

[DougieLawson]

If you're on a regular Raspbian installation then rpi-update should have got you to V1.3.12 of raspivid

The version /usr/bin/raspivid should be a symbolic link to /opt/vc/bin/raspivid

Code: Select all

[email protected] /usr/bin # ls -la raspi*
-rwxr-xr-x 1 root root 29575 Jan 31 20:15 raspi-config
lrwxrwxrwx 1 root root    22 Mar 30 11:53 raspistill -> /opt/vc/bin/raspistill
lrwxrwxrwx 1 root root    20 Mar 30 11:53 raspivid -> /opt/vc/bin/raspivid
lrwxrwxrwx 1 root root    20 Mar 30 11:53 raspiyuv -> /opt/vc/bin/raspiyuv
[email protected] /usr/bin #