Recherche avancée

Sur d’autres sites (9167)

• IOException on watermarking video on Android

  19 septembre 2016, par Stefan Ionescu

  I am trying to programmatically watermark a video in Android using WritingMinds’ Ffmpeg library from Github :

  https://github.com/WritingMinds/ffmpeg-android-java

  I did all they said in their documentation and imported the library in Android Studio.

  Still, it gives me an IOExeption with "No such file or directory".

  CODE

  public class MainActivity extends Activity {
  
  
  
  Button btn;
  
  Context context;
  
  
  
  String str;
  
  
  
  @Override
  
  protected void onCreate(Bundle savedInstanceState) {
  
  super.onCreate(savedInstanceState);
  
  setContentView(R.layout.activity_main);
  
  
  
  btn = (Button) findViewById(R.id.button);
  
  
  
  context = this;
  
  
  
  str = "ffmpeg -i /storage/extSdCard/DCIM/Camera/video.avi -i /storage/extSdCard/DCIM/Camera/logo.png -filter_complex 'overlay=10:main_h overlay_h-10' /storage/extSdCard/DCIM/Camera/watermarked.avi";
  
  
  
  btn.setOnClickListener(new View.OnClickListener() {
  
  @Override
  
  public void onClick(View view) {
  
  
  
  doFfmpeg(str.split(" "));
  
  
  
      }
  
    });
  
   }
  
  }
  
  
  
  public void doFfmpeg(String[] loc){
  
  
  
  FFmpeg ffmpeg = FFmpeg.getInstance(context);
  
  
  
  try {
  
  // to execute "ffmpeg -version" command you just need to pass "-version"
  
  ffmpeg.execute(loc, new ExecuteBinaryResponseHandler() {
  
  
  
  @Override
  
  public void onStart() {
  
  }
  
  
  
  @Override
  
  public void onProgress(String message) {
  
  }
  
  
  
  @Override
  
  public void onFailure(String message) {
  
  }
  
  
  
  @Override
  
  public void onSuccess(String message) {
  
  
  
  Toast.makeText(getApplicationContext(), "Success !", Toast.LENGTH_LONG).show();
  
  
  
  }
  
  
  
  @Override
  
  public void onFinish() {
  
    }
  
   });
  
  } catch (FFmpegCommandAlreadyRunningException e) {
  
  // Handle if FFmpeg is already running
  
  } catch (Exception e){
  
  
  
  }
  
  
  
   }
  
  }

  LOGS

  691 5092-5311/com.app.watermark.watermark E/FFmpeg: Exception while trying to run: [Ljava.lang.String;@338dbc60
  
  java.io.IOException: Error running exec(). Command: [/data/data/com.app.watermark.watermark/files/ffmpeg, -i, /storage/extSdCard/DCIM/Camera/video.avi, -i, /storage/extSdCard/DCIM/Camera/logo.png, -filter_complex, 'overlay=10:main_h-overlay_h-10', /storage/extSdCard/DCIM/Camera/watermarked.avi] Working Directory: null Environment: null
  
  at java.lang.ProcessManager.exec(ProcessManager.java:211)
  
  at java.lang.Runtime.exec(Runtime.java:173)
  
  at java.lang.Runtime.exec(Runtime.java:128)
  
  at com.github.hiteshsondhi88.libffmpeg.ShellCommand.run(ShellCommand.java:10)
  
  at com.github.hiteshsondhi88.libffmpeg.FFmpegExecuteAsyncTask.doInBackground(FFmpegExecuteAsyncTask.java:38)
  
  at com.github.hiteshsondhi88.libffmpeg.FFmpegExecuteAsyncTask.doInBackground(FFmpegExecuteAsyncTask.java:10)
  
  at android.os.AsyncTask$2.call(AsyncTask.java:288)
  
  at java.util.concurrent.FutureTask.run(FutureTask.java:237)
  
  at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:231)
  
  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
  
  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
  
  at java.lang.Thread.run(Thread.java:818)
  
  Caused by: java.io.IOException: No such file or directory
  
  at java.lang.ProcessManager.exec(Native Method)
  
  at java.lang.ProcessManager.exec(ProcessManager.java:209)
  
  at java.lang.Runtime.exec(Runtime.java:173) 
  
  at java.lang.Runtime.exec(Runtime.java:128) 
  
  at com.github.hiteshsondhi88.libffmpeg.ShellCommand.run(ShellCommand.java:10) 
  
  at com.github.hiteshsondhi88.libffmpeg.FFmpegExecuteAsyncTask.doInBackground(FFmpegExecuteAsyncTask.java:38)
  
  at com.github.hiteshsondhi88.libffmpeg.FFmpegExecuteAsyncTask.doInBackground(FFmpegExecuteAsyncTask.java:10)
  
  at android.os.AsyncTask$2.call(AsyncTask.java:288) 
  
  at java.util.concurrent.FutureTask.run(FutureTask.java:237) 
  
  at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:231) 
  
  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112) 
  
  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587) 
  
  at java.lang.Thread.run(Thread.java:818) 

  How can I make this work ?

• Piwik 3 Development Update #1 – New UI design, API changes & release date

  1er septembre 2016, par Thomas Steur — Community, Development

  Over the last months, we have been actively working on the Piwik 3 release and we want to introduce you to the changes that we have done so far. They include a new and modern UI redesign, new widgets for your dashboard, and technical improvements under the hood.

  New Piwik 3 UI

  Based on Material Design we have revamped the user interface which is now more responsive, more usable and faster. While the UI is not yet finished, we invite you to check it out already and to let us know what you think.

  

  This new Piwik material design is a visual language that synthesizes classic principles of good design with the innovation and possibility of technology and science.

  More responsive

  Piwik 3 will look and feel much better on your mobile phone and tablet. Many elements have been improved : the menus, the segment editor and dashboard selector, the widgets, the settings pages and most other pages so you can fully experience and enjoy Piwik on any device !

  

  Improved usability

  We have updated the menu structure, the dashboard selector as well as the footer in reports to make your life easier when using Piwik. We love to keep these complicated things simple. There are also many other tiny improvements that you will appreciate.

  

  The Zen Mode lets you view in full screen your analytics reports and dashboards. Users love this feature and it can now be accessed by pressing “z” key.

  

  Faster

  To make the Piwik interface faster, we have refactored most of our CSS, HTML and JavaScript and moved more and more of our code into the client. As a result, Piwik now needs to reload the page much less often ! For example when you change the date or change the segment, Piwik will now load the reports instantly. To improve performance even further, Piwik will now load multiple reports on a single page in parallel.

  Native fonts

  Over the last months more and more web services have started using system fonts, and so will Piwik 3. System fonts look better, improve language support and give you a more native, familiar feeling.

  For more details and screenshots have a look at the pull request for the Piwik 3 UI update.

  New widgets

  With the “Latest Piwik Plugin Updates” widget you won’t miss any newly added or updated plugin anymore. This will help you learn about and discover the useful plugins and themes available on the Marketplace.

  

  Super users can now see at a glance the current state of the Piwik system, thanks to the new “System Check” and “System Summary” widgets.

  

  API Changes

  Piwik is the leading open analytics platform, highly customisable and extensible thanks to a flexible plugins architecture and a design based on APIs. In this new major Piwik 3 release, we significantly improve the foundation of our open platform and several of its core APIs.

  The new Widgets and Reporting API makes it possible to add reports and widgets to any existing reporting page. In the past, reporting pages had to be created manually which was time consuming and it was hard to maintain a consistent look across different reporting pages. Now reporting pages are generated automatically by the Piwik platform.

  The Plugin Settings API was changed to improve performance and to let plugin developers customize the Websites Manager. This is one step towards our goal to let users not only manage websites but also mobile apps, cars, coffee machines or any other thing.

  To see a full list of changes in the Piwik 3 analytics platform, have a look at the developer changelog.

  Developer docs

  The Piwik Developer Zone is full of guides and API references to help developers understand, integrate and extend Piwik. As some APIs have changed in the Piwik 3 release it is now possible to select the Piwik version in the top right corner of the developer zone.

  

  We are updating guides for Piwik 3 and added a Piwik 2 -> Piwik 3 Migration Guide for plugin developers. Many other guides were updated such as Menus, Custom Report and Widgets.

  Release date

  The first Piwik 3 beta release will be available in the next four weeks. Beta testers automatically receive the update if they are subscribed to the “Latest Beta” release channel. The final Piwik 3 release will be ready before the end of the year. If you want to give it a try, you can either use Piwik from Git and check out the “3.x-dev” branch, or download Piwik 3 from GitHub.

  Closing thoughts

  With faster & more beautiful reports, better APIs and more stability, Piwik 3 is a big step forward for all Piwik users. As our mission is to create, as a community, the leading international open source web analytics platform that gives every user full control of their data, we are very excited to introduce you to this upcoming release.

  We now offer Custom Development services if you like to sponsor a new feature or bug fix, or if you have any custom requirements. And if you use Piwik Analytics to grow your business and need quality help, contact the Piwik analytics experts to get started.

  Until our next Piwik 3 dev update, Happy analysis !

• How to create a custom processor for audio files in Ruby on Rails(5) with Paperclip

  11 novembre 2016, par Thomas Roest

  So I’m trying to convert mp3 files into .flac with Paperclip custom processors and ffmpeg. The following code runs the ffmpeg command and creates a temporary flac file. However, it is not saved ? Currently only the original file is saved. What am I missing here ?

  class AudioFile < ApplicationRecord
  
    has_attached_file :raw_audio, processors: [:custom], styles: { original: {}}

  the custom processor

  module Paperclip
  
   class Custom < Processor
  
  
  
    def initialize(file, options = {}, attachment = nil)
  
      super
  
      @file = file
  
      @basename = File.basename(@file.path)
  
      @format = options[:format] || 'flac'
  
      @params = options[:params] || '-y -i' 
  
    end
  
  
  
    def make
  
      source = @file
  
      output = Tempfile.new([@basename, ".#{@format}"])
  
      begin
  
        parameters = [@params, ':source',':dest'].join(' ')
  
        Paperclip.run('ffmpeg', parameters, :source => File.expand_path(source.path), :dest => File.expand_path(output.path), :sample_rate => @sample_rate, :bit_rate => @bit_rate)
  
      end
  
     output
  
    end
  
  
  
   end
  
  end