Recherche avancée

Sur d’autres sites (6356)

• Unable to stream file onto localhost - ffmpeg

  18 octobre 2013, par trueblue

  I am new to ffmpeg/ffserver. I am trying to stream a local file named Trial onto a localhost using ffserver. I want to run the file in browser as http://localhost:8090/feed1.ffm
  I am executing the below command in Ubuntu(Trial is a Mpeg TS file) :

    ffmpeg -i Trial http://localhost:8090/feed1.ffm

  Upon execution of above command I am getting below error :

  FFmpeg version SVN-r0.5.9-4:0.5.9-0ubuntu0.10.04.3, Copyright (c) 2000-2009 Fabrice Bellard, et al.
  
    configuration: --extra-version=4:0.5.9-0ubuntu0.10.04.3 --prefix=/usr --enable-avfilter --enable-avfilter-lavf --enable-vdpau --enable-bzlib --enable-libgsm --enable-libschroedinger --enable-libspeex --enable-libtheora --enable-libvorbis --enable-pthreads --enable-zlib --disable-stripping --disable-vhook --enable-runtime-cpudetect --enable-gpl --enable-postproc --enable-swscale --enable-x11grab --enable-libdc1394 --enable-shared --disable-static
  
    libavutil     49.15. 0 / 49.15. 0
  
    libavcodec    52.20. 1 / 52.20. 1
  
    libavformat   52.31. 0 / 52.31. 0
  
    libavdevice   52. 1. 0 / 52. 1. 0
  
    libavfilter    0. 4. 0 /  0. 4. 0
  
    libswscale     0. 7. 1 /  0. 7. 1
  
    libpostproc   51. 2. 0 / 51. 2. 0
  
    built on Jan 24 2013 19:42:59, gcc: 4.4.3
  
  
  
  Seems stream 0 codec frame rate differs from container frame rate: 119.88 (120000/1001) -> 59.94 (60000/1001)
  
  Input #0, mpegts, from 'Trial':
  
    Duration: 00:00:04.22, start: 0.177633, bitrate: 40368 kb/s
  
    Program 2 
  
      Stream #0.0[0x21]: Video: mpeg2video, yuv420p, 1280x720 [PAR 1:1 DAR 16:9], 45000 kb/s, 59.94 tbr, 90k tbn, 119.88 tbc
  
  Output #0, ffm, to 'http://localhost:8090/feed1.ffm':
  
      Stream #0.0: Video: flv, yuv420p, 352x288, q=1-5, 100 kb/s, 1000k tbn, 15 tbc
  
      Stream #0.1: Audio: mp2, 44100 Hz, mono, s16, 32 kb/s
  
      Stream #0.2: Video: mpeg1video, yuv420p, 160x128, q=3-31, 64 kb/s, 1000k tbn, 3 tbc
  
      Stream #0.3: Audio: mp2, 22050 Hz, mono, s16, 64 kb/s
  
      Stream #0.4: Video: msmpeg4, yuv420p, 352x240, q=3-31, 256 kb/s, 1000k tbn, 15 tbc
  
  Could not find input stream matching output stream #0.1

  My ffserver.conf file goes 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.
  
  Port 8090
  
  
  
  # Address on which the server is bound. Only useful if you have
  
  # several network interfaces.
  
  BindAddress 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 -
  
  
  
  # Suppress that if you want to launch ffserver as a daemon.
  
  NoDaemon
  
  
  
  
  
  ##################################################################
  
  # 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 &#39;ffmpeg&#39; 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 5M
  
  
  
  # 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
  
  
  
  </feed>
  
  
  
  
  
  
  
  <stream>
  
  Feed feed1.ffm
  
  Format swf
  
  VideoCodec flv
  
  VideoFrameRate 15
  
  VideoBufferSize 80000
  
  VideoBitRate 100
  
  VideoQMin 1
  
  VideoQMax 5
  
  VideoSize 352x288
  
  PreRoll 0
  
  Noaudio
  
  </stream>
  
  
  
  ##################################################################
  
  # Now you can define each stream which will be generated from the
  
  # original audio and video stream. Each format has a filename (here
  
  # &#39;test1.mpg&#39;). FFServer will send this stream when answering a
  
  # request containing this filename.
  
  
  
  <stream>
  
  
  
  # coming from live feed &#39;feed1&#39;
  
  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 &#39;ACL allow localhost&#39; only allows access from localhost.
  
  # &#39;ACL deny 1.0.0.0 1.255.255.255&#39; 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
  
  #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
  
  #Author "Me"
  
  #Copyright "Super MegaCorp"
  
  #Title "Test stream from disk"
  
  #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>
  
  
  
  
  
  ##################################################################
  
  # 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
  
  # &#39;sdp&#39; 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 &#39;NoLoop&#39; 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>

  Kindly anyone please assist me whether I am missing something or do i need to change my server.conf file ? I have referred many websites. But still I am unable to fix it. Thanks in advance.

• VeriSilicon and WebM Support

  24 janvier 2011, par noreply@blogger.com (John Luther)

  Guest blogger Tomi Jalonen is Director of Product Marketing for Hantro video IP at VeriSilicon

  2011 is shaping up to be an exciting year at VeriSilicon Holdings in terms of WebM support. With the new year upon us, I want to share some updates about the work we are doing at VeriSilicon to move the WebM platform forward.

  VeriSilicon has been a longtime partner of On2/Hantro (Hantro is the video IP brand that Google acquired with On2 Technologies) and we were among the first hardware partners to commit to WebM video when the codec was open-sourced last year. After promoting WebM to the semiconductor industry during 2010, we’re excited that at CES 2011 the first tablet supporting WebM with full 1080p resolution was demonstrated. VeriSilicon licensed the WebM IP to this tablet manufacturer and provided engineering support to bring the technology to the showroom floor.

  In addition to licensing IPs, this year we’ll be taking the WebM experience a step further by taping out several application processor chips—including the WebM video IP for Android phones, xPad, and Google TV—to accelerate the deployment of WebM and HTML5 video playback into the market.

  The entire VeriSilicon team is very excited about the future of WebM. We believe that the availability of high-quality, optimized WebM hardware video IP, combined with other VeriSilicon audio and multimedia IP, will be a key ingredient for semiconductor companies to create competitive consumer products. After the launch of WebM, the interest in hardware-accelerated WebM video has been immense and we will continue working with the WebM Project to enable WebM and VP8 in many more chips in 2011.

  

• The First Problem

  19 janvier 2011, par Multimedia Mike — HTML5

  A few years ago, The Linux Hater made the following poignant observation regarding Linux driver support :

  Drivers are only just the beginning... But for some reason y’all like to focus on the drivers. You know why lusers do that ? Because it just happens to be the problem that people notice first.

  And so it is with the HTML5 video codec debate, re-invigorated in the past week by Google’s announcement of dropping native H.264 support in their own HTML5 video tag implementation. As I read up on the fiery debate, I kept wondering why people are so obsessed with this issue. Then I remembered the Linux Hater’s post and realized that the video codec issue is simply the first problem that most people notice regarding HTML5 video.

  I appreciate that the video codec debate has prompted Niedermayer to post on his blog once more. Otherwise, I’m just munching popcorn on the sidelines, amused and mildly relieved that the various factions are vociferously attacking each other rather than that little project I help with at work.

  Getting back to the "first problem" aspect— there’s so much emphasis on the video codec ; I wonder why no one ever, ever mentions word one about an audio codec. AAC is typically the codec that pairs with H.264 in the MPEG stack. Dark Shikari once mentioned that "AAC’s licensing terms are exponentially more onerous than H.264′s. If Google didn’t want to use H.264, they would sure as hell not want to use AAC." Most people are probably using "H.264" to refer to the entire MPEG/H.264/AAC stack, even if they probably don’t understand what all of those pieces mean.

  Anyway, The Linux Hater’s driver piece continues :

  Once y’all have drivers, the fight will move to the next layer up. And like I said, it’s a lot harder at that layer.

  A few months ago, when I wanted to post the WebM output of my new VP8 encoder and thought it would be a nice touch to deliver it via a video tag, I ignored the video codec problem (just encoded a VP8/WebM file) only to immediately discover a problem at a different layer— specifically, embedding a file using a video tag triggers a full file download when the page is loaded, which is unacceptable from end user and web hosting perspectives. This is a known issue but doesn’t get as much attention, I guess because there are bigger problems to solve first (c.f. video codec issue).

  For other issues, check out the YouTube blog’s HTML5 post or Hulu’s post that also commented on HTML5. Issues such as video streaming flexibility, content protection, fullscreen video, webcam/microphone input, and numerous others are rarely mentioned in the debates. Only "video codec" is of paramount importance.

  But I’m lending too much weight to the cacophony of a largely uninformed internet debate. Realistically, I know there are many talented engineers down in the trenches working to solve at least some of these problems. To tie this in with the Linux driver example, I’m consistently stunned these days regarding how simple it is to get Linux working on a new computer— most commodity consumer hardware really does just work right out of the box. Maybe one day, we’ll wake up and find that HTML5 video has advanced to the point that it solves all of the relevant problems to make it the simple and obvious choice for delivering web video in nearly all situations.

  It won’t be this year.