Recherche avancée

Sur d’autres sites (8251)

• Revision ebb583d291 : Add a test vector for loopfilter The test vector exercises the loopfilter behav

  4 décembre 2013, par Jingning Han

  Changed Paths :
   Modify /test/test.mk

  
   Modify /test/test_vector_test.cc

  
  
  Add a test vector for loopfilter

  The test vector exercises the loopfilter behavior at frame boundary.

  blue_sky_1080p25.y4m —good —cpu-used=2 —threads=0 —profile=0
  — lag-in-frames=25 —limit=300 —min-q=0 —max-q=63 —cq-level=20
  — end-usage=0 —auto-alt-ref=1 -p 2 —kf-max-dist=9999 —kf-min-dist=0
  — drop-frame=0 —static-thresh=0 —bias-pct=50 —minsection-pct=0
  — maxsection-pct=2000 —arnr-maxframes=7 —arnr-strength=5
  — arnr-type=3 —sharpness=0 —undershoot-pct=100 —target-bitrate=6000

  Change-Id : Ibd0807395d2fe87f24f81f990369678df3de7c23

• Running Background Process using FFMPEG on Google Cloud Run stopping in middle

  7 juillet 2021, par pashaplus

  I have an external bash script that transcodes audio files using FFmpeg and then uploads the files to google cloud storage. I am using the google cloud run platform for this process but the process is stopping in the middle and not getting any clue from the logs. I am using the node js spawn command to execute the bash script

  


      const createHLSVOD = spawn('/bin/bash', [script, file.path, file.destination, contentId, EPPO_MUSIC_HSL_URL, 'Content', speed]);
    createHLSVOD.stdout.on('data', d => console.log(`stdout info: ${d}`));
    createHLSVOD.stderr.on('data', d => console.log(`stderr error: ${d}`));
    createHLSVOD.on('error', d => console.log(`error: ${d}`));
    createHLSVOD.on('close', code => console.log(`child process ended with code ${code}`));


  


  on cloud run beginning the process itself taking a lot of time but in my local machine transcoding and uploading is very fast. after some time transcoding logs are being stopped and no new logs appear. I have no clue what is happening

  


  

  


  so what is happening here ? why it is very slow in the first place and why the process is being stopped in middle without any error

  


  node js script

  


  Transcoding script

  


  Dockerfile

  


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