Recherche avancée

Sur d’autres sites (11158)

• python/flask ffmpeg m3u8 download

  17 mai 2017, par kittencornball

  I got ffmpeg working in the command line/app.py just fine with

  os.popen("ffmpeg -i LIVESTREAMURL -c copy thevideo.MP4")

  the end goal is to have this running on a site so i can just plop the m3u8 live stream in and download the video in a mp4 format

  heres what ive tried on my heroku app

  from flask import Flask
  
  from flask import send_file
  
  app = Flask(__name__)
  
  import os
  
  import subprocess
  
  import ffmpy
  
  
  
  
  
  farts = os.popen("ffmpeg -i LIVESTREAMURL -c copy thevideo.ts")
  
  
  
  @app.route("/")
  
  def hello():
  
      return "Hello World!"
  
      return farts

• Why I became a HTML5 co-editor

  15 août 2012, par silvia

  A few weeks ago, I had the honor to be appointed as part of the editorial team of the W3C HTML5 specification.

  Since Ian Hickson had recently decided to focus solely on editing the WHATWG HTML living standard specification, the W3C started looking for other editors to take the existing HTML5 specification to REC level. REC level is what other standards organizations call a “ratified standard”.

  But what does REC level really mean for HTML ?

  In my probably somewhat subjective view, recommendation level means that a snapshot is taken of the continuously evolving HTML spec, which has a comprehensive feature set, that is implemented in a cross-browser interoperable way, has a complete test set for the features, and has received wide review. The latter implies that other groups in the W3C have had a chance to look at the specification and make sure it satisfies their basic requirements, which include e.g. applicability to all users (accessibility, internationalization), platforms, and devices (mobile, TV).

  Basically it means that we stop for a “moment”, take a deep breath, polish the feature set that we’ve been working on this far, and make sure we all agree on it, before we get back to changing the world with cool new stuff. In a software project we would call it a release branch with feature freeze.

  Now, as productive as that may sound for software – it’s not actually that exciting for a specification. Firstly, the most exciting things happen when writing new features. Secondly, development of browsers doesn’t just magically stop to get the release (REC) happening. And lastly, if we’ve done our specification work well, there should be only little work to do. Basically, it’s the unthankful work of tidying up that we’re looking at here.

  So, why am I doing it ? I am not doing this for money – I’m currently part-time contracting to Google’s accessibility team working on video accessibility and this editor work is not covered by my contract. It wasn’t possible to reconcile polishing work on a specification with the goals of my contract, which include pushing new accessibility features forward. Therefore, when invited, I decided to offer my spare time to the W3C.

  I’m giving this time under the condition that I’d only be looking at accessibility and video related sections. This is where my interest and expertise lie, and where I’m passionate to get things right. I want to make sure that we create accessibility features that will be implemented and that we polish existing video features. I want to make sure we don’t digress from implementations which continue to get updated and may follow the WHATWG spec or HTML.next or other needs.

  I am not yet completely sure what the editorship will entail. Will we look at tests, too ? Will we get involved in HTML.next ? This far we’ve been preparing for our work by setting up adequate version control repositories, building a spec creation process, discussing how to bridge to the WHATWG commits, and analysing the long list of bugs to see how to cope with them. There’s plenty of actual text editing work ahead and the team is shaping up well ! I look forward to the new experiences.

• Not able to configure FFserver for RTSP

  2 novembre 2015, par Sujith

  I am kind of new to the streaming world... so, please forgive me if I ask kind of dumb question.

  I am trying to stream my pre-recorded file over RTSP through FFserver.

  My config file is :

  RTSPPort 8544
  
  <feed>
  
      File /home/xyz/tmp/feed2.ffm
  
      FileMaxSize 200K
  
      ACL allow 127.0.0.1
  
  </feed>
  
  
  
  <stream>
  
      Feed feed2.ffm
  
      Format rtsp
  
      VideoFrameRate 15
  
      VideoSize 352x240
  
      VideoBitRate 256
  
      VideoBufferSize 40
  
      VideoGopSize 30
  
      AudioBitRate 64
  
      StartSendOnKey
  
  </stream>

  After starting the server, it give the below log :

  $ ./ffserver -f doc/ffserver.conf
  
  ffserver version 0.11.1 Copyright (c) 2000-2012 the FFmpeg developers
  
  built on Sep 17 2012 19:46:38 with gcc 4.1.2 20080704 (Red Hat 4.1.2-52)
  
  configuration: --enable-gpl --enable-libmp3lame --enable-libtheora --enable-libvo-aacenc 
  
  -enable-libvorbis --enable-libvpx --enable-libx264 --enable-version3
  
  libavutil 51. 54.100 / 51. 54.100
  
  libavcodec 54. 23.100 / 54. 23.100
  
  libavformat 54. 6.100 / 54. 6.100
  
  libavdevice 54. 0.100 / 54. 0.100
  
  libavfilter 2. 77.100 / 2. 77.100
  
  libswscale 2. 1.100 / 2. 1.100
  
  libswresample 0. 15.100 / 0. 15.100
  
  libpostproc 52. 0.100 / 52. 0.100
  
  Wed Sep 19 17:03:32 2012 FFserver started.

  And now from my VLC client I am trying to type the URL : rtsp ://xxx.xxx.xxx.xxx:8554/test.sdp

  But, what happens is that, there is no response on the ffserver.

  I have no clue what might be the problem. Thanks in advance.