Hi,
Can you confirm for me that this is a bug?
My camera is visible :
But when in a scene I ask to retrieve and send the latest image, I get nothing :
Hi,
Can you confirm for me that this is a bug?
My camera is visible :
But when in a scene I ask to retrieve and send the latest image, I get nothing :
After some research, I confirm two things :
Update every 2 seconds, after a few minutes:
Same, one minute later:
Same one minute later:
You can see a lot of new ffmpeg threads, never closed (should there be a 2-second timeout otherwise?).
Finally, I changed the port used for RTSP on my camera (#DIY) and I still see threads using the old port. Proof they were not stopped in time.
Note: I use the camera on only one dashboard, which wasn’t even open at the time of the tests and screenshots.
So it’s 100% related to this thread: Gladys utilisation de la ram
What’s your refresh rate?
For me, the request via chat works.
Is it possible to display in Gladys the % of RAM used by the system?
Like the ping or the % of disk used.
With a refresh rate of 1min I only have a single process left, indeed.
But originally I would have wanted quasi-live, hence the 10 seconds for my part.
And I agree that there is really a bug at that level which is still quite annoying — to say « who cares, leave it at 1min » ![]()
Is a timeout possible?
Or is it simply impossible?
I see it differently, the refresh should stay as is. Maybe even remove the 1s refresh. And see how we could set up a live stream.
And that would be comfortable because we’d have a Dashboard that stays light and if live is needed you click on the image or a button.
I don’t know if that’s clear ![]()
Both points are indeed justified ![]()
I had made a request a while ago to zoom the camera on click.
Maybe that’s what would make the stream more interesting ![]()
To display the stream, we discussed it here:
Very good memory, or research ^^, January 2021 haha that takes me back
Too bad that @pierre-gilles has closed the thread ^^
Well, we’ll reopen it, I think.
To answer the questions, I was trying to have a continuous stream with the 1-second option.
It was running fine, except for the reported bug.
Isn’t it possible to put a continuous stream on the dashboard only when it’s visible?
Yes it’s indeed a bug as said in the other thread, we need to investigate, it shouldn’t be too serious. Regression on the ffmpeg side in my opinion / or a change related to Node 18 in the management of child processes. In any case it’s a bug to fix, we can keep the other thread for that ![]()
I haven’t had time to look yet, if someone wants to do the research it would help me ![]()
I closed the thread because it was a duplicated request with a request that had more votes:
Even though I agree @spenceur, your request doesn’t seem to say exactly that, but in any case I had understood that you wanted to open the live stream from the front end.
The live topic interests me a lot and on the contrary it’s a topic I worked on a bit at the end of the year (for now only at the research stage)
I managed to do conclusive tests that could lead to a development if it’s a highly requested feature.
In any case it’s a dev in the « very large development » category, because on the Gladys Plus side it’s a whole end-to-end encrypted video streaming infra that needs to be put in place. Very exciting but time-consuming project, it’s a multi-month project in my opinion ![]()
Ah yes I had forgotten my ticket ahah ^^’
Great if you were able to start looking into the subject ![]()
Thanks for your feedback!
As mentioned above, switching to 1 minute is a medium-term solution while waiting for someone to look at the real issue, thanks!
It’s true that I hadn’t thought about the Gladys Plus infrastructure. Especially if (or when) the number of users becomes significant, streaming is resource-intensive!
I edited it so it talks about the live stream, does that work for you?