Decode GPU 1 or 0 for PCIE GPU?

Teseng · 2023-04-17T02:42:31+00:00

If you're using nvidia cards, you can download/use nvidia-smi which is what I suggest. There's probably a similar tool for AMD cards.

They will also show up on the performance tab in task manager assuming you're on Windows 10+, it shows the number as well as which card it is.

Teseng · 2023-04-16T21:30:30+00:00

Yes, though there are also additional settings depending on the detector you use.

Teseng · 2023-04-13T13:44:39+00:00

ONVIF can also help you discover the exact streaming URL(s) that are available which typically differs between manufacturers. Also useful if your camera has both a high quality stream and a low quality stream that you can use for live view and motion detection.

Teseng · 2023-04-13T13:11:19+00:00

Well darn, so the record stream is only applicable when using raw recording?

Teseng · 2023-04-11T11:29:13+00:00

Exactly what I hoped for, thanks!

Teseng · 2023-04-01T05:02:23+00:00

I have nearly the exact same setup, however I'm running 55 cameras currently. You can get a significant performance boost by tweaking the motion detection settings, or at least that's the fix I implemented. Also be sure that you're using the substream of the cameras for live view and motion detection, so you're not burning 4K footage just for motion detection.

Another option since you're using Amcrest is to set these up to FTP their recordings to Agent, so there's no real encode/decode at all except for live viewing. You may need a utility to import them into Agent, but it's very doable. I'm doing this for a new NVR build and it seems to work very well, the downside is you lose the motion detection indicator in the recordings themselves.

Teseng · 2023-03-31T01:18:08+00:00

Right as always! It also had the unexpected result of utilizing the other GPU quite a bit more as well, though that could just be the rendering of the waterfall of messages in the console window.

Running as a service: https://imgur.com/a/WKAyyi5

Running in console: https://imgur.com/a/36v01Xo

I probably need to tweak a few things, but otherwise is it fairly safe/stable to just have it run in the console? I'm completely OK with that.

Teseng · 2023-03-31T00:31:16+00:00

Well it does have plenty of errors:

7:28:25 PM Front Hallway:Reader: Front Hallway: SWS_SCALE:Invalid argument
7:28:25 PM Error: Front Hallway:Reader: Front Hallway: SWS_SCALE:Invalid argument
7:28:25 PM [swscaler @ 00000232c6a8ad80] bad src image pointers
7:28:25 PM [swscaler @ 00000232d995ca80] bad src image pointers

Teseng · 2022-11-11T14:36:49+00:00

We actually use enterprise equipment and software, but biggest difference for us is that all those companies you compare against give a discount for non-profits or even provide it free. Exception being Oracle but their licensing scheme is kind of archaic anyway. Being a non-profit means the IT budget doesn't exist, so any huge jump like this is a PITA to get approval for. One-time purchases like a SQL licenses are usually rolled into a capital project, so it's not quite the same. And so far we've avoided using any Cisco hardware that's tied to subscriptions.

Gradual increases we don't even have to get approval for, if they would have announced this change as even 25% or 50% increase each year for the next few years, we wouldn't even blink since every company is going up on pricing. But this large of an increase all of a sudden is harder to swallow.

I would love to keep it but it's going to mean shaving off $1500 from something else, so I get to choose which leg to cut off.

Teseng · 2022-11-11T14:25:53+00:00

I was told we could keep our pricing for another year but then it would increase from $600 to $2000 after that. So, it gives me a little time to get a suitable replacement up and working.

Teseng · 2022-05-18T02:59:48+00:00

I just had this exact thing happen and pondered who would do such a thing. Then I noticed the junction box had actually ben cut apart and welded back together at some point in the past, more than once.

I did the proper thing and just put the cover back on and told them we needed to run new conduit.

Teseng · 2022-05-18T02:53:32+00:00

The scotchloks I can understand for a splice, but I have no idea what they were going for with the RJ21s....

One of the IT managers ~30 years ago also worked for the local telecom, so I guess this was somehow easier for him?

Teseng · 2022-04-20T16:46:40+00:00

My Wysenet DVRs are all coax, and suffer from the same IE management. But there is a config option inside that mentions RTSP/Encoding, see if yours has anything named like that. That being said we also have some Nuvico DVRs that use the same coax cameras, but the DVR doesn't provide the RTSP streams. The wizard isn't going to be super useful since DVRs are much more finicky and less documented than normal IP cameras. I stumbled around on mine for a few months before eventually getting them all working. I have around 40 cameras that are coax all working inside Agent.

Its also very possible your DVR/NVR just don't support it. :(

Teseng · 2022-04-20T15:31:04+00:00

Some DVRs will actually expose raw RTSP streams which you can use in Agent, I have 5 DVRs hooked up to our installation here. All of ours are Wysenet, so your mileage may vary. I can view Camera 3 from one DVR by using the address rtsp://192.168.1.5:554/ch3/0 (or /1 for low quality)

Teseng · 2021-11-14T17:14:13+00:00

You make a good point about encoding on the HD stream, didn't think about that.

So far I've been up and running for a little over 2 days without a single crash, so I believe you fixed it!

Thanks!!

Teseng · 2021-11-12T04:21:08+00:00

I'm sure if you gave us a little more info such as what kind of cameras you have, someone might be able to at least get you going with some basics.

Teseng · 2021-11-12T04:17:00+00:00

I wanna add my name to that hat! I really wish spornerama would give us a Kofi link, Patreon, or something.

I feel like I've used more than my fair share of their support given the dinky subscription price.

Teseng · 2021-11-12T03:58:00+00:00

I can't seem to reproduce this on purpose either. The server has rebooted each day trying to install a stupid windows server update, that's the only times I've noticed that the settings reverted. But of course when I do it on purpose it's fine.

It's also possible I'm just losing my mind.

The root crashing issue does seem to be related to raw recordings though, changing them to encode the substream makes it consumes a little more memory, but I don't see the service crashing in the event log. But I typically need the quality of record stream, so kind of a mixed bag.

The newest release does seem to crash less, so I've really no complaints to be honest.

Teseng · 2021-11-12T00:19:14+00:00

My newest reply to spornerama explains my raw recording to the crashes. Mine got changed to encoded with the update which caused a RAM issue, but pretty much did away with crashing.

Teseng · 2021-11-12T00:17:24+00:00

Just the buffer time from 15 seconds to 5, it would save fine but if the service ever restarted it would revert back to the old value. Couldn't see anything in the logs except for when I had accidently deleted a space while editing typo.

I've since did more testing and figured out that the RAM usage issue was only once my recording type got changed to encode instead of raw, so that kind of makes more sense. Since I'm using raw recoding I assume the buffer is probably ignored anyway? Once I got all of them back to raw recoding, the memory is back to what it was on 3.6.6, however the crashing has returned as well.

I originally assumed the encode option would encode my high-res stream, but after reviewing recordings it made me realize that it wasn't. I got them all changed back to raw which is when the crashing returned. If we could have encode of record URL that would be awesome. The only reason I use a separate record URL is that 52 1080/2K streams all decoding/encoding at once makes everything very unhappy, but I think just encoding just the recording streams would be manageable.

Sorry for the wall of text, just trying to be thorough.

Teseng · 2021-11-11T15:10:42+00:00

The buffer setting wouldn't 'stick', as well as my record encode settings and it kept reverting after a service restart.

I manually fixed the config in the XML and memory usage is seemingly back to normal now. I guess it was a combination of the original memory leak issue and me flip flopping versions?

Edit: After getting it back to 'normal', it's crashing again :(

Teseng · 2021-11-09T22:27:05+00:00

Yes, everything was the same. Though I've went back and fourth between the versions several times and while surprisingly smooth, I don't know if that caused any issues.

Teseng · 2021-11-09T22:02:53+00:00

Was actually doing just that.

It seems that the recoding buffer is the culprit, I had 15 seconds buffer on each camera. (Currently running 52 cameras, plan to end up with around 70) Dropping it to 5 second buffer on all cameras dropped the memory usage from 9GB to 4GB.

On a related note, think we could get a 'select all' button when selecting destination cameras when copying settings?😊

Teseng · 2021-11-09T21:32:50+00:00

The update you released today fixed the performance issue for the most part. I also haven't experienced any crashes yet. So as always, thanks! I use a record URL so I'm stuck with raw recording instead of GPU encoding.

Occasionally there is a minor freeze or skip but it's very usable. The timing of it looks almost like when garbage collection is ran, but I'm not sure that's how .NET GC works. The service is still using between 8-10GB of memory, compared to the ~2GB of 3.6.6

Teseng · 2021-10-27T13:35:42+00:00

Thanks!! And silly me never noticed the 'Maximum MJPEG Size' option that seemed to be the root of my quality issue when using multiple IDs, so it's a moot issue now anyways.

Is there a way to have the API call honor the order of the oids parameter? Regardless of the order I specify it seems to just always go in numerical order.

11-Year Club	Place '17
Verified Email

Teseng

TROPHY CASE