Neolink starts okay but 'app source is closed' soon after #316
Answered
by
QuantumEntangledAndy
EricLauber
asked this question in
Q&A
-
|
I am currently testing running neolink in a docker container on a Linux VM. I am able to start neolink, it connects to the camera, reports the streams available, and I can connect to it from another machine running ffplay. However after a short period of time (often 10 seconds) I get warnings from neolink and the stream in ffplay freezes. Here are initial logs from neolink when starting up. The camera name is At this point I start running ffplay: About 10 seconds later, I see these warnings in neolink. They lead in first with a large amount of There is also When this happens, the stream in ffplay freezes. The time on the camera image no longer changes. I am testing with ffplay because of running into issues with VLC Player - I've seen it come up in other threads here. When testing with VLC Player, I see the same results from neolink, only VLC simply closes the stream when the |
Beta Was this translation helpful? Give feedback.
Answered by
QuantumEntangledAndy
Oct 30, 2024
Replies: 1 comment 3 replies
-
|
Yea seems to be something happening on master, perhaps try an earlier branch. I've been reworking the method that frames are sent to gstreamer to try and deal with some latency issues. But it seems gstreamer is not happy about it anymore. |
Beta Was this translation helpful? Give feedback.
3 replies
-
|
Good recommendation... going back to release tag |
Beta Was this translation helpful? Give feedback.
-
|
In the other discussion where I had posted, you asked another for the gstreamer logs. I forgot to post that here. Here's a sample of all the logs including those when Lots of logs |
Beta Was this translation helpful? Give feedback.
-
|
@QuantumEntangledAndy I can create a new discussion topic if it makes sense to do so - I have noticed that while v0.6.2 is more stable and avoids the issues described in this thread, that configuring for mqtt simply doesn't seem to work due to the dockerfile configuration from that build. It always runs rtsp independent of the env. That of course has been fixed, I may need to try and run 0.6.2 with a custom dockerfile to get the source from that time but enable mqtt. Anyway I noticed a few more logs in case they are relevant when running |
Beta Was this translation helpful? Give feedback.
Answer selected by
EricLauber
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Yea seems to be something happening on master, perhaps try an earlier branch.
I've been reworking the method that frames are sent to gstreamer to try and deal with some latency issues. But it seems gstreamer is not happy about it anymore.