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. Re: Freezing of movie output during short periods of      no
      motion (Colin Law)
   2. ioctl sign-extension warning on FreeBSD (Ben)


----------------------------------------------------------------------

Message: 1
Date: Fri, 19 May 2017 13:50:07 +0100
From: Colin Law <clan...@gmail.com>
To: Motion discussion list <motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] Freezing of movie output during short
        periods of      no motion
Message-ID:
        <CAL=0gLv6rofEbpHF=ddue2hgw2vzsjge1fw3o3k6gujhexs...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"

Having built the latest trunk version all is working as expected.

Thanks

Colin

On 18 May 2017 at 17:59, Colin Law <clan...@gmail.com> wrote:
> OK, thanks, I will give that a go.
>
> Colin
>
> On 17 May 2017 at 09:15, tosiara <tosi...@gmail.com> wrote:
>> The very first, I would suggest you to compile the latest trunk from github.
>> 4.0.1 is pretty wide range of version which also included bugs and fixes.
>>
>> On Wed, May 17, 2017 at 11:04 AM, Colin Law <clan...@gmail.com> wrote:
>>>
>>> Hi
>>>
>>> Using motion 4.0.1 from the Ubuntu 16.04 (Xenial) repository I am
>>> having a bit of difficulty with the movie output.  I have set
>>> event_gap to 10 and my understanding is that this means that if there
>>> is a gap between motion events of less than 10 seconds then the events
>>> will be concatenated into one event, and this does appear to be the
>>> case. The movie file output that I get in this case does consist of
>>> the two motion events together, but in the gap between instead of
>>> seeing the scene as it was during the gap the picture freezes and then
>>> starts again for the second motion event.
>>>
>>> So for example if there is motion for 5 seconds then 5 seconds without
>>> motion and a further 5 seconds of motion then the movie file is 15
>>> seconds long consisting of the first 5 seconds of motion, 5 seconds of
>>> frozen image and the second 5 seconds of motion.  It is clear that it
>>> is frozen as there is a section of the scene masked out with a mask
>>> file where there is ongoing activity. When I used an earlier version
>>> of Motion I believe that the movie skipped over periods of no motion,
>>> but I may be mistaken in this.
>>>
>>> Is this the expected way that Motion should perform?
>>>
>>> If it is not clear what I am trying to describe then I can probably
>>> extract a short section of video to demonstrate it.
>>>
>>> Below are what I hope are the relevant sections of the config:
>>>
>>> Cheers
>>>
>>> Colin
>>>
>>> ############################################################
>>> # Motion Detection Settings:
>>> ############################################################
>>>
>>> # Threshold for number of changed pixels in an image that
>>> # triggers motion detection (default: 1500)
>>> threshold 25
>>>
>>> # Automatically tune the threshold down if possible (default: off)
>>> threshold_tune off
>>>
>>> # Noise threshold for the motion detection (default: 32)
>>> noise_level 32
>>> #noise_level 16
>>>
>>> # Automatically tune the noise threshold (default: on)
>>> #noise_tune on
>>> noise_tune off
>>>
>>> # Despeckle motion image using (e)rode or (d)ilate or (l)abel
>>> (Default: not defined)
>>> # Recommended value is EedDl. Any combination (and number of) of E, e,
>>> d, and D is valid.
>>> # (l)abeling must only be used once and the 'l' must be the last letter.
>>> # Comment out to disable
>>> despeckle_filter EedDl
>>>
>>> # Detect motion in predefined areas (1 - 9). Areas are numbered like
>>> that:  1 2 3
>>> # A script (on_area_detected) is started immediately when motion is
>>>      4 5 6
>>> # detected in one of the given areas, but only once during an event.
>>>      7 8 9
>>> # One or more areas can be specified with this option. Take care: This
>>> option
>>> # does NOT restrict detection to these areas! (Default: not defined)
>>> ; area_detect value
>>>
>>> # PGM file to use as a sensitivity mask.
>>> # Full path name to. (Default: not defined)
>>> mask_file /home/colinl/Videos/motion/lawn.pgm
>>>
>>> # Dynamically create a mask file during operation (default: 0)
>>> # Adjust speed of mask changes from 0 (off) to 10 (fast)
>>> smart_mask_speed 0
>>>
>>> # Ignore sudden massive light intensity changes given as a percentage
>>> of the picture
>>> # area that changed intensity. Valid range: 0 - 100 , default: 0 =
>>> disabled
>>> lightswitch 30
>>>
>>> # Picture frames must contain motion at least the specified number of
>>> frames
>>> # in a row before they are detected as true motion. At the default of 1,
>>> all
>>> # motion is detected. Valid range: 1 to thousands, recommended 1-5
>>> minimum_motion_frames 1
>>>
>>> # Specifies the number of pre-captured (buffered) pictures from before
>>> motion
>>> # was detected that will be output at motion detection.
>>> # Recommended range: 0 to 5 (default: 0)
>>> # Do not use large values! Large values will cause Motion to skip
>>> video frames and
>>> # cause unsmooth movies. To smooth movies use larger values of
>>> post_capture instead.
>>> pre_capture 0
>>>
>>> # Number of frames to capture after motion is no longer detected (default:
>>> 0)
>>> post_capture 1
>>>
>>> # Event Gap is the seconds of no motion detection that triggers the
>>> end of an event.
>>> # An event is defined as a series of motion images taken within a
>>> short timeframe.
>>> # Recommended value is 60 seconds (Default). The value -1 is allowed
>>> and disables
>>> # events causing all Motion to be written to one single movie file and
>>> no pre_capture.
>>> # If set to 0, motion is running in gapless mode. Movies don't have
>>> gaps anymore. An
>>> # event ends right after no more motion is detected and post_capture is
>>> over.
>>> event_gap 10
>>>
>>> # Maximum length in seconds of a movie
>>> # When value is exceeded a new movie file is created. (Default: 0 =
>>> infinite)
>>> max_movie_time 600
>>>
>>> # Always save images even if there was no motion (default: off)
>>> emulate_motion off
>>>
>>> ############################################################
>>> # FFMPEG related options
>>> # Film (movies) file output, and deinterlacing of the video input
>>> # The options movie_filename and timelapse_filename are also used
>>> # by the ffmpeg feature
>>> ############################################################
>>>
>>> # Use ffmpeg to encode movies in realtime (default: off)
>>> ffmpeg_output_movies on
>>>
>>> # Use ffmpeg to make movies with only the pixels moving
>>> # object (ghost images) (default: off)
>>> ffmpeg_output_debug_movies off
>>>
>>> # Use ffmpeg to encode a timelapse movie
>>> # Default value 0 = off - else save frame every Nth second
>>> ffmpeg_timelapse 0
>>>
>>> # The file rollover mode of the timelapse video
>>> # Valid values: hourly, daily (default), weekly-sunday, weekly-monday,
>>> monthly, manual
>>> ffmpeg_timelapse_mode daily
>>>
>>> # Bitrate to be used by the ffmpeg encoder (default: 400000)
>>> # This option is ignored if ffmpeg_variable_bitrate is not 0 (disabled)
>>> ffmpeg_bps 400000
>>>
>>> # Enables and defines variable bitrate for the ffmpeg encoder.
>>> # ffmpeg_bps is ignored if variable bitrate is enabled.
>>> # Valid values: 0 (default) = fixed bitrate defined by ffmpeg_bps,
>>> # or the range 1 - 100 where 1 means worst quality and 100 is best.
>>> ffmpeg_variable_bitrate 0
>>>
>>> # Codec to used by ffmpeg for the video compression.
>>> # Timelapse videos have two options.
>>> #   mpg - Creates mpg file with mpeg-2 encoding.
>>> #     If motion is shutdown and restarted, new pics will be appended
>>> #     to any previously created file with name indicated for timelapse.
>>> #   mpeg4 - Creates avi file with the default encoding.
>>> #     If motion is shutdown and restarted, new pics will create a
>>> #     new file with the name indicated for timelapse.
>>> # Supported formats are:
>>> # mpeg4 or msmpeg4 - gives you files with extension .avi
>>> # msmpeg4 is recommended for use with Windows Media Player because
>>> # it requires no installation of codec on the Windows client.
>>> # swf - gives you a flash film with extension .swf
>>> # flv - gives you a flash video with extension .flv
>>> # ffv1 - FF video codec 1 for Lossless Encoding
>>> # mov - QuickTime
>>> # mp4 - MPEG-4 Part 14 H264 encoding
>>> # mkv - Matroska H264 encoding
>>> # hevc - H.265 / HEVC (High Efficiency Video Coding)
>>> ffmpeg_video_codec mpeg4
>>>
>>> # When creating videos, should frames be duplicated in order
>>> # to keep up with the requested frames per second
>>> # (default: true)
>>> ffmpeg_duplicate_frames false
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> 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 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: 2
Date: Fri, 26 May 2017 13:45:06 +0200
From: Ben <mot...@stuyts.nl>
To: motion-user@lists.sourceforge.net
Subject: [Motion-user] ioctl sign-extension warning on FreeBSD
Message-ID: <e92918ae-ded7-434a-9751-10a1d801e...@stuyts.nl>
Content-Type: text/plain; charset=utf-8

Hi,

I?m running Motion 4.0.1 on FreeBSD 10.3-STABLE amd64. I have four ipcams and 
one webcam (Logitech C920) connected and everything works fine except for one 
thing: the console gives a continues stream of messages like this:

May 26 13:42:11 aurora kernel: WARNING pid 40273 (motion): ioctl sign-extension 
ioctl ffffffffc058560f
May 26 13:42:11 aurora kernel: WARNING pid 40273 (motion): ioctl sign-extension 
ioctl ffffffffc0585611
May 26 13:42:11 aurora kernel: WARNING pid 40273 (motion): ioctl sign-extension 
ioctl ffffffffc058560f
May 26 13:42:11 aurora kernel: WARNING pid 40273 (motion): ioctl sign-extension 
ioctl ffffffffc0585611
? etc

It seems to come from the USB camera, because these message are gone when I 
disable it. I can?t find which call is causing this warning message. It seems 
to be harmless except that it?s filling up my log files in high tempo.

Any ideas for solving this problem?

Thanks,
Ben




------------------------------

------------------------------------------------------------------------------
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 131, Issue 3
*******************************************

Reply via email to