ZoneMinder Forums

Only ZM needs to be restarted so that zms can retrive the info.

i did restart zm....and i still have my 1.21.3 working with zm4ms with 3 cams, but adding the one cam i have running on my 121.4 box doesn't work...

ok, nevermind....

i restarted agian an now its working...maybe i was dreaming before

ok then, can you get a live stream from the web interface and let me know the whole path. do this for one of the 1.21.3 cams too. im wondering if this is a path issue somewhere

lol glad ur sorted, ignore my post then

ok,

question:

lets say i have 10 cam's defined. whatme nice if i could define a pattern which of them is actually pulling data...

e.g. you could have a on/off switch next to the config of each cam....

perfect would a schema to load/save

e.g. load schema building a or buidling b which then switches the cam 's on or off....

hmm, or well....maybe i'm wrong but if i don't watch a cam then you don't pull the data ? that would work too...

but then we need to load/define/save themes

the new beta allows upto 2 custom views, basically add all the cams you have in setup, open all cams required

either press 36 if enabled or click views for the camera bar

close and position as required, press save, click 1 then ok. repeat with different cams for custom 2.

then recall custom 1 and 2 from the toolbar when req.

I also added a time switchover for custom views. This was designed for security guard, ie custom 1 on at 9am then custom 2 for evening use etc.

Is this the type of thing you mean?

no, not really...

because it only gets you 2 views...

i was thinking about endless config....where you define which cam is seen and the size of the window and position and then just save the view and name it...

then when you want to recall you juts load that view...

maybe better woduld be if you just could save the hole config to xml and load them ?

that also would give someone the possiblity to make 2 totally different setups with cam and views and the just switch..

i think i see what your saying. The only way i can see thus being achievable is to use a db to store the config instead of xml as it does now. How many views would you want though. I wouldnt want to increase the number too much as the amount if info req to store eaxh custom view is
camera 1-36 visible true/false
camera 1-36 size
camera 1-36 position
HA size position visible
cycle size position visible

currently x 2

so you can see that 2 custom views req 220 rows of info in the xml file.
The bigger this file gets to slower it will be whan refering to it.



I think ultimatly i will need to store the settings in something more secure and scaleable, and im thinking this will either be sql express or access. I dont want to store on the zm server as it might not always be available. I want the app to be completely standalone so all it needs zm for images. I think i may need to make a list of wishes and features etc.

Sorry about this

that also would give someone the possiblity to make 2 totally different setups with cam and views and the just switch..

This i dont understand cos you can do this with custom views, I have a site that uses zm4ms and during the day they have cameras 1-6 on display and at night 4-16 on the screen. This can be changed manualy or autoamatically. I think realistically we could get 4 custom views out of the config file, maybe it would go higher but im concerned about speed issues, as i have enough of those as it is.

Anything else for the wish list (hopefully something i can do lol)

ok, maybe i didn't make it clear

i just want to save one setup ALL settings give it a name in xml.... e.g. "building-main.xml"

then i could load that setup back when needed...

so, you could load "building-gym.xml" and watch all the cams over there

and then load another xml file like

load "building-storage.xml" to watch all the cams over there....

etc...

aside from my request for saving complete settings to xml files...

i'm running the beta, but it aways crashes after some time...looks like its eating all my memory...?

well this is a new one!! try disabling the instant replay in settings as that does eat ram but i havnt had it crash yet. can you do a screenshot of the stop error and ket me see it?

how did you get on with this crash thing? I still havnt got one to lock up yet even on really old hardware. The instant replay can cause problems also if the refresh rate is set to low that will stress things too. Let me know

Basically the intatnt replay keeps the last 16 images grabbed from the camera in ram, Unfortunatly this is stored as a non compressed image file and really chews up all you ram. I usally have it set to mac 10 cams on older hardware but my machjine is ok with all 36. (basically though 36 cams * 16 images per cam = a lot of images, stored as uncompressed files means it uses a lot of ram. If you remove the checkbox and disbale instant replay it wont store any images in ram and the usage will be aroung 40 meg, if you enable it on all 36 cams you will hit a peak of around 700 meg

Hopefully that explains your mem issue i have checked i havnt got a leak anywhere as it will run for weeks with the ram gradually rising then .nety clears its buffers and drops again.

James

ok,

the crash happens if you run xp with 256 mb of ram... i upgraded and now it doesn't happen anymore...

so, guess thats fixed...

did you think about my idea to save all settings into a xml file ?

i have been, i think what i understand is you want a different app basicalyy for different sites.
Ity currently uses an xml file for all settings anyway and i suppose it wouldnt be possible to make it reload from different xml files (i would have to learn as i dont currently know how)
Plus i would have to make it move xml files or refernce different xml files dependant upon site required, which im thinking wouldnt scale very well.

I am thinking about upping the camera number as 36 isnt really enough and i could make a second app that saved all settings to a local db (which would scale) basically you would when loading select a schema and then that db entry would be used for all settings. The other way would be to still use a db but have a site selection tree and then all settings cams refresh rates paths etc could be read when a new site/machine was loaded.

I would need to work the db in such a way that would still allow multiple zm servers per entry and then it could grow to limitless cams.

but all this goes above the original scope of the app. and i think i would have to write another one that worked this way. The reason im concerned about the db route is it would make client setup a lot harder. Its hard enough as it is putting all the settings in if you are installing accross multiple machines.

Im thinking that a better way would be to get these settings from a zm server but this would limit the app to opeing one server at a time.

How many different sites/setup choices are you currently thinking of;. Im thinking this will be a lot quicker and easer to add than any of the above

James