Recherche avancée

Sur d’autres sites (7451)

• Batch Convert .264 files to any Video Format

  9 août 2022, par Reydan Gatchalian

  I've been trying to find a software that will batch convert .264 files to any video format. The source of the video files is from an IP Camera. I found a software from HiP2P Client that has a converter.exe but only converts 1 file at a time.

  


  

  


  I tried checking if it can be run in the Command Line and just pass parameteres but it doesn't. Then I tried referrencing the DLL files included on the application but I got the error below.

  


  

  


  Then I found ffmpeg (version : 2022-08-08-git-56973eb687-full_build-www.gyan.dev) and tried different commands but to no avail.

  


  ffmpeg -f h264 -i A220806_000015_000029.264 -c:v copy libx264 -an dest.avi


  


  


  


  I also tried looking for libraries so I can develop it using C# but I still can't find a library that works.

  


  I also tried VLC just to play it but I can't even play the files.

  


• Format video to upload on instagram API (Nodejs)

  6 octobre 2022, par Rafael de Carvalho

  I'm trying to automate the process of posting photos and videos on instagram but I constantly get errors when uploading to instagram.

  


  I will leave a video duration error here but several others happen, I need to follow the following requirements :

  


  

  • Container : MOV or MP4 (MPEG-4 Part 14), no edit lists, atom moov in front of file

  


  • Audio codec : AAC, 48 kHz maximum sampling rate, 1 or 2 channel (mono or stereo)

  


  • Video codec : HEVC or H.264, progressive scan, closed GOP, 4:2:0 chroma subsampling

  


  • Frame rate : from 23 to 60 FPS

  


  • photo size :

    

    • Maximum columns (horizontal pixels) : 1,920

    


    • Minimum aspect ratio [columns/rows] : 4/5

    


    • Maximum aspect ratio [columns/rows] : 9/16

    


    


  


  • Video bitrate : 5Mbps maximum VBR

  


  • Audio bitrate : 128 kbps

  


  • Duration : maximum 60 seconds and minimum 3 seconds

  


  • File size : max 100 MB

  


  


  My code :

  


  import { S3 } from 'aws-sdk';
import { IgApiClient } from 'instagram-private-api';
import fs from 'fs';

const s3 = new S3();
const ig = new IgApiClient();
const bucket = 'posts';
const { INSTA_USER, INSTA_PASS } = process.env;

ig.state.generateDevice(INSTA_USER);

export const main = async () => {
  try {
    await ig.account.login(INSTA_USER, INSTA_PASS);

    const { Contents } = await s3.listObjectsV2({ Bucket: bucket, MaxKeys: 2, Prefix: 'memes/geral' }).promise();

    const files = await Promise.all(Contents.map(async ({ Key }) => {
      const file = await s3.getObject({
        Bucket: bucket,
        Key,
      }).promise();

      return file.Body;
    }));

    const publishResult = await ig.publish.video({
      video: files[0],
      coverImage: await fs.readFileAsync("../../src/assets/cover.png")
    });

    console.dir({ publishResult }, { depth: null })
  } catch (error) {
    console.error(error);
    throw error;
  }
}


  


  When I get a file from s3, it comes in the following format.
I'm taking the content of the body property and put it in the video property of the publish method.
Is it right ?
I also tried to save the file with fs.writeFile and dps use readFileSync like in the example but it also gave the same error.

  


  {
    AcceptRanges: 'bytes',
    LastModified: 2022-08-04T23:15:24.000Z,
    ContentLength: 3252472,
    ETag: '"c491cfe2fb5bc29777fc34391fc1d56a"',
    ContentType: 'application/octet-stream',
    Body: Buffer(3252472) [Uint8Array] [
        0,   0,   0,  32, 102, 116, 121, 112, 105, 115, 111, 109,
        0,   0,   2,   0, 105, 115, 111, 109, 105, 115, 111,  50,
       97, 118,  99,  49, 109, 112,  52,  49,   0,   0, 209,   0,
      109, 111, 111, 118,   0,   0,   0, 108, 109, 118, 104, 100,
        0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,
        0,   0,   3, 232,   0,   0, 250,  17,   0,   1,   0,   0,
        1,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,
        0,   1,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,
        0,   0,   0,   0,
      ... 3252372 more items
    ]
  }


  


  Error :

  


  {
    "errorMessage": "POST /api/v1/media/upload_finish/?video=1 - 400 Bad Request; server processing error: VideoSourceDurationCheckException",
    "errorType": "IgUploadVideoError",
    "stackTrace": [
        "IgUploadVideoError: POST /api/v1/media/upload_finish/?video=1 - 400 Bad Request; server processing error: VideoSourceDurationCheckException",
        "    at C:\\Users\\User\\Desktop\\dev\\Insta\\.webpack\\service\\src\\functions\\webpack:\\instagram-private-api\\dist\\services\\publish.service.js:26:1",  
        "    at tryCatcher (C:\\Users\\User\\Desktop\\dev\\Insta\\.webpack\\service\\src\\functions\\webpack:\\bluebird\\js\\release\\util.js:16:1)"
}


  


  when I try to post a video under 60 seconds (apparently within the requirements) :

  


  {
    "errorMessage": "POST /api/v1/media/configure/?video=1 - 403 Forbidden; ",
    "errorType": "IgConfigureVideoError",
    "stackTrace": [
        "IgConfigureVideoError: POST /api/v1/media/configure/?video=1 - 403 Forbidden; ",
        "    at PublishService.video (C:\\Users\\User\\Desktop\\dev\\Insta\\.webpack\\service\\src\\functions\\webpack:\\instagram-private-api\\dist\\services\\publish.service.js:123:1)",        
        "    at C:\\Users\\User\\Desktop\\dev\\Insta\\.webpack\\service\\src\\functions\\webpack:\\src\\functions\\cronFreefireMemes.js:71:31",
        "    at async Promise.all (index 1)",
        "    at main (C:\\Users\\User\\Desktop\\dev\\Insta\\.webpack\\service\\src\\functions\\webpack:\\src\\functions\\cronFreefireMemes.js:47:5)"
    ]
}


  


  I know that the error above is happening because of the size of the video which is longer than 60 seconds.

  


  But I would like to know if there is any way I can format any video to fit the instagram requirements.

  


  Any nodejs library ?

  


• ffmpeg crashes with "Internal bug", "Failed to inject frame into filter network" while trying to convert PNG files into an animated gif using filters

  12 août 2022, par EigentlichOracler

  ffmpeg version : ffmpeg version 4.2.7-0ubuntu0.1

  


  Kernel : 5.4.0-122-lowlatency #138-Ubuntu SMP PREEMPT x86_64 x86_64 x86_64 GNU/Linux

  


  PNG-Images : 996 pieces, all equal in size : 1000x50

  


  Then trying to build palette using palettegen :

  


  export filters="scale=1000:-1:flags=lanczos"
export palette=./stripes_palette.png
ffmpeg -v warning -i ./palette_source_stripes.png -vf "$filters,palettegen=stats_mode=diff" -y $palette
[Parsed_palettegen_1 @ 0x55f0eea30e00] Dupped color: FF63000D


  


  Palette file has been created, looks good so far. Then I tried to convert all 996 PNG files into one single (space optimized) animated GIF file using paletteuse :

  


  ffmpeg -v warning -framerate 5 -thread_queue_size 2048 -i ./tmp/temp.%04d.png -i $palette -lavfi "$filters,paletteuse=dither=bayer:bayer_scale=5:diff_mode=rectangle" -r 5 -loop -1 -y testanim.gif
Error while filtering: Internal bug, should not have happened
Failed to inject frame into filter network: Internal bug, should not have happened
Error while processing the decoded data for stream #0:0


  


  The reason for "-framerate 5" for the input and "-r 5" for the output is : I wanted the animated GIF to use a determined time for running through animation. It already had worked out without using complex filtering, but the results were huge GIF files which are hard to handle.
But even when I avoid both framerate parameters, still the same error message occurs.

  


  Should I look deeper into the "Dupped color" which has been mentioned ? Did anybody encounter a similar issue using ffmpeg ?
I'm not used to deal with filters (nor "complex filters") in ffmpeg, I'm very new at this, but I've found no tips regarding an ffmpeg crash like I've right here.

  


  ------------------------------- EDIT 2022-08-12/1 ---------------------

  


  Same error occurs with current stable version
ffmpeg version 4.4.2-0ubuntu0.22.04.1 Copyright (c) 2000-2021 the FFmpeg developers

  


  ------------------------------- EDIT 2022-08-12/2 ---------------------

  


  Found workaround, see answer below