home.social

#picamera — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #picamera, aggregated by home.social.

  1. Spent all day trying to get #libcamera to produce a good quality video stream using #MediaMTX under IR light. In the end I've gone back to RPi Cam Control using #picamera
    The quality was awful, and no matter how much I fiddled with the mediamtx.yml it didn't improve.
    Back to #Raspbian #Buster #raspberrypi

  2. Spent all day trying to get #libcamera to produce a good quality video stream using #MediaMTX under IR light. In the end I've gone back to RPi Cam Control using #picamera
    The quality was awful, and no matter how much I fiddled with the mediamtx.yml it didn't improve.
    Back to #Raspbian #Buster #raspberrypi

  3. Spent all day trying to get #libcamera to produce a good quality video stream using #MediaMTX under IR light. In the end I've gone back to RPi Cam Control using #picamera
    The quality was awful, and no matter how much I fiddled with the mediamtx.yml it didn't improve.
    Back to #Raspbian #Buster #raspberrypi

  4. Spent all day trying to get #libcamera to produce a good quality video stream using #MediaMTX under IR light. In the end I've gone back to RPi Cam Control using #picamera
    The quality was awful, and no matter how much I fiddled with the mediamtx.yml it didn't improve.
    Back to #Raspbian #Buster #raspberrypi

  5. Spent all day trying to get #libcamera to produce a good quality video stream using #MediaMTX under IR light. In the end I've gone back to RPi Cam Control using #picamera
    The quality was awful, and no matter how much I fiddled with the mediamtx.yml it didn't improve.
    Back to #Raspbian #Buster #raspberrypi

  6. I think that @Raspberry_Pi has got a #PiCamera problem.

    PiCameras are amazing pieces of hardware with a software that could probably be managed better.

    The original PiCamera libraries haven’t seen a commit in 4 years, as they were deprecated with the Bullseye release. I can still run some code that uses that library on some old #RaspberryPi just because I’m keeping them on some ancient version of Raspbian. Otherwise, raspistill and friends break in many possible ways both on both Bullseye and Bookworm, and the package doesn’t even install on Arch ARM because raspberrypi-firmware is now gone.

    A couple of years down the line, and its replacement, PiCamera2, is still in beta. It can be installed through a relatively smooth process only on the last two versions of RPi OS via apt, and it’s otherwise very hard to get installed on any other distro - on Arch it depends on packages that officially aren’t even available for ARM (like python-av), when installed via pip it tries to build the world even if some packages (like numpy) are already installed on the system, and I didn’t manage to get it to run on Ubuntu because of permission issues.

    It’s really a pity because a vibrant ecosystem of camera apps and scripts had been written using the old version of PiCamera, which could do a lot of things with very low entry barriers. Then a sudden deprecation was announced without a viable alternative, and a couple of years down the line that alternative isn’t quite stable yet. I’ve eventually resorted to leverage the native v4l2 integration over ffmpeg as a cross-platform workaround, but that moves most of the burden to the CPU and I’m not really leveraging this hardware at its best, plus it probably raises the technical bar for a lot of hobbyist makers.

    Why was something so important to many users deprecated without any stable alternative on the horizon?

  7. I think that @Raspberry_Pi has got a #PiCamera problem.

    PiCameras are amazing pieces of hardware with a software that could probably be managed better.

    The original PiCamera libraries haven’t seen a commit in 4 years, as they were deprecated with the Bullseye release. I can still run some code that uses that library on some old #RaspberryPi just because I’m keeping them on some ancient version of Raspbian. Otherwise, raspistill and friends break in many possible ways both on both Bullseye and Bookworm, and the package doesn’t even install on Arch ARM because raspberrypi-firmware is now gone.

    A couple of years down the line, and its replacement, PiCamera2, is still in beta. It can be installed through a relatively smooth process only on the last two versions of RPi OS via apt, and it’s otherwise very hard to get installed on any other distro - on Arch it depends on packages that officially aren’t even available for ARM (like python-av), when installed via pip it tries to build the world even if some packages (like numpy) are already installed on the system, and I didn’t manage to get it to run on Ubuntu because of permission issues.

    It’s really a pity because a vibrant ecosystem of camera apps and scripts had been written using the old version of PiCamera, which could do a lot of things with very low entry barriers. Then a sudden deprecation was announced without a viable alternative, and a couple of years down the line that alternative isn’t quite stable yet. I’ve eventually resorted to leverage the native v4l2 integration over ffmpeg as a cross-platform workaround, but that moves most of the burden to the CPU and I’m not really leveraging this hardware at its best, plus it probably raises the technical bar for a lot of hobbyist makers.

    Why was something so important to many users deprecated without any stable alternative on the horizon?

  8. I think that @Raspberry_Pi has got a #PiCamera problem.

    PiCameras are amazing pieces of hardware with a software that could probably be managed better.

    The original PiCamera libraries haven’t seen a commit in 4 years, as they were deprecated with the Bullseye release. I can still run some code that uses that library on some old #RaspberryPi just because I’m keeping them on some ancient version of Raspbian. Otherwise, raspistill and friends break in many possible ways both on both Bullseye and Bookworm, and the package doesn’t even install on Arch ARM because raspberrypi-firmware is now gone.

    A couple of years down the line, and its replacement, PiCamera2, is still in beta. It can be installed through a relatively smooth process only on the last two versions of RPi OS via apt, and it’s otherwise very hard to get installed on any other distro - on Arch it depends on packages that officially aren’t even available for ARM (like python-av), when installed via pip it tries to build the world even if some packages (like numpy) are already installed on the system, and I didn’t manage to get it to run on Ubuntu because of permission issues.

    It’s really a pity because a vibrant ecosystem of camera apps and scripts had been written using the old version of PiCamera, which could do a lot of things with very low entry barriers. Then a sudden deprecation was announced without a viable alternative, and a couple of years down the line that alternative isn’t quite stable yet. I’ve eventually resorted to leverage the native v4l2 integration over ffmpeg as a cross-platform workaround, but that moves most of the burden to the CPU and I’m not really leveraging this hardware at its best, plus it probably raises the technical bar for a lot of hobbyist makers.

    Why was something so important to many users deprecated without any stable alternative on the horizon?

  9. I think that @Raspberry_Pi has got a #PiCamera problem.

    PiCameras are amazing pieces of hardware with a software that could probably be managed better.

    The original PiCamera libraries haven’t seen a commit in 4 years, as they were deprecated with the Bullseye release. I can still run some code that uses that library on some old #RaspberryPi just because I’m keeping them on some ancient version of Raspbian. Otherwise, raspistill and friends break in many possible ways both on both Bullseye and Bookworm, and the package doesn’t even install on Arch ARM because raspberrypi-firmware is now gone.

    A couple of years down the line, and its replacement, PiCamera2, is still in beta. It can be installed through a relatively smooth process only on the last two versions of RPi OS via apt, and it’s otherwise very hard to get installed on any other distro - on Arch it depends on packages that officially aren’t even available for ARM (like python-av), when installed via pip it tries to build the world even if some packages (like numpy) are already installed on the system, and I didn’t manage to get it to run on Ubuntu because of permission issues.

    It’s really a pity because a vibrant ecosystem of camera apps and scripts had been written using the old version of PiCamera, which could do a lot of things with very low entry barriers. Then a sudden deprecation was announced without a viable alternative, and a couple of years down the line that alternative isn’t quite stable yet. I’ve eventually resorted to leverage the native v4l2 integration over ffmpeg as a cross-platform workaround, but that moves most of the burden to the CPU and I’m not really leveraging this hardware at its best, plus it probably raises the technical bar for a lot of hobbyist makers.

    Why was something so important to many users deprecated without any stable alternative on the horizon?

  10. I think that @Raspberry_Pi has got a #PiCamera problem.

    PiCameras are amazing pieces of hardware with a software that could probably be managed better.

    The original PiCamera libraries haven’t seen a commit in 4 years, as they were deprecated with the Bullseye release. I can still run some code that uses that library on some old #RaspberryPi just because I’m keeping them on some ancient version of Raspbian. Otherwise, raspistill and friends break in many possible ways both on both Bullseye and Bookworm, and the package doesn’t even install on Arch ARM because raspberrypi-firmware is now gone.

    A couple of years down the line, and its replacement, PiCamera2, is still in beta. It can be installed through a relatively smooth process only on the last two versions of RPi OS via apt, and it’s otherwise very hard to get installed on any other distro - on Arch it depends on packages that officially aren’t even available for ARM (like python-av), when installed via pip it tries to build the world even if some packages (like numpy) are already installed on the system, and I didn’t manage to get it to run on Ubuntu because of permission issues.

    It’s really a pity because a vibrant ecosystem of camera apps and scripts had been written using the old version of PiCamera, which could do a lot of things with very low entry barriers. Then a sudden deprecation was announced without a viable alternative, and a couple of years down the line that alternative isn’t quite stable yet. I’ve eventually resorted to leverage the native v4l2 integration over ffmpeg as a cross-platform workaround, but that moves most of the burden to the CPU and I’m not really leveraging this hardware at its best, plus it probably raises the technical bar for a lot of hobbyist makers.

    Why was something so important to many users deprecated without any stable alternative on the horizon?

  11. I'm an eager #RaspberryPi shopper. Each time a new module is released, I get my hands on it. Which gave me a unique opportunity to compare all Raspberry Pi camera modules together:
    #PiCamera #RaspberryPiCamera #net_r
    notenoughtech.com/raspberry-pi

  12. I'm an eager #RaspberryPi shopper. Each time a new module is released, I get my hands on it. Which gave me a unique opportunity to compare all Raspberry Pi camera modules together:
    #PiCamera #RaspberryPiCamera #net_r
    notenoughtech.com/raspberry-pi

  13. I'm an eager #RaspberryPi shopper. Each time a new module is released, I get my hands on it. Which gave me a unique opportunity to compare all Raspberry Pi camera modules together:
    #PiCamera #RaspberryPiCamera #net_r
    notenoughtech.com/raspberry-pi

  14. I'm an eager #RaspberryPi shopper. Each time a new module is released, I get my hands on it. Which gave me a unique opportunity to compare all Raspberry Pi camera modules together:
    #PiCamera #RaspberryPiCamera #net_r
    notenoughtech.com/raspberry-pi

  15. I'm an eager #RaspberryPi shopper. Each time a new module is released, I get my hands on it. Which gave me a unique opportunity to compare all Raspberry Pi camera modules together:
    #PiCamera #RaspberryPiCamera #net_r
    notenoughtech.com/raspberry-pi

  16. Found an old #raspberrypi 1 b+ in a forgotten box last night. Its a bit old now (9+ years I think) and probably underpowered these days but I have a handful of #picamera sitting doing nothing so thought I'd set one up above my desk where i do my painting, tinkering and #making stuff and perhaps record some Timelapses.
    I've not written the python for it yet, will do that tonight. Thinking I can connect it to a toggle switch to start and stop the timelapse recording. pic on monitor is the output.

  17. Found an old #raspberrypi 1 b+ in a forgotten box last night. Its a bit old now (9+ years I think) and probably underpowered these days but I have a handful of #picamera sitting doing nothing so thought I'd set one up above my desk where i do my painting, tinkering and #making stuff and perhaps record some Timelapses.
    I've not written the python for it yet, will do that tonight. Thinking I can connect it to a toggle switch to start and stop the timelapse recording. pic on monitor is the output.

  18. Found an old #raspberrypi 1 b+ in a forgotten box last night. Its a bit old now (9+ years I think) and probably underpowered these days but I have a handful of #picamera sitting doing nothing so thought I'd set one up above my desk where i do my painting, tinkering and #making stuff and perhaps record some Timelapses.
    I've not written the python for it yet, will do that tonight. Thinking I can connect it to a toggle switch to start and stop the timelapse recording. pic on monitor is the output.

  19. Found an old #raspberrypi 1 b+ in a forgotten box last night. Its a bit old now (9+ years I think) and probably underpowered these days but I have a handful of #picamera sitting doing nothing so thought I'd set one up above my desk where i do my painting, tinkering and #making stuff and perhaps record some Timelapses.
    I've not written the python for it yet, will do that tonight. Thinking I can connect it to a toggle switch to start and stop the timelapse recording. pic on monitor is the output.

  20. Found an old #raspberrypi 1 b+ in a forgotten box last night. Its a bit old now (9+ years I think) and probably underpowered these days but I have a handful of #picamera sitting doing nothing so thought I'd set one up above my desk where i do my painting, tinkering and #making stuff and perhaps record some Timelapses.
    I've not written the python for it yet, will do that tonight. Thinking I can connect it to a toggle switch to start and stop the timelapse recording. pic on monitor is the output.

  21. I just did a quick evaluation of the new raspberrypi camera 3.

    I use it like an embedded camera to monitor my 3dprinting process in detail.

    The capacities of this little beast are really impressive !

    The autofocus is fast to follow this hardware process !😂😄