Send Motion-user mailing list submissions to
[email protected]
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
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Motion-user digest..."
Today's Topics:
1. Re: Preview Picture with Netcam_highres - Distorted Image (Gordon)
2. Re: Preview Picture with Netcam_highres - Distorted Image (Gordon)
----------------------------------------------------------------------
Message: 1
Date: Mon, 4 Dec 2017 13:36:41 -0600 (CST)
From: Gordon <[email protected]>
To: Motion discussion list <[email protected]>
Subject: Re: [Motion-user] Preview Picture with Netcam_highres -
Distorted Image
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="utf-8"
This may be related to the image corruption but more likely it is related to
the problem I describe below. Motion 4.1 terminates and will not restart
without a reboot of the system (Ubuntu 16.04 LTS server). Nothing is logged
when I try to restart motion with "sudo service motion start" command, but it
does start fine after the reboot.
The last thing in the log I see is:
motion_detected: Motion detected - starting event 59
vid_mjpegtoyuv420p: Corrupt image ... continue
jpgutl_error_exit: Unsupported marker type 0xf2
No start failure notice on the command line. It responds as if it started.
Nothing is logged in syslog after the error above until I reboot. I did
increase the logging to 9 before I reboot it but that didn't make a difference.
Under normal conditions I can start, stop, and restart Motion without a
problem.
The crash has happened twice so far.
But this may be triggered by a non-Motion problem I am having with two Amcrest
cameras. Those cameras are switching the main high-res stream setting from H264
to MJPEG on their own, almost as if they are on some sort of schedule or timer.
The Motion crash may occur as a result of the setting change. I can't say for
sure because I can't determine the time when the cameras switch to MJPEG. But
that H264-MJPEG switch has happened twice, and the 2 crash events may have been
around the same time.
Thank you.
From: "MrDave" <[email protected]>
To: [email protected]
Sent: Monday, November 27, 2017 9:21:55 PM
Subject: Re: [Motion-user] Preview Picture with Netcam_highres - Distorted
Image
I've been able to recreate this and have opened a issue for tracking. It occurs
whenever the "first", "Center" or "Best" option is selected. When it is only
specified as "on", the high resolution image is saved.
Thanks.
MrDave
On 11/27/2017 5:50 PM, Gordon wrote:
Thank you for the new netcam_highres option in Motion 4.1. High-res movie file
creation (H.264, 720P) and motion detection works fine with an Amcrest camera
set with low-res substream (H.264, VGA) enabled. However using the options
below at the same time:
output_pictures best
picture_filename preview
...creates a distorted preview picture. It is green tint and is the same size
of the high-res video (1280*720), but it looks like it is composed of two of
the low-res images side by side at the top, with a dark green band on the
bottom. I can tell it's referencing the low-res feed because I can see the text
overlay in the image that the documentation states will not appear on the
high-res video when netcam_highres is used. I'm not sure how that could happen
because a low-res video is not being recorded. It is only being used to detect
motion in this case.
In the network cameraX.conf file I set:
width 640
height 480
...to match the low-res feed from the camera Motion is using to detect motion,
not matching the resolution of the high-res feed being recorded. I assume that
is correct.
The best/preview picture works properly without distortion on a cameraX.conf
file for a USB camera connected to the same system, where netcam_highres is not
in use.
Thank you.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! [ http://sdm.link/slashdot |
http://sdm.link/slashdot ]
_______________________________________________
Motion-user mailing list [ mailto:[email protected] |
[email protected] ] [
https://lists.sourceforge.net/lists/listinfo/motion-user |
https://lists.sourceforge.net/lists/listinfo/motion-user ] [
https://motion-project.github.io/ | https://motion-project.github.io/ ]
Unsubscribe: [ https://lists.sourceforge.net/lists/options/motion-user |
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/motion-user
https://motion-project.github.io/
Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 2
Date: Mon, 4 Dec 2017 14:05:03 -0600 (CST)
From: Gordon <[email protected]>
To: Motion discussion list <[email protected]>
Subject: Re: [Motion-user] Preview Picture with Netcam_highres -
Distorted Image
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="utf-8"
It looks like it is the original picture corruption problem causing the crash,
not the second problem I mentioned.
I had temporarily disabled all pictures by setting "output_pictures off" in
case that was the problem, but tried to re-enable it just now to prevent making
too many changes at once to help isolate the problem. With "output_pictures
best" set again Motion died again not long after the restart. I changed it back
to "off" and will reboot.
I checked and the Amcrest cameras are still on H264 so no problem there.
From: "Gordon" <[email protected]>
To: "Motion discussion list" <[email protected]>
Sent: Monday, December 4, 2017 2:36:41 PM
Subject: Re: [Motion-user] Preview Picture with Netcam_highres - Distorted
Image
This may be related to the image corruption but more likely it is related to
the problem I describe below. Motion 4.1 terminates and will not restart
without a reboot of the system (Ubuntu 16.04 LTS server). Nothing is logged
when I try to restart motion with "sudo service motion start" command, but it
does start fine after the reboot.
The last thing in the log I see is:
motion_detected: Motion detected - starting event 59
vid_mjpegtoyuv420p: Corrupt image ... continue
jpgutl_error_exit: Unsupported marker type 0xf2
No start failure notice on the command line. It responds as if it started.
Nothing is logged in syslog after the error above until I reboot. I did
increase the logging to 9 before I reboot it but that didn't make a difference.
Under normal conditions I can start, stop, and restart Motion without a
problem.
The crash has happened twice so far.
But this may be triggered by a non-Motion problem I am having with two Amcrest
cameras. Those cameras are switching the main high-res stream setting from H264
to MJPEG on their own, almost as if they are on some sort of schedule or timer.
The Motion crash may occur as a result of the setting change. I can't say for
sure because I can't determine the time when the cameras switch to MJPEG. But
that H264-MJPEG switch has happened twice, and the 2 crash events may have been
around the same time.
Thank you.
From: "MrDave" <[email protected]>
To: [email protected]
Sent: Monday, November 27, 2017 9:21:55 PM
Subject: Re: [Motion-user] Preview Picture with Netcam_highres - Distorted
Image
I've been able to recreate this and have opened a issue for tracking. It occurs
whenever the "first", "Center" or "Best" option is selected. When it is only
specified as "on", the high resolution image is saved.
Thanks.
MrDave
On 11/27/2017 5:50 PM, Gordon wrote:
Thank you for the new netcam_highres option in Motion 4.1. High-res movie file
creation (H.264, 720P) and motion detection works fine with an Amcrest camera
set with low-res substream (H.264, VGA) enabled. However using the options
below at the same time:
output_pictures best
picture_filename preview
...creates a distorted preview picture. It is green tint and is the same size
of the high-res video (1280*720), but it looks like it is composed of two of
the low-res images side by side at the top, with a dark green band on the
bottom. I can tell it's referencing the low-res feed because I can see the text
overlay in the image that the documentation states will not appear on the
high-res video when netcam_highres is used. I'm not sure how that could happen
because a low-res video is not being recorded. It is only being used to detect
motion in this case.
In the network cameraX.conf file I set:
width 640
height 480
...to match the low-res feed from the camera Motion is using to detect motion,
not matching the resolution of the high-res feed being recorded. I assume that
is correct.
The best/preview picture works properly without distortion on a cameraX.conf
file for a USB camera connected to the same system, where netcam_highres is not
in use.
Thank you.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! [ http://sdm.link/slashdot |
http://sdm.link/slashdot ]
_______________________________________________
Motion-user mailing list [ mailto:[email protected] |
[email protected] ] [
https://lists.sourceforge.net/lists/listinfo/motion-user |
https://lists.sourceforge.net/lists/listinfo/motion-user ] [
https://motion-project.github.io/ | https://motion-project.github.io/ ]
Unsubscribe: [ https://lists.sourceforge.net/lists/options/motion-user |
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
[email protected]
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/motion-user
https://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
[email protected]
https://lists.sourceforge.net/lists/listinfo/motion-user
------------------------------
End of Motion-user Digest, Vol 138, Issue 1
*******************************************
