Recherche avancée

Sur d’autres sites (6938)

• Getting video properties with Python without calling external software

  24 juillet 2019, par ullix

  [Update :] Yes, it is possible, now some 20 months later. See Update3 below ! [/update]

  Is that really impossible ? All I could find were variants of calling FFmpeg (or other software). My current solution is shown below, but what I really would like to get for portability is a Python-only solution that doesn’t require users to install additional software.

  After all, I can easily play videos using PyQt’s Phonon, yet I can’t get simply things like dimension or duration of the video ?

  My solution uses ffmpy (http://ffmpy.readthedocs.io/en/latest/ffmpy.html ) which is a wrapper for FFmpeg and FFprobe (http://trac.ffmpeg.org/wiki/FFprobeTips). Smoother than other offerings, yet it still requires an additional FFmpeg installation.

      import ffmpy, subprocess, json
  
      ffprobe = ffmpy.FFprobe(global_options="-loglevel quiet -sexagesimal -of json -show_entries stream=width,height,duration -show_entries format=duration -select_streams v:0", inputs={"myvideo.mp4": None})
  
      print("ffprobe.cmd:", ffprobe.cmd)  # printout the resulting ffprobe shell command
  
      stdout, stderr = ffprobe.run(stderr=subprocess.PIPE, stdout=subprocess.PIPE)
  
      # std* is byte sequence, but json in Python 3.5.2 requires str
  
      ff0string = str(stdout,'utf-8')
  
  
  
      ffinfo = json.loads(ff0string)
  
      print(json.dumps(ffinfo, indent=4)) # pretty print
  
  
  
      print("Video Dimensions: {}x{}".format(ffinfo["streams"][0]["width"], ffinfo["streams"][0]["height"]))
  
      print("Streams Duration:", ffinfo["streams"][0]["duration"])
  
      print("Format Duration: ", ffinfo["format"]["duration"])

  Results in output :

      ffprobe.cmd: ffprobe -loglevel quiet -sexagesimal -of json -show_entries stream=width,height,duration -show_entries format=duration -select_streams v:0 -i myvideo.mp4
  
      {
  
          "streams": [
  
              {
  
                  "duration": "0:00:32.033333",
  
                  "width": 1920,
  
                  "height": 1080
  
              }
  
          ],
  
          "programs": [],
  
          "format": {
  
              "duration": "0:00:32.064000"
  
          }
  
      }
  
      Video Dimensions: 1920x1080
  
      Streams Duration: 0:00:32.033333
  
      Format Duration:  0:00:32.064000

  UPDATE after several days of experimentation : The hachoire solution as proposed by Nick below does work, but will give you a lot of headaches, as the hachoire responses are too unpredictable. Not my choice.

  With opencv coding couldn’t be any easier :

  import cv2
  
  vid = cv2.VideoCapture( picfilename)
  
  height = vid.get(cv2.CAP_PROP_FRAME_HEIGHT) # always 0 in Linux python3
  
  width  = vid.get(cv2.CAP_PROP_FRAME_WIDTH)  # always 0 in Linux python3
  
  print ("opencv: height:{} width:{}".format( height, width))

  The problem is that it works well on Python2 but not on Py3. Quote : "IMPORTANT NOTE : MacOS and Linux packages do not support video related functionality (not compiled with FFmpeg)" (https://pypi.python.org/pypi/opencv-python).

  On top of this it seems that opencv needs the presence of the binary packages of FFmeg at runtime (https://docs.opencv.org/3.3.1/d0/da7/videoio_overview.html).

  Well, if I need an installation of FFmpeg anyway, I can stick to my original ffmpy example shown above :-/

  Thanks for the help.

  UPDATE2 : master_q (see below) proposed MediaInfo. While this failed to work on my Linux system (see my comments), the alternative of using pymediainfo, a py wrapper to MediaInfo, did work. It is simple to use, but it takes 4 times longer than my initial ffprobe approach to obtain duration, width and height, and still needs external software, i.e. MediaInfo :

  from pymediainfo import MediaInfo
  
  media_info = MediaInfo.parse("myvideofile")
  
  for track in media_info.tracks:
  
      if track.track_type == 'Video':
  
          print("duration (millisec):", track.duration)
  
          print("width, height:", track.width, track.height)

  UPDATE3 : OpenCV is finally available for Python3, and is claimed to run on Linux, Win, and Mac ! It makes it really easy, and I verfied that external software - in particular ffmpeg - is NOT needed !

  First install OpenCV via Pip :

  pip install opencv-python

  Run in Python :

  import cv2
  
  cv2video = cv2.VideoCapture( videofilename)
  
  height = cv2video.get(cv2.CAP_PROP_FRAME_HEIGHT)
  
  width  = cv2video.get(cv2.CAP_PROP_FRAME_WIDTH) 
  
  print ("Video Dimension: height:{} width:{}".format( height, width))
  
  
  
  framecount = cv2video.get(cv2.CAP_PROP_FRAME_COUNT ) 
  
  frames_per_sec = cv2video.get(cv2.CAP_PROP_FPS)
  
  print("Video duration (sec):", framecount / frames_per_sec)
  
  
  
  # equally easy to get this info from images
  
  cv2image = cv2.imread(imagefilename, flags=cv2.IMREAD_COLOR  )
  
  height, width, channel  = cv2image.shape
  
  print ("Image Dimension: height:{} width:{}".format( height, width))

  I also needed the first frame of a video as an image, and used ffmpeg for this to save the image in the file system. This also is easier with OpenCV :

  hasFrames, cv2image = cv2video.read()   # reads 1st frame
  
  cv2.imwrite("myfilename.png", cv2image) # extension defines image type

  But even better, as I need the image only in memory for use in the PyQt5 toolkit, I can directly read the cv2-image into an Qt-image :

  bytesPerLine = 3 * width
  
  # my_qt_image = QImage(cv2image, width, height, bytesPerLine, QImage.Format_RGB888) # may give false colors!
  
  my_qt_image = QImage(cv2image.data, width, height, bytesPerLine, QImage.Format_RGB888).rgbSwapped() # correct colors on my systems

  As OpenCV is a huge program, I was concerned about timing. Turned out, OpenCV was never behind the alternatives. I takes some 100ms to read a slide, all the rest combined takes never more than 10ms.

  I tested this successfully on Ubuntu Mate 16.04, 18.04, and 19.04, and on two different installations of Windows 10 Pro. (Did not have Mac avalable). I am really delighted about OpenCV !

  You can see it in action in my SlideSorter program, which allows to sort images and videos, preserve sort order, and present as slideshow. Available here : https://sourceforge.net/projects/slidesorter/

• My journey to Coviu

  27 octobre 2015, par silvia

  My new startup just released our MVP – this is the story of what got me here.

  I love creating new applications that let people do their work better or in a manner that wasn’t possible before.

  My first such passion was as a student intern when I built a system for a building and loan association’s monthly customer magazine. The group I worked with was managing their advertiser contacts through a set of paper cards and I wrote a dBase based system (yes, that long ago) that would manage their customer relationships. They loved it – until it got replaced by an SAP system that cost 100 times what I cost them, had really poor UX, and only gave them half the functionality. It was a corporate system with ongoing support, which made all the difference to them.

  The story repeated itself with a CRM for my Uncle’s construction company, and with a resume and quotation management system for Accenture right after Uni, both of which I left behind when I decided to go into research.

  Even as a PhD student, I never lost sight of challenges that people were facing and wanted to develop technology to overcome problems. The aim of my PhD thesis was to prepare for the oncoming onslaught of audio and video on the Internet (yes, this was 1994 !) by developing algorithms to automatically extract and locate information in such files, which would enable users to structure, index and search such content.

  Many of the use cases that we explored are now part of products or continue to be challenges : finding music that matches your preferences, identifying music or video pieces e.g. to count ads on the radio or to mark copyright infringement, or the automated creation of video summaries such as trailers.

  

  This continued when I joined the CSIRO in Australia – I was working on segmenting speech into words or talk spurts since that would simplify captioning & subtitling, and on MPEG-7 which was a (slightly over-engineered) standard to structure metadata about audio and video.

  In 2001 I had the idea of replicating the Web for videos : i.e. creating hyperlinked and searchable video-only experiences. We called it “Annodex” for annotated and indexed video and it needed full-screen hyperlinked video in browsers – man were we ahead of our time ! It was my first step into standards, got several IETF RFCs to my name, and started my involvement with open codecs through Xiph.

  Around the time that YouTube was founded in 2006, I founded Vquence – originally a video search company for the Web, but pivoted to a video metadata mining company. Vquence still exists and continues to sell its data to channel partners, but it lacks the user impact that has always driven my work.

  As the video element started being developed for HTML5, I had to get involved. I contributed many use cases to the W3C, became a co-editor of the HTML5 spec and focused on video captioning with WebVTT while contracting to Mozilla and later to Google. We made huge progress and today the technology exists to publish video on the Web with captions, making the Web more inclusive for everybody. I contributed code to YouTube and Google Chrome, but was keen to make a bigger impact again.

  The opportunity came when a couple of former CSIRO colleagues who now worked for NICTA approached me to get me interested in addressing new use cases for video conferencing in the context of WebRTC. We worked on a kiosk-style solution to service delivery for large service organisations, particularly targeting government. The emerging WebRTC standard posed many technical challenges that we addressed by building rtc.io , by contributing to the standards, and registering bugs on the browsers.

  Fast-forward through the development of a few further custom solutions for customers in health and education and we are starting to see patterns of need emerge. The core learning that we’ve come away with is that to get things done, you have to go beyond “talking heads” in a video call. It’s not just about seeing the other person, but much more about having a shared view of the things that need to be worked on and a shared way of interacting with them. Also, we learnt that the things that are being worked on are quite varied and may include multiple input cameras, digital documents, Web pages, applications, device data, controls, forms.

  So we set out to build a solution that would enable productive remote collaboration to take place. It would need to provide an excellent user experience, it would need to be simple to work with, provide for the standard use cases out of the box, yet be architected to be extensible for specialised data sharing needs that we knew some of our customers had. It would need to be usable directly on Coviu.com, but also able to integrate with specialised applications that some of our customers were already using, such as the applications that they spend most of their time in (CRMs, practice management systems, learning management systems, team chat systems). It would need to require our customers to sign up, yet their clients to join a call without sign-up.

  Collaboration is a big problem. People are continuing to get more comfortable with technology and are less and less inclined to travel distances just to get a service done. In a country as large as Australia, where 12% of the population lives in rural and remote areas, people may not even be able to travel distances, particularly to receive or provide recurring or specialised services, or to achieve work/life balance. To make the world a global village, we need to be able to work together better remotely.

  The need for collaboration is being recognised by specialised Web applications already, such as the LiveShare feature of Invision for Designers, Codassium for pair programming, or the recently announced Dropbox Paper. Few go all the way to video – WebRTC is still regarded as a complicated feature to support.

  

  With Coviu, we’d like to offer a collaboration feature to every Web app. We now have a Web app that provides a modern and beautifully designed collaboration interface. To enable other Web apps to integrate it, we are now developing an API. Integration may entail customisation of the data sharing part of Coviu – something Coviu has been designed for. How to replicate the data and keep it consistent when people collaborate remotely – that is where Coviu makes a difference.

  We have started our journey and have just launched free signup to the Coviu base product, which allows individuals to own their own “room” (i.e. a fixed URL) in which to collaborate with others. A huge shout out goes to everyone in the Coviu team – a pretty amazing group of people – who have turned the app from an idea to reality. You are all awesome !

  With Coviu you can share and annotate :

  • images (show your mum photos of your last holidays, or get feedback on an architecture diagram from a customer),
  • pdf files (give a presentation remotely, or walk a customer through a contract),
  • whiteboards (brainstorm with a colleague), and
  • share an application window (watch a YouTube video together, or work through your task list with your colleagues).

  All of these are regarded as “shared documents” in Coviu and thus have zooming and annotations features and are listed in a document tray for ease of navigation.

  This is just the beginning of how we want to make working together online more productive. Give it a go and let us know what you think.

  http://coviu.com/

• Anomalie #3305 (Nouveau) : Balise fermée automatiquement dans un bloc code

  21 octobre 2014, par Franck Dalot

  Bonjour
  Je viens de me rendre compte d’un bug sur contrib (le bug est également présent sous SPIP 3.0.18-dev [21616]) mais semble absent sous spip 3.1
  Quand une personne répond dans le forum en entourant par "code"

  <necessite version="[2.0.0;2.1.99]"></necessite>
  La prévisalisation est ok, par contre après avoir valider le message, cela écris :
  <necessite version="[2.0.0;2.1.99]"></necessite>
  Cordialement, Franck