Skip to content
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

ver 2.9.0 - error when using quality > 255 #1185

Closed
Anc0dia opened this issue May 12, 2024 · 2 comments · Fixed by #1192
Closed

ver 2.9.0 - error when using quality > 255 #1185

Anc0dia opened this issue May 12, 2024 · 2 comments · Fixed by #1192

Comments

@Anc0dia
Copy link

Anc0dia commented May 12, 2024

With version 2.9.0 does the higher bitrate setting work with the Wyze firmware for v3/v3 pro? Anything above 255 gives me an error :

here I tried HD10000:

[WyzeBridge] 🎬 3 streams enabled
[WyzeBridge] 🎉 Connecting to WyzeCam V3 - back on 192.168.200.105
[WyzeBridge] 🎉 Connecting to WyzeCam V3 Pro - front2k on 192.168.200.107
[front2k] 📡 Getting 10000kb/s 2K stream (H264/20fps) via LAN mode (WiFi: 61%) FW: 4.58.11.8391 🔒
[front2k] WARNING: Skipping wrong frame_size at start of stream [frame_size=1]
[WyzeBridge] ✅ '/front2k stream is UP! (3/3)
[back] 📡 Getting 10000kb/s HD stream (H264/20fps) via LAN mode (WiFi: 92%) FW: 4.36.11.8391 🔒
[WyzeBridge] 🎉 Connecting to WyzeCam V3 - side on 192.168.200.106
[back] WARNING: Skipping wrong frame_size at start of stream [frame_size=1]
[WyzeBridge] ✅ '/back stream is UP! (3/3)
[side] 📡 Getting 10000kb/s HD stream (H264/20fps) via LAN mode (WiFi: 97%) FW: 4.36.11.8391 🔒
[side] WARNING: Skipping wrong frame_size at start of stream [frame_size=1]
[WyzeBridge] ✅ '/side stream is UP! (3/3)
[back] bitrate=16 does not match 10000
[back] Requesting frame_size=0, bitrate=10000, fps=0
[front2k] bitrate=16 does not match 10000
[front2k] Requesting frame_size=3, bitrate=10000, fps=0
[side] bitrate=16 does not match 10000
[side] Requesting frame_size=0, bitrate=10000, fps=0

mrlt8 added a commit that referenced this issue May 12, 2024
@mrlt8
Copy link
Owner

mrlt8 commented May 12, 2024

whoops, can you try the dev branch?

@Anc0dia
Copy link
Author

Anc0dia commented May 12, 2024

that fixed it. I also get the correct bitrate when I check via the API:

http://192.168.200.15:5001/api/front2k/bitrate

{"command":"bitrate","payload":null,"response":10000,"status":"success","value":10000}

@mrlt8 mrlt8 linked a pull request May 13, 2024 that will close this issue
mrlt8 added a commit that referenced this issue May 13, 2024
* unpack k10050 response #1185

* add back bitrate check for HL_CFL2 #1112

* Ignore api request value and add api header #1189

* changelog
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants