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: H.265 (HEVC) netcam and motion (Scott Holmes)
   2. Re: H.265 (HEVC) netcam and motion (MrDave)
   3. Re: H.265 (HEVC) netcam and motion (Scott Holmes)


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

Message: 1
Date: Thu, 5 Jul 2018 20:46:07 +0000 (UTC)
From: Scott Holmes <[email protected]>
To: Motion discussion list <[email protected]>
Subject: Re: [Motion-user] H.265 (HEVC) netcam and motion
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"

I tried ffplay last night.? The camera works with ffplay in both H.2645 and 
H.265 modes.

For the record, I'm running Motion v4.1.1+git46be66f.? Is it worth trying the 
latest non-stable version?


------------------------------------------- Scott Holmes, [email protected] 
------------------------------------------- 

    On Thursday, 5 July 2018, 10:30:05 am AEST, MrDave <[email protected]> 
wrote: 

I would say to try ffplay with the url to be sure in addition to checking all 
the parameters inside the camera set up.? Some of my cameras are H265 and they 
work.? 
 
 
  
-------------- next part --------------
An HTML attachment was scrubbed...

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

Message: 2
Date: Thu, 5 Jul 2018 17:41:41 -0600
From: MrDave <[email protected]>
To: Scott Holmes via Motion-user <[email protected]>
Subject: Re: [Motion-user] H.265 (HEVC) netcam and motion
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"; Format="flowed"

I would say that you do not need to try the latest version. There has 
not been much with respect to opening files implemented.? Motion simply 
provides a URL to the ffmpeg libs and lets ffmpeg figure out the 
encoding.? The particular function Motion is failing upon with the 
"operation not permitted" is the "avformat_find_stream_info" function 
which is part of ffmpeg.

If you've built from source or are using a version of ffmpeg which isn't 
part of your package manager, make sure that the version of ffplay that 
was able to open the file is in sync with the library versions being 
used by Motion.? When you start ffplay it reports out the library 
version it is using.? Validate those are exactly the same library 
versions that Motion is reporting in its log. (Motion only reports two 
of the libraries but that is enough of a confirmation).

If they are the same version, I'm at a loss as to why it will not open.? 
>From the log, it does indicate problems with the DTS so perhaps an 
update ffmpeg is needed?


On 7/5/2018 2:46 PM, Scott Holmes via Motion-user wrote:
> I tried ffplay last night.? The camera works with ffplay in both 
> H.2645 and H.265 modes.
>
> For the record, I'm running Motion v4.1.1+git46be66f.? Is it worth 
> trying the latest non-stable version?
>
>
> ------------------------------------------- Scott Holmes, 
> [email protected] -------------------------------------------
>
>
> On Thursday, 5 July 2018, 10:30:05 am AEST, MrDave 
> <[email protected]> wrote:
>
> I would say to try ffplay with the url to be sure in addition to 
> checking all the parameters inside the camera set up.? Some of my 
> cameras are H265 and they work.
>
>
>
>
> ------------------------------------------------------------------------------
> 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: 3
Date: Fri, 6 Jul 2018 05:05:10 +0000 (UTC)
From: Scott Holmes <[email protected]>
To: Motion discussion list <[email protected]>
Subject: Re: [Motion-user] H.265 (HEVC) netcam and motion
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"

Thanks MrDave.? I think you are on to something.

Output from ffplay:

? libavutil????? 55. 34.101 / 55. 34.101
? libavcodec???? 57. 64.101 / 57. 64.101
? libavformat??? 57. 56.101 / 57. 56.101
? libavdevice??? 57.? 1.100 / 57.? 1.100
? libavfilter???? 6. 65.100 /? 6. 65.100
? libavresample?? 3.? 1.? 0 /? 3.? 1.? 0
? libswscale????? 4.? 2.100 /? 4.? 2.100
? libswresample?? 2.? 3.100 /? 2.? 3.100
? libpostproc??? 54.? 1.100 / 54.? 1.100


Output from motion:

 
[0:motion] [NTC] [ENC] [Jul 06 14:41:08] ffmpeg_global_init: ffmpeg libavcodec 
version 56.1.0 libavformat version 56.1.0


The next question is: how do I force motion to use libavcodec57?? I've 
re-compiled from source, but it still uses libavcodec v56.1.0.? Should I remove 
the package libavcodec56? (I'm using Debian Jessie).



    On Friday, 6 July 2018, 9:42:23 am AEST, MrDave <[email protected]> 
wrote:  
 
  
I would say that you do not need to try the latest version.? There has not been 
much with respect to opening files implemented.? Motion simply provides a URL 
to the ffmpeg libs and lets ffmpeg figure out the encoding.? The particular 
function Motion is failing upon with the "operation not permitted" is the 
"avformat_find_stream_info" function which is part of ffmpeg.? 
 
If you've built from source or are using a version of ffmpeg which isn't part 
of your package manager, make sure that the version of ffplay that was able to 
open the file is in sync with the library versions being used by Motion.? When 
you start ffplay it reports out the library version it is using.? Validate 
those are exactly the same library versions that Motion is reporting in its 
log. (Motion only reports two of the libraries but that is enough of a 
confirmation).?? 
 
 
If they are the same version, I'm at a loss as to why it will not open.? From 
the log, it does indicate problems with the DTS so perhaps an update ffmpeg is 
needed?
 
 
  
-------------- 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 145, Issue 17
********************************************

Reply via email to