gstreamer // ffmpeg #739
Comments
|
Sorry thought i replied to this but must've missed to publish. The documentation is there just to hint that if you need to set some output filters on the recordings, it has to be FFmpeg commands and not GStreamer commands. Are you having any issues or do you need to set parameters on the recording? |
|
Well, I have trouble setting up on my Jetson Nano. This is my configuration: And this is the log output: |
|
@roflcoopter is there any debug logging I could do to get this solved? Thanks |
|
A quick google didnt yield any good results sadly. You can enable debug logs this way: logger:
default_level: debugThe GStreamer command might have to be tweaked a little to work with that camera, just have to figure out what! |
|
Ok thanks, I now have debug logging: |
|
Do you have many files present in the folder |
|
Nothing at all. This is a clean install. So the directory is completely empty. |
|
Strange, you would need to play around with the Issues like these are near impossible for me to assist with since i dont have access to the same hardware |
|
I don't have any gstreamer experiences. Can you please give me a starting point? Such like what is the current command now for example..... |
|
Sure! The command can be found in your debug logs, the default that is used right now is this: It is quite long but you can try to simplify it by removing the audio part for instance. To quickly test new pipelines you can exec into the container and play around with the command: |
|
Does it prove anything if I say that the command won't crash when I leave out the "location=/segments/patscam/%01d.mp4" |
|
fyi if I run the original command (with correct username/password): |
|
Hmm strange. What audio and video codecs is your camera sending? Could you try updating to |
Still no go. Even with 3.0.0b5. |
|
Nothing obvious still :( Can you try without audio? |
|
Tried it. Still no video in the live view, nor is it recording any events. And the message |
|
By the way I'm running this image: https://github.com/Qengineering/Jetson-Nano-Ubuntu-20-image |
|
Hmm that could possibly be the reason why. Is it possible for you to backup your SD card, flash the official Jetson Nano image and try again? If it still doesn't work we can rule that out at least And hey, thanks for the coffees! 🎉 |
|
Sure, will try that! I'll let you know how it goes. |
|
Too bad... Apart from the old docker version (had to use docker-dash-compose again. felt like a time traveller) |
|
OK, I've did a test with a vm on ESXi running Centos stream 9. config.yaml: |
|
Interesting, i suspect the camera is doing something funky that GStreamer cant handle. If you switch |
|
What Reolink model do you have? |
|
It's the Reolink Doorbell PoE version. But I think I found something. Somewhere along the line I've set the codec to hevc instead of h264. |
|
By the way I found it when I was trying to put in a test stream of https://rtsp.stream/ . This site seems to offer nice free test streams. I couldn't find any other working rtsp streams.. |
|
OK, I've ordered a Google Coral. We can close this one. |
|
So this was caused by some misconfiguration between your camera and Viseron? |
Not really. I still couldn't get it to work. Only thing is somewhere along the line while trying and testing I messed up the codec setting. Will continue testing, but now with the Coral TPU. Thanks for the help so far! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm using a Jetson Nano and I read that I need to use GStreamer for hardware offloading. But I cannot get the recordings to work.
The documentation states "As of now the gstreamer integration uses FFmpeg to create recordings when an object is detected and FFprobe to read stream information. Therefore, if you make changes to the recorder config you should keep in mind that it is in FFmpeg syntax."
I don't understand what I actually need to do for the recordings to work with GStreamer.
It is also not mentioned in the example config on the top of the page.
Thanks!
The text was updated successfully, but these errors were encountered: