Recent content by DurandClan

Yeah...CPU didn't change much but the RAM went down profusely. Hardware acceleration is completely turned off and every camera does have a working substream so I believe this is now optimal...not to mention BI has not crashed since.

ok....I think I have it all set correctly now...adjusted everything to match your referenced doc, went into each camera's vendor interface and made sure both streams were configured properly and aligned settings in BI to match for each stream. Removed the hardware acceleration from each camera...

I think I was misunderstanding....you are referring to the 'viewing' and not the recording of the cameras? So the recorded video is defined in the video configuration and the higher quality is still recorded to disk but the lower quality is used for the UI only. Honestly had no idea. I did...

It was working fine before...what changed? I have a system dedicated to the cameras so I could care less if the CPU is 90%....that is what it is there for. The only reason I went with the nVidia route was the make sure the CPU was there for other tasks, i.e. export operations, and handling...

checking....I think I went the path of the nVidia card because of the AMD processor. When you say 'sub-stream', you're not talking about the crappy, quality secondary camera stream, are you?

This has been happening since 7/1/22 and the errors on the July dates oddly enough show the BlueIris.exe version to be 1.0.0.1 which obviously is not correct. For the record, I have tried rolling back a number of times over the last month or so and no change in behavior. All of the crashes but...

Seems more likely to happen if I'm viewing remotely from UI3 using either Chrome or Edge. These are the two errors with the 2nd being the most common. This has been happening for quite a few versions now and I guess I keep hoping it will be addressed with each update that comes along. Any...

OK....so an update....both remaining issues are fixed and here was how. Issue 1, I switched the BI service to use an administrator account...in my case, a domain account which has local admin rights on the system since it is domain-joined. One key note here is in doing so, many of my tweaks...

I have New on the S: drive, dropped alerts on another partition (not as concerned about them) and when New gets full, I want the files copied to W: but this step is not working. I continue to get MOVEFILE ERROR 3 errors in the status screen. If error 3 means 'path not found', why is it I can...

So a database rebuild should provide current location of files and then follow the clips/archiving rules accordingly, correct?

So let's say New and Stored are on the same disk....what is the purpose of setting Stored to 0? Wouldn't I benefit from everything just being written to Stored? If I were to choose to use different folders for the cameras, etc., I still want files to eventually get over to W: which has more...

OK....most of those things are simple corrections. I can write alerts to SSD and I'll bring the other items over to spindle.

The intent is for files to start off on fast storage on the Blue Iris machine (i.e. SSD)...this would be H:, then move to S: which is locally connected on WDPurple storage and then the aux locations...which are the same cloud storage bucket at Wasabi connected with RaiDrive as a "local" device...

Here we go...

Got it....rounding them up.