ZoneMinder Forums

Just upgraded from 1.32 to 1.34... So in a nutshell, when you set a maximum event length of 600 seconds in 1.32 in Record mode, it would start the next event on the 600 second boundaries, so 00:00, 00:10, 00:20, even if you turned on a feed at say 00:23 the first event would only be 7 minutes and the next one would start at 00:30. This was the behaviour all the way back to the first 1.2x version I used.

Not anymore, the next event starts every 600 seconds on the dot, regardless of when it started. So 00:23 ends at 00:33 now.

This is a huge problem for a time lapse video I've been making for a few years now... the first frame of the day is no longer midnight, it's up to 10 minutes after midnight. I only have vague ideas of how to compensate for this in my own code, I used to be able to start in one folder and skip every n images, but now... maybe start checking files from the previous day, scan forward and check the image file dates to know when the desired day begins and ends (for synchronization reasons it's very important that every camera in the time lapse has the same start frame at 00:00 every day).

I've got about 3 days to figure this out before I have to manually intervene, after 3 days frames start to get overwritten if I haven't captured what I need by then.

I'm encountering the same issue.

In my case, it gets close to the ten minute boundary (I'm also using 600 second event lengths), but not exactly.

Reviewing the last few days, the segments starts at :13 seconds, :05 seconds, :21 seconds, :53 seconds, but never right on :00 seconds.

This started after upgrading from 1.30 to 1.34.

The time crunch is off, as I've downgraded to 1.32.3 again.

I just discovered bugs, and some removed functionality, in the web interface that made 1.34.16 unusable (past events only successfully play at regular speed without corrupting the image, current event only plays back a few frames before corruption, and speed over 8X is no longer an option?).

I really should test these things in a virtual machine first, every version has been less useful than the last (I think I started at 1.28), at least for what I do with it (combination home security and that time lapse video thing). Adapting to 1.32 was only just possible (the bugs I mentioned in a post last year were never fixed, I guess because 1.34 was just around the corner, I had to write some workarounds and change how I use the web interface), I can't adapt to 1.34 at all.

Not sour grapes as such, and I'll still make the annual donation (because even the trouble I had getting 1.32 to work for me was less work than coding something from scratch), but let's just say I'm soooo glad that downgrading from 1.34 to 1.32 is apparently easy as pie, no hiccups.

I think the issue here is the Options->Config->EVENT_CLOSE_MODE

In the case of record, ending on an even time boundary, it has to be set to Time.

Ideally this setting would be applied to each monitor instead of a global.

Also, if in record mode, Idle and Alarm don't make any sense... so....

Maybe I'll have this fixed in .17

I... *think* I tried that? So many hours and tries ago... I can't be sure.

If I find the energy to try this again but virtually this time, I'll report back on that setting...

FYI, I was wrong about no hiccups during the downgrade, heh... just spent hours massaging the database because filter settings were not being read/saved properly and here's a warning to you all, in my particular case this means it started purging *every* event because the PurgeWhenFull triggers were basically blank and therefore applied to every event. Again, I really, really should try these things out virtually first, but the something compelled me to just dive into this at 2AM this morning, go figure... I'd say I learned something here but these episodes are so few and far between they rarely stick, half the time I can't even remember that I took notes if I did, heh... I did this time.