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. Blurry image after few seconds (Clara Anton)
   2. Re: Lines on displayed image (Timothy Buchanan)


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

Message: 1
Date: Tue, 26 Dec 2017 16:07:36 +0100
From: Clara Anton <canto...@mtu.edu>
To: motion-user@lists.sourceforge.net
Subject: [Motion-user] Blurry image after few seconds
Message-ID: <4d9fb4bf-b4f5-cb94-5521-3a8f7b4fc...@mtu.edu>
Content-Type: text/plain; charset="utf-8"; Format="flowed"

Hi,

I am using motion 4.1.1+dirty20171217-35cd0b3 (from source) on raspbian 
stretch. I am trying to monitor a uniti G3 camera through rtsp.

After starting motion (rtsp_uses_tcp on) I get a short video where 
everything looks fine. When an event starts (not a real event but it 
detects something) I get a video where the upper half (approximately) of 
the image looks fine and the other half blurred. I think the change in 
the quality of the image triggers an event.

If I run ffmpeg -rtsp_transport tcp? -i? rtsp://some.ip -acodec copy 
-vcodec copy /media/pi/motion/lala2.mp4 everything looks fine (I run it 
for about 2 mins), no error, perfect image.

My log (level 6) looks fine, but on level 9 I get lots of errors like this

[3:nc3] [INF] [ENC] [Dec 25 20:45:46] ffmpeg_avcodec_log: error while 
decoding MB 103 26, bytestream -6


Which I don't get if I just run ffmpeg (with the example above). Any 
help is greatly appreciated.
Clara




-------------- next part --------------
An HTML attachment was scrubbed...

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

Message: 2
Date: Tue, 26 Dec 2017 10:14:35 -0700
From: Timothy Buchanan <timothyebucha...@gmail.com>
To: Motion discussion list <motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] Lines on displayed image
Message-ID: <020d7f52-79c1-4cba-87bf-0ee94148c...@gmail.com>
Content-Type: text/plain; charset="utf-8"

I upgraded to 4.1.1. Using netcam_url v4l2:///dev/video1 and each palette 0 
through 17 and 21, I get ?unable to open video device,? except with palette 8, 
which causes a program abort. Running ffplay ?f /dev/video1 produces a good 
image, though I get repeated warnings that the dequeued vl42 buff contains 
corrupted data (691200 bytes). Suggestions? Thanks.

 

Timothy

 

From: MrDave <motionmrd...@gmail.com>
Reply-To: Motion discussion list <motion-user@lists.sourceforge.net>
Date: Sunday, December 24, 2017 at 2:12 PM
To: <motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] Lines on displayed image

 

Yes, the v4l2 via the netcam_url option functionality was added starting in 
version 4.1 so it will not work with 4.0. 

Regarding the  "unhelpful" message on the standard being set.  45056 means it 
set it to V4L2_STD_NTSC.  Other video standards Motion may report are 16711680 
for V4L2_STD_SECAM and 255 for V4L2_STD_PAL.  (This is legacy code to print the 
number rather than a readable message).

This is the first that I've heard of a usb device reporting options to use 
different video standards so changing that parameter may assist.

MrDave

 

On 12/24/2017 11:46 AM, Timothy Buchanan wrote:


I decided to start again from scratch by installing stretch (had been using 
Jessie). The included add/remove GUI installed motion 4.0, not 4.1. That 
version?s motion.conf offers the netcam option, but using netcam_url 
v4l2:///dev/video0 returns a gray image with the error ?could not open.? Is it 
only 4.1 that works with netcam? Curiously, vlc media player will open the 
camera and display v4l2:///dev/video0 when doing so.

 

As to the usb-to-analog device, it is the UCEC adapter sold on amazon and has 
the UTV007 chipset. I have not installed any drivers. Where would I find the 
driver Linux is using?

 

Thanks again for help.

 

Timothy

 

From: tosiara <tosi...@gmail.com>
Reply-To: Motion discussion list <motion-user@lists.sourceforge.net>
Date: Thursday, December 21, 2017 at 9:59 AM
To: Motion discussion list <motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] Lines on displayed image

 

I have had some issues with usb-to-analog devices, like Easycap and similar. At 
that time indeed only motion had those issues, but after some changes in the 
driver the issues were resolved. So it could be some compatibility with the 
hardware's driver. Can you provide more details what kind of capture card you 
are using?

As a workaround you can use the way MrDave mentioned - capture through the 
netcam. Specify this url:
netcam_url v4l2:///dev/video0

Please report back if you still get corrupted image using netcam

 

On Thu, Dec 21, 2017 at 6:43 PM, Timothy Buchanan <timothyebucha...@gmail.com> 
wrote:

MrDave and tosiara, thanks for help. I?ve attached the motion log and output of 
one of the cameras (there are three, but all the same) to the command v4l2-ctl 
-d /dev/video0 ?all.

Palette YUYV seems to be the only one supported, and that is chosen. I set the 
config to use NTSC, but it always chooses ?standard method 45056.? I don?t find 
any info on that.

Do you see problems in the output files I?ve attached? Thanks again.

timothy




------------------------------------------------------------------------------
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




------------------------------------------------------------------------------
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

-------------- 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 138, Issue 14
********************************************

Reply via email to