Recherche avancée

Sur d’autres sites (10058)

• TCP connection refused with FFMPEG

  2 février 2017, par Samul

  OFFICIAL EDIT :

  I thank you so much for your help but I am still encountering problems.

  My ffserver.conf file is like this :

  # Port on which the server is listening. You must select a different
  
  # port from your standard HTTP web server if it is running on the same
  
  # computer.
  
  HTTPPort 8090
  
  
  
  # Address on which the server is bound. Only useful if you have
  
  # several network interfaces.
  
  HTTPBindAddress 0.0.0.0
  
  
  
  # Number of simultaneous HTTP connections that can be handled. It has
  
  # to be defined *before* the MaxClients parameter, since it defines the
  
  # MaxClients maximum limit.
  
  MaxHTTPConnections 2000
  
  
  
  # Number of simultaneous requests that can be handled. Since FFServer
  
  # is very fast, it is more likely that you will want to leave this high
  
  # and use MaxBandwidth, below.
  
  MaxClients 1000
  
  
  
  # This the maximum amount of kbit/sec that you are prepared to
  
  # consume when streaming to clients.
  
  MaxBandwidth 1000
  
  
  
  # Access log file (uses standard Apache log file format)
  
  # '-' is the standard output.
  
  CustomLog -
  
  
  
  ##################################################################
  
  # Definition of the live feeds. Each live feed contains one video
  
  # and/or audio sequence coming from an ffmpeg encoder or another
  
  # ffserver. This sequence may be encoded simultaneously with several
  
  # codecs at several resolutions.
  
  
  
  <feed>
  
  
  
  # You must use 'ffmpeg' to send a live feed to ffserver. In this
  
  # example, you can type:
  
  #
  
  # ffmpeg http://localhost:8090/feed1.ffm
  
  
  
  # ffserver can also do time shifting. It means that it can stream any
  
  # previously recorded live stream. The request should contain:
  
  # "http://xxxx?date=[YYYY-MM-DDT][[HH:]MM:]SS[.m...]".You must specify
  
  # a path where the feed is stored on disk. You also specify the
  
  # maximum size of the feed, where zero means unlimited. Default:
  
  # File=/tmp/feed_name.ffm FileMaxSize=5M
  
  File /tmp/feed1.ffm
  
  FileMaxSize 200K
  
  
  
  # You could specify
  
  # ReadOnlyFile /saved/specialvideo.ffm
  
  # This marks the file as readonly and it will not be deleted or updated.
  
  
  
  # Specify launch in order to start ffmpeg automatically.
  
  # First ffmpeg must be defined with an appropriate path if needed,
  
  # after that options can follow, but avoid adding the http:// field
  
  #Launch ffmpeg
  
  
  
  # Only allow connections from localhost to the feed.
  
  #ACL allow 127.0.0.1
  
  #ACL allow 189.34.0.158
  
  </feed>
  
  
  
  
  
  ##################################################################
  
  # Now you can define each stream which will be generated from the
  
  # original audio and video stream. Each format has a filename (here
  
  # 'test1.mpg'). FFServer will send this stream when answering a
  
  # request containing this filename.
  
  
  
  <stream>
  
  
  
  # coming from live feed 'feed1'
  
  Feed feed1.ffm
  
  
  
  # Format of the stream : you can choose among:
  
  # mpeg       : MPEG-1 multiplexed video and audio
  
  # mpegvideo  : only MPEG-1 video
  
  # mp2        : MPEG-2 audio (use AudioCodec to select layer 2 and 3 codec)
  
  # ogg        : Ogg format (Vorbis audio codec)
  
  # rm         : RealNetworks-compatible stream. Multiplexed audio and video.
  
  # ra         : RealNetworks-compatible stream. Audio only.
  
  # mpjpeg     : Multipart JPEG (works with Netscape without any plugin)
  
  # jpeg       : Generate a single JPEG image.
  
  # asf        : ASF compatible streaming (Windows Media Player format).
  
  # swf        : Macromedia Flash compatible stream
  
  # avi        : AVI format (MPEG-4 video, MPEG audio sound)
  
  Format mpeg
  
  
  
  # Bitrate for the audio stream. Codecs usually support only a few
  
  # different bitrates.
  
  AudioBitRate 32
  
  
  
  # Number of audio channels: 1 = mono, 2 = stereo
  
  AudioChannels 1
  
  
  
  # Sampling frequency for audio. When using low bitrates, you should
  
  # lower this frequency to 22050 or 11025. The supported frequencies
  
  # depend on the selected audio codec.
  
  AudioSampleRate 44100
  
  
  
  # Bitrate for the video stream
  
  VideoBitRate 64
  
  
  
  # Ratecontrol buffer size
  
  VideoBufferSize 40
  
  
  
  # Number of frames per second
  
  VideoFrameRate 3
  
  
  
  # Size of the video frame: WxH (default: 160x128)
  
  # The following abbreviations are defined: sqcif, qcif, cif, 4cif, qqvga,
  
  # qvga, vga, svga, xga, uxga, qxga, sxga, qsxga, hsxga, wvga, wxga, wsxga,
  
  # wuxga, woxga, wqsxga, wquxga, whsxga, whuxga, cga, ega, hd480, hd720,
  
  # hd1080
  
  VideoSize 160x128
  
  
  
  # Transmit only intra frames (useful for low bitrates, but kills frame rate).
  
  #VideoIntraOnly
  
  
  
  # If non-intra only, an intra frame is transmitted every VideoGopSize
  
  # frames. Video synchronization can only begin at an intra frame.
  
  VideoGopSize 12
  
  
  
  # More MPEG-4 parameters
  
  # VideoHighQuality
  
  # Video4MotionVector
  
  
  
  # Choose your codecs:
  
  #AudioCodec mp2
  
  #VideoCodec mpeg1video
  
  
  
  # Suppress audio
  
  #NoAudio
  
  
  
  # Suppress video
  
  #NoVideo
  
  
  
  #VideoQMin 3
  
  #VideoQMax 31
  
  
  
  # Set this to the number of seconds backwards in time to start. Note that
  
  # most players will buffer 5-10 seconds of video, and also you need to allow
  
  # for a keyframe to appear in the data stream.
  
  #Preroll 15
  
  
  
  # ACL:
  
  
  
  # You can allow ranges of addresses (or single addresses)
  
  #ACL ALLOW <first address="address"> <last address="address">
  
  
  
  # You can deny ranges of addresses (or single addresses)
  
  #ACL DENY <first address="address"> <last address="address">
  
  
  
  # You can repeat the ACL allow/deny as often as you like. It is on a per
  
  # stream basis. The first match defines the action. If there are no matches,
  
  # then the default is the inverse of the last ACL statement.
  
  #
  
  # Thus 'ACL allow localhost' only allows access from localhost.
  
  # 'ACL deny 1.0.0.0 1.255.255.255' would deny the whole of network 1 and
  
  # allow everybody else.
  
  
  
  </last></first></last></first></stream>
  
  
  
  
  
  ##################################################################
  
  # Example streams
  
  
  
  
  
  # Multipart JPEG
  
  
  
  #<stream>
  
  #Feed feed1.ffm
  
  #Format mpjpeg
  
  #VideoFrameRate 2
  
  #VideoIntraOnly
  
  #NoAudio
  
  #Strict -1
  
  #</stream>
  
  
  
  
  
  # Single JPEG
  
  
  
  #<stream>
  
  #Feed feed1.ffm
  
  #Format jpeg
  
  #VideoFrameRate 2
  
  #VideoIntraOnly
  
  ##VideoSize 352x240
  
  #NoAudio
  
  #Strict -1
  
  #</stream>
  
  
  
  
  
  # Flash
  
  
  
  #<stream>
  
  #Feed feed1.ffm
  
  #Format swf
  
  #VideoFrameRate 2
  
  #VideoIntraOnly
  
  #NoAudio
  
  #</stream>
  
  
  
  
  
  # ASF compatible
  
  
  
  <stream>
  
  Feed feed1.ffm
  
  Format asf
  
  VideoFrameRate 15
  
  VideoSize 352x240
  
  VideoBitRate 256
  
  VideoBufferSize 40
  
  VideoGopSize 30
  
  AudioBitRate 64
  
  StartSendOnKey
  
  </stream>
  
  
  
  
  
  # MP3 audio
  
  
  
  #<stream>
  
  #Feed feed1.ffm
  
  #Format mp2
  
  #AudioCodec mp3
  
  #AudioBitRate 64
  
  #AudioChannels 1
  
  #AudioSampleRate 44100
  
  #NoVideo
  
  #</stream>
  
  
  
  
  
  # Ogg Vorbis audio
  
  
  
  #<stream>
  
  #Feed feed1.ffm
  
  #Metadata title "Stream title"
  
  #AudioBitRate 64
  
  #AudioChannels 2
  
  #AudioSampleRate 44100
  
  #NoVideo
  
  #</stream>
  
  
  
  
  
  # Real with audio only at 32 kbits
  
  
  
  #<stream>
  
  #Feed feed1.ffm
  
  #Format rm
  
  #AudioBitRate 32
  
  #NoVideo
  
  #NoAudio
  
  #</stream>
  
  
  
  
  
  # Real with audio and video at 64 kbits
  
  
  
  #<stream>
  
  #Feed feed1.ffm
  
  #Format rm
  
  #AudioBitRate 32
  
  #VideoBitRate 128
  
  #VideoFrameRate 25
  
  #VideoGopSize 25
  
  #NoAudio
  
  #</stream>
  
  
  
  
  
  ##################################################################
  
  # A stream coming from a file: you only need to set the input
  
  # filename and optionally a new format. Supported conversions:
  
  #    AVI -> ASF
  
  
  
  #<stream>
  
  #File "/usr/local/httpd/htdocs/tlive.rm"
  
  #NoAudio
  
  #</stream>
  
  
  
  #<stream>
  
  #File "/usr/local/httpd/htdocs/test.asf"
  
  #NoAudio
  
  #Metadata author "Me"
  
  #Metadata copyright "Super MegaCorp"
  
  #Metadata title "Test stream from disk"
  
  #Metadata comment "Test comment"
  
  #</stream>
  
  
  
  
  
  ##################################################################
  
  # RTSP examples
  
  #
  
  # You can access this stream with the RTSP URL:
  
  #   rtsp://localhost:5454/test1-rtsp.mpg
  
  #
  
  # A non-standard RTSP redirector is also created. Its URL is:
  
  #   http://localhost:8090/test1-rtsp.rtsp
  
  
  
  #<stream>
  
  #Format rtp
  
  #File "/usr/local/httpd/htdocs/test1.mpg"
  
  #</stream>
  
  
  
  
  
  # Transcode an incoming live feed to another live feed,
  
  # using libx264 and video presets
  
  
  
  #<stream>
  
  #Format rtp
  
  #Feed feed1.ffm
  
  #VideoCodec libx264
  
  #VideoFrameRate 24
  
  #VideoBitRate 100
  
  #VideoSize 480x272
  
  #AVPresetVideo default
  
  #AVPresetVideo baseline
  
  #AVOptionVideo flags +global_header
  
  #
  
  #AudioCodec libfaac
  
  #AudioBitRate 32
  
  #AudioChannels 2
  
  #AudioSampleRate 22050
  
  #AVOptionAudio flags +global_header
  
  #</stream>
  
  
  
  ##################################################################
  
  # SDP/multicast examples
  
  #
  
  # If you want to send your stream in multicast, you must set the
  
  # multicast address with MulticastAddress. The port and the TTL can
  
  # also be set.
  
  #
  
  # An SDP file is automatically generated by ffserver by adding the
  
  # 'sdp' extension to the stream name (here
  
  # http://localhost:8090/test1-sdp.sdp). You should usually give this
  
  # file to your player to play the stream.
  
  #
  
  # The 'NoLoop' option can be used to avoid looping when the stream is
  
  # terminated.
  
  
  
  #<stream>
  
  #Format rtp
  
  #File "/usr/local/httpd/htdocs/test1.mpg"
  
  #MulticastAddress 224.124.0.1
  
  #MulticastPort 5000
  
  #MulticastTTL 16
  
  #NoLoop
  
  #</stream>
  
  
  
  
  
  ##################################################################
  
  # Special streams
  
  
  
  # Server status
  
  
  
  <stream>
  
  Format status
  
  
  
  # Only allow local people to get the status
  
  ACL allow localhost
  
  ACL allow 192.168.0.0 192.168.255.255
  
  
  
  #FaviconURL http://pond1.gladstonefamily.net:8080/favicon.ico
  
  </stream>
  
  
  
  
  
  # Redirect index.html to the appropriate site
  
  
  
  <redirect>
  
  URL http://www.ffmpeg.org/
  
  </redirect>

  I started my server and executed :

  ffserver -d -f /usr/share/doc/ffmpeg-2.6.8/ffserver.conf

  No error message and everything looks fine.

  After that I execute this (in your answer, I think you forgot the port number) :

  ffmpeg -i "rtsp://200.180.90.95:554/onvif1" -r 25 -s 640x480 -c:v libx264 -flags +global_header -f flv "http://45.79.207.38:8090/feed1.ffm"

  Then I get this log :

    libavutil      54. 20.100 / 54. 20.100
  
    libavcodec     56. 26.100 / 56. 26.100
  
    libavformat    56. 25.101 / 56. 25.101
  
    libavdevice    56.  4.100 / 56.  4.100
  
    libavfilter     5. 11.102 /  5. 11.102
  
    libavresample   2.  1.  0 /  2.  1.  0
  
    libswscale      3.  1.101 /  3.  1.101
  
    libswresample   1.  1.100 /  1.  1.100
  
    libpostproc    53.  3.100 / 53.  3.100
  
  [h264 @ 0x1a23580] RTP: missed 1 packets
  
  [pcm_alaw @ 0x1a24360] RTP: missed 2 packets
  
  [h264 @ 0x1a23580] RTP: missed 1 packets
  
  Invalid UE golomb code
  
  [h264 @ 0x1a23580] cbp too large (3199971767) at 76 33
  
  [h264 @ 0x1a23580] error while decoding MB 76 33
  
  [h264 @ 0x1a23580] Cannot use next picture in error concealment
  
  [h264 @ 0x1a23580] concealing 933 DC, 933 AC, 933 MV errors in P frame
  
  [h264 @ 0x1a23580] RTP: missed 1 packets
  
  [h264 @ 0x1a23580] cbp too large (62) at 50 24
  
  [h264 @ 0x1a23580] error while decoding MB 50 24
  
  [h264 @ 0x1a23580] Cannot use next picture in error concealment
  
  [h264 @ 0x1a23580] concealing 1679 DC, 1679 AC, 1679 MV errors in P frame
  
  [h264 @ 0x1a23580] RTP: missed 2 packets
  
  [h264 @ 0x1a23580] Cannot use next picture in error concealment
  
  [h264 @ 0x1a23580] concealing 1965 DC, 1965 AC, 1965 MV errors in P frame
  
  [pcm_alaw @ 0x1a24360] RTP: missed 1 packets
  
      Last message repeated 1 times
  
  [h264 @ 0x1a23580] RTP: missed 3 packets
  
  [h264 @ 0x1a23580] mb_type 49 in P slice too large at 74 25
  
  [h264 @ 0x1a23580] error while decoding MB 74 25
  
  [h264 @ 0x1a23580] Cannot use next picture in error concealment
  
  [h264 @ 0x1a23580] concealing 1575 DC, 1575 AC, 1575 MV errors in P frame
  
  [h264 @ 0x1a23580] RTP: missed 2 packets
  
  [h264 @ 0x1a23580] P sub_mb_type 29 out of range at 30 26
  
  [h264 @ 0x1a23580] error while decoding MB 30 26
  
  [h264 @ 0x1a23580] Cannot use next picture in error concealment
  
  [h264 @ 0x1a23580] concealing 1539 DC, 1539 AC, 1539 MV errors in P frame
  
  [h264 @ 0x1a23580] RTP: missed 1 packets
  
  [h264 @ 0x1a23580] out of range intra chroma pred mode at 72 29
  
  [h264 @ 0x1a23580] error while decoding MB 72 29
  
  [h264 @ 0x1a23580] Cannot use next picture in error concealment
  
  [h264 @ 0x1a23580] concealing 1257 DC, 1257 AC, 1257 MV errors in P frame
  
  [h264 @ 0x1a23580] RTP: missed 3 packets
  
  [h264 @ 0x1a23580] negative number of zero coeffs at 48 5
  
  [h264 @ 0x1a23580] error while decoding MB 48 5
  
  [h264 @ 0x1a23580] Cannot use next picture in error concealment
  
  [h264 @ 0x1a23580] concealing 3201 DC, 3201 AC, 3201 MV errors in P frame
  
  [pcm_alaw @ 0x1a24360] RTP: missed 1 packets
  
  [rtsp @ 0x1a20ee0] decoding for stream 0 failed
  
  Guessed Channel Layout for  Input Stream #0.1 : mono
  
  Input #0, rtsp, from 'rtsp://200.180.90.95:554/onvif1':
  
    Metadata:
  
      title           : H.264 Video, RtspServer_0.0.0.2
  
    Duration: N/A, start: 0.000000, bitrate: N/A
  
      Stream #0:0: Video: h264 (Baseline), yuv420p, 1280x720, 90k tbr, 90k tbn, 180k tbc
  
      Stream #0:1: Audio: pcm_alaw, 8000 Hz, 1 channels, s16, 64 kb/s
  
  [libx264 @ 0x1b728a0] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX AVX2 FMA3 LZCNT BMI2
  
  [libx264 @ 0x1b728a0] profile High, level 3.0
  
  [libx264 @ 0x1b728a0] 264 - core 142 r2495 6a301b6 - H.264/MPEG-4 AVC codec - Copyleft 2003-2014 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=1 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=25 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
  
  [flv @ 0x1a66300] FLV does not support sample rate 8000, choose from (44100, 22050, 11025)
  
  [flv @ 0x1a66300] Audio codec mp3 not compatible with flv
  
  Output #0, flv, to 'http://45.79.207.38:8090/feed1.ffm':
  
    Metadata:
  
      title           : H.264 Video, RtspServer_0.0.0.2
  
      encoder         : Lavf56.25.101
  
      Stream #0:0: Video: h264 (libx264) ([7][0][0][0] / 0x0007), yuv420p, 640x480, q=-1--1, 25 fps, 1k tbn, 25 tbc
  
      Metadata:
  
        encoder         : Lavc56.26.100 libx264
  
      Stream #0:1: Audio: mp3 (libmp3lame) ([2][0][0][0] / 0x0002), 8000 Hz, mono, s16p
  
      Metadata:
  
        encoder         : Lavc56.26.100 libmp3lame
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (h264 (native) -> h264 (libx264))
  
    Stream #0:1 -> #0:1 (pcm_alaw (native) -> mp3 (libmp3lame))
  
  Could not write header for output file #0 (incorrect codec parameters ?): Function not implemented

  I am doing this in a clean install of CENTOS, no customization. Could you please helpe me ?

• How Media Analytics for Piwik gives you the insights you need to measure how effective your video and audio marketing is – Part 1

  31 janvier 2017, par InnoCraft — Community

  Do you have video or audio content on your website or in your app ? If you answered this with yes, you should continue reading and learn everything about our Media Analytics premium feature.

  When you produce video or audio content, you are either spending money or time or often both money and time on your content in the hope of increasing conversions or sales. This means you have to know how your media is being used, when it is used, for how long and by whom. You can simply not afford not to know how this content affects your overall business goals as you are likely losing money and time by not making the most out of it. Would you be able to answer any of the above questions ? Do you know whether you can justify the cost and time for producing them, which videos work better than others and how they support your marketing strategy ? Luckily, getting all these insights is now so trivial it is almost a crime to not measure it.

  Getting Media Analytics and Installation

  Media Analytics can be purchased from the Piwik Marketplace where you find all sorts of free plugins as well as several premium features such as A/B Testing or Funnel. After the purchase you will receive a license key that you can enter in your Piwik to install and update the plugin with just one click.

  The feature will in most cases automatically start tracking your media content and you don’t even need to change the tracking code on your website. Currently supported players are for example YouTube, Vimeo, HTML 5, JW Player, VideoJS and many more players. You can also easily extend it by adding a custom media player or simply by letting us know which player you use and we will add support for it for you.

  By activating this feature, you get more than 15 new media reports, even more exportable widgets, new segments, APIs, and more. We will cover some of those features in this blog post and in part 2. For a full list of features check out the Media Analytics page on the Piwik Marketplace.

  Media Overview

  As the name says, it gives you an overview over your media usage and how it performs over time. You can choose any media metrics in the big evolution graph and the sparklines below give you an overview over all important metrics in a glance.

  

  It lets you for example see how often media was shown to your users, how often users start playing your media, for how long they watched it, how often they finished it, and more. If you see some spikes there, you should definitely have a deeper look at the other reports. When you hover a metric, it will show you a tooltip explaining how the data for this is collected and what it means.

  Real-Time Media

  On the Real-Time page you can see how your content is being used by your visitors right now, for example within the last 30 minutes, last 60 minutes and last 24 hours.

  It shows you how many plays you had in the last minutes, for how long they played it, and it shows you currently most popular media titles. This is great to discover which media content performs best right now and lets you make decisions based on user behaviour that is happening right now.

  

  Below you can see our Audience Real-Time Map that shows you from where in the world your media is being played. A bigger circle indicates that a media play happened more recently and of course you can zoom in down to countries and regions.

  

  All the reports update every few seconds so you can always have a look at it and see in just a second how your content is doing and how certain marketing campaigns affect it. All these real-time reports can be also added as widgets to any of your Piwik Dashboards and they can be exported for example as an iframe.

  Video, Audio and Media Player reports

  Those reports come with so many features, we need a separate blog post and cover this in part 2.

  Events

  Media Analytics will automatically track events so you can see how often users pressed for example play or pause, how often they resumed a video and how often they finished a video. This helps you better understand how your media is being used.

  

  For example in the past we noticed a couple of videos with lots of pause and resume events. We then had a look at the Audience Log – which we will cover next – to better understand why visitors paused the videos so often. We then realized they did this especially for videos that were served from a specific server and because the videos were loading so slow, users often pressed pause to let the media buffer, then played the media for a few seconds and then paused it again as they had to wait for the video to load. Moving those videos to another, faster server showed us immediate results in the number of pauses going down and on average visitors watched the videos for much longer.

  Audience Log

  At InnoCraft, we understand that not only aggregated metrics matter but also that you often need the ability to dig into your data and “debug” certain behaviours to understand the cause for some unusual high or low metrics. For example you may find out that many of your users often pause a video, then you wonder how each individual user behaved so you can better understand the why.

  

  The audience log shows you a detailed log of every visitor. You can chronologically see every action a visitor has performed during their whole visit. If you click on the visitor profile link, you can even see all visits of a specific visitor, and all actions they have ever performed on your website.

  This lets you ultimately debug and understand your visitors and see exactly which actions they performed before playing your media, which media they played, how they played your media, and how they behaved after playing your media.

  The visitor log of course also shows important information about each visitor like where they came from (referrer), their location, software, device and much more information.

  Audience Map

  The Audience Map is similar to the Real-Time Map but it shows you the locations of your visitors based on a selected date range and not in real time. The darker the blue, the more visitors from that country, region or city have interacted with your media.

  

  Coming in part 2

  In the next part we will cover which video, audio and media player reports Media Analytics provides, how segmenting gives you insights into different personas, and how nicely it integrates into Piwik.

  How to get Media Analytics and related features

  You can get Media Analytics on the Piwik Marketplace. If you want to learn more about this feature, you might be also interested in the Media Analytics User Guide and the Media Analytics FAQ.

• How to remove colour background into transparent or other colour with ffmpeg ?

  30 janvier 2017, par FillzZ

  My video is like in this picture. I need to remove blue background into transparent or other colour. How can I make it ?enter image description here