Recherche avancée

Sur d’autres sites (8315)

• What does "Error in the pull function" mean while executing ffmpeg command ?

  8 avril 2022, par Alex Rypun

  I'm trying to generate a video from multiple video sources (https urls).

  


  If I use say 8 video sources it works as expected. But if I need say 30 sources, it starts to work as expected, but at some moment a lot of errors appear.

  


  

  


  I believe the main one is Error in the pull function..

  


  Such a video-source appears in the output file but not a full requested part (e.g., I set trim=0:5, but ffmpeg generates only 3 seconds).

  


  I tried different videos, different cropped parts, loaded sources to aws s3, but can't identify a "bad case", it's reproduced with different options.

  


  My command looks like this :

  


  ffmpeg -y
-i "https://player.vimeo.com/external/399541658.hd.mp4?s=5432956383527af00bb74b41c120bbb84ff3ac5e&profile_id=175&oauth2_token_id=57447761"
...
-i "https://player.vimeo.com/external/464966383.hd.mp4?s=648aa8277259c499f1d05d6330f9922932c080a6&profile_id=175&oauth2_token_id=57447761"
-i "https://test.com/development/videos/dc3c32cf9a194db1bb52/sources/5q5e3j2h57.mp3"
-filter_complex "[0:v]trim=0:5.64,setpts=PTS-STARTPTS,scale=1920x1080,setdar=16/9[v0];[1:v]trim=0:8,setpts=PTS-STARTPTS,scale=1920x1080,setdar=16/9,loop=0:32767[v1]; ... [10:v]trim=0:13,setpts=PTS-STARTPTS,scale=1920x1080,setdar=16/9[v10];[v0] ... [v10] concat=n=11:v=1 [video];[11:a] atrim=0:99.29 [audio]"
-vsync 2 -map [video] -map [audio] output.mp4


  


  When I downloaded all sources to my local machine and tried to use them in the ffmpeg command it worked fine without errors.

  


  Also, I figured out that it depends on the CPU. When I restricted my CPU the errors appeared earlier. And some commands might produce errors with a restricted CPU but finished successfully with no CPU restriction.

  


  As I understand, for some reason, ffmpeg fails to receive a particular part of a file data, but I believe it should retry to receive lost packages (it's https).

  


  And I don't understand, how it could be related to CPU or sources quantity.

  


  By not understanding the core of evil, I can think about 2 ways (both ugly) :

  


  

  1. to download all sources and generate the final video from local files ;

  


  2. to chunk sources, generate intermediate outputs for each chunk (and save locally), and concatenate them into the final one.

  


  


  Any better suggestions or at least where to seek ?

  


• FFMPEG creating mp3 with "Junk" at the end

  13 juillet 2022, par Johnaras

  I have a web application which converts WebM files to mp3 using FFMPEG.js in the Client-Side. Once the mp3 conversion finishes, users are prompted to download their file.

  


  Lately, I realized that a lot of mp3 files which I tried to converted have a different duration value than the original WebM file. The duration is usually longer. For instance, a WebM file with duration of 2:16 gets converted to an mp3 file with a duration of 2:29. Once the player reaches at 2:16 it just goes back to the start.

  


  I have tried to open the file in Audacity but it keeps saying that this MP3 file seems to be "Malformed".

  


  I also tried to use MP3val and it says the file has junk at the end.

  


  Code Snippets :

  


  const worker = new Worker("/ffmpeg-worker-mp4.js");
import { fetchFile } from "@ffmpeg/ffmpeg"; // https://www.npmjs.com/package/@ffmpeg/ffmpeg

const convertSong = async (title, id, bitrate) => {
    setProgress("Initializing...")
    ffmpegVars = [title]
    
    worker.postMessage({
      type: "run",
      arguments: ["-i", `input.webm`, "-c:a", "libmp3lame",  "-vn", "-ab", `${bitrate ? bitrate : 256}k`, "-ar", "44100", "-f", "mp3", `output.mp3`],
      MEMFS: [{ name: "input.webm", data: await fetchFile(`/api/download/stream?video=${id}`) }]
    });
}

convertSong(data.title, data.id, data.bitrate)


  


  I'm literally willing to pay anyone who helps me fix this.

  


• Can't upload huge video to google storage. I using "@ffmpeg-installer/ffmpeg" and @google-cloud/storage

  20 juillet 2022, par Dmytro Petskovych

  I upload file to google storage using "@ffmpeg-installer/ffmpeg" and @google-cloud/storage in my node.js App.
Step 1. file uploading to fs is in child processes - one process for each type of resolution (totaly six).
step 2. encription (converting to stream)
step 3. upload to google storage

  


  I use "Upload a directory to a bucket" in order to send the video from the client to the Google Cloud Storage bucket.

  


  This way is working fine only with small file.

  


  when I upload video, actually I upload six videos, one for each type resolution

  


  for example when I upload video with duration one hour it split on chunk and totally I get more three thousands files.

  


  So actually i upload folder with large amount of files, but not all of this files are uploaded to cloud.

  


  maybe someone had the similar problem and helps fix it.

  


  


  


  const uploadFolder = async (bucketName, directoryPath, socketInstance) => {
    try {
      let dirCtr = 1;
      let itemCtr = 0;
      const fileList = [];

      const onComplete = async () => {
        const folderName = nanoid(46);

        await Promise.all(
          fileList.map(filePath => {
            const fileName = path.relative(directoryPath, filePath);
            const destination = `${ folderName }/${ fileName }`;

            return storage
              .bucket(bucketName)
              .upload(filePath, { destination })
              .then(
                uploadResp => ({ fileName: destination, status: uploadResp[0] }),
                err => ({ fileName: destination, response: err })
              );
          })
        );

        if (socketInstance) socketInstance.emit('uploadProgress', {
          message: `Added files to Google bucket`,
          last: false,
          part: false
        });

        return folderName;
      };

      const getFiles = async directory => {
        const items = await fs.readdir(directory);
        dirCtr--;
        itemCtr += items.length;
        for(const item of items) {
          const fullPath = path.join(directory, item);
          const stat = await fs.stat(fullPath);
          itemCtr--;
          if (stat.isFile()) {
            fileList.push(fullPath);
          } else if (stat.isDirectory()) {
            dirCtr++;
            await getFiles(fullPath);
          }
        }
      }

      await getFiles(directoryPath);

      return onComplete();
    } catch (e) {
      log.error(e.message);
      throw new Error('Can\'t store folder.');
    }
  };