Recherche avancée

Sur d’autres sites (6417)

• Recapping WebM’s First Week

  25 mai 2010, par noreply@blogger.com (John Luther) — webm, vp8, vorbis

  The WebM project launched last Wednesday with broad industry backing (watch video of the announcement). The list of supporters keeps growing with new additions such as the popular VLC media player, Miro Video Converter, HeyWatch cloud encoding platform, and videantis programmable processor platform. We’re also happy to see that future versions of IE will support playback of VP8 when the user has installed the codec.

  Our announcement sparked discussions in the community around the design and quality of our developer release. We’ve done extensive testing of VP8 and know that the codec can match or exceed the quality of other leading codecs. Starting this week, the engineers behind WebM will post frequently to this blog with details on how to make optimal use of its VP8 video codec and Vorbis audio codec. We are confident that the open development model will bring additional improvements that will further optimize WebM. In fact, the power of open development is already visible, with developers submitting patches and the folks at Flumotion enabling live streaming support in their product just three days after the project was launched.

  Keep an eye on this blog for regular updates on the adoption and development of WebM. To participate in the conversation or to ask questions of the WebM team, please join our discussion group.

  John Luther
  Product Manager, Google

  

• How to get your Piwik plugin translated in many languages ?

  8 septembre 2015, par Stefan Giehl — Community, Development, Plugins

  About a year ago we introduced the Piwik Marketplace to make it easy for developers to share their plugins with all Piwik users.

  As Piwik is currently available in 54 languages we would love to have as many plugins as possible available in at least a few of those languages.

  Currently most plugins on the Marketplace are only available in English and sometimes some other languages. To improve this situation, we offer plugin developers the possibility to use the power of our translators community to get their plugins translated.

  Some plugin developers are already using this service and some very popular plugins like BotTracker or CustomOptOut have already been translated in more than 10 languages !

  Getting translations for your plugin

  As long as you are developing an open source plugin hosted on Github, you may get in touch with us (translations@piwik.org) in order to get your plugin translated by the Piwik translators community.

  You will need an account on Transifex.com. If you use Transifex with a social login, please ensure to set a password in your account settings. This will be required for fetching new translations into your plugin repository.

  Importing your plugin’s strings in the translation platform

  While doing the initial setup for your plugin, we will import your english translation file (en.json) in your Github plugin repository and we will configure an auto-update for this file. Source strings on Transifex will automatically synchronise with your plugin repository. When you change any string in your en.json translation file, the updated English strings will automatically be imported in Transifex.

  How to fetch your plugins translations into your repository

  As soon as we have set up your plugin within our Piwik project on Transifex and there are new translations available, you will be able to update your plugin translations using the Piwik console. You will need a locally installed Piwik with development mode enabled, and your plugin installed. To update the translations go to the Piwik directory on your development box and execute the following command :

  ./console translations:update -u {YourTransifexUserName} -p {YourTransifexPassword} -P {YourPluginName}

  We are looking forward to seeing your Piwik plugins available in more languages ! For more information, check out our Translations plugin developer guide.

  Happy hacking,

• FFMPEG with VP9 + RTSP

  4 janvier 2021, par Jim Jin

  When we use HEVC + RTSP, ffmpeg works fine. The stream is captured by webcam.

  


  ffmpeg -f dshow -rtbufsize 100M  -f vfwcap -i "0" -strict experimental -c:v hevc_qsv -f rtsp -rtsp_transport tcp rtsp://127.0.0.1/live/test


  


  The output is like :

  


  frame=  355 fps= 37 q=-0.0 size=N/A time=00:00:11.27 bitrate=N/A dup=159 drop=0 speed=1.18x


  


  Then we switch to VP9 + RTSP.

  


  ffmpeg -f dshow -rtbufsize 100M  -f vfwcap -i "0" -strict experimental -c:v libvpx-vp9 -f rtsp -rtsp_transport tcp rtsp://127.0.0.1/live/test


  


  The fps and speed looks too slow :

  


  frame=  263 fps=9.5 q=0.0 size=N/A time=00:00:07.94 bitrate=N/A dup=119 drop=0 speed=0.288x


  


  Then we use ffplay to play the stream. There are a lot of error messages and the video seems frozen.

  


  [vp9 @ 000001c3da86c200] Not all references are available
[vp9 @ 000001c3dffd5700] Not all references are available
[vp9 @ 000001c3da8477c0] Not all references are available
[vp9 @ 000001c3da848240] Not all references are available
[vp9 @ 000001c3da848e40] Not all references are available
[vp9 @ 000001c3e01d2fc0] Not all references are available
[vp9 @ 000001c3e01dd280] Not all references are available
[vp9 @ 000001c3e01e8980] Not all references are available
[vp9 @ 000001c3e01f1880] Not all references are available
[vp9 @ 000001c3da86c200] Not all references are available
[vp9 @ 000001c3dffd5700] Not all references are available
[vp9 @ 000001c3da8477c0] Not all references are available
[vp9 @ 000001c3da848240] Not all references are available
[vp9 @ 000001c3da848e40] Not all references are available
[vp9 @ 000001c3e01d2fc0] Not all references are available
[vp9 @ 000001c3e01dd280] Not all references are available0B f=0/0
[vp9 @ 000001c3e01e8980] Not all references are available
[vp9 @ 000001c3e01f1880] Not all references are available
[vp9 @ 000001c3da86c200] Not all references are available
[vp9 @ 000001c3dffd5700] Not all references are available
[vp9 @ 000001c3da8477c0] Not all references are available
[vp9 @ 000001c3da848240] Not all references are available
[vp9 @ 000001c3da848e40] Not all references are available
[vp9 @ 000001c3e01d2fc0] Not all references are available
[vp9 @ 000001c3e01dd280] Not all references are available
[vp9 @ 000001c3e01e8980] Not all references are available
[vp9 @ 000001c3e01f1880] Not all references are available


  


  Finally, we try hardware VP9 encoder.

  


  ffmpeg -f dshow -rtbufsize 100M  -f vfwcap -i "0" -strict experimental -c:v vp9_qsv -f rtsp -rtsp_transport tcp rtsp://127.0.0.1/live/test


  


  It can't work.

  


  [swscaler @ 0000021e88df9fc0] deprecated pixel format used, make sure you did set range correctly
[vp9_qsv @ 0000021e8687df80] Selected ratecontrol mode is unsupported
[vp9_qsv @ 0000021e8687df80] Low power mode is unsupported
[vp9_qsv @ 0000021e8687df80] Current frame rate is unsupported
[vp9_qsv @ 0000021e8687df80] Current picture structure is unsupported
[vp9_qsv @ 0000021e8687df80] Current resolution is unsupported
[vp9_qsv @ 0000021e8687df80] Current pixel format is unsupported
[vp9_qsv @ 0000021e8687df80] some encoding parameters are not supported by the QSV runtime. Please double check the input parameters.
Error initializing output stream 0:0 -- Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height
Conversion failed!


  


  So, how can we deal with VP9 + RTSP successfully ?