Recherche avancée

Sur d’autres sites (11306)

• ffplay playing videos very slow and choppy

  2 juin 2014, par Pavan K

  I am trying to compile ffplay from sources to run on pcduino running ubuntu

  If I install ffplay via sudo apt-get install ffmpeg the videos play perfectly But I tried to compile ffplay from the sources using the guide here ffmpeg compilation the videos play terribly slowand look very very choppy.

  Do I have to use some specific flags for compilation. I just would like a bare bones video player ffplay. I do not want to encode or do any heavy computation with the binary.

  ffplay verison is

      ./ffplay -version    
  
  ffplay version git-2013-06-14-d891d35
  
  built on Jun  2 2014 14:15:57 with gcc 4.6 (Ubuntu/Linaro 4.6.3-1ubuntu5)
  
  configuration: --extra-libs=-ldl --enable-gpl --enable-libass --enable-libfdk-aac --enable-libfreetype --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-nonfree
  
  libavutil      52. 35.101 / 52. 35.101
  
  libavcodec     55. 16.100 / 55. 16.100
  
  libavformat    55.  8.102 / 55.  8.102
  
  libavdevice    55.  2.100 / 55.  2.100
  
  libavfilter     3. 77.101 /  3. 77.101
  
  libswscale      2.  3.100 /  2.  3.100
  
  libswresample   0. 17.102 /  0. 17.102
  
  libpostproc    52.  3.100 / 52.  3.100

  And this is from apt-get

  ffplay -version 
  
  avplay version 0.8.10-4:0.8.10-0ubuntu0.12.04.1, Copyright (c) 2003-2013 the Libav developers
  
    built on Feb  6 2014 21:09:10 with gcc 4.6.3
  
  avplay 0.8.10-4:0.8.10-0ubuntu0.12.04.1
  
  libavutil    51. 22. 2 / 51. 22. 2
  
  libavcodec   53. 35. 0 / 53. 35. 0
  
  libavformat  53. 21. 1 / 53. 21. 1
  
  libavdevice  53.  2. 0 / 53.  2. 0
  
  libavfilter   2. 15. 0 /  2. 15. 0
  
  libswscale    2.  1. 0 /  2.  1. 0
  
  libpostproc  52.  0. 0 / 52.  0. 0

  i have the following error when I play with the built ffplay

  ALSA lib pcm.c:7339:(snd_pcm_recover) underrun occurred  0B f=0/0
  
  ALSA lib pcm.c:7339:(snd_pcm_recover) underrun occurred  0B f=0/0

• Is there a locale that supports all symbols ?

  2 juin 2014, par user3698015

  I’m having this problem with ffmpeg basically this
  https://github.com/rg3/youtube-dl/issues/2999

  so what happens is that if the video title has a symbol that isn’t supported by your current locale then ffmpeg won’t be able to get to that file properly. (or at least that’s what i’ve been thinking)

  ►2 HOURS BEST MELODIC DUBSTEP MIX APRIL 2013◄ ヽ( ≧ω≦)ﾉ

  Here’s one example
  as you may or may not be able to see, lots of symbols from seemingly everywhere.
  So which locale supports all the symbols, or at least as many as possible ?
  Also, is there a disadvantage to using a locale that’s not your native locale ?

  edit : i just remembered that in the past when i used a locale that wasn’t supported the symbol would appear as a questionmark in a box...

  but the triangle didn’t appear as that, it appeared as it was... so this is odd

  so i figured that i should give the error message precisely

      [ffmpeg] Adding metadata to 'C:\Music\ToBeDone\2014-06-01\►2 HOURS DUBSTEP_DRUMS
  
      TEP MIX AUGUST 2013◄ ヽ( ≧ω≦)ﾉ.mp4'
  
      ERROR: C:\Music\ToBeDone\2014-06-01\2 HOURS DUBSTEP_DRUMSTEP MIX AUGUST 2013 ヽ(
  
      ≧ω≦)ﾉ.mp4: No such file or directory
  
      ERROR: WARNING: unable to obtain file audio codec with ffprobe

  and this is what’s going on (everything)

  @echo off
  
  setlocal
  
  cd C:\youtube-dl
  
  
  
  set /p "var1=Enter URL: " %=% pause
  
  if defined var1 set "var1=%var1:"=%"
  
  set "var2=%date:/=-%" 
  
  set "var3=%%(title)s.%%(ext)s"
  
  youtube-dl "%var1%" -ci -o "C:\Music\ToBeDone\%var2%\%var3%" -f best -x --no-mtime --add-metadata 
  
  youtube-dl "%var1%" --skip-download -ci -o "C:\Music\ToBeDone\%var2%\Thumbnail\%var3%" --write-thumbnail
  
  youtube-dl "%var1%" --skip-download -ci -o "C:\Music\ToBeDone\%var2%\Description\%var3%" --write-description

  second edit :
  http://www.fileformat.info/info/unicode/char/25c4/index.htm
  so i found the symbol but i’m having trouble in finding out how each locale relates to the symbol...

  Like what about each locale makes the symbol usable to cmd ?

  third edit :
  worse come to worse and there is no locale that supports all unicode characters, or to do what i want it to,
  These are the unique characters that i’ve identified and have problems with right now,
  Ö

  ◄ ヽ( ≧ω≦)ﾉ

  ( ͡° ͜ʖ ͡°)

  (_≧∇≦)

  †

  【

• Piwik 2.1 – Changes for Plugin developers

  24 février 2014, par Piwik Core Team — Development

  This blog post is aimed at developers of Piwik Plugins. If you are simply using Piwik and not developing plugins for Piwik, you do not need to read this post.

  Piwik 2.1 will be released in a few days . This blog post will inform Piwik Plugin developers of the changes in Piwik 2.1 that may require that you update your plugin to work with this latest version.

  Breaking API changes

  Piwik can now handle an unlimited number of users having Super User access (#2589 #4564). In the past Piwik was limited to one Super User who was defined in the config file. From now on all users with Super User access are defined in the database the same way a regular user is. This brought some API changes but we will stay backward compatible until the first of April 2014. This gives you some time to migrate any custom plugins you may use. Although there is a layer for backward compatibility we recommend to make sure your plugin works with Piwik as soon as possible before April 1st.

  List of changes

  Deprecated methods

  The following methods are deprecated and we recommend to use the new methods from now on. There are also some methods which won’t be replaced so make sure to adjust the logic of your plugin.

  \Piwik\Piwik::isUserIsSuperUser => \Piwik\Piwik::hasUserSuperUserAccess
  
  \Piwik\Piwik::setUserIsSuperUser => \Piwik\Piwik::setUserHasSuperUserAccess
  
  \Piwik\Piwik::checkUserIsSuperUser => \Piwik\Piwik::checkUserHasSuperUserAccess
  
  \Piwik\Access::isSuperUser => \Piwik\Access::hasSuperUserAccess
  
  \Piwik\Access::checkUserIsSuperUser => \Piwik\Access::checkUserHasSuperUserAccess
  
  \Piwik\Access::setSuperUser => \Piwik\Access::setSuperUserAccess
  
  \FakeAccess::checkUserIsSuperUser => FakeAccess::checkUserHasSuperUserAccess
  
  \FakeAccess::setSuperUser => FakeAccess::setSuperUserAccess
  
  \Piwik\Piwik::isUserIsSuperUserOrTheUser => \Piwik\Piwik::hasUserSuperUserAccessOrIsTheUser
  
  \Piwik\Piwik::checkUserIsSuperUserOrTheUser => \Piwik\Piwik::checkUserHasSuperUserAccessOrIsTheUser
  
  \FakeAccess::getSuperUserLogin => No replacement
  
  \Piwik\Piwik::getSuperUserLogin => No replacement, returns the userLogin of the first Super User we find in the database 
  
  \Piwik\Piwik::getSuperUserEmail => No replacement, returns an empty string from now on
  
  \Piwik\Access::getSuperUserLogin => No replacement, returns the userLogin of the first Super User we find in the database

  Config Super User

  As mentioned, the Super User was defined in the config and you have accessed the Super User’s data either by using a convenient method like Piwik::getSuperUserLogin or directly via the Config object as follows :

  \Piwik\Config::getInstance->superUser

  As the config user is no longer defined in the config this will no longer work in the future. To stay backward compatible we return the first super user found in the database. This is not necessarily always the same user. So if you have used the super user login in some way in your plugin, make sure you are using the new function such as Piwik::getSuperUserLogin

  Extended Auth Interface

  The last change affects plugins who specify their own Authentication mechanism, for instance when using the custom LoginLDAP plugin. From now on the interface \Piwik\Auth (​https://github.com/piwik/piwik/blob/master/core/Auth.php) requires the methods setTokenAuth and setLogin. There is no backward compatibility layer but we had a look at some plugins defining a custom Authentication adapter to make sure those methods are already defined there as expected.

  For another example of a Login plugin, check out the LoginHttpAuth plugin on the Marketplace.

  After updating the plugin

  After you have made changes in your plugin to keep it compatible with Piwik 2.1, your plugin will no longer work with previous Piwik versions. Therefore you should define the minimum required version in your plugin.json file as follows :

  "require": {
  
   "piwik": ">=2.1" 
  
  }

  Summary

  Piwik 2.1 introduces some changes in the Piwik Core APIs. This blog post explains how to modify any Plugins compatible with Piwik 2.0 to be compatible with Piwik 2.1. Thank you for taking the time to update your plugins !

  Let us know if you have any feedback. Happy hacking !

  PS : if you use the Web Analytics APIs and the Web Tracking APIs, we guarantee that we will support backwards compatibility of our Web APIs.