search

Anonymousdog / displaycameras

System for displaying RTSP feeds from IP cameras on the Raspberry Pi
Apache License 2.0
565 stars 112 forks source link

What about using vlc player instead of omxplayer? #74

Closed akoryuerek closed 2 years ago

Anonymousdog commented 3 years ago

The future is vlc since omxplayer won't be in future releases of Raspbian (IIRC), but I haven't done any of the work necessary to port this over to vlc command line.

Andy

On Thu, Aug 13, 2020, 6:01 PM akoryuerek notifications@github.com wrote:

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Anonymousdog/displaycameras/issues/74, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHIYIKJT5E7FDXTE7ZU4IIDSARPCTANCNFSM4P64KALQ .

jeremy-walker commented 3 years ago

Just curious, do you have any plans on porting to VLC?

I have a 21 camera setup and omxplayer refuses to work beyond 16 cameras. Up to 16 works absolutely fine. Starting the 17th feed, it keeps throwing Failed to connect to TV service: -1.

Starting omxplayer for cam17
tvservice-client: Failed to connect to TV service: -1
Waiting for cam17 omxplayer startup 0
Waiting for cam17 omxplayer startup 1
Waiting for cam17 omxplayer startup 2
Waiting for cam17 omxplayer startup 3
Waiting for cam17 omxplayer startup 4
Waiting for cam17 omxplayer startup 5
cam17 failed playback

I'm running Debian Buster (10.4) on a Raspberry Pi 3B with 512mb allocated towards GPU RAM. Even with the 16 feeds running, my main memory usage is at 25% which means it's not a memory issue.

I'm wondering if this is a limitation with omxplayer.

Anonymousdog commented 3 years ago

Yes, this is covered elsewhere. This appears to be an omxplayer issue.

On Mon, Sep 21, 2020, 9:07 AM jeremy-walker notifications@github.com wrote:

Just curious, do you have any plans on porting to VLC?

I have a 21 camera setup and omxplayer refuses to work beyond 16 cameras. Up to 16 works absolutely fine. Starting the 17th feed, it keeps throwing Failed to connect to TV service: -1.

Starting omxplayer for cam17 tvservice-client: Failed to connect to TV service: -1 Waiting for cam17 omxplayer startup 0 Waiting for cam17 omxplayer startup 1 Waiting for cam17 omxplayer startup 2 Waiting for cam17 omxplayer startup 3 Waiting for cam17 omxplayer startup 4 Waiting for cam17 omxplayer startup 5 cam17 failed playback

I'm running Debian Buster (10.4) on a Raspberry Pi 3B with 512mb allocated towards GPU RAM. Even with the 16 feeds running, my main memory usage is at 25% which means it's not a memory issue.

I'm wondering if this is a limitation with omxplayer.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Anonymousdog/displaycameras/issues/74#issuecomment-696101818, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHIYIKKX2WXZHDTZWMRT7HDSG5FZHANCNFSM4P64KALQ .

jeremy-walker commented 3 years ago

So, any chance you might consider porting displaycameras to vlc?

SvenVD commented 3 years ago

This is exactly what Rpisurv 3 is doing, Replaced omxplayer with vlc player.