issues with latest raspistill/raspivid
Closed this issue · 19 comments
so with the new version of raspistill/vid the -t option has changed.
a -t 0 will continuously take pictures/video whereas your code is assuming
this to mean dont wait at all. Using -t 1 for a 1 millisecond wait is good enough
it seems.
also when calling setup_camera the part that checks to see if the raspivid is
working (with -t 1) returns something other then your python is expecting.
So it always thinks it fails. I just commented out the checks and all
is well.
Thanks Steve I'll check it out...
Hi Steve, I just tried this and can't find any problems...
I've updated, upgraded and dist-upgraded, I'll try downloading a new image.
This is the version I have:
root@raspberrypi:# ll /usr/bin/raspistill# ll /opt/vc/bin/raspistill
lrwxrwxrwx 1 root root 22 Sep 4 21:14 /usr/bin/raspistill -> /opt/vc/bin/raspistill*
root@raspberrypi:
-rwxr-xr-x 1 root root 45K Sep 4 21:12 /opt/vc/bin/raspistill*
what version do you have?
root@raspberrypi:~# raspistill -v -w 1920 -h 1080 -o test.jpg
raspistill Camera App v1.3.4
root@raspberrypi:~# raspistill -v
raspistill Camera App v1.2
That would explain it.
I'll grab a new image and do some testing.
Shame it doesn't update in the normal way.
Hmm according to this t 0 should still mean take the picture instantly?
http://www.raspberrypi.org/phpBB3/viewtopic.php?f=43&t=57960
Maybe theres a buggy version out there?
I'll check it anyway and add the 1ms workaround if thats what it takes, its harmless after all.
umm well that is certainly a possibility. I will followup with the raspistill people to see what they say.
thanks
steve
Hi Steve,
I just did a fresh install and an update and I still have v1.2?
I did find some GPIO security problems though due to some changes in Raspbian :(
Just released v1.9.1 to fix it...
I have created the current os image about a week ago from a fresh raspian download.
maybe it had a new version that a apt-get dist-upgrade will take you to.
But in trying the git versions of both "stable" and "devel" of raspistill/vid both still have
the issue with -t0. thought I did see mention of "the -t" problem on their forums. But
I couldnt find any git repo that had it fixed.
I downloaded 2013-09-25-wheezy-raspbian, did an apt-get update, upgrade and a dist-upgrade still had 1.2 :(
I'll see if I can get the newer one from github.
By the way is your GPIO working in BerryIO?
If its not either download the latest installer and run it or do a sudo berryio upgrade. If its still not working reboot and try again.
I havent actually tried using the gpio interface. well at least not lately.
Been doing camera stuff mostly these days.
Hi Steve, Just been looking into this and I managed to build raspistill v1.3.5 and you are right it doesn't work with berryio but even when run normally on the command line I get lots of errors. After investigation it seems the newer 1.3 versions of raspistill don't work with the current raspbian firmware which is why there are problems. I'm getting stuff like:
mmal: mmal_vc_port_parameter_set: failed to set port parameter 64:0:ENOSYS
mmal: Function not implemented
Is it possible you are running a dev version of Raspbian?
Or have you run rpi-update or something like that?
If so maybe you have some early release or something?
I have run rpi-update recently. Hopefully I didnt grab a dev raspian install.
the release files say:
PRETTY_NAME="Raspbian GNU/Linux 7 (wheezy)"
NAME="Raspbian GNU/Linux"
VERSION_ID="7"
VERSION="7 (wheezy)"
ID=raspbian
I'm not 100% sure how it works but yes I think rpi-update takes you to the dev versions. If you want to stay on the standard versions you have to use apt-get update, upgrade and dist-upgrade :(
I just did a google and found this:
http://www.raspberrypi.org/phpBB3/viewtopic.php?f=91&t=58963
That seems to imply it takes you to the bleeding edge releases.
I remember in the old days it was recommended everyone do it, but these days I don't think thats the case as the packages come through the normal channels.
huh, ok so I guess I need to forget about rpi-update from now on.
I hadnt seen that before. thanks.
so then I guess this -t0 bug wont be hit by anyone but those poor fools
that still try the occasional rpi-update :)
Well we don't know that yet, they could roll it out and we will all get it :)
Thanks for spotting it though, I'll make a note about rpi-update in the install info. Oh and you did help me out as I didn't know about the GPIO issue either until I did a fresh install to try this :p
Hi there,
is the a way (easy) to uninstall BerryIO without starting from scratch? Have it working on wheezy install. But now i need my system to be clean as possible :)
Cheers
Ralf
Hi Ralf,
Usually we recommend you restore from the backup image you made prior to installing but you can get rid of most of BerryIO with a few simple commands.
You can disable the web interface and set Apache back to default by typing:
sudo a2dissite berryio
sudo a2ensite default
sudo apache2 restart
You can disable the command line by typing:
sudo rm -f /usr/bin/berryio
At that point BerryIO wont run anymore but some of the Linux applications it uses and its files will still be on your system.
If disk space is a problem you can get rid of the BerryIO application files, log files and settings with these commands:
sudo rm -fr /usr/share/berryio
sudo rm -fr /var/log/berryio
sudo rm -fr /etc/berryio
You can remove the Linux applications installed by BerryIO as well but make sure you are not using them for anything else first!
The biggest one is probably the Apache Webserver:
sudo apt-get purge apache2
Then theres msmtp:
sudo apt-get purge msmtprc
There are lots of other little things but they are mostly harmless command line utilities.
Hope this helps...
Daniel
Thx Daniel :)