Recherche avancée

Sur d’autres sites (9354)

• Capture ffmpeg's metadata output in powershell

  17 janvier 2021, par xdhmoore

  I'm trying to capture the output of ffmpeg in PowerShell(tm) to get some metadata on some ogg & mp3 files. But when I do :

  



  ffmpeg -i file.ogg 2>&1 | sls GENRE


  



  The output includes a bunch of lines without my matching string, "GENRE" :

  



        album_artist    : Post Human Era
      ARTIST          : Post Human Era
      COMMENT         : Visit http://posthumanera.bandcamp.com
      DATE            : 2013
      GENRE           : Music
      TITLE           : Supplies
      track           : 1
At least one output file must be specified


  



  I am guessing something is different in the encoding. ffmpeg's output is colored, so maybe there are color control characters in the output that are breaking things ? Or, maybe ffmpeg's output isn't playing nicely with powershell's default UTF-16 ? I can't figure out if there is another way to redirect stderr and remove the color characters or change the encoding of stderr.

  



  EDIT :
Strangely, I also get indeterminate output. Sometimes the output is as shown above. Sometimes with precisely the same command the output is :

  



        GENRE           :


  



  

  



  Which makes slightly more sense, but is still missing the part of the line I care about ('Music').

  



  Somewhere powershell is interpreting something as newlines that is not newlines.

  


• Capture ffmpeg's metadata output in powershell

  17 mars 2016, par xdhmoore

  I’m trying to capture the output of ffmpeg in PowerShell(tm) to get some metadata on some ogg & mp3 files. But when I do :

  ffmpeg -i file.ogg 2>&1 | sls GENRE

  The output includes a bunch of lines without my matching string, "GENRE" :

        album_artist    : Post Human Era
  
        ARTIST          : Post Human Era
  
        COMMENT         : Visit http://posthumanera.bandcamp.com
  
        DATE            : 2013
  
        GENRE           : Music
  
        TITLE           : Supplies
  
        track           : 1
  
  At least one output file must be specified

  I am guessing something is different in the encoding. ffmpeg’s output is colored, so maybe there are color control characters in the output that are breaking things ? Or, maybe ffmpeg’s output isn’t playing nicely with powershell’s default UTF-16 ? I can’t figure out if there is another way to redirect stderr and remove the color characters or change the encoding of stderr.

  EDIT :
  Strangely, I also get indeterminate output. Sometimes the output is as shown above. Sometimes with precisely the same command the output is :

        GENRE           :

  

  Which makes slightly more sense, but is still missing the part of the line I care about (’Music’).

  Somewhere powershell is interpreting something as newlines that is not newlines.

• Piwik 2.10.0 – Release Candidate

  22 décembre 2014, par Piwik Core Team — Community

  We are proud to announce that the release candidate for Piwik 2.10.0 is now available !

  How do I upgrade to the release candidate ?

  You can upgrade to the release candidate in one click, by following instructions in this FAQ.

  Think you’ve found a bug ?

  Please create a bug report in our issue tracker.

  What’s new in Piwik 2.10.0 ?

  Since our last release Piwik 2.9.1 one month ago, over 100 issues have been closed. We’ve focused on fixing bugs, improving performance, and we created a new plugin that will let you better scale Piwik to very high traffic websites using Redis.

  Much improved Log Analytics

  Log Analytics is the powerful little-known feature of Piwik that lets you import dozens of different server logs into Piwik. In Piwik 2.10.0 you can now import Netscaler logs, IIS Advanced Logging Module logs, W3C extended logs and AWS CloudFront logs. Piwik will also automatically track the username as the User ID and/or the Page Generation Time when it is found in the server logs.

  Better scalability using Redis (advanced users)

  At Piwik PRO we are working on making Piwik scale when tracking millions of requests per month. In this release we have revamped the Tracking API. By using the new QueuedTracking plugin you can now queue tracking requests in a Redis database, which lets you scale the Piwik tracking service. The plugin is included as Free/libre software in the core Piwik platform. More information in the QueuedTracking user guide.

  Better performance

  A few performance challenges have been fixed in this release.

  The Visitor Log and the Live API will render much faster on very high traffic websites. Any custom date ranges that you have selected as default in your User Settings (eg. ‘Last 7 days’ or ‘Previous 30 days’) will now be pre-processed so that your analytics dashboard will always load quickly.

  For users on shared hosting, the real time widgets could be use a lot of server resource as they are refreshed every ten seconds. We’ve improved this by only requesting data when the Browser Tab containing the Real time widgets is active.

  Other changes

  We packed in many other changes in this release such as compatibility with Mysql 5.6 and Geo location support for IPv6 addresses. A community member made Piwik compatible with Internet Explorer 9 when running in compatibility mode (which is still used in several companies).

  The Tracker algorithm has been updated : when an existing visit uses a new Campaign then it will force creating a new visit (same behavior as Google Analytics).

  If you need professional support or guidance, get in touch with Piwik PRO.

  Changelog for Piwik 2.10.0 – we plan to release Piwik 2.10.0 around 2015 Jan 5th.

  Happy Analytics, and we wish you a nice holiday season !