Recherche avancée

Médias (1)

Mot : - Tags -/école

Autres articles (53)

  • Les autorisations surchargées par les plugins

    27 avril 2010, par

    Mediaspip core
    autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs

  • Encoding and processing into web-friendly formats

    13 avril 2011, par

    MediaSPIP automatically converts uploaded files to internet-compatible formats.
    Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
    Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
    Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
    All uploaded files are stored online in their original format, so you can (...)

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

  • Run ffmpeg from its parent directory in node js application in its own directory

    3 septembre 2022, par Belb

    I have a node js application which needs to access ffmpeg. My approach to this has been to use exec from the child_processes module built into Node. The problem is that exec always starts the cmd line from the current directory and I can't figure out how to point the directory context to where ffmpeg.exe is located so that I can access the program. Is my approach flawed ? How can I access a seperate CLI application from Node ?
    
This code returns "'ffmpeg' is not recognized as an internal or external command" because I'm obviously in Node's execution context which is not where ffmpeg is located.
    
I also do not want to store the node application in the directory of ffmpeg.exe because that's just lazy and impractical.

    


    exec(`ffmpeg -i ${filepathToMedia} --vf fps=1 ${outputdirectory}/out%d.png`, (error, stdout, stderr) => {
if (error) {
    console.log(`error: ${error.message}`);
    return;
}
if (stderr) {
    console.log(`stderr: ${stderr}`);
    return;
}
if(stdout) {
    console.log(`success: ${stdout}`)
} });


    


  • aacenc_tns : rework coefficient quantization and filter application

    1er septembre 2015, par Rostislav Pehlivanov
    aacenc_tns : rework coefficient quantization and filter application
    

    This commit reworks the TNS implementation to a hybrid between what
    the specifications say, what the decoder does and what’s the best
    thing to do.

    The filter application function was copied from the decoder and
    modified such that it applies the inverse AR filter to the
    coefficients. The LPC coefficients themselves are fed into the
    same quantization expression that the specifications say should
    be used however further processing is not done, instead they’re
    converted to the form that the decoder expects them to be in
    and are sent off to the compute_lpc_coeffs function exactly the
    way the decoder does. This function does all conversions and will
    return the exact coefficients that the decoder will generate, which
    are then applied to the coefficients.
    Having the exact same coefficients on both the encoder and decoder
    is a must since otherwise the entire sfb’s over which the filter
    is applied will be attenuated.

    Despite this major rework, TNS might not work fine on some audio
    types at very low bitrates (e.g. sub 90kbps) as it can attenuate
    some coefficients too much. Users are advised to experiment with
    TNS at higher bitrates if they wish to use this tool or simply
    wait for the implementation to be improved.

    Signed-off-by : Rostislav Pehlivanov <atomnuker@gmail.com>

    • [DH] libavcodec/aacenc.c
    • [DH] libavcodec/aacenc.h
    • [DH] libavcodec/aacenc_tns.c
    • [DH] libavcodec/aacenc_tns.h
  • FFMPEG : Application Error 0xc0000005

    9 septembre 2014, par oneofakind

    I have been running a script on ffmpeg and does fine in most of the PC that I deployed in. But, on few of them it keeps displaying an error 0xc0000005. I believe this is a Access Violation Error from the windows updates.

    I ran this command :

     fmpeg -r 4 -f dshow -an -i video="screen-capture-recorder" -video_size 2880x900 "C:\test.mp4"

    I tried to uninstall the windows update 2859537 but it does not exist. Is there any other way to fix this issue ? Please Help.

    Thank you.