Recherche avancée

Médias (1)

Mot : - Tags -/wave

Autres articles (79)

  • MediaSPIP Core : La Configuration

    9 novembre 2010, par

    MediaSPIP Core fournit par défaut trois pages différentes de configuration (ces pages utilisent le plugin de configuration CFG pour fonctionner) : une page spécifique à la configuration générale du squelettes ; une page spécifique à la configuration de la page d’accueil du site ; une page spécifique à la configuration des secteurs ;
    Il fournit également une page supplémentaire qui n’apparait que lorsque certains plugins sont activés permettant de contrôler l’affichage et les fonctionnalités spécifiques (...)

  • Emballe médias : à quoi cela sert ?

    4 février 2011, par

    Ce plugin vise à gérer des sites de mise en ligne de documents de tous types.
    Il crée des "médias", à savoir : un "média" est un article au sens SPIP créé automatiquement lors du téléversement d’un document qu’il soit audio, vidéo, image ou textuel ; un seul document ne peut être lié à un article dit "média" ;

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

  • Setup FFMpegCore in Visual Studio 2019

    27 juillet 2022, par DsiakMondala

    I am confused on the basics of using a library. I understand that there is a library called FFMpeg and a wrapper called FFMpegCore so we can use FFMpeg with C#, correct ? I downloaded both FFMpeg and FFMpegCore and I have them in my project's folder. Although I didn't perceive any class named FFMpegOptions in either of the file's folders.
I am stuck on how to actually set it up so I can use it in my little project, I never downloaded someone's library before. Can somebody please walk me though the motions of connecting the three of them together ?

    


    So far I experimented with :

    


      

    • Add a reference to my project, but there doesn't seem to be any .dll, .tlb, .olb, .ocx or .exe files to add
    • 


    • Add an existing project to my solution. There is a project called FFMpegCore.csproj but adding it raises a missing SDK error. Weirdly enough, opening the same project as a standalone doesn't raise any issues which makes me thing the operation I am trying is inadequate.
    • 


    


    I am sure this is a silly and easy setup to perform but I just don't know enough to find a solution.

    


  • FFMPEG for Android - missing alsa format

    24 août 2012, par user1545779

    @rowntreerob has an android-ffmpeg implementation that build successfully using the default file settings.

    When you remove disble-avdevice and disbale-devices from the configure_ffmpeg script, ndk-build fails. The following is the error message :

    CP ffmpeg
    STRIP ffmpeg
     /android-ffmpeg/Project/jni
     /android-ffmpeg/Project/jni
     /android-ffmpeg/Project/jni
    jasongipsyblues@android-master : /android-ffmpeg/Project/jni$ ndk-build
    Compile thumb : ffmpeg <= ffmpeg.c
    Compile thumb : ffmpeg <= cmdutils.c
    Executable : ffmpeg
    /home/jasongipsyblues/android-ffmpeg/Project/obj/local/armeabi- >v7a/objs/ffmpeg/ffmpeg/ffmpeg.o : In function `main' :

    /home/jasongipsyblues/android-ffmpeg/Project/jni/ffmpeg/ffmpeg.c:6130 : undefined >reference to `avdevice_register_all'

    /home/jasongipsyblues/android-ffmpeg/Project/obj/local/armeabi- >v7a/objs/ffmpeg/ffmpeg/cmdutils.o : In function `print_all_libs_info' :

    /home/jasongipsyblues/android-ffmpeg/Project/jni/ffmpeg/cmdutils.c:639 : undefined >reference to `avdevice_configuration'

    /home/jasongipsyblues/android-ffmpeg/Project/jni/ffmpeg/cmdutils.c:639 : undefined >reference to `avdevice_version'

    collect2 : ld returned 1 exit status

    make : ** [/home/jasongipsyblues/android-ffmpeg/Project/obj/local/armeabi-v7a/ffmpeg] >Error 1

    Please pardon my poor formating skills, I still dont get the formating thing. It appears the deletion of the references is to avdevices is definitely affecting the use of ndk-build.

    All the alsa source files exist in the ffmpeg code. How does one build ffmpeg in such a way that alsa is included in the formats ?

  • Console Log Stream information using ffmpeg node.js

    5 mars 2019, par Matteo

    I have created a work application that links in room encoders to live stream onto Facebook, Twitter and Youtube. I am wondering as to how to properly log the stream quality on the CMD. Below are snippets of the code and where I think the logic should be to properly pull the stream quality and display it in the cmd :

    Pushing Stream :

       if (req.query.french_facebook) {
     var streamComplete = req.query.fb_fre_streamURL + req.query.fb_fre_streamKey;
     temp = checkValidity('Facebook', 'French', req.query.fb_fre_streamURL, req.query.fb_fre_streamKey, status);
     status = temp[0];
     valid = temp[1];
     if (valid == true) {
       var command = `ffmpeg -re -i ${inputURL2('French',req.query.fb_fre_venue)} -c:v copy -acodec aac -ac 1 -ar 44100 -x264-params keyint=60:scenecut=0 -strict -2 -f flv "${streamComplete}"`;
       var process = nodeCmd.run(command);
       createStream(req.query.username, 'Facebook', 'French', req.query.fb_fre_streamKey, process.pid);
     } else {
       console.error("ERROR: unable to create stream");
     }
    }

    App initialization :

       var createError = require('http-errors');
    var express = require('express');
    var path = require('path');
    var cookieParser = require('cookie-parser');
    var logger = require('morgan');

    var indexRouter = require('./routes/index');
    var usersRouter = require('./routes/users');

    var app = express();

    var fs = require('fs');

    // view engine setup
    app.set('views', path.join(__dirname, 'views'));
    app.set('view engine', 'ejs');

    // app.use(logger('dev'));
    app.use(express.json());
    app.use(express.urlencoded({ extended: false }));
    app.use(cookieParser());
    app.use(express.static(path.join(__dirname, 'public')));

    app.use('/', indexRouter);
    app.use('/users', usersRouter);

    // catch 404 and forward to error handler
    app.use(function(req, res, next) {
     next(createError(404));
    });

    // error handler
    app.use(function(err, req, res, next) {
     // set locals, only providing error in development
     res.locals.message = err.message;
     res.locals.error = req.app.get('env') === 'development' ? err : {};

     // render the error page
     res.status(err.status || 500);
     res.render('error');
    });

    module.exports = app;

    If there is anything I am not making clear please let me know