Recherche avancée

Sur d’autres sites (9181)

• Summary Video Accessibility Talk

  1er janvier 2014, par silvia

  I’ve just got off a call to the UK Digital TV Group, for which I gave a talk on HTML5 video accessibility (slides best viewed in Google Chrome).

  The slide provide a high-level summary of the accessibility features that we’ve developed in the W3C for HTML5, including :

  • Subtitles & Captions with WebVTT and the track element
  • Video Descriptions with WebVTT, the track element and speech synthesis
  • Chapters with WebVTT for semantic navigation
  • Audio Descriptions through synchronising an audio track with a video
  • Sign Language video synchronized with a main video

  I received some excellent questions.

  The obvious one was about why WebVTT and not TTML. While for anyone who has tried to implement TTML support, the advantages of WebVTT should be clear, for some the decision of the browsers to go with WebVTT still seems to be bothersome. The advantages of CSS over XSL-FO in a browser-context are obvious, but not as much outside browsers. So, the simplicity of WebVTT and the clear integration with HTML have to speak for themselves. Conversion between TTML and WebVTT was a feature that was being asked for.

  I received a question about how to support ducking (reduce the volume of the main audio track) when using video descriptions. My reply was to either use video descriptions with WebVTT and do ducking during the times that a cue is active, or when using audio descriptions (i.e. actual audio tracks) to add an additional WebVTT file of kind=metadata to mark the intervals in which to do ducking. In both cases some JavaScript will be necessary.

  I received another question about how to do clean audio, which I had almost forgotten was a requirement from our earlier media accessibility document. “Clean audio” consists of isolating the audio channel containing the spoken dialog and important non-speech information that can then be amplified or otherwise modified, while other channels containing music or ambient sounds are attenuated. I suggested using the mediagroup attribute to provide a main video element (without an audio track) and then the other channels as parallel audio tracks that can be turned on and off and attenuated individually. There is some JavaScript coding involved on top of the APIs that we have defined in HTML, but it can be implemented in browsers that support the mediagroup attribute.

  Another question was about the possibilities to extend the list of @kind attribute values. I explained that right now we have a proposal for a new text track kind=”forced” so as to provide forced subtitles for sections of video with foreign language. These would be on when no other subtitle or caption tracks are activated. I also explained that if there is a need for application-specific text tracks, the kind=”metadata” would be the correct choice.

  I received some further questions, in particular about how to apply styling to captions (e.g. color changes to text) and about how closely the browser are able to keep synchronization across multiple media elements. The earlier was easily answered with the ::cue pseudo-element, but the latter is a quality of implementation feature, so I had to defer to individual browsers.

  Overall it was a good exercise to summarize the current state of HTML5 video accessibility and I was excited to show off support in Chrome for all the features that we designed into the standard.

• ffmpeg status & quality / cuda (CPU/GPU)

  18 avril 2015, par cocco

  ffmpeg am i doing it right ?

  So much time has passed since i use ffmpeg to convert clips on my home web server, now that mp4 (h264 & aac) is the current overall standard (works on every console, smartphone, smartTV, pc) i decided to convert my old clips from various digital cameras to to this new container/codecs.

  1. less space & the same quality.
  2. compatibility
  3. support for tags (subler for mac)

  after some research i opted for ffmpeg because of various reasons

  1. commandline (i made my simple web interface with default settings wich i execute with php’s exec)
  2. the quality/size amount

  I read that many expensive video conversion softwares are not able to handle low bitrate videos properly. I also tested some of them and personally i could not find the proper export settings or i was not impressed by the results... some had fixed default export setings, most had a lower video quality at the same filesize. ffmpeg allows me to set the -crf (18-24 usually) and -preset (veryslow, fast..) witch allows me to reduce the filesize drastically mantaining the same
  visible quality.

  Said that i’m using the preset at veryslow.(there is also placebo but the final video file is only 1% smaller in size).

  And here is the command i use

  ffmpeg
  
  -y //overwrite the file if it exists
  
  
  
  -i INPUTFILE // replace with the input file
  
  
  
  -metadata title=THETITLE // set a nice title, visible on modern devices
  
  -metadata date=THEDATE // set a nice title, visible on modern devices
  
  
  
  -c:v libx264 // use the h264 codec
  
   -crf 21 // try different numbers between 18-26
  
   -preset veryslow // placebo,slow,fast,ultrafast==big file 
  
   -tune film // tune it a little
  
   -pix_fmt yuv420p // preferred on most modern devices
  
   -profile:v main // preferred on most modern devices
  
   -level 3.1 // preferred on most modern devices 
  
   -refs 4 // preferred on most modern devices
  
  
  
  -c:a libfdk_aac // use aac
  
   -metadata:s:a language=eng // set a language, visible on modern devices 
  
   -b:a 128k // audio bitrate 128k is like mp3 192k
  
   -ar 48000 // 44100 ... whatever
  
   -ac 2 // audiochannels
  
   -movflags +faststart //move the metadata in the front of the video so it loads faster
  
  
  
  OUTPUTFILE

  some camcorder clips with m2ts already have the avc/h264 compatible codec so i just copy the stream.
  some have the ac3/dolby sorround audio. I convert the audio but keep the ac3 as second audio track mapping the ffmpeg streams.this allows me to watch the mp4 on browsers and mobile devices but i’m able to keep the surround sound to playback on some tv’s, advanced media players or devices like apple tv.

  not that i’m not happy with the speed (using quad core’s) but i recently read again about cuda opencl and there is also the simple fact that i’m not using other converters than ffmpeg since alot of time.

  Is ffmpeg (with the setting i use) a good converter to keep the same video quality than the source reducing the space occupied by and average of 30-40% ?

  Is GPU conversion really that bad (cuda .. testing a gtx970) ?
  it would be nice to add some more speed to the conversions by using both the gpu and the cpu..but for my understanding they cannot work together ??? and using only gpu is a drastical quality loss...cpu si more precise, gpu is faster in calculation are too imprecise from what i read.. so expensive softwares use cuda only for preview purpose... right ?

  Is ffmpeg or another software compatible with CPU+GPU encoding ?
  i really don’t remember where, but i read that the ffmpeg is not a good videoconverter.

  i’m really happy with the size/quality, i gained an average of 30% in space with no visible quality loss. With some extra parameters i can adjust some really old analog videos that are deinterlaced in a really bad way.

  maybe i could gain more size/quality with another software ???

  note : i like ffmpeg.it’s free and it has commandline so i can create my own interface with php html & js and use it on various machines without the need to install it in every device i use. i uplad the idevice clips directly to the ffmpeg server.

  btw. : explain the downvotes...

  EDIT :

  @talonmies ...cuda tag removed :

  http://www.nvidia.com/object/cuda_home_new.html

  CUDA® is a parallel computing platform and programming model invented
  by NVIDIA. It enables dramatic increases in computing performance by
  harnessing the power of the graphics processing unit (GPU). With
  millions of CUDA-enabled GPUs sold to date, software developers,
  scientists and researchers are finding broad-ranging uses for GPU
  computing with CUDA. Here are a few examples : - See more at :
  http://www.nvidia.com/object/cuda_home_new.html#sthash.dEYaqae7.dpuf

  isn’t cuda the programming model that a theoretical ffmpeg library should support to handle GPU encoding on nvidia cards like the gtx 970 ?? like the badaboom software http://www.geforce.com/games-applications/pc-applications/badaboom-media-converter.

• Piwik and Piwik PRO featured in TrustRadius buyer’s guide

  3 septembre 2014, par Piwik Core Team — About, Meta

  We are proud that Piwik and Piwik PRO are being featured in the TrustRadius Buyer’s Guide to Digital Analytics Software and scooping up two awards :

  

  Piwik Named A Leader in TrustRadius Digital Analytics TrustMap™ for Small Businesses.

  Piwik Rated Strong Performer in TrustRadius Digital Analytics TrustMap ™ for Enterprise.

  Rankings Based on User Ratings and Market Segment Adoption

  Learn more

  The TrustRadius TrustMaps™ guide features reviews from authenticated TrustRadius users on a number of digital analytics platforms from the biggest names in the digital analytics industry – Piwik and Piwik PRO being two of them. You can download your free copy of the buyer’s guide here (Note : there is a form to fill before you can download the PDF).

  Read the TrustRadius user reviews about Piwik on their website.

  Or view other awards won by Piwik here.