-
Notifications
You must be signed in to change notification settings - Fork 139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Picture quality pi zero #4
Comments
I have ssh into pi zero w and pasted this command. |
What kind output do you get on that command:
and can you explain me what it does? |
I'm seeing this on my Pi Zero too. The Cam works fine, but the quality is not as good as in the screens on the website. |
i checked the logfile from hkcam, and there i see that the video resolution ist set to 1024*768 perhaps there is the problem:
the cam module should provide 1080p video |
HomeKit decides which resolution is used to stream the video. The HomeKit Accessory Protocol supports up- and downgrading the video resolution on the fly. This functionality is currently not implemented. Not sure if that is even possible with ffmpeg! |
That is good to know, but why is it so blurry on my setup and your screenshots are in good quality. |
Mainly because those screenshots are not taken directly from the camera – they are mockups. But the snapshots, which are shown in the HomeKit apps, are way higher quality than the video stream. |
thanks for the feedback |
Running this on startup increases the image quality for me:
|
You are a star bro! The video feed is still a little grainy but it has a lot less latency. Well done it’s much closer to the pi zero default video output viewed in browser. |
I've just pushed 48e4dbc which offers a new command line argument for specifying the minimum video bitrate. This argument in combination with specifying the video size via v4l2-ctl should significantly improve the video quality. You can set the video size to 720p and the bit rate to 800kbps by updating the run script #!/bin/sh -e
exec 2>&1
v4l2-ctl --set-fmt-video=width=1280,height=720,pixelformat=YU12
exec hkcam --min_video_bitrate=800 --data_dir=/var/lib/hkcam/data --verbose=true Then restart the service via Note: Once you specify a minimum bit rate, the streaming to Apple Watch might not work anymore. The Apple Watch wants to have a much lower bit rate. |
I changed the run but I get the following message in log
|
ok, can I build it directly on PI? |
Yes |
mmmm, for me it does not work...:-(
I did it like here described: Update from source You can also compile the binary yourself. These steps require Git and Go to be installed. On macOS you can install it via Homebrew. brew install git |
just apply 48e4dbc and it works perfect 🥇 . Video quality and responsiveness improved a lot 👍 . From the current log file these messages show up, not sure if that's okay? #14 still remains an issue... I guess you @brutella made a note of that ;)
|
Can u explain me how did u do it? |
The wiki tells you more about updating hkcam from source. |
I run hkcam version 0.0.8. When I change the file run in /etc/sv/hkcam/ the camera does not respond in the Home App. When set to default again the camera works again in the Home App. |
@RobPijpers Do you see an error message in the log file when you try to start a stream from your iOS device with the update |
@brutella Maybe this is the problem: Below the content of my run file: I used the image from this link https://github.com/brutella/hkcam/releases/download/v0.0.8/raspbian-stretch-lite-2019-04-08-hkcam-v0.0.8-armv6.img.zip |
The |
@brutella Please post a reply if v0.0.9 is available, thanks! |
v0.0.9 is now available. |
Your camera seems to be out of focus. Try to change the focus. |
@hindsc52 please post your run file here. |
I have moved this to a new issue as to not clutter up this one, as others have suggested this is a focus issue. Will post my run in on the nw issue. |
Hello first off brilliant bit of code. Do you have recommended settings for the pi zero? The picture quality is very grainy and slow fps. Thanks
The text was updated successfully, but these errors were encountered: