Recherche avancée

Sur d’autres sites (8152)

• ffmpeg : error on large input file [duplicate]

  1er octobre 2016, par ingenious

  This question already has an answer here :

  • ffmpeg convert from H.264 (High 4:4:4 Profile) to H.264 (Main Profile)
    
    1 answer
    

  I have a large Mov file with this info :

  

  I want convert it to mp4 by this ffmpeg command :

  ffmpeg -i 57d5092f59418.mov -codec:v libx264 -profile:v high -preset slow 
  
  -b:v 360k -maxrate 424k -bufsize 720k -vf scale=-1:360 -threads 0 -b:a 64k
  
  out.mov

  But I get this error :

  Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height

  detail :

          ffmpeg version N-81784-g92de2c2 Copyright (c) 2000-2016 the FFmpeg developers
  
        built with gcc 5.4.0 (GCC)
  
        configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-dx
  
      va2 --enable-libmfx --enable-nvenc --enable-avisynth --enable-bzlib --enable-lib
  
      ebur128 --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --ena
  
      ble-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libfree
  
      type --enable-libgme --enable-libgsm --enable-libilbc --enable-libmodplug --enab
  
      le-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-lib
  
      openh264 --enable-libopenjpeg --enable-libopus --enable-librtmp --enable-libschr
  
      oedinger --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheor
  
      a --enable-libtwolame --enable-libvidstab --enable-libvo-amrwbenc --enable-libvo
  
      rbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --ena
  
      ble-libx265 --enable-libxavs --enable-libxvid --enable-libzimg --enable-lzma --e
  
      nable-decklink --enable-zlib
  
        libavutil      55. 30.100 / 55. 30.100
  
        libavcodec     57. 58.100 / 57. 58.100
  
        libavformat    57. 51.100 / 57. 51.100
  
        libavdevice    57.  0.102 / 57.  0.102
  
        libavfilter     6. 63.100 /  6. 63.100
  
        libswscale      4.  1.100 /  4.  1.100
  
        libswresample   2.  2.100 /  2.  2.100
  
        libpostproc    54.  0.100 / 54.  0.100
  
      Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '57d5092f59418.mov':
  
        Metadata:
  
          major_brand     : qt
  
          minor_version   : 537199360
  
          compatible_brands: qt
  
          creation_time   : 2016-02-09T07:33:27.000000Z
  
        Duration: 00:00:13.71, start: 0.000000, bitrate: 72247 kb/s
  
          Stream #0:0(eng): Video: qtrle (rle  / 0x20656C72), bgra, 1920x1080, 72242 k
  
      b/s, SAR 1:1 DAR 16:9, 29.97 fps, 29.97 tbr, 30k tbn, 30k tbc (default)
  
          Metadata:
  
            creation_time   : 2016-02-09T07:33:27.000000Z
  
            handler_name    : Apple Alias Data Handler
  
            encoder         : Animation
  
            timecode        : 00:00:08;17
  
          Stream #0:1(eng): Data: none (tmcd / 0x64636D74), 0 kb/s (default)
  
          Metadata:
  
            creation_time   : 2016-02-09T07:33:46.000000Z
  
            handler_name    : Apple Alias Data Handler
  
            timecode        : 00:00:08;17
  
      File 'out.mov' already exists. Overwrite ? [y/N] y
  
      No pixel format specified, yuv444p for H.264 encoding chosen.
  
      Use -pix_fmt yuv420p for compatibility with outdated media players.
  
      x264 [error]: high profile doesn't support 4:4:4
  
      [libx264 @ 00000000006f2f20] Error setting profile high.
  
      [libx264 @ 00000000006f2f20] Possible profiles: baseline main high high10 high42
  
      2 high444
  
      Output #0, mov, to 'out.mov':
  
        Metadata:
  
          major_brand     : qt
  
          minor_version   : 537199360
  
          compatible_brands: qt
  
          Stream #0:0(eng): Video: h264, none, q=2-31, SAR 1:1 DAR 0:0, 29.97 fps (def
  
      ault)
  
          Metadata:
  
            creation_time   : 2016-02-09T07:33:27.000000Z
  
            handler_name    : Apple Alias Data Handler
  
            timecode        : 00:00:08;17
  
            encoder         : Lavc57.58.100 libx264
  
      Stream mapping:
  
        Stream #0:0 -> #0:0 (qtrle (native) -> h264 (libx264))
  
      Error while opening encoder for output stream #0:0 - maybe incorrect parameters
  
      such as bit_rate, rate, width or height

  What shoud I do ?

  thanks

• af_hdcd : disable auto-convert by default

  5 octobre 2016, par Burt P

  af_hdcd : disable auto-convert by default
  As all known valid HDCD sample formats and sample rates are now handled
  
  by the filter, remove the scan that "invades the privacy" of the filter graph
  
  and turn off autoconvert by default as requested by Nicolas George.
  http://ffmpeg.org/pipermail/ffmpeg-devel/2016-August/197571.html
  Signed-off-by : Burt P <pburt0@gmail.com>
  

  • [DH] libavfilter/af_hdcd.c

• Piwik 3 Development Update #4 – Important notes and breaking changes

  2 octobre 2016, par Piwik Core Team — Community, Development

  As mentioned in the previous development updates #1 New UI design, API changes & release date, #2 Git master branch will become Piwik 3 and #3 Marketplace we are actively working on the Piwik 3 update and we will release a first beta of it soon. While the update brings many new features and bugfixes, it also comes with some important changes that may require your attention which we detail in this blog post.

  Database updates

  To keep Piwik upgrades as easy as possible, we have usually avoided database schema changes that affect large tables during the Piwik 2.X release cycle. The Piwik 3 update will however require several database updates in order to fix some limitations and bugs in the Piwik database schema. If you have a fair amount of traffic and/or large Piwik database, we recommend to execute the database updates for Piwik 3 on the command line.

  If you struggle updating Piwik you can also get in touch with the Piwik Support and ask for a quote so we can help you with upgrading.

  New server & browser Requirements

  Piwik 3 updates the server requirements. Piwik 3 now requires :

  • PHP 5.5.9 or newer (we used to require PHP 5.3+),
  • MySQL 5.5 or newer or MariaDB (we used to require MySQL 4.1+).

  If you are still on an old PHP and MySQL version we highly recommend to update directly to PHP 7 and a recent MySQL version (MySQL 5.7+).

  Piwik 3 also drops support for the older browsers IE8 and IE9.

  Default filter_limit now applies to all HTTP API methods (#8458)

  In the past the default filter_limit of 100 rows was applied to HTTP API methods that return a report. This means that by default :

  • when you requested a method like SitesManager.getAllSites, UsersManager.getUsers or Goals.getGoals (which are not reports), we returned all rows.
  • when you fetched a report like Actions.getPageUrls (which is a report), the result was limited to 100 rows.

  This behaviour was inconsistent and it was hard to understand which methods apply the default limit and which did not. We now apply the default limit to all HTTP API methods by default.

  If your API consumer or app needs to fetch all results for an API method, you can append the following parameter to the URL : &filter_limit=-1. Alternatively, if you wish to change the default filter_limit automatically for all APIs, you can override the API_datatable_default_limit config setting in your config/config.ini.php file.

  For more information about the various APIs parameters you can use, see Piwik Analytics HTTP API Reference.

  Proxy client IP detection (#10342)

  This is only important if you are using the proxy_client_headers[] config in the config/config.ini.php file, ie. your Piwik server is behind a proxy.

  When Piwik is set up to fetch the client IP address from the proxy headers, and the header contained more than one IP address, we used to use the last IP address. From Piwik 3 we will be using the first IP address which is in line with the protocol definition. For example if HTTP_X_FORWARDED_FOR contains multiple IP addresses, we now use the first IP instead of the last one.

  Writable Piwik JavaScript Tracker file piwik.js

  From Piwik 3 we recommend to have the file /piwik.js writable in your Piwik directory, so that the PHP and webserver processes can edit this file. It is not required to have the file writable for Piwik to function well, but we are working on some enhanced features that will only work when the file is writable. If you don’t know whether this file is writable, go to “Administration => System Check” as a Super User and Piwik will display a warning if the file is not writable. If needed, you might be able to make the file writable by executing a command like chmod 0755 piwik.js or chown $webuser piwik.js (on Linux).

  Changes for plugin developers

  In the previous development updates we have already introduced some of the changes that affect Piwik plugin developers. We have made several improvements to the Marketplace that allow developers to promote their plugin better and to maintain their plugin page easier. We have also created a migration guide for plugin developers to make it easier to migrate a plugin to Piwik 3.

  For a list of all changes have a look at the developer changelog.

  Until our next Piwik 3 update, be well, and Happy Analytics !