Send Motion-user mailing list submissions to
motion-user@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/motion-user
or, via email, send a message with subject or body 'help' to
motion-user-requ...@lists.sourceforge.net
You can reach the person managing the list at
motion-user-ow...@lists.sourceforge.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Motion-user digest..."
Today's Topics:
1. using netcam_highres parameter (thomas)
2. Re: using netcam_highres parameter (MrDave)
3. Re: Recorded videos freeze after several seconds (Jon Wedell)
----------------------------------------------------------------------
Message: 1
Date: Sat, 3 Feb 2018 19:18:17 +0100
From: thomas <674...@web.de>
To: motion-user@lists.sourceforge.net
Subject: [Motion-user] using netcam_highres parameter
Message-ID: <1946c41d-6fc3-35ae-14c9-2fb9879c5...@web.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Hi together,
with PR #634 <https://github.com/Motion-Project/motion/pull/634>
"netcam_highres" is now finaly working.
Some remarks what maybe could be better
My setup: two HD cams with 3 streams.
Stream0 1920x1080
Stream1 640x360
Stream2 320x180
In the past i use Stream1 for motion detection, when motion was detected
i startet via
"on_event_start" an external ffmpeg which records Stream0.
That gave me:
40 percent cpu usage (from 400percent)
100 kbps network
55 Degree cpu temperature
900 MHz avg cpu clock
now i want to use the new parameter, so dont need an external script
anymore.
the result was:
130 percent cpu
1300 kbps
80 degree cpu temp
1200 MHz cpuclock
the reason seems to be that motion is always recording the lowres and
the highres stream.
wouldn't it be better to monitor only the lowres stream and only on
motion recording highres?
i know, i lost 1-2 sec until the stream is recording.
once more, with passthrue the videofile is always stored with mp4 extension.
is this wanted?
only my 2 cent,
Thomas
------------------------------
Message: 2
Date: Sat, 3 Feb 2018 11:49:40 -0700
From: MrDave <motionmrd...@gmail.com>
To: motion-user@lists.sourceforge.net
Subject: Re: [Motion-user] using netcam_highres parameter
Message-ID: <176a5c6b-b86b-0740-0e49-827f049a0...@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
I think you can lower the CPU by only monitoring motion on stream2 vs
stream1.? Testing on my PI 2 with a 1920x1080 high resolution and
monitoring motion on a 320x240 stream resulted in ~70% cpu.
Regarding only starting the high resolution stream once an event occurs,
I don't think that this would be appropriate for most users.? There
wouldn't be any pre capture functionality anymore and for devices like a
PI, the starting process would be so slow that by the time the high
resolution stream starts, the entire event could be over.
For the passthough output, the only container is MP4 and it was an
intentional choice due to its flexibility.? The configuration parameter
for the ffmpeg output container is ignored.
Dave
On 2/3/2018 11:18 AM, thomas wrote:
> Hi together,
> with PR #634 <https://github.com/Motion-Project/motion/pull/634>
> "netcam_highres" is now finaly working.
>
> Some remarks what maybe could be better
>
> My setup: two HD cams with 3 streams.
> Stream0 1920x1080
> Stream1 640x360
> Stream2 320x180
>
> In the past i use Stream1 for motion detection, when motion was
> detected i startet via
> "on_event_start" an external ffmpeg which records Stream0.
> That gave me:
> 40 percent cpu usage (from 400percent)
> 100 kbps network
> 55 Degree cpu temperature
> 900 MHz avg cpu clock
>
> now i want to use the new parameter, so dont need an external script
> anymore.
> the result was:
> 130 percent cpu
> 1300 kbps
> 80 degree cpu temp
> 1200 MHz cpuclock
>
> the reason seems to be that motion is always recording the lowres and
> the highres stream.
> wouldn't it be better to monitor only the lowres stream and only on
> motion recording highres?
> i know, i lost 1-2 sec until the stream is recording.
>
> once more, with passthrue the videofile is always stored with mp4
> extension.
> is this wanted?
>
> only my 2 cent,
> Thomas
>
>
>
> ------------------------------------------------------------------------------
>
>
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Motion-user mailing list
> Motion-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/motion-user
> https://motion-project.github.io/
>
> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
>
------------------------------
Message: 3
Date: Sat, 03 Feb 2018 18:57:58 +0000
From: Jon Wedell <jonwed...@gmail.com>
To: Motion discussion list <motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] Recorded videos freeze after several
seconds
Message-ID:
<CAHXwULyrD_W3crMrRtBgBzer=aZHs4PXDqQaT=efeq8h98s...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hello everyone,
Thanks for the help. The issue is now resolved.
Just for the record, I see now in 4.1 I need to set the webcontrol_parms
parameter to access the web interface as I was.
The frozen video issue persisted but I resolved it with changing the output
format to mkv as my computer apparently can't keep up with hevc.
Best,
Jon
> MrDave
>>
>>
>> Motion-user mailing list
>> Motion-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/motion-user
>> https://motion-project.github.io/
>>
>> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
>>
>> On 2/3/2018 9:12 AM, Jon Wedell wrote:
>>
>> Interesting. The video has the same sort of corruption when I set the
>> motion configuration parameters via the static configuration files and
>> start running it. This didn't used to be the case, the videos used to
>> record properly. I have multiple cameras and recording with any of them
>> triggers this issue. Also worth noting is that I have two different types
>> of IP cameras and since the issue affects both I suspect it has to do with
>> motion rather than the cameras themselves.
>>
>> I updated my configuration to have just one camera and the issue
>> persists. I've attached the motion log and an example file. If you look at
>> the time on the upper right of the video you will see it stop after ~2
>> seconds, whereas the video runtime is 6 seconds.
>>
>> I could try recording jpegs instead and make videos, but I would really
>> only want to do that as a last resort. Hopefully I can figure out this
>> issue and get the videos working directly. Especially since they were
>> working before.
>>
>> Thanks for your help everyone.
>>
>> Best,
>> Jon
>>
>>
>>
>> On Fri, Feb 2, 2018 at 6:14 AM <dou...@highmoor.co.uk> wrote:
>>
>>> Possibly of no relevance but on the occasion I've experimented with
>>> video I discovered a lot of problems with frozen playback. Using mplayer
>>> for example, the timer would continue to advance but playback would be
>>> frozen. This was when I configured motion to create video 'on the fly'.
>>>
>>> If instead I created video manually using the jpegs it was fine.
>>>
>>> As Colin says, I'd try and eliminate IR from the enquiry, then perhaps,
>>> if you have raw jpegs, create a video from them and see if that's ok.
>>>
>>> Dougie
>>>
>>>
>>> On 01/02/18 20:51, Jon Wedell wrote:
>>>
>>> Hello,
>>>
>>> I'm using IR motion sensors to turn recording on and off via the motion
>>> API. I've found using these sensors to trigger the recording to be more
>>> reliable than relying on detecting motion from the frames. I'm encountering
>>> an issue where only the first 1-3 seconds of the video I record is actual
>>> video, and then the frame freezes for the remaining duration of the
>>> recording time.
>>>
>>> To activate the motion recording, I make the following API calls (using
>>> the python requests library):
>>>
>>> # Enable video recording
>>> r = requests.get("http://%s:%s/%s/config/set?ffmpeg_output_movies=%s"; %
>>> (args.host, args.port, camera, state), auth=(args.user, args.password))
>>> # Fake constant motion
>>> r = requests.get("http://%s:%s/%sconfig/set?emulate_motion=%s"; %
>>> (args.host, args.port, camera, state), auth=(args.user, args.password))
>>>
>>> And to disable recording when the motion event ends I use the same
>>> commands but with "state" set to "off" rather than "on".
>>>
>>> The recorded videos play for however long I have "ffmpeg_output_movies"
>>> and "emulate_motion" set to "on", but only the first 1-3 seconds are actual
>>> live video before the video freezes.
>>>
>>> It seems like a bug, but I'm writing in case I'm doing something that
>>> wasn't intended.
>>>
>>> Thanks for the help,
>>> Jon
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>
>>>
>>>
>>> _______________________________________________
>>> Motion-user mailing
>>> listMotion-user@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/motion-userhttps://motion-project.github.io/
>>>
>>> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>> _______________________________________________
>>> Motion-user mailing list
>>> Motion-user@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/motion-user
>>> https://motion-project.github.io/
>>>
>>> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>
>>
>>
>> _______________________________________________
>> Motion-user mailing
>> listMotion-user@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/motion-userhttps://motion-project.github.io/
>>
>> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
>>
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
------------------------------
Subject: Digest Footer
_______________________________________________
Motion-user mailing list
Motion-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/motion-user
------------------------------
End of Motion-user Digest, Vol 140, Issue 15
********************************************
