Recherche avancée

Médias (91)

Autres articles (31)

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

  • Submit bugs and patches

    13 avril 2011

    Unfortunately a software is never perfect.
    If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
    If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
    You may also (...)

  • Contribute to translation

    13 avril 2011

    You can help us to improve the language used in the software interface to make MediaSPIP more accessible and user-friendly. You can also translate the interface into any language that allows it to spread to new linguistic communities.
    To do this, we use the translation interface of SPIP where the all the language modules of MediaSPIP are available. Just subscribe to the mailing list and request further informantion on translation.
    MediaSPIP is currently available in French and English (...)

Sur d’autres sites (3837)

  • Anomalie #2214 (Nouveau) : référence à breves

    9 août 2011, par Julien -

    dans objets/infos/rubrique.html au niveau du on a une référence à ’BREVES’ alors que c’est l’extension breves qui devrait trouver le moyen d’afficher des infos ici (l’extension breves doit se suffire a elle même...) en s’appuyant sur le Objectif : ceux qui vont développer de nouveaux objets (...)

  • Passing streams from Fluent-ffmpeg to Google Cloud Storage

    31 octobre 2019, par Emilio Faria

    Is there a way to pass a stream from Fluent-mmpeg to Google Cloud Storage ? I’m trying to allow the user to upload any kind of media (audio or video), and I want to convert it to flac before uploading it to GCS.

    I’m using a few middlewares on my route, such as :

    routes.post(
    
  '/upload',
    
  multer.single('audio'),
    
  ConvertController.convert,
    
  UploadController.upload,
    
  FileController.save,
    
  (req, res, next) => res.send('ok')
    
);

    I was able to stream from Multer to Fluent-mmpeg and save to a file using this code on ConvertController :

    async convert(req, res, next) {
    
    ffmpeg(streamifier.createReadStream(req.file.buffer))
    
      .format('flac')
    
      .output('outputfile.flac')
    
      .audioChannels(1)
    
      .on('progress', function(progress) {
    
        console.log(progress);
    
      })
    
      .run();
    
  }

    But I would like to use .pipe() to pass it to UploadController, where I would then upload to GCS :

    class UploadController {
    
  async upload(req, res, next) {
    
    const gcsHelpers = require('../helpers/google-cloud-storage');
    
    const { storage } = gcsHelpers;
    

    
    const DEFAULT_BUCKET_NAME = 'my-bucket-name';
    

    
    const bucketName = DEFAULT_BUCKET_NAME;
    
    const bucket = storage.bucket(bucketName);
    
    const fileName = `test.flac`;
    
    const newFile = bucket.file(fileName);
    

    
    newFile.createWriteStream({
    
      metadata: {
    
        contentType: file.mimetype
    
      }
    
    })
    

    
    file.on('error', err => {
    
      throw err;
    
    });
    

    
    file.on('finish', () => console.log('finished'));
    
  }

    The problem is that I cannot find anywhere explaining how I can pass down a stream to the next middleware.

    Is it possible ?

  • vaapi_encode_h265 : Support more complex reference structures

    20 décembre 2018, par Mark Thompson
    vaapi_encode_h265 : Support more complex reference structures

    The reference picture sets are now constructed directly from the DPB
    
information.
    • [DH] libavcodec/vaapi_encode_h265.c

Navigation