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
Bitrate Selection appears to be broken #1070
Comments
I found the v3 Pan will complain if not set to HD120. Manually set its quality to that. Not sure why it does not like the default HD180 |
Can you post the firmware version? There seems to be a bug in newer versions of the firmware where the camera isn't reporting the correct bitrate. |
Firmware and other details below. Thanks for checking. Also posted logs #1037 as been much less stable since adding this camera. |
Mine are all on 4.50.4.7252 as well. Also uncertain why the one requires a different bitrate than the other two since the only difference between the three is the drive cam is further out from wifi. |
Thanks for the feedback. can someone try the dev branch to see if the bitrate is updating? |
Forced homeassistant addon to use dev image: I forced bitrate to 180 and removed bitrate override and no bitrate errors either way! Thanks. A few of my cameras are taking their time coming up and saw some new error messages, but the bitrate on the v3Cam seems fixed. I did see one bitrate error on another camera, but it fixed itself. Not sure why my cameras are not stable. I'll let it sit for a few hours. [video] super slow [WyzeBridge] ❌ '/side-door' stream is down [garage] [CONTROL] ERROR - error=AssertionError('Please call _connect() first!'), cmd='_bitrate' |
Thanks! Some of those errors are related to the sync changes in the dev branch. |
* Drop late audio frames to keep sync #388 * show running architecture * Don't log failed tutk if stream is down #990 * Use valid FPS for sleep #388 * Refactor * Adjust sleep_interval #388 * Increase sleep time between frames #388 * Set larger buf size #388 * add SLEEP_INTERVAL_FPS #388 * Adjust sleep interval #388 * use genpts #388 * avoid conflicting names with errno module * refactor _audio_frame_slow * LOW_LATENCY mode * show github SHA on dev build * substream support and more refactoring #388 * div tag for jittery video in Firefox #1025 * Re-encoding audio for WebRTC/MTX * reduce sleep time for audio thread #388 * Target firefox for jittery video fix in css #1025 * Use K10050GetVideoParam for FW 4.50.4.x #1070 * Use K10006 for newer doorbell #742 and refactor * Reduce audio pipe flushing #388 * show gap when audio out of sync #388 * don't include ARCH in version * Update iotc.py * reset frame_ts on clock sync * update auth api * Restructure and cleanup * remove unneeded files * update path * Forget alarm/siren state #953 #1051 * use addon_config for Home Assistant * Additional refactoring to auth api * don't skip keyframes #388 * Update ffmpeg.py * delay audio when ahead #388 * format iotc logging so we know what cam is late * drop late video frame and speed up audio #388 * Add Floodlight V2 * Set default sample rate for all cams * Delay audio by 1 second if ahead of video #388 * tweak ffmpeg buffer #388 * Retain MQTT Discovery Message #920 * Update change log Special thanks to @carlosnasillo!
@mrlt8 For example if i run with no bitrate set at all then set SD30. it will request 180 bitrate (the default I guess) and give this error:
If I run HD60 then SD30:
If i run HD120 then SD30:
Actually hmm some further testing shows that even HD60 to SD30 can result in 120 so I guess it's not even consistent.
Seems like SD30 is broken? This is on a WyzeCam V3 running firmware: 4.36.9.139 Also can SD also use higher bitrates then 30? Such as SD40? for possibly higher quality 360p? |
Apparently I forgot to comment on this again. The update did fix the issues I was having originally. |
So no matter what bitrate I select using the environment options for Docker it seems the cameras just send the bitrate they want.
I was trying to match the cameras to the SD option in the app which the Wiki says is HD60. However setting the cameras to anything other than 200 or 180 for bitrate respectively always throws the following errors. They even occur when the app is closed so it isn't like the app is requesting a different bitrate that is somehow overriding it.
Edit: All 3 are v3 Pan Camd
The text was updated successfully, but these errors were encountered: