Recherche avancée

Sur d’autres sites (4372)

• error : `FFMPEG` can not read `` in google colab

  3 avril 2023, par 5opka

  the error occurs when loading a video file (mp4) previously the code worked with this video.
to run https://colab.research.google.com/github/AliaksandrSiarohin/first-order-model/blob/master/demo.ipynb
you need to put !pip install -U scikit-image==0.18.0 in the first cell.
video can download this https://youtu.be/smQvWpqX13I (144p).


  


  InitializationError         Traceback (most recent call last)&#xA;/usr/local/lib/python3.9/dist-packages/imageio/core/imopen.py &#xA;in imopen(uri, io_mode, plugin, extension, format_hint, &#xA;legacy_mode, **kwargs)&#xA;    141         try:&#xA;--> 142             return loader(request, **kwargs)&#xA;    143         except InitializationError as class_specific:&#xA;    &#xA;20 frames&#xA;    &#xA;InitializationError: `FFMPEG` can not read `<bytes>`.&#xA;&#xA;The above exception was the direct cause of the following &#xA;exception:&#xA;&#xA;RuntimeError           Traceback (most recent call last)&#xA;/usr/local/lib/python3.9/dist-packages/imageio/core/imopen.py &#xA;in imopen(uri, io_mode, plugin, extension, format_hint, &#xA;legacy_mode, **kwargs)&#xA;    158 &#xA;    159         request.finish()&#xA;--> 160         raise err_type(err_msg) from err_from&#xA;    161 &#xA;    162     # fast-path based on format_hint&#xA;&#xA;RuntimeError: `FFMPEG` can not handle the given uri.&#xA;</bytes>

  


• Google App Engine - Access file after uploaded to bucket

  28 mai 2021, par jessiPP

  I have uploaded a file using my google app engine backend to my storage bucket but now I cannot access the file to pass in into ffmpeg. I am getting this error message from the try-catch : "The input file does not exist". I can see that the file was uploaded because I checked my developer console under the storage bucket. I am using the boilerplate code provided by google but added the ffmpeg for testing. I am trying to access the path to the uploaded file using, but it is incorrect, though I am getting the bucket.name value and the blob.name value. I am using the "flex" environment for this.

  


  const originalFilePath = `gs://${bucket.name}/${blob.name}`; 


  


  here is the full code :

  


  const process = require('process'); // Required to mock environment variables
const express = require('express');
const helpers = require('./helpers/index');
const Multer = require('multer');
const bodyParser = require('body-parser');
const ffmpeg = require("ffmpeg"); //https://www.npmjs.com/package/ffmpeg
const {Storage} = require('@google-cloud/storage');

// Instantiate a storage client
const storage = new Storage();

const app = express();
app.set('view engine', 'pug');
app.use(bodyParser.json());

// Multer is required to process file uploads and make them available via
// req.files.
const multer = Multer({
storage: Multer.memoryStorage(),
 limits: {
  fileSize: 5 * 1024 * 1024, // no larger than 5mb, you can change as needed.
 },
});

// A bucket is a container for objects (files).
const bucket = storage.bucket(process.env.GCLOUD_STORAGE_BUCKET);

// Display a form for uploading files.
app.get('/', (req, res) => {
 res.render('form.pug');
});

// Process the file upload and upload to Google Cloud Storage.
app.post('/upload', multer.single('file'), (req, res, next) => {

if (!req.file) {
 res.status(400).send('No file uploaded.');
 return;
}

// Create a new blob in the bucket and upload the file data.
const blob = bucket.file(req.file.originalname);
const blobStream = blob.createWriteStream({
 resumable: false,
});

blobStream.on('error', err => {
 next(err);
});

blobStream.on('finish', () => {

const audioFile = helpers.replaceAllExceptNumbersAndLetters(new Date());

// this path is incorrect but I cannot find correct way to do it
const originalFilePath = `gs://${bucket.name}/${blob.name}`; 

const filePathOutput = `gs://${bucket.name}/${audioFile}.mp3`;

try {
 const process = new ffmpeg(originalFilePath);
 process.then(function (video) {
 // Callback mode
 video.fnExtractSoundToMP3(filePathOutput, (error, file) => {
 if (!error)
  res.send(`audio file: ${file}`);
 });
}, (error) => {
 res.send(`process error: ${error}`);

});
} catch (e) {
 res.send(`try catch error: ${JSON.stringify(e)} | bucket: ${JSON.stringify(bucket)} | 
 blob: : ${JSON.stringify(blob)}`);
}  


});

blobStream.end(req.file.buffer);

});

const PORT = process.env.PORT || 8080;
app.listen(PORT, () => {
 console.log(`App listening on port ${PORT}`);
 console.log('Press Ctrl+C to quit.');
});


module.exports = app;


  


• Revision 25eeac0518 : Skip COMDAT sections when parsing COFF Fixes https://code.google.com/p/chromium

  4 février 2014, par Rui Ueyama

  Changed Paths :
   Modify /build/make/obj_int_extract.c

  
  
  Skip COMDAT sections when parsing COFF

  Fixes https://code.google.com/p/chromium/issues/detail?id=339889
  when building Clang-based ASan on Windows

  Change-Id : Ib77d9593636f46827dbb77f087d407ec0f463fc7