Wrong FPS for recordings [v2.8.x] #1159
Comments
|
Looking into this. If you don't mind, can you post a short clip so I can inspect the FPS in the recording? |
voortuin_20240423_21_30_00.-.Trim.mp4achtertuin_20240424_16_30_01.-.Trim.mp4 |
|
It is not every clip, just a few. |
|
Hmm, does this only happen when audio is enabled? If so, can you try Another option would be to set the FPS to - FFMPEG_CMD=ffmpeg -hide_banner -loglevel info -fflags +flush_packets+nobuffer+genpts -flags +low_delay -thread_queue_size 8 -analyzeduration 32 -probesize 32 -f H264 -r 20 -i pipe:0 -map 0:v -c:v copy -max_muxing_queue_size 1 -max_delay 0.1 -rtbufsize 32 -f tee [use_fifo=1:fifo_options=attempt_recovery=1\\:drop_pkts_on_overflow=1:f=rtsp:rtsp_transport=tcp]rtsp://0.0.0.0:8554/{cam_name}|[onfail=ignore:f=segment:segment_time=60:segment_atclocktime=1:segment_format=mp4:reset_timestamps=1:strftime=1:use_fifo=1]/Record/{cam_name}/{cam_name}_%Y%m%d_%H_%M_%S.mp4 |
i have no audio. My docker-compose: |
|
videoParm { "bitRate": "30", "fps": "20", "horizontalFlip": "1", "logo": "1", "resolution": "2", "time": "1", "type": "H264", "verticalFlip": "1" } |
|
http://j-mulderij.nl:5000/api/voortuin/fps
|
-- | --
command | "fps"
payload | "1,2,3,4,5,6,7,21,22,27,50"
response | 20
status | "success"
value | 20
============================ command | "fps" -- | -- payload | "1,2,3,4,5,6,7,21,22,27,50" response | 20 status | "success" value | 20 |
|
The last few day's there seems no problems at all ... |
|
I closed this to early. Long time ago, i remember an ffmpeg command, to record (So day/night time was no issue) Am i the only one with this issue? |
|
Can you try the ffmpeg command I posted? |
This one? I'll try! |
|
|
can you try: |
`🚀 DOCKER-WYZE-BRIDGE v2.8.3 ARMV7L [WyzeBridge] ♻️ Clearing local cache... [WyzeBridge] Configuring LL-HLS [WyzeBridge] 🔍 Could not find local cache for 'auth' [WyzeBridge] ☁️ Fetching 'auth' from the Wyze API...
[WyzeBridge] WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
[WyzeBridge] Press CTRL+C to quit [WyzeBridge] 💾 Saving 'auth' to local cache... [WyzeBridge] 🔍 Could not find local cache for 'user' [WyzeBridge] ☁️ Fetching 'user' from the Wyze API... [WyzeBridge] 💾 Saving 'user' to local cache... [WyzeBridge] 🔍 Could not find local cache for 'cameras' [WyzeBridge] ☁️ Fetching 'cameras' from the Wyze API... [WyzeBridge] [API] Fetched [2] cameras [WyzeBridge] 💾 Saving 'cameras' to local cache... [WyzeBridge] [+] Adding Voortuin [HL_CAM3P] [WyzeBridge] [+] Adding Achtertuin [HL_CAM3P] [WyzeBridge] starting MediaMTX 1.1.1 [WyzeBridge] 🎬 2 streams enabled [WyzeBridge] 🎉 Connecting to WyzeCam V3 Pro - Voortuin on 192.168.178.70 [WyzeBridge] 🎉 Connecting to WyzeCam V3 Pro - Achtertuin on 192.168.178.69 [achtertuin] 📡 Getting 180kb/s 2K stream (H264/10fps) via LAN mode (WiFi: 70%) FW: 4.58.12.9751 🔒 [voortuin] 📡 Getting 180kb/s 2K stream (H264/10fps) via LAN mode (WiFi: 44%) FW: 4.58.12.9751 🔒 [voortuin] WARNING: Skipping wrong frame_size at start of stream [frame_size=1] [achtertuin] WARNING: Skipping wrong frame_size at start of stream [frame_size=1] [h264 @ 0xb6f6ce20] Stream #0: not enough frames to estimate rate; consider increasing probesize Input #0, h264, from 'pipe:0': Duration: N/A, bitrate: N/A Stream #0:0: Video: h264 (High), yuv420p(tv, bt709, progressive), 2560x1440, 10 tbr, 1200k tbn Output #0, tee, to '[use_fifo=1:fifo_options=attempt_recovery=1\:drop_pkts_on_overflow=1:f=rtsp:rtsp_transport=tcp]rtsp://0.0.0.0:8554/voortuin|[onfail=ignore:f=segment:segment_time=60:segment_atclocktime=1:segment_format=mp4:reset_timestamps=1:strftime=1:use_fifo=1]/Record/voortuin/voortuin_%Y%m%d_%H_%M_%S.mp4': Metadata: Stream #0:0: Video: h264 (High), yuv420p(tv, bt709, progressive), 2560x1440, q=2-31, 10 tbr, 20 tbn Stream mapping: Stream #0:0 -> #0:0 (copy) [segment @ 0xb6e8f230] Opening '/Record/voortuin/voortuin_20240503_00_20_28.mp4' for writing [segment @ 0xb6e8f230] Failed to open segment '/Record/voortuin/voortuin_20240503_00_20_28.mp4' [WyzeBridge] ✅ '/voortuin stream is UP! (3/3) frame= 0 fps=0.0 q=-1.0 size= 0kB time=-577014:32:22.77 bitrate= -0.0kbits/s speed=N/A Input #0, h264, from 'pipe:0': Duration: N/A, bitrate: N/A Stream #0:0: Video: h264 (High), yuv420p(tv, bt709, progressive), 2560x1440, 10 tbr, 1200k tbn Output #0, tee, to '[use_fifo=1:fifo_options=attempt_recovery=1\:drop_pkts_on_overflow=1:f=rtsp:rtsp_transport=tcp]rtsp://0.0.0.0:8554/achtertuin|[onfail=ignore:f=segment:segment_time=60:segment_atclocktime=1:segment_format=mp4:reset_timestamps=1:strftime=1:use_fifo=1]/Record/achtertuin/achtertuin_%Y%m%d_%H_%M_%S.mp4': Metadata: Stream #0:0: Video: h264 (High), yuv420p(tv, bt709, progressive), 2560x1440, q=2-31, 10 tbr, 20 tbn [segment @ 0xb6ec9220] Opening '/Record/achtertuin/achtertuin_20240503_00_20_29.mp4' for writing Stream mapping: Stream #0:0 -> #0:0Failed to open segment '/Record/achtertuin/achtertuin_20240503_00_20_29.mp4' (copy) [WyzeBridge] ✅ '/achtertuin stream is UP! (3/3) frame= 0 fps=0.0 q=-1.0 size= 0kB time=-577014:32:22.77 bitrate= -0.0kbits/s speed=N/A [tee @ 0xb6e9b220] Slave muxer #1 failed: No such file or directory, continuing with 1/2 slaves. frame= 3 fps=1.8 q=-1.0 size=N/A time=00:00:01.10 bitrate=N/A speed=0.657x frame= 1 fps=0.9 q=-1.0 size=N/A time=00:00:00.75 bitrate=N/A speed=0.641x ` |
|
Overall, since i've tried both '- FFMPEG_CMD=ffmpeg' commands, there are no recordings at all ?!? 🤣 |
|
a more basic path: |
Will try this! |
|
exactly on 21:45 and 30 seconds (9u45m30s pm) just one camera (achtertuin) is going faster (night-time?) |
|
Exactly on 05::23 and 25 seconds (5u23m25s am) that exact same camera is going normal again. while the other camera in the 'voortuin' is going superfast exactly on 01:13 and 48 seconds (1u13m48s am) superspeed til the next 2 recordings. They are going crazy fast as wel. between 2u20m00s and 2u29m00s 'voortuin' is buffering to get normal speed and normal speed is back again at 2u29m00s am changed command:
to
so recordings ar 30 minutes instead of 1 minute |
mrlt8
changed the title
|
@JA16122000 could you try the latest dev build without any custom ffmpeg commands? |
Will try! [WyzeBridge] WARNING: invalid escape sequence ':'
|
Both camera's change recordingspeed, on different times. It looks like it have something to do with the darkness sensors from both camera's? exactly on 05:27 and 12 seconds (5u26m12s am) camera (achtertuin) is going slower (night-time?) NOTE: This night the bridge found an new DEV update and is used since 02:56 last night, sow the very last DEV update is used right now == exactly on 05:19 and 08 seconds (5u19m8s am) the other camera (voortuin) is going slower (night-time?) NOTE: This night the bridge found an new DEV update and is used since 02:56 last night, sow the very last DEV update is used right now Achtertuin (See around 05:27:12): Vooruin (See around 05:19:08): |
|
Can you try setting the FPS to 20 via the webUI, then reboot each cam to see if that might help? Edit: was the day/night recording fine on v2.6.x? |
2.6.x was just fine (i think) EDIT: There was a new 'dev' build and portainer just installed tis automaticly, so now the speed is normal. |
|
Any changes with the current dev build @JA16122000 ? |
Hard to tell. But we will see and report if it stil is going on! :D |
|
Nope, still the same problem. |
|
@JA16122000 can you try setting the FPS and doing a reboot via the WebUI: This seems to have cleared up some weird issues I had with one of my shared cameras. Can you also disable auto updates temporarily so we can keep track of the build number that is having issues? |
I've paused automatic updates now, so build: Did your commands only with another port (instead of 5001, i have used: 5000 with succes.) 192.168.178.78:5000/api/voortuin/fps/20 |
|
Last night, I opened the Wyze APP. I then experienced 'disconnections' which caused the cameras to reconnect. This resulted in (after the reconnection) the 'backyard' camera recording 1x slower (30 minutes, became 1 hour). |
* Sign motion event request #1125 * use device id instead of mac #1125 * remove wrong flags from mkfifo #1174 * less aggressive flush #1159 #1167 * Use K10052 for setting FPS #1161 * Refactor bits for going above 255 for quality * Revert ffmpeg changes #1159 #1167 * version is obsolete * default quality to hd180 * Update Wyze iOS App version from v2.44.5.3 to v2.50.6.1 (#1176) * use struct pack * Token based auth over the webUI * Fix redirect for Home Assistant Ingress * Use request headers to fix redirect for HA * Change GET to POST for webhooks data * Deprecate ifttt_webhook in favor of webhooks * use yml for HA config and make credentials optional * keep trying to identify audio #1172 * Snapshot on motion and push to mqtt #709 #970 * Add event time to motion message * refactor auth * EVENT_API option #1125 * Add additional headers #1125 * Audio sync with higher bitrate * Debug api request #1125 * Update api.py * only debug on error * Tweak audio sync * don't raise error on lost frame * clear buffer if out of sync * Unique macs only #1125 Co-Authored-By: Cameron <32912464+kiwi-cam@users.noreply.github.com> * Require auth by default and block non-ingress access #1181 * Allow non-ingress access with auth #1181 * Remove retain flag from commands #1182 * update webrtc to work with auth streams * Add WB_API and rename WEB to WB #1181 WEB_USERNAME > WB_USERNAME WEB_PASSWORD > WB_PASSWORD * HA move /config/wyze-bridge/ to /config/ * Don't notify substream event and remove v2 #1125 * WebUI Auth related config for HA * Don't retain discovery message? #1182 * Case sensitive credentials for WebUI * changelog and readme --------- Co-authored-by: Cameron <32912464+kiwi-cam@users.noreply.github.com>
|
Hmm, so it works fine until the app is opened? |
I don't think that's the issue. Your previous suggestion #1159 (comment) indeed do what it's supposed to. However, after a disconnect or reconnect, it fails. Is it possible to have #1159 (comment) run automatically after each start? |
|
sorry your links don't seem to work. Was it the |
This worked: ============================
============================= But however, after a disconnect or reconnect, it fails. Is it possible to have above commands, run automatically after each (re)start? |
|
Today i've upgraded to 2.9.0 and did after the upgrade, above commands. |
|
hmm, I believe |
So this will be:
? I could try this like the old way? |
|
Using: 2.9.1 I did use force_fps_camname=20 but this is not working @mrlt8 :(
|
|
I believe the videoParm only gets sent on connection to the camera, so it probably wouldn't update even if you manually changed the fps. |
|
is this still an issue with 2.9.2? the dev branch has an updated mediamtx which can do the recording for us. |
Monitoring every day! |
Now 2.8.1 is perfect
No more delay, but now ar my recordings wrong.
Cam 'voortuin' should be 30 minutes, but it is only 2.50 minutes
cam 'achtertuin' should also be 30 minutes, but is record in slowmotion and takes an hour to play.
So 1 is speedy forwarding recording, the otherone is in slomo 🤣
Originally posted by @JA16122000 in #1042 (reply in thread)
The text was updated successfully, but these errors were encountered: