Recherche avancée

Sur d’autres sites (10752)

• We're Creating a New AI tool and Got Stuck on This 1 Step [closed]

  22 février 2024, par Daniel

  Thanks for helping with this question,

  


  Anybody who knows PHP, React js, FFmpeg, or Open AI API can help here :

  


  We are currently creating a tool with PHP laravel and React JS. It lets normal creators input a simple text prompt and they'll get a fully original short (30 video fast-paced video) for their channel. But we have an output problem :

  


  

  • On the output of the videos, there's supposed to be AI generated images that have cool animations in order to make everything more fast paced. But our developers are making animations that are super slow and not dynamic or interesting enough. What open source library/tech could we use to create stunning animations and more action ?! Any suggestions would help here,

  


  


  ---

  


  We are currently using an FFmpeg to create a video automatically for our users. The videos consists of [images, captions, voiceover, background music, and animations) all generated by our AI tool and put together.

  


  Here's what we want as a video (dynamic, fast paced, and many animations) : https://drive.google.com/file/d/1ONCczJh_Uk9m6oRDPGFQYjJPWUhy8hdV/view?usp=sharing

  


  Here's what we're getting : https://drive.google.com/file/d/1sMKGB88ouTHsEdahc0Zyt8rKEvZWhTco/view?usp=sharing

  


  Thanks for any help here.

  


• Fileupload and ffmpeg processing in one step

  22 septembre 2023, par user3142695

  This is how I handle a file upload in my nodeJS / nestJS application. The file gets directly stored in mongodb using GridFSBucket.

  


  const upload = async (file): Promise<any> => {&#xA;    const res = await new Promise(async (resolve, reject) => {&#xA;        const { filename, mimetype, createReadStream } = await file&#xA;&#xA;        // Write image to db&#xA;        const bucket = new GridFSBucket(this.db)&#xA;        const stream = createReadStream()&#xA;        const writeStream = bucket.openUploadStream(filename, { contentType: mimetype })&#xA;        writeStream.on(&#x27;finish&#x27;, async (file) => {&#xA;            // do some stuff&#xA;            resolve()&#xA;        })&#xA;        writeStream.on(&#x27;error&#x27;, (error) => {&#xA;            console.error(error)&#xA;            reject(error)&#xA;        })&#xA;        stream.on(&#x27;error&#x27;, (error) => writeStream.destroy(error))&#xA;        stream.pipe(writeStream)&#xA;    })&#xA;    return res&#xA;}&#xA;</any>

  


  While this is working, I need to convert video files. Therefore I would like to use ffmpeg.

  


  Something like (did not test this)

  


  new Promise((resolve, reject) => {
    ffmpeg()
    .input(downloadStream)
    .inputFormat("mp4")
    .setFfprobePath(pathToFfprobe.path)
    .setFfmpegPath(pathToFfmpeg)
    .videoCodec("libx264")
    .audioCodec("libmp3lame")
    .on("error", (err) => {
        console.error(err);
    })
    .save("./??.mp4"); // -> to DB
});


  


  Is it possible to do the upload, processing and db storage in one workflow ? In my code I do the upload and db storing in one step, but I do not get it how to handle the video file processing...

  


• Recover h264 stream from gstreamer written to disk after h264parse step

  3 juillet 2023, par nioroso

  I have some files that were written to disk after the following pipeline :

  


  libcamera-vid -t 0 -n -o - | gst-launch1.0 fdsrc fd=0 ! h264parse config-interval=-1 ! tee name=output .output ! queue ! rtph264pay ! udpsink host=127.0.0.1 port=5600 .output ! queue ! filesink location=/video/$(date).h264 


  


  The problem is the pipeline is wrong, h264parse should have been before rtph264pay and now the file outputs are all invalid h264 bytestreams and I cant read them. The correct pipeline works fine and the h264 files are in the correct format for ffmpeg etc, but I need to recover the wrong format files.

  


  I tried the following pipelines but none where able to find valid data :

  


  gst-launch-1.0 filesrc location=./test.h264 ! decodebin ! avdec_h264 ! fakesink
gst-launch-1.0 filesrc location=./test.h264 ! h264parse ! avdec_h264 ! fakesink


  


  also ffmpeg cannot read this output file. Is there any way to recover these files ?

  


  Hexdump of some of the starting bytes of the file, in case its useful :

  


  00000000  00 00 00 25 27 64 00 28  ac 2b 40 28 83 df dc 20
00000010  00 00 03 00 20 00 00 03  01 5c 94 00 04 c4 b0 00
00000020  0b eb cd ef 70 0f 12 26  a0 00 00 00 05 28 ee 06
00000030  f2 c0 00 01 ef 3b 25 88  80 4f 89 47 d2 7b aa 73