#zoneminder

ic0n: maybe not all filters need to run in parallel, but in some situations one would need to be able to configure the amount of parallel instances of a given filter. But of course this means that internally there must be some mechanism to avoid contention between parallel jobs.

Why has my Axis-stream turned blue? It shows up as connected just fine, when I look at the same url outside of Zoneminder it works great too.

I've tried reconnecting it too.

plundra, just to ditto your error

ive got escam cams which seem to do the same

a power cycle of the cam seems to cure that

but it does need investigating

I've restarted both the camera and ZM, still blue.

(No powercycling, but that seems redundant :))

This might have happened when I upgraded the firmware to 5.85.x from 5.65.y, although I doubt the mjpeg format would have changed? :) Still works fine in browser and with mpv.

I wonder if I should try using the H264 stream instead.

Switching to rtsp/http works fine, switching back to mjpeg over http - Still blue.

So I'll just keep it that way.

plundra, i use the h264 stream

that also goes blue ... but it's not often

the only way ive had to get rid of it is to powercyle them

hi Friends, congrats on new release

any assumptions when are .rpm and .deb are going to be available?

ooh that was faster

it's always warned that -j 8 was not supported to add -j+ to cmake conf or something

now ive just seen all 4 cores + HT fully loaded

nice

Database upgrade to version 1.29.0 successful.

good good

excellent

ZoneMinder Console - Stopped - default v1.29.0

even better

ZoneMinder Console - Running - default v1.29.0

and feature-h264-storage is updated ... thanks chaps

oh and congrats on 129.0 :D

Good morning all

morning ic0n

You're here early

I get up at 0600 with the wife. Conf. call for a client that is 2 hours ahead of me at 0700. I usually do the call from the kitchen while making coffee but decided to hurry up and do it from the office today

geez want to all update the same issue at the same time

hehe

Any of you know where I can pick up the new skylake-based Xeons?

They're not at microcenter. :(

Starts breaking shit so he can get a 2.0

Since all interested parties are here in IRC, lets quickly move the convo here

haha rexd666 you're an ass

So rexd666, with your long-running branch, that is essentially still a feature branch, right?

Feature branches can certainly span multiple releases.

h264? it is just that feature

I meant 'ZoneMinder2_The_Quickening '

but yeah, h264

it is pretty much all the feature branches

and ripped out autotools and ripped out xml, eyezm

rexd666 I'm going to become more active on h264 because I'm going to be needing it soon. I really need h264 passthrough in remote mode. Also need to reduce ram usage.

ic0n: welcome to make changes, I did have some code for remote, but was not working yet

I know, which is why I couldn't use it.

Let me see if I can find the branch I had it in and have a look

so rexd666, we're trying to do monthly releases now

Only questionable thing in quickening is angular-ui, which I took to have a play with

about the ui...

I think I am throwing it away and starting anew.

Namely: angular-ui is built on angular 1, angular-ui is very incomplete, angular 2 is out and is not backwards compatible with angular 1.

Is it too much for one person? I ask as modern and angular-ui you made good starts on but never got there. Not having a go, just maybe we need a way to share the load

I think we need to stay away from bleeding edge technologies.

Well, that's part of it, the other part is I didn't do incremental releases. So both modern and angular-ui were to be released at 100% working. Bad idea.

Moving foward, I'm going to stage the release. For example, https://github.com/ZoneMinder/ZoneMinder/issues/12 is targeted to 1.30 and will be the first of many views written in a new ui

Until eventually we get all views complete and then the new ui is 'fully' released.

Yep I like that, so we can document the view and assign it to someone

morning

knnniggett: A ton of requests for /f/23/x86_64/zoneminder-1.29.0-1.fc23.x86_64.rpm which doesn't exist in the repo.

where? what?

not sure if it helps much but zenhub.io adds some nice stuff to github to manage milestones. Only a chrome addon

ic0n: where do you see that?

apache logs

Well, they are going to have to wait then.

hihi

188.93.81.142 is requesting about every 5 seconds

haven't had time to build rpms

zoneminder-1.29.0-1.fc23.x86_64.rpm is not going to exist. It is going to be zoneminder-1.29.0-4.fc23.x86_64.rpm

we've gotta sort out this branching / version thingy

well... I don't think the linux kernel strategy works exactly for us.

Fair enough, but I do appreciate the 'merge window' idea

Oh, I agree with that.

Titler: A successful Git branching model >> nvie.com

right, that

so this has features and develop

I proposed that years ago. IIRC, mastertheknife didn't like the 'develop' branch

and master becomes release only

right

We branch to release from develop when develop is nearing what we want to call a new release.

So, lets so we go back to that

That leaves two issues: 1) deciding what gets merged back into develop and when, and 2) release numbers / dev numbers

s/so/say/

I was about to go look at how develop handles versioning

it should be something like commit I suspect

That article only says that 'until and not before a release branch is made, a release is only 'the next release''

more or less

I think DB needs to be completely separated from release version onto it’s own versioning http://blog.codinghorror.com/get-your-database-...

Titler: Get Your Database Under Version Control

I don't see the point. You can't run newer code on older db.

mmm trying to explain this is hard

um... our db is under version control....

OK so we start using 1.29.0-Snapshot… for develop versions, but the db is 1.29.1, 1.29.2, then we release 1.29.1 which updates the db to 1.29.2