Recherche avancée

Médias (1)

Mot : - Tags -/Rennes

Autres articles (67)

  • List of compatible distributions

    26 avril 2011, par

    The table below is the list of Linux distributions compatible with the automated installation script of MediaSPIP. Distribution nameVersion nameVersion number Debian Squeeze 6.x.x Debian Weezy 7.x.x Debian Jessie 8.x.x Ubuntu The Precise Pangolin 12.04 LTS Ubuntu The Trusty Tahr 14.04
    If you want to help us improve this list, you can provide us access to a machine whose distribution is not mentioned above or send the necessary fixes to add (...)

  • Submit bugs and patches

    13 avril 2011

    Unfortunately a software is never perfect.
    If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
    If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
    You may also (...)

  • Création définitive du canal

    12 mars 2010, par

    Lorsque votre demande est validée, vous pouvez alors procéder à la création proprement dite du canal. Chaque canal est un site à part entière placé sous votre responsabilité. Les administrateurs de la plateforme n’y ont aucun accès.
    A la validation, vous recevez un email vous invitant donc à créer votre canal.
    Pour ce faire il vous suffit de vous rendre à son adresse, dans notre exemple "http://votre_sous_domaine.mediaspip.net".
    A ce moment là un mot de passe vous est demandé, il vous suffit d’y (...)

Sur d’autres sites (7390)

  • Why is exec('which ffmpeg') returning nothing in my application ?

    28 avril 2015, par EchoLogic

    I’m trying to deal with FFMpeg for my application, but I’m encountering some difficulty in getting it set up. To instantiate or create an instance of FFMpeg, I need to call a create() method and pass through the operating locations of FFMpeg and FFProbe. To do this, I was hoping to be able to write :

           $ffmpeg = FFMpeg\FFMpeg::create([
                   'ffmpeg.binaries' => exec('which ffmpeg'),
                   'ffprobe.binaries' => exec('which ffprobe')
           ]);

    But, sadly, the command exec('which ffmpeg') returns an empty string. If I run the ’which ffmpeg’ command in Terminal, I get a response :

    /usr/local/bin/ffmpeg

    So why does it work in my terminal, but not when my PHP script tries to execute it ?

    I’ve tried a few solutions, such as appending 2>&1 to the end of the command, which did not help, running the command in shell_exec(), and placing the output in the second parameter of exec() which also did not solve my issue.

    I feel like this may be some sort of weird permissions issue...

    Addendum

    It has been brought to my attention that PHP cannot see my $PATH variable. From the console, echo $PATH produces :

    /Applications/MAMP/bin/php/php5.6.2/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:‌​/sbin:/opt/X11/bin:/usr/local/git/bin:/opt/ImageMagick/bin

    While calling the same from my application with exec() produces :

    /usr/bin:/bin:/usr/sbin:/sbin237.671000
  • How to run one script after another in Apple Script

    19 juillet 2015, par mskx4

    I’m trying with Apple Script to run three different scripts that would alow me to :

    1. Convert a purchased m4a file into an "anonymized" m4a file and extract its artwork (with ffmpeg)
    2. Attach the artwork to the file previously converted, since the converted file won’t maintain its artwork (with AtomicParsley)
    3. Remove the artwork from his path

    I don’t have any kind of programming knowledge, I’ve collected different script from the web and tried to make an app that could do these 3 simple task :

    on open argv
      set paths to ""
      repeat with f in argv
          set paths to paths & quoted form of POSIX path of f & " "
      end repeat
      tell application "Terminal"
           do script "for f in " & paths & "; do ffmpeg -i \"$f\" -acodec copy -y \"$f\" output.jpg; done"
           activate
           do script "for f in " & paths & "; do AtomicParsley \"$f\" --artwork output.jpg; done"
           activate
           do script "rm output. jpg"
           activate
      end tell
    end open

    The problem is that, when I drop a file on the app, it opens three terminal windows at once and it runs the three tasks in the same time, with the obvious result that the conversion fails : the first task overwrites the input file, and the second script should use the output of the first one as its input file. So I need the three scripts to be executed successively, one after another.

  • Using FFMPEG in Java (developing on Mac)

    1er mai 2012, par Luuk D. Jansen

    I am trying to evoke FFMPEG directly in my Java code (running under the Playframework !).
    The final product will run on a Linux/Debian distro, but I first need to test on my Mac (I don't know if it works on Debian yet).

    I try to execute the simple code :

    Process pr = Runtime.getRuntime().exec(new String[]{"bash","-c", "ffmpeg"});

    or simpler :

    Process pr = Runtime.getRuntime().exec("ffmpeg")

    or using ProcessBuilder :

    Process pr = new ProcessBuilder("/opt/local/bin/ffmpeg").start();

    What I get is an error code 133, but I cannot find what this means.
    In the terminal the command gives the normal output. I can also replace 'ffmpeg' with e.g. 'ls -la' and get the directory listing. But I don't know what the problem is that ffmpeg does not work.

    Anybody any clues ?
    Thanks !

    UPDATE :
    I looked at the error stream. These are the errors I get. How is it that it works in the terminal, but not in using Java ?

    14:43:19,619 DEBUG ~ FFMPEG: dyld: Library not loaded: /opt/local/lib/libogg.0.dylib
    14:43:19,619 DEBUG ~ FFMPEG:   Referenced from: /opt/local/bin/ffmpeg
    14:43:19,619 DEBUG ~ FFMPEG:   Reason: Incompatible library version: ffmpeg requires version 9.0.0 or later, but libogg.0.dylib provides version 6.0.0