Recherche avancée

Médias (0)

Mot : - Tags -/interaction

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (64)

  • Des sites réalisés avec MediaSPIP

    2 mai 2011, par

    Cette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
    Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page.

  • Support audio et vidéo HTML5

    10 avril 2011

    MediaSPIP utilise les balises HTML5 video et audio pour la lecture de documents multimedia en profitant des dernières innovations du W3C supportées par les navigateurs modernes.
    Pour les navigateurs plus anciens, le lecteur flash Flowplayer est utilisé.
    Le lecteur HTML5 utilisé a été spécifiquement créé pour MediaSPIP : il est complètement modifiable graphiquement pour correspondre à un thème choisi.
    Ces technologies permettent de distribuer vidéo et son à la fois sur des ordinateurs conventionnels (...)

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

  • libavcodec : Set hidden visibility on global symbols accessed from AArch64 assembly

    11 juillet 2022, par Martin Storsjö
    libavcodec : Set hidden visibility on global symbols accessed from AArch64 assembly
    

    The AArch64 assembly accesses those symbols directly, without
    indirection via e.g. the GOT on ELF. In order for this not to
    require text relocations, those symbols need to be resolved fully
    at link time, i.e. those symbols can't be interposable.

    Normally, so far, this is achieved when linking shared libraries
    in two ways ; we have a version script (libavcodec/libavcodec.v) which
    marks all symbols that don't start with av* as local. Additionally,
    we try to add -Wl,-Bsymbolic to the linker options if supported,
    making sure that such symbol references are resolved fully at link
    time, instead of making them interposable.

    When the libavcodec static library is linked into another shared
    library, there's no guarantee that it uses similar options (even though
    that would be favourable), which would end up requiring text relocations
    in the AArch64 assembly.

    Explicitly mark the symbols that are accessed from AArch64 assembly
    as hidden, so that they are resolved fully at link time even without
    the version script and -Wl,-Bsymbolic.

    Signed-off-by : Martin Storsjö <martin@martin.st>

    • [DH] libavcodec/aacsbrdata.h
    • [DH] libavcodec/fft.h
    • [DH] libavcodec/vp9dsp.h
    • [DH] libavutil/attributes_internal.h
  • FFMPEG mp3 file segmentation on Mac OSx Error . Only one full mp3 file generated as segmented file

    2 novembre 2017, par iThirst

    What I am trying to achieve is to take an MP3 file as source file and generate multiple segments of approx 10s each from it. I am using node’s fluent ffmpeg inside node js application. Below code works absolutely fine and generates proper results on Linux/Ubuntu 16.04 server while fails with below error on mac osx. It ends by generating single .mp3 file and .m3u8 playlist file on mac osx while it generates multiple segmented mp3 files (each 11s) if executed on ubuntu server.

    Error Log:
    [mp3 @ 0x7fc469010c00] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 9223372036854422218 >= -9223372033278215478
    [segment @ 0x7fc469006a00] Packets poorly interleaved, failed to avoid negative timestamp -9223372033277846838 in stream 0.

    // Node js code to execute ffmpeg command is given below

    var command = ffmpeg(fs.createReadStream(directoryPath + fileName), {timeout : 900})
                       .inputFormat('mp3')
                       .inputOptions([                    
                           //'-re',
                           //'-i input.mp3',
                           //directoryPath +'albumart.jpg',
                           '-codec copy',
                           '-map 0',
                           '-f segment',
                           '-segment_list ' + directoryPath + fileName_noExtension + '.m3u8',
                           '-segment_list_flags +live',
                           '-segment_time 10',
                            directoryPath + 'out%03d.mp3'
                       ]);
    command.on('start',{}).on('stderror').on('end').output(directoryPath +  'Out.mp3')
           .run()

    //

    Any help is appreciated in this direction.

  • Batch file to add separate audio file to MP4 file [closed]

    30 janvier 2021, par MrRoso

    I have a couple of video files (MP4) with audio in France.&#xA;Video1.mp4, Video2.mp4, Video3.mp4, ……&#xA;In the same directory, I have the same couple of audio files in English (m4a).&#xA;Audio1.m4a, Audio2.m4a, Audio3.m4a, ……

    &#xA;

    The command

    &#xA;

    ffmpeg -i "Video1.mp4" -i "Audio1m4a" -map 0 -map 1:a -c copy "Out.mp4"&#xA;

    &#xA;

    to add the audio file to the Video file works fine, but I need to do this for each video and audio file manually.

    &#xA;

    I want to do this in a batch file, like this :

    &#xA;

    @Echo off&#xA;for %%i in (*.MP4) %%j in (*.m4a) do ffmpeg -i "%%i" -i "%%j" -map 0 -map 1:a -codec copy "/new/%%~nI.mp4"&#xA;

    &#xA;

    But I get the follow error message :&#xA;"% j" cannot be processed syntactically at this point.

    &#xA;

    Also the new batch file ends in an error :

    &#xA;

    @Echo off&#xA;for /F tokens=i,j %%i in (*.MP4) %%j in (*.m4a) do ffmpeg -i "%%i" -i "%%j" -map 0 -map 1:a -codec  copy "/new/%%~nI.mp4"&#xA;

    &#xA;

    Error Message :&#xA;"i" cannot be processed syntactically at this point.

    &#xA;

    Has someone a batch file for me, which is working ?

    &#xA;

    Best regards

    &#xA;