The frames table contains information on each frame in the video, like when it occurred and whether there was motion. Back when we were just storing jpegs, we needed this timing info to know when each frame happened.
These days with mp4's, we _could_ make this table optional in terms of playback. However this is also where we store whether there was motion, so we would lose that too.
In terms of support contract I would generally quote 10 hours for $2000 to review, setup, apply back practices etc. Training, whatever to get the system up and stable.
50+ Camera setup, Struggling here
Re: 50+ Camera setup, Struggling here
iconnor wrote: ↑Fri Apr 07, 2023 9:09 pm The frames table contains information on each frame in the video, like when it occurred and whether there was motion. Back when we were just storing jpegs, we needed this timing info to know when each frame happened.
These days with mp4's, we _could_ make this table optional in terms of playback. However this is also where we store whether there was motion, so we would lose that too.
In terms of support contract I would generally quote 10 hours for $2000 to review, setup, apply back practices etc. Training, whatever to get the system up and stable.
Hm, even after disabling that Option the tables are still getting massive. Over the weekend they had about 15million entries each... something is not right here. We might take you up on your offer, at this point we just want something that is reliable and gets the job done. Our needs aren't enormous, mainly just the amount of cameras, and the playback to look at specific incidents is all we use them for.
Re: 50+ Camera setup, Struggling here
Okay, huge update and hopefully the conclusion.
I create an empty copy and then redropped my frames and stats tables since they once again became massive. Then, I turned all cameras to just Record instead of Mocord. That stopped the stats table completely, and since they are in Record they can use and upload frames with the BULK_FRAME_INTERVAL option. That drastically reduces the frames, as expected, but it also stopped the absurd load times and crashes from loading footage.
So it seems like the queries got hung up on searching the 10s of 100s of thousands of records for each individual frame data and stats, and allows multiple cameras to be loading footage across days with 0 issues. I hope this might help others or might offer a suggestion for development, such as maybe not trying to load this tables when in montage review? Not sure, I'm not the expert, just a noobie being a noob. Thank you all for your attempts at helping, and hopefully this will be the final conclusion!
I create an empty copy and then redropped my frames and stats tables since they once again became massive. Then, I turned all cameras to just Record instead of Mocord. That stopped the stats table completely, and since they are in Record they can use and upload frames with the BULK_FRAME_INTERVAL option. That drastically reduces the frames, as expected, but it also stopped the absurd load times and crashes from loading footage.
So it seems like the queries got hung up on searching the 10s of 100s of thousands of records for each individual frame data and stats, and allows multiple cameras to be loading footage across days with 0 issues. I hope this might help others or might offer a suggestion for development, such as maybe not trying to load this tables when in montage review? Not sure, I'm not the expert, just a noobie being a noob. Thank you all for your attempts at helping, and hopefully this will be the final conclusion!
Re: 50+ Camera setup, Struggling here
montage review is not designed with large data in mind. It is being drastically changed in master.