-
-
Notifications
You must be signed in to change notification settings - Fork 161
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
BUG: Recording Playback Issues #1319
Comments
Different cameras versions use different audio codecs. You can force a different audio codec like VLC will buffer the RTSP stream so that's probably why it takes a while to load, but you can go into the advanced settings to reduce the buffer. As for seeking, it's probably based on the media player's cache/buffer as livestreams are usually meant to playback at the edge. |
Apologies, I should have been more specific. It isn't the livestream playback that I am having issues with. Rather It is the recorded stream. I have been using the docker version for more than a year now, records onto a HDD and plays back without issues. However with the new version, playback of the recorded stream is now having the listed issues. The older files playback properly as expected. |
Same issue here. I tried 2.10.1 for a day and had to roll back to 2.9.10. There seemed to be something fundamentally different in the codec or formatting or something else, that messed up the timeline when I tried to play on mobile devices and TVs. Perhaps that could be fixed by applying a custom ffmpeg command but I have not figured it out yet... |
Unfortunately, this is probably because we switched from recording the streams directly from the camera to having mediaMTX do the recording from the RTSP stream. Will need to look into this further. |
Could you try changing the audio codec? environment:
....
- AUDIO_CODEC=libopus |
Has anyone been able to test out if We could try setting the default audio codec to libopus if that works. |
Sorry, I rolled back to 2.9.12 for stability and playback. I am planning on deploying a secondary NAS and can possibly test there. |
Adding the audio codec fixed the error message, however the recorded file is till a little wonky. |
Actually the other thing I liked about 2.9.x version was the automated sectioning when I set it to record 2hrs. The system would start a file every 2hrs according to the clock time instead of actually going by the video length. That made the recording organization much easier. @mrlt8 |
I noticed that as well. Unfortunately, v2.10+ is using mediaMTX to do all the recording, so we have limited control and may have to revert back to the old style of recording to fix some of these issues. |
Describe the bug
When attempting to playback on windows, the media player fails to play the audio, there's a pop up saying "we can't play the audio for xxxx-xx-xx_xx-xx-xx. It's encoded in ipcm format which isn't supported. You can still watch the video".
The video plays however I am unable to seek forward or backwards.
When I try to use VLC media player, it takes some time to "parse the file" before playback begins. It is able to play the video and audio, and seek works, h
owever it is not very responsive.
Affected Bridge Version
v2.10.1
Bridge type
Docker Run/Compose
Affected Camera(s)
No response
Affected Camera Firmware
No response
docker-compose or config (if applicable)
The text was updated successfully, but these errors were encountered: