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. clip quality issues (B?lint Tak?cs)
----------------------------------------------------------------------
Message: 1
Date: Wed, 14 Aug 2019 10:15:34 +0200
From: B?lint Tak?cs <tak...@gmail.com>
To: motion-user@lists.sourceforge.net
Subject: [Motion-user] clip quality issues
Message-ID:
<CA+qeA5ijmLTkDTxTqt5YoB9uEzAWhNfHWUwbY=fkfsmsryb...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi,
I am trying to use motion for my 4x RLC-WS411 camera setup over 896x512 25
fps streams.
OS is Ubuntu 18.04, first trying the official package, then the latest git
master that I have compiled myself.
My problem is that motion output clips that seems to have frame repeats and
missing segments. However, running "ffmpeg -i rtmp://URL -vcodec copy
-acodec copy out.mp4 "runs without problems, and the generated clips are
perfect.
I am connecting through rtmp as rtsp generates lots of artifacts. The
connection is wifi, and the connection does seem to have drops, but
generally, this stream is possible to view without any problems in the
camera's own client. (The high quality stream is over the available
bandwidth.)
The CPU is an 8-core Ryzen. 'top' shows motion to run at 30-50% on one core
(with 4 cams). Also has a relatively weak Nvidia 610 card, but I suspect it
is not used anywhere.
I have also noticed that with movie_passthrough on, the recorded .mp4 clips
seems to have garbled timestamps, at least VirtualDub gets quite confused
when reading them, showing impossible lengths. Sometimes this occurs with
passthrough off as well, and the motion clips or pictures also have this
problem.
Also noticed that with movie_passthrough off, the recorded clips are 30x
bigger in size.
I have tried the following:
1. recoding frames with picture save. At the problematic parts, motion
outputs the same frame repeatedly. It does not seem to skip frames that
time, only later.
2. flipping options netcam_use_tcp and movie_passthrough, no change.
3. increasing framerate, pre_capture, post_capture values to large numbers.
No change.
4. removing filters to limit the impact of processing - no change.
5. Given the .logs had lots of resizing messages, I have tried increasing
the packet ring buffer size in netcam_rtsp.c from 30 to 512. This seems to
have a positive effect if passthrough is off, the pauses are smaller,
although the repeated frame issue remains.
Attached my current motion.conf I am using to experiment with, a camera
setup, and a sample .log file.
I have also noticed that the .log has this impossible entries like
"event_new_video: Source FPS 751"; maybe that gives a hint.
Any ideas what to try?
Many thanks for your help,
Balint
-------------- next part --------------
An HTML attachment was scrubbed...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: camera-back_in.conf
Type: application/octet-stream
Size: 236 bytes
Desc: not available
-------------- next part --------------
A non-text attachment was scrubbed...
Name: motion.conf
Type: application/octet-stream
Size: 4934 bytes
Desc: not available
-------------- next part --------------
A non-text attachment was scrubbed...
Name: motion.log
Type: application/octet-stream
Size: 39470 bytes
Desc: not available
------------------------------
------------------------------
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 158, Issue 24
********************************************
