roflcoopter

For transparency if anyone has similar issues, the solution to the problem above was transcoding to supported formats: https://github.com/roflcoopter/viseron/discussions/1180

Its sadly impossible for me to say without access to the same hardware. Did you try disabling audio? My only recommendation is that you fiddle with the FFmpeg command until you find something that works, and then we can adapt it to meet the needs of Viseron.

I'm not sure the audio is the issue, AAC is a standard codec. You can try disabling it by setting audio_codec: null under the recorder block for the camera

Sadly no, only Nvidia GPUs are supported currently. I dont have an Intel GPU at hand so cant build the support for it myself

Nothing special should be required in order for the Coral to work in the container. However, i dont use Unraid myself so i am not sure how to achieve that

Any specific reason you are using GStreamer? FFmpeg is better implemented in Viseron and should solve your issues

Sorry i dont have any experience setting up Reolinks. Try if the defaults work for you, otherwise you can search the repo and see if someone else has solved the issue already. No it is not needed anymore. Recordings was a confusing name for it since 24/7 recordings were introduced Not familiar with how to pass USB devices on Unraid but it should be done in the standard way, nothing special requried for Viseron

Interesting, there is no special handling of Reolinks in Viseron, i know they are a bit finnicky sometimes but they should work. The template has been updated with these new parameters, but it seems its gone from the CA store? Something might be broken. Anyone knows how to check whats wrong?

You seem to have a typo in teh snapshots volume mount. You are missing a forward slash there if you look carefully at the docker run command. Unsure how to fix that tho, its not from the template however

I am not too familiar with Unraid sadly, but the template has the folders defined for v3+. Is there some sort of refresh needed in the CA store for it to pick up the new version of the template?

Made some changes to the template. Hopefully the formatting is correct. Will convert the image to a PNG but cant push it yet since i have other changes pending locally

Sorry for the delayed response! I dont hang out much here since i do not use Unraid. That is also the reason for your other issues, the template is outdated now that v3+ is out. Ill see if i can fix the template but there is no way for me to test which is less than ideal sadly.

I would recommend pulling the latest beta tag, 3.0.0b12, as that contains multiple improvements and bugfixes (and a log file in the config directory) I am not sure how that is done in Unraid tho. If that is not an option, can you check the Docker container logs? They should give an indication to whats going on

Sorry forgot to reply here. I see, then you need to transcode it. Viseron can do it by setting audio_codec: aac in the camera configuration

Sorry for the late reply. Its hard to know for sure with errors related to specific hardware since i cant run tests. You can copy/paste the ffmpeg segments command to the shell and then do some google searches (or ask Chat GPT) on the errors you are getting.

You can exec into the container, `docker exec -it viseron bash` And then you can paste the default command and start working with it

Seems to be issues with your camera, see this: https://stackoverflow.com/questions/22823599/ffmpeg-decode-video-h264-with-warning-sei-type-truncated-error-concealment My recommendation would be to play around with the ffmpeg command using the command line and when you find a working solution i can assist in configuring Viseron. You can see the default ffmpeg command by turning on debug logging: https://viseron.netlify.app/components-explorer/components/logger Sorry for not being able to assist more, its hard for me to solve issues like these that are related to hardware

The cameras settings look okay, but can you try changing it to h264 and then restart Viseron?

Seems to be something wrong with the cameras encoding. What brand and model is it?

The first page of the Recordings shows the latest recording per camera. You can then press the button in the bottom right corner of each camera card to drill down to the second page. There you will see the latest recording for each day. You can drill down further and see all recordings for a specific day using the same method.

If your host is setup correctly all you need to do is pull the roflcoopter/amd64-cuda-viseron image and it will use your GPU automagically if it is detected properly. I fully agree that the config should be editable in the GUI and i plan to do that at some point, but it is a pretty huge amount of work so i cant give a timeline on that sadly. Viseron v3 is in beta right now which brings a lot of improvements however, like 24/7 recordings

Seems to be working fine here right since it is recording? Or are you using CPU detector here?

Can you restart Viseron and paste the full log? It should give a hint of what's going on. Thanks for the heads up on the icon!

@parish99Sorry for not responding sooner, glad you figured it out

VA-API not working often boils down to permission issues. Does it work if you run with PUID=0 and PGID=0 and/or privileged? What do you mean by recordings are stored with random names? Could you show an example? They should be stored in a separate folder per camera/date with a timestamped file. The error in your log is simply the object detector which takes some time to initialize the first time, nothing to worry about!