QuantumEntangledAndy / neolink

An RTSP bridge to Reolink IP cameras
GNU Affero General Public License v3.0
346 stars 47 forks source link

Possible to statically link gstreamer? #306

Open ForksCoolStuff opened 1 week ago

ForksCoolStuff commented 1 week ago

I'm trying to use neolink with the Frigate home assistant addon.

I can install gstreamer libs and get neolink working BUT the changes are lost on restart.

Is it possible gstreamer could be statically linked in with neolink?

If not, any other methods you can think of? I've tried setting LD_LIBRARY_PATH to pwd and sticking the libs in there. That makes neolink stop complaining about gstreamer but introduces new errors like unknown symbol something something. Maybe I forgot a lib but I would have thought it'd continue complaining about libs until they were all satisfied.

Any help is appreciated. Technically I could pipe Frigate's back channel audio through netcat to a server that DOES have gstreamer libs, but that's not really a super elegant way to go about it.

QuantumEntangledAndy commented 5 days ago

No gstreamer is used through a plugin system and doesn't really support statics in that way.

It sounds like you are using a frigate container, any changes made to a container will always be lost on restart. The way around this is to make a new base image with the libraries you need. We provide a base image for neolink and there is a separate project which integrates that image into a HA plugin. You should use that and do container to container networking and not modify the frigate container at all

ForksCoolStuff commented 5 days ago

Do I need to use the talk subcommand to do the two way audio or does 2 way audio also work through the RTSP stream neolink provides? That's mainly what I'm after.

QuantumEntangledAndy commented 5 days ago

Has to be though the talk. The ONVIF protocol in gatreamer dosent really exposed the back-audio for us to use