Recherche avancée

Médias (2)

Mot : - Tags -/media

Autres articles (95)

  • 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 (...)

  • Multilang : améliorer l’interface pour les blocs multilingues

    18 février 2011, par

    Multilang est un plugin supplémentaire qui n’est pas activé par défaut lors de l’initialisation de MediaSPIP.
    Après son activation, une préconfiguration est mise en place automatiquement par MediaSPIP init permettant à la nouvelle fonctionnalité d’être automatiquement opérationnelle. Il n’est donc pas obligatoire de passer par une étape de configuration pour cela.

  • HTML5 audio and video support

    13 avril 2011, par

    MediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
    The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
    For older browsers the Flowplayer flash fallback is used.
    MediaSPIP allows for media playback on major mobile platforms with the above (...)

Sur d’autres sites (11146)

  • ffmpeg fails with a wall of red hex output but only when in a bash loop

    5 septembre 2018, par jozxyqk

    Similar question here, but no solution : https://www.reddit.com/r/linuxquestions/comments/m00f0/hex_output_from_ffmpeg_when_run_in_a_loop/

    I’m trying to batch encode some video. I have a list of filenames in a text file and read each one in a bash loop. This is it :

    OUT=./out
    mkdir -p $OUT

    while read inputfile; do
    b=$(basename "$inputfile")
    outputfile="$OUT/$b"
    echo
    echo
    echo "$inputfile"
    echo "$outputfile"
    echo
    ffmpeg -i "$inputfile" "$outputfile" || exit
    done < files.txt

    When I run it, the ffmpeg command seems to start OK, then spits out a massive wall of red hex dump like text (as below). It does finish without error, but the file is only a few hundred frames long.

    [libx264 @ 0x1b68d60] frame= 537 QP=31.44 NAL=0 Slice:B Poc:70  I:2    P:239  SKIP:987  size=516 bytes
    stream #1:                                                                                                                                                
     keyframe=1                                                                                                                                              
     duration=0.024                                                                                                                                          
     dts=25.992  pts=25.992                                                                                                                                  
     size=336                                                                                                                                                
    00000000  ff fb 84 64 1a 0e d3 21 3f d4 93 18 6a e6 33 a4 ...d...!?...j.3.
    00000010  6a 63 25 22 4a 0c d1 1d 52 6c bd ab c0 bf 23 69 jc%"J...Rl....#i
    ... LOTS MORE

    The other really weird thing is that the next inputfile in the bash loop is broken and has only the last few characters, which does not happen if I simply comment out the ffmpeg line.

    What could ffmpeg be doing to interfere with the bash loop like this ?

    (ffmpeg 2.8.6, bash 4.3.42(1), fedora 23)

  • ffmpeg fails with a wall of red hex output but only when in a bash loop

    2 avril 2016, par jozxyqk

    Similar question here, but no solution : https://www.reddit.com/r/linuxquestions/comments/m00f0/hex_output_from_ffmpeg_when_run_in_a_loop/

    I’m trying to batch encode some video. I have a list of filenames in a text file and read each one in a bash loop. This is it :

    OUT=./out
    mkdir -p $OUT

    while read inputfile; do
    b=$(basename "$inputfile")
    outputfile="$OUT/$b"
    echo
    echo
    echo "$inputfile"
    echo "$outputfile"
    echo
    ffmpeg -i "$inputfile" "$outputfile" || exit
    done < files.txt

    When I run it, the ffmpeg command seems to start OK, then spits out a massive wall of red hex dump like text (as below). It does finish without error, but the file is only a few hundred frames long.

    [libx264 @ 0x1b68d60] frame= 537 QP=31.44 NAL=0 Slice:B Poc:70  I:2    P:239  SKIP:987  size=516 bytes
    stream #1:                                                                                                                                                
     keyframe=1                                                                                                                                              
     duration=0.024                                                                                                                                          
     dts=25.992  pts=25.992                                                                                                                                  
     size=336                                                                                                                                                
    00000000  ff fb 84 64 1a 0e d3 21 3f d4 93 18 6a e6 33 a4 ...d...!?...j.3.
    00000010  6a 63 25 22 4a 0c d1 1d 52 6c bd ab c0 bf 23 69 jc%"J...Rl....#i
    ... LOTS MORE

    The other really weird thing is that the next inputfile in the bash loop is broken and has only the last few characters, which does not happen if I simply comment out the ffmpeg line.

    What could ffmpeg be doing to interfere with the bash loop like this ?

    (ffmpeg 2.8.6, bash 4.3.42(1), fedora 23)

  • Value in a const global structure changed [closed]

    9 juillet 2023, par codeconscious

    I have a weird problem, I am compiling FFmpeg for an arm64 target and it is crashing due to what seems like a global buffer overflow. I have localized the culprit to something very odd.

    


    There's a structure in FFmpeg :

    


    static const AVClass codec2_mux_class = {
    .class_name = "codec2 muxer",
    .item_name  = av_default_item_name,
    .version    = LIBAVUTIL_VERSION_INT,
    .category   = AV_CLASS_CATEGORY_DEMUXER, // the value is 4
};



    


    so even though this is a static const, when accessing it the .category element is not 4 when it should be and the last element of the structure which is not initialized is not NULL, but interestingly points to the next structure (which is right under it in the codec2.c).

    


    Any clue what could be going on here ?

    


    Also since this is static const I thought this would be put in data.ro and from the objdump this does indeed seem to be the case. But the value still somehow manages to get changed in the global structure ?

    


    Notes :

    


    The structure is defined in this : https://github.com/FFmpeg/FFmpeg/blob/master/libavutil/log.h#L66