-
-
Notifications
You must be signed in to change notification settings - Fork 100
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
Wont stream RTSP Failed to connect to the D-Bus session #153
Comments
So, I thought I may try suggested versions from a while back, so installed a fresh 2021-05-07-raspios-buster-armhf Same issue
VLC is at least trying to run. I can stream rtsp://192.168.44.4:7447/zR4CkwuhXKsMKu2a just fine from my MAC VLC
|
Ok this is interesting, I decided to try stream same quality camera off my local home NVR and it works, then tried medium and high quality, they all worked. So its only the remote stuff thats not working. I suspect there is some buffer setting that needs to be used for remote RTSP?? |
You could try playing with network_caching_ms config option |
Any update? |
I am facing the same issue. I also tried the network_caching_ms without any luck. |
I've been battling this issue also, and found I was able to pull a PC RTSP stream from my PC on my home network, but as soon as I plug it into the network on site (which is far less complex, same subnet, no firewalls), I get this same buffer deadlock error. Really is doing my head in and I've tried so many different iterations but nothing seems to stop triggering the deadlock. Did you manage to find any solutions yet? |
any update? |
Trying to convert from v2 to v3, and seeing this often on the pi3/bullseye/vlc install I've done. video streams all reset, and logs show
For now I'm going back to my buster/2.0 install. the video stays on screen for hours with zero blips. :( (for context, video is coming from a go2rtc server running at 0% cpu, wired gigabit path between server & pi.) |
I wonder if its as simple as needing to manually set the environment within the script, given its running in headless mode it doesnt have a desktop environment running. I'm not nearby my CCTV pi and dont currently have a spare to test on so cant test for the next week or so. `` if 'XDG_RUNTIME_DIR' not in os.environ:
`` |
Per camera buffering seems to make it better, but having to run a 3000-5000ms "buffer" on each camera dramatically reduces the "realtime" effect, especially when it's things like a front door. They can be walking away before you hear the doorbell. v2/omxplayer - no such issues. Going back for now. @SvenVD - given any thought to using SDL2 to replace MMAL? (since omx is long gone) I've seen some work around ffmpeg / vlc and SDL as an output option. Hopefully that could survive longer than OMX or MMAL did. |
I did not do any tests with sdl, not sure if it used hardware acceleration or that it can be use to provide specific coordinates. Vlc on raspberry pi os is compiled with mmal support |
Hi,
I just installed 2022-01-28-raspios-buster-armhf on a RPi4, followed the
gpu_mem=512 to your /boot/config.txt
framebuffer_width=1920' and 'framebuffer_height=1080
The demo boots fine and plays the video of the mkv and says connecting in a few other boxes.
I commented out all the streams and added mine:
Trying single stream with RTSP over TCP true or false just shows connecting to stream on the screen.
/var/log/syslog shows the following.
I have tried changing GL Driver in Advanced settings to all 3, and gone back to legacy now as G3 wouldn't work at all
-G1 Legacy Original non-GL desktop driver
-G2 GL (Fake KMS) OpenGL desktop driver with fake KMS
-G3 GL (Full KMS) OpenGL desktop driver with full KMS
Additional logs
The text was updated successfully, but these errors were encountered: