Recherche avancée

Médias (29)

Mot : - Tags -/Musique

Autres articles (106)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

  • Personnaliser en ajoutant son logo, sa bannière ou son image de fond

    5 septembre 2013, par

    Certains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;

  • Use, discuss, criticize

    13 avril 2011, par

    Talk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
    The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
    A discussion list is available for all exchanges between users.

Sur d’autres sites (12965)

  • ffmpeg converting mov to mp4

    16 mai 2019, par alienbuild

    Trying to convert .mov to .mp4. Tried various suggestion codes on stackoverflow but nothing seems to be working.

    `...muxer does not support non seekable output [48] => Could not write header for output file #0 (incorrect codec parameters ?): Invalid argument [49] => Error initializing output stream 0:0 -- [50] => Conversion failed! ) 1`

    I’ve tried various codec properties such as ac3, aac, libvo_aacenc

    exec('
    /usr/local/bin/ffmpeg -y -i https://***.***.com/assets/regions/region-1/input.mov' .
    ' -c:a ac3 '
    . 'https://***.***.com/assets/regions/region-1/output.mp4'
    . ' 2>&1', $out, $res);

    $modx->log(modX::LOG_LEVEL_ERROR, print_r($out));
    $modx->log(modX::LOG_LEVEL_ERROR, $res);

    return true;
  • No such file or Directory in android FFMpeg [duplicate]

    4 mai 2017, par Anil kumar

    This question is an exact duplicate of :

    Hi i am using FFMpeg for splitting recorded video files and i searched lot in google for executing FFMpeg splitting command,But no one provided me
    right solution and i am facing this issue since 3 days on words.

    I am using below code for splitting video per every 8 seconds but i am getting exception No such file or Directory,I hope some one help me

    code :

    public void executeBinaryCommand(FFmpeg ffmpeg) {

               try {

                   if (ffmpeg != null) {

               inputFileUrl=  /storage/emulated/0/1492848702.mp4;
               outputFileUrl= /storage/emulated/0/1492848702.mp4;

               String cmd[] = new String[]{"-i ",inputFileUrl+" ","-c ","copy ","-map ","0 ",
                   "-segment_time ","8 ","-f ","segment/sdcard/Download/output%03d.mp4"};

                       ffmpeg.execute(command,
                               new ExecuteBinaryResponseHandler() {

                                   @Override
                                   public void onFailure(String response) {
                                       System.out.println("failure====>" + response.toString());
                                   }

                                   @Override
                                   public void onSuccess(String response) {
                                       System.out.println("resposense====>" + response.toString());
                                   }

                                   @Override
                                   public void onProgress(String response) {
                                       System.out.println("on progress");
                                   }

                                   @Override
                                   public void onStart() {
                                       System.out.println("start");
                                   }

                                   @Override
                                   public void onFinish() {
                                       System.out.println("Finish");
                                   }
                               });
                   }
               } catch (FFmpegCommandAlreadyRunningException exception) {
                   exception.printStackTrace();
               }
  • How are ARM GPUs supported by Video display/decoding/encoding Programs ?

    7 juillet 2020, par John Allard

    I often see ARM-based chips advertising onboard GPUs, like the RPI3 that came with "Broadcom VideoCore IV @ 250 MHz" and the OdroidC2 that comes with a "Mali-450 GPU". These chips advertise stuff like "Decode 4k/30FPS, Encode 1080p,30FPS" as the capabilities of the GPU for encoding and decoding videos.

    


    My question is this - how does a program like Kodi, VLC, or FFMPEG come to make use of these GPUs for actual encoding and decoding ? When I do research on how to make use of the Mali-450 GPU, for example, I find some esoteric and poorly documented C-examples of sending compressed frames to the GPU and getting decoded frames back. If I were to use a device like the OdroidC2 and install VLC on it, how does VLC make use of the GPU ? Did someone have to write logic into VLC to use the specific encoding/decoding API exposed by the Mali GPU in order to use it or do these GPUs follow some sort of consistent API that is exposed by all GPUs and VLC/Kodi can just program against this system API ?

    


    The reason I ask this question is that VLC and Kodi tend to support these GPUs out of the Box, but a very popular program like FFMPEG that prides itself on supporting as many codecs and accelerators as possible has no support for decoding and encoding with the Mali GPU series. Why would VLC/Kodi support encoding/decoding and not FFMPEG ? Why do these manufacturers claim wild decoding and encoding support if these GPUs are difficult to program against and one must use their custom esoteric APIs instead of something like libavcodec ?

    


    I hope my question makes sense, I guess what I'm curious about is that GPUs on most systems whether it be the Intel HD Graphics, Nvidia cards, AMD cards, etc seem to be used automatically by most video players but when it comes to using something like FFMPEG against these devices the process becomes much more process and you need to custom compile the build and give special flags to use the device as intended. Is there something I'm missing here ? Is VLC programmed to make use of all of these different type of GPUs ? And why, in that case, does FFMEPG not support Mali GPUs out of the Box ?