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: How view alternate /dev/video channel? (Barry Martin)
   2. Re: How view alternate /dev/video channel? (David Powell)
   3. Re: How view alternate /dev/video channel? (Barry Martin)


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

Message: 1
Date: Tue, 8 Jun 2021 10:22:34 -0500
From: Barry Martin <barry3mar...@gmail.com>
To: motion-user@lists.sourceforge.net
Subject: Re: [Motion-user] How view alternate /dev/video channel?
Message-ID: <b1a54050-3076-8064-2966-8b6696b60...@gmail.com>
Content-Type: text/plain; charset="utf-8"; Format="flowed"

Hi tosiaria!

> Input pixel format does not affect recorded movie size directly. Both 
> MJPEG and H264 will be converted into raw 420 and then encoded into 
> whatever you have configured.
> It will only have difference if you use passthrough which skips 
> encoding of the movies at all and writes the stream as-is

Found if I use the second ?channel? (for lack of a better term) of the 
camera ? *netcam_url v4l2:///dev/video2* ? then moving stuff like cars 
and pedestrians have a ?pixelation smear? while the rest of the image 
remains clear. If switch back to the primary ?channel? ? ? *netcam_url 
v4l2:///dev/video**0* ? then normal.


Tried to test using VLC but it wouldn?t open the camera; I don?t know if 
the second ?channel (video2) had the same pixelation smear issue as very 
low activity out there so maybe just didn?t notice.


Right now waiting for Mother Nature to warm things up ? if accessing 
using netcam_url works when the Storage Area is hot either ?channel? is 
fine as long as it works.


Barry



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

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

Message: 2
Date: Tue, 08 Jun 2021 12:48:09 -0500
From: David Powell <da...@depowell.com>
To: Motion discussion list <motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] How view alternate /dev/video channel?
Message-ID:
        <179ecbd23a8.279e.ce3d8395e0ae66063e5e142696dac...@depowell.com>
Content-Type: text/plain; charset="utf-8"; Format="flowed"

Most IP cameras support two streams, one at a high resolution and one at a 
lower resolution.  Motion lets you use the lower res one for motion 
detection and record the other when motion is detected.  I bet it's the 
high res stream that is smearing due to insufficient horsepower in the PC 
or camera.

On June 8, 2021 10:24:14 AM Barry Martin <barry3mar...@gmail.com> wrote:
>
> Hi tosiaria!
>
>> Input pixel format does not affect recorded movie size directly. Both MJPEG 
>> and H264 will be converted into raw 420 and then encoded into whatever you 
>> have configured.
>> It will only have difference if you use passthrough which skips encoding of 
>> the movies at all and writes the stream as-is
>
> Found if I use the second ?channel? (for lack of a better term) of the 
> camera ? netcam_url v4l2:///dev/video2 ? then moving stuff like cars and 
> pedestrians have a ?pixelation smear? while the rest of the image remains 
> clear. If switch back to the primary ?channel? ? ? netcam_url 
> v4l2:///dev/video0 ? then normal.
>
> Tried to test using VLC but it wouldn?t open the camera; I don?t know if 
> the second ?channel (video2) had the same pixelation smear issue as very 
> low activity out there so maybe just didn?t notice.
>
> Right now waiting for Mother Nature to warm things up ? if accessing using 
> netcam_url works when the Storage Area is hot either ?channel? is fine as 
> long as it works.
>
> Barry
>
>
>
> _______________________________________________
> 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...

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

Message: 3
Date: Tue, 8 Jun 2021 14:38:36 -0500
From: Barry Martin <barry3mar...@gmail.com>
To: motion-user@lists.sourceforge.net
Subject: Re: [Motion-user] How view alternate /dev/video channel?
Message-ID: <600e00fc-199b-c890-156e-355bcb051...@gmail.com>
Content-Type: text/plain; charset="utf-8"; Format="flowed"


Hi David!


> Most IP cameras support two streams, one at a high resolution and one 
> at a lower resolution.? Motion lets you use the lower res one for 
> motion detection and record the other when motion is detected.? I bet 
> it's the high res stream that is smearing due to insufficient 
> horsepower in the PC or camera.

You seem to be right; not quite sure about ?resolution? in the way I 
usually think about it (?1280x720?) but the ?pixelation-smear? on the 
second stream I could also interpret as ?resolution?.


I have been play? err, experimenting and VLC also shows the same 
smearing, so not apparently not an issue with Motion. At least now I 
know to only use the ?primary? stream.


I?m going back to my original configuration of *videodevice /dev/video0* 
as the *netcam_url v4l2:///dev/video**0* isn?t recording; probably 
something semi-simple but easier to keep everything the same amongst the 
various units.? Plus it is a USB camera.


Thanks for the hint!


Barry


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

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



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

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 180, Issue 8
*******************************************

Reply via email to