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: AllSky Camera - Absolute exposure (Bryan Ramsey)
2. pixelation (Harlan Daneker)
----------------------------------------------------------------------
Message: 1
Date: Sat, 30 Jun 2018 23:48:55 +0000
From: "Bryan Ramsey" <pterod...@gmail.com>
To: "Motion discussion list" <motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] AllSky Camera - Absolute exposure
Message-ID: <emfcd8109d-62a5-4a94-8838-48f7bd2c18ac@pteromobile>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Thanks for that! Working putting the paramters in the config file
directly as in:
for day mode:
vid_control_params ID10094849=1,"ID09963795=260, ID10094850=1
derived from the log:
v4l2_ctrls_list: ID09963776 Brightness, 0 to 63
v4l2_ctrls_list: ID09963792 Gamma, 1 to 500
v4l2_ctrls_list: ID09963795 Gain, 260 to 1023
v4l2_ctrls_list: ID10094849 Exposure, Auto, 0 to 3
v4l2_ctrls_list: menu item: Value 1 Manual Mode
v4l2_ctrls_list: menu item: Value 3 Aperture Priority Mode
v4l2_ctrls_list: ID10094850 Exposure (Absolute), 1 to 36000000
so that is Exposure set to manual, and then the two lowest possible
values for daytime (this camera is overexposed even at the lowest
setting.
then night, 60 seconds is adequate:
vid_control_params ID10094849=1,"ID09963795=800, ID10094850=60000
still on manual, Gain of 800 and exposure of 60 seconds.
I can of course use cron or something else to change out the settings
even at sunset using the program sunwait.
Still it would be better to use auto_brightness. I know that the windows
WDM driver for this camera can't adjust auto brightness past .5 seconds
but I suspect since motion is entirely different that wouldn't be an
issue.
The only thing I don't understand now is how do I change the
auto_brightness parameter to use absolute exposure with a target of 128?
The old config file had a brightness parameter that states that it
works in tandem with auto_brightness. I don't see that parameter
anymore.
Thanks again!
Bryan Ramsey
------ Original Message ------
From: "MrDave" <motionmrd...@gmail.com>
To: motion-user@lists.sourceforge.net
Sent: 6/29/2018 11:11:21 PM
Subject: Re: [Motion-user] AllSky Camera - Absolute exposure
>The configuration parameter of "vid_control_params" which allows for
>specification of any v4l2 parameter within Motion is not in version
>4.1. It will be part of the next release. You would need to build
>your own deb or build from source from the master branch to get this.
>
>Link to get to the build deb script:
>https://motion-project.github.io/motion_download.html
>
>General build from source guide:
>https://motion-project.github.io/motion_build.html
>
>
>
>
>On 6/29/2018 7:06 PM, Bryan Ramsey wrote:
>>Thanks to everyone who has made this project. It's great and easy to
>>setup for most normal applications. My application is a bit different
>>however, and I like motion for all the obvious reasons.
>>
>>Primary need: Ability to set v4l2-ctl absolute_exposure to 60 seconds
>>or more for night time images of the entire sky.
>> - Or equivalent. Ive experimented with trying to set absolute
>>exposure using vid_control_params, but that interface doesn't seem to
>>pull the absolute exposure that v4l2-ctrl does
>>Secondary optional need: Be able to switch to a daytime profile that
>>is using automatic exposure.
>>
>>Specs:
>>
>>Raspberry PI 3 B - Raspbian stretch
>>Imaging Source DFX21BU04 (ID 199e:8101 The Imaging Source Europe GmbH
>>DFx 21BU04 Camera)
>>Motion 4.1.1
>>
>>Output of V4l2-ctl
>>
>>v4l2-ctl -l
>> brightness (int) : min=0 max=63 step=1
>>default=-8193 value=62
>> gamma (int) : min=1 max=500 step=1
>>default=57343 value=100
>> gain (int) : min=260 max=1023 step=1
>>default=57343 value=260
>> exposure_auto (menu) : min=0 max=3 default=0
>>value=3
>> exposure_absolute (int) : min=1 max=36000000 step=1
>>default=333 value=1 flags=inactive
>>
>>
>>
>>Mostly I have used Indilib to capture images which also uses v4l2 on
>>this camera and I can take images up to 1 hour exposure time.
>>
>>I can control the exposure to 60 seconds and the gain to 800 using
>>v4l2-ctl:
>>
>>v4l2-ctl --set-ctrl=exposure_absolute=60000 --set-ctrl=gain=800
>>
>>But motion seems to override even though I currently have
>>autobrightness off in motion.conf
>>
>>As to the vid_control_params, it would be nice if I could used
>>absolute exposure there, but I set my log to INF level and I don't see
>>that control:
>>
>>cap.driver: "uvcvideo"
>>cap.card: "DMx 41AU02.AS <http://41au02.as/>: DMx 41AU02.AS
>><http://41au02.as/>"
>>cap.bus_info: "usb-3f980000.usb-1.4"
>>cap.capabilities=0x84200001
>>------------------------
>>[1:ml1] [NTC] [VID] [Jun 29 18:25:58] v4l2_get_capability: -
>>VIDEO_CAPTURE
>>[1:ml1] [NTC] [VID] [Jun 29 18:25:58] v4l2_get_capability: - STREAMING
>>[1:ml1] [NTC] [VID] [Jun 29 18:25:58] v4l2_select_input: name =
>>"Camera 1", type 0x00000002, status 00000000
>>[1:ml1] [NTC] [VID] [Jun 29 18:25:58] v4l2_select_input: - CAMERA
>>[1:ml1] [NTC] [VID] [Jun 29 18:25:58] v4l2_select_input: Device does
>>not support specifying PAL/NTSC norm
>>[1:ml1] [NTC] [VID] [Jun 29 18:25:58] v4l2_do_set_pix_format: Testing
>>palette GREY (1280x960)
>>[1:ml1] [NTC] [VID] [Jun 29 18:25:58] v4l2_do_set_pix_format: Using
>>palette GREY (1280x960) bytesperlines 1280 sizeimage 1228800
>>colorspace 00000000
>>[1:ml1] [NTC] [VID] [Jun 29 18:25:58] v4l2_scan_controls: found
>>control 0x00980900, "Brightness", range 0,63
>>[1:ml1] [NTC] [VID] [Jun 29 18:25:58] v4l2_scan_controls:
>>"Brightness", default -8193, current 0
>>[1:ml1] [NTC] [VID] [Jun 29 18:25:58] v4l2_scan_controls: found
>>control 0x00980910, "Gamma", range 1,500
>>[1:ml1] [NTC] [VID] [Jun 29 18:25:58] v4l2_scan_controls:
>>"Gamma", default 57343, current 100
>>[1:ml1] [NTC] [VID] [Jun 29 18:25:58] v4l2_scan_controls: found
>>control 0x00980913, "Gain", range 260,1023
>>[1:ml1] [NTC] [VID] [Jun 29 18:25:58] v4l2_scan_controls:
>>"Gain", default 57343, current 800
>>[1:ml1] [NTC] [ALL] [Jun 29 18:25:58] image_ring_resize: Resizing
>>pre_capture buffer to 1 items
>>[1:ml1] [NTC] [STR] [Jun 29 18:25:58] http_bindsock: listening on any
>>IPv4 address port 8081
>>
>>
>>I suppose if that feature worked, I could ask for a frame with a
>>median exposure of 128 and have it adjust the exposure until it
>>reaches it, even into the 60 second range for night sky and
>>milliseconds for the day time. My old windows based Allsky camera
>>software took a center portion of the frame and essentially did that,
>>but alas the camera is on it's own now in a housing with a raspberry
>>pi.
>>
>>any thoughts would be appreciated!
>>
>>thanks.
>>
>>
>>Bryan Ramsey
>>
>>
>>
>>------------------------------------------------------------------------------
>>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.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...
------------------------------
Message: 2
Date: Sun, 1 Jul 2018 04:30:19 -0400
From: Harlan Daneker <hdane...@gmail.com>
To: Motion discussion list <motion-user@lists.sourceforge.net>
Subject: [Motion-user] pixelation
Message-ID:
<CAC1WkiS5ADWM2rk_KhLJwCzU8_J9siYGa2jpuEg6=efbdZ=d...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi:
Fedora 28 OS - Intel I3 - ASUS MB
I'm using a bluecherry PV-981 4 port PCIE video capture card with 4
Hikvision cameras.
https://store.bluecherry.net/product/pv-981-4-port-video-cap
ture-card-120fps-realtime-recording-pci-e-version/
https://www.amazon.com/gp/product/B00QL4TQ72/ref=oh_aui_sear
ch_detailpage?ie=UTF8&psc=1
https://www.youtube.com/watch?v=zCg470ZmHq8
30 FPS
ffmpeg_bps 1200000
I'm getting pixelation when I record. I didn't notice this as much with
older versions of motion. Is something being done differently with the way
ffmpeg is implemented in the newer versions of motion > 3?
Any ideas how I could improve my recording when motion is detected?
ffplay /dev/video0 it looks good
Viewing through motion real time 1 FPS it looks good
Thanks
-------------- 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 145, Issue 1
*******************************************
