Recherche avancée

Sur d’autres sites (7554)

• ffmpeg failed to load audio file

  14 avril 2024, par Vaishnav Ghenge

  Failed to load audio: ffmpeg version 5.1.4-0+deb12u1 Copyright (c) Failed to load audio: ffmpeg version 5.1.4-0+deb12u1 Copyright (c) 2000-2023 the FFmpeg developers
  built with gcc 12 (Debian 12.2.0-14)
  configuration: --prefix=/usr --extra-version=0+deb12u1 --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --arch=amd64 --enable-gpl --disable-stripping --enable-gnutls --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libdav1d --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libglslang --enable-libgme --enable-libgsm --enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librabbitmq --enable-librist --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libsrt --enable-libssh --enable-libsvtav1 --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzimg --enable-libzmq --enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opencl --enable-opengl --enable-sdl2 --disable-sndio --enable-libjxl --enable-pocketsphinx --enable-librsvg --enable-libmfx --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libx264 --enable-libplacebo --enable-librav1e --enable-shared
  libavutil      57. 28.100 / 57. 28.100
  libavcodec     59. 37.100 / 59. 37.100
  libavformat    59. 27.100 / 59. 27.100
  libavdevice    59.  7.100 / 59.  7.100
  libavfilter     8. 44.100 /  8. 44.100
  libswscale      6.  7.100 /  6.  7.100
  libswresample   4.  7.100 /  4.  7.100
  libpostproc    56.  6.100 / 56.  6.100
/tmp/tmpjlchcpdm.wav: Invalid data found when processing input


  


  backend :

  


  
@app.route("/transcribe", methods=["POST"])
def transcribe():
    # Check if audio file is present in the request
    if 'audio_file' not in request.files:
        return jsonify({"error": "No file part"}), 400
    
    audio_file = request.files.get('audio_file')

    # Check if audio_file is sent in files
    if not audio_file:
        return jsonify({"error": "`audio_file` is missing in request.files"}), 400

    # Check if the file is present
    if audio_file.filename == '':
        return jsonify({"error": "No selected file"}), 400

    # Save the file with a unique name
    filename = secure_filename(audio_file.filename)
    unique_filename = os.path.join("uploads", str(uuid.uuid4()) + '_' + filename)
    # audio_file.save(unique_filename)
    
    # Read the contents of the audio file
    contents = audio_file.read()

    max_file_size = 500 * 1024 * 1024
    if len(contents) > max_file_size:
        return jsonify({"error": "File is too large"}), 400

    # Check if the file extension suggests it's a WAV file
    if not filename.lower().endswith('.wav'):
        # Delete the file if it's not a WAV file
        os.remove(unique_filename)
        return jsonify({"error": "Only WAV files are supported"}), 400

    print(f"\033[92m{filename}\033[0m")

    # Call Celery task asynchronously
    result = transcribe_audio.delay(contents)

    return jsonify({
        "task_id": result.id,
        "status": "pending"
    })


@celery_app.task
def transcribe_audio(contents):
    # Transcribe the audio
    try:
        # Create a temporary file to save the audio data
        with tempfile.NamedTemporaryFile(suffix=".wav", delete=False) as temp_audio:
            temp_path = temp_audio.name
            temp_audio.write(contents)

            print(f"\033[92mFile temporary path: {temp_path}\033[0m")
            transcribe_start_time = time.time()

            # Transcribe the audio
            transcription = transcribe_with_whisper(temp_path)
            
            transcribe_end_time = time.time()
            print(f"\033[92mTranscripted text: {transcription}\033[0m")

            return transcription, transcribe_end_time - transcribe_start_time

    except Exception as e:
        print(f"\033[92mError: {e}\033[0m")
        return str(e)


  


  frontend :

  


      useEffect(() => {
        const init = () => {
            navigator.mediaDevices.getUserMedia({audio: true})
                .then((audioStream) => {
                    const recorder = new MediaRecorder(audioStream);

                    recorder.ondataavailable = e => {
                        if (e.data.size > 0) {
                            setChunks(prevChunks => [...prevChunks, e.data]);
                        }
                    };

                    recorder.onerror = (e) => {
                        console.log("error: ", e);
                    }

                    recorder.onstart = () => {
                        console.log("started");
                    }

                    recorder.start();

                    setStream(audioStream);
                    setRecorder(recorder);
                });
        }

        init();

        return () => {
            if (recorder && recorder.state === 'recording') {
                recorder.stop();
            }

            if (stream) {
                stream.getTracks().forEach(track => track.stop());
            }
        }
    }, []);

    useEffect(() => {
        // Send chunks of audio data to the backend at regular intervals
        const intervalId = setInterval(() => {
            if (recorder && recorder.state === 'recording') {
                recorder.requestData(); // Trigger data available event
            }
        }, 8000); // Adjust the interval as needed


        return () => {
            if (intervalId) {
                console.log("Interval cleared");
                clearInterval(intervalId);
            }
        };
    }, [recorder]);

    useEffect(() => {
        const processAudio = async () => {
            if (chunks.length > 0) {
                // Send the latest chunk to the server for transcription
                const latestChunk = chunks[chunks.length - 1];

                const audioBlob = new Blob([latestChunk]);
                convertBlobToAudioFile(audioBlob);
            }
        };

        void processAudio();
    }, [chunks]);

    const convertBlobToAudioFile = useCallback((blob: Blob) => {
        // Convert Blob to audio file (e.g., WAV)
        // This conversion may require using a third-party library or service
        // For example, you can use the MediaRecorder API to record audio in WAV format directly
        // Alternatively, you can use a library like recorderjs to perform the conversion
        // Here's a simplified example using recorderjs:

        const reader = new FileReader();
        reader.onload = () => {
            const audioBuffer = reader.result; // ArrayBuffer containing audio data

            // Send audioBuffer to Flask server or perform further processing
            sendAudioToFlask(audioBuffer as ArrayBuffer);
        };

        reader.readAsArrayBuffer(blob);
    }, []);

    const sendAudioToFlask = useCallback((audioBuffer: ArrayBuffer) => {
        const formData = new FormData();
        formData.append('audio_file', new Blob([audioBuffer]), `speech_audio.wav`);

        console.log(formData.get("audio_file"));

        fetch('http://34.87.75.138:8000/transcribe', {
            method: 'POST',
            body: formData
        })
            .then(response => response.json())
            .then((data: { task_id: string, status: string }) => {
                pendingTaskIdsRef.current.push(data.task_id);
            })
            .catch(error => {
                console.error('Error sending audio to Flask server:', error);
            });
    }, []);


  


  I was trying to pass the audio from frontend to whisper model which is in flask app

  


• Top Conversion Metrics to Track in 2024

  22 janvier 2024, par Erin

  2023 boasts  2.64 billion online shoppers worldwide ; that’s more than a third of the global population. With these numbers on an upward trajectory in 2024, conversion metrics are more important than ever to help marketers optimise the online shopping experience. 

  In this article, we’ll provide predictions for the most important conversion metrics you should keep track of in 2024. We’ll also examine how social media can make or break your brand engagement strategy. Keep reading to stay ahead of the competition for 2024 and gain tips and tricks for improving conversion performance.

  What are conversion metrics ?

  In technical terms, conversion metrics are the quantifiable measurements used to track the success of specific outcomes on a website or marketing campaign. Conversion metrics demonstrate how well your website prompts visitors to take desirable actions, like signing up for a newsletter, making a purchase, or filling out a form, for instance.

  Let’s say you’re running a lemonade stand, and you want to compare the number of cups sold to the number of people who approached your stand (your conversion rate). This ratio of cups sold to the total number of people can help you reassess your sales approach. If the ratio is low, you might reconsider your approach ; if it’s high, you can analyse what makes your technique successful and double down.

  

  In 2023, we saw the average conversion rate for online shopping grow by 5.53% compared to the previous year. An increase in conversion rate typically indicates a higher percentage of website visitors converting to buyers. It can also be a good sign for marketing teams that marketing campaigns are more effective, and website experiences are more user-friendly than the previous year. 

  Conversion metrics are a marketers’ bread and butter. Whether it’s through measuring the efficacy of campaigns, honing in on the most effective marketing channels or understanding customer behaviour — don’t underestimate the power of conversion metrics. 

  Conversion rate vs. conversion value 

  Before we dive into the top conversion metrics to track in 2024, let’s clear up any confusion about the difference between conversion rate and conversion value. Conversion rate is a metric that measures the ratio of website visitors/users who complete a conversion action to the total number of website visitors/users. Conversion rates are communicated as percentages.

  A conversion action can mean many different things depending on your product or service. Some examples of conversion actions that website visitors can take include : 

  • Making a purchase
  • Filling out a form
  • Subscribing to a newsletter
  • Any other predefined goal

  Conversion rate is arguably one of the most valuable conversion metrics if you want to pinpoint areas for improvement in your marketing strategy and user experience (UX).

  A good conversion rate completely depends on the type of conversion being measured. Shopify has reported that the average e-commerce conversion rate will be 2.5%-3% in 2023, so if you fall anywhere in this range, you’re in good shape. Below is a visual aid for how you can calculate conversion rate depending on which conversion actions you decide to track :

  

  Conversion value is also a quantifiable metric, but there’s a key difference : conversion value assigns a numerical value to each conversion based on the monetary value of the completed conversion action. Conversion value is not calculated with a formula but is assigned based on revenue generated from the conversion. Conversion value is important for calculating marketing efforts’ return on investment (ROI) and is often used to allocate marketing budgets better. 

  Both conversion rate and conversion value are vital metrics in digital marketing. When used in tandem, they can provide a holistic perspective on your marketing efforts’ financial impact and success. 

  9 important conversion metrics to track in 2024

  Based on research and results from 2023, we have compiled this list of predictions for the most important metrics to track in 2024. 

  

  1. Conversion rate 

  To start things out strong, we’ve got the timeless and indispensable conversion rate. As we discussed in the previous section, conversion rate measures how successfully your website convinces visitors to take important actions, like making purchases or signing up for newsletters. 

  An easy-to-use web analytics solution like Matomo can help in tracking conversion rates. Matomo automatically calculates conversion rates of individual pages, overall website and on a goal-by-goal basis. So you can compare the conversion rate of your newsletter sign up goal vs a form submission goal on your site and see what is underperforming and requires improvement.

  

  In the example above in Matomo, it’s clear that our goal of getting users to comment is not doing well, with only a 0.03% conversion rate. To improve our website’s overall conversion rate, we should focus our efforts on improving the user commenting experience.

  For 2024, we predict that the conversion rate will be just as important to track as in 2023. 

  2. Average visit duration

  This key metric tracks how long users spend on your website. A session typically starts when a user lands on your website and ends when they close the browser or have been inactive for some time ( 30 minutes). Tracking the average visit duration can help you determine how well your content captures users’ attention or how engaged users are when navigating your website. 

  Average Visit Duration = Total Time Spent / Number of Visits

  

  Web analytics tools like Matomo help in monitoring conversion rate metrics like average visit duration. Timestamps are assigned to each interaction within a visit, so that average visit duration can be calculated. Analysing website visit information like average visit duration allows you to evaluate the relevance of your content with your target audience. 

  3. Starter rate

  If your business relies on getting leads through forms, paying attention to Form Analytics is crucial for improving conversion rates. The “starter rate” metric is particularly important—it indicates the number of who people start filling out the form, after seeing it. 

  When you’re working to increase conversion rates and capture more leads, keeping an eye on the starter rate helps you understand where users might encounter issues or lose interest early in the form-filling process. Addressing these issues can simplify the form-filling experience and increase the likelihood of successful lead captures.

  Try Matomo for Free

  Get the web insights you need, without compromising data accuracy.

  Start for free

  No credit card required

  Concrete CMS tripled their leads using Form Analytics in Matomo—see how in their case study.

  4. Bounce rate

  Bounce rate reflects the percentage of visitors who exit your site after interacting with a single page. Bounce rate is an important metric for understanding how relevant your content is to visitors or how optimised your user experience is. A high bounce rate can indicate that visitors are having trouble navigating your website or not finding what they’re looking for. 

  Matomo automatically calculates bounce rate on each page and for your overall website.

  

  Bounce Rate = (# of Single-Page Sessions / Total # of Sessions) * 100

  5. Cost-per-conversion

  This metric quantifies the average cost incurred for each conversion action (i.e., sale, acquired lead, sign-up, etc.). Marketers use cost-per-conversion to assess the cost efficiency of a marketing campaign. You want to aim for a lower cost-per-conversion, meaning your advertising efforts aren’t breaking the bank. A high cost-per-conversion could be acceptable in luxury industries, but it often indicates a low marketing ROI. 

  Cost-per-Conversion = Ad Spend / # of Conversions

  By connecting your Matomo with Google Ads through Advertising Conversion Export feature in Matomo, you can keep tabs on your conversions right within the advertising platform. This feature also works with Microsoft Advertising and Yandex Ads.

  Try Matomo for Free

  Get the web insights you need, without compromising data accuracy.

  Start for free

  No credit card required

  6. Average order value (AOV)

  AOV is a conversion metric that calculates the average monetary value of each order. AOV is crucial for helping e-commerce businesses understand the value of their transactions. A high AOV means buyers spend more per transaction and could be more easily influenced by upselling or cross-selling. Low AOV isn’t necessarily bad — you can compensate for a low AOV by boosting transaction volume. 

  

  AOV = Total Revenue / Total # of Orders 

  Matomo automatically tracks important e-commerce metrics such as AOV, the percentage of visits with abandoned carts and the conversion rate for e-commerce orders.

  7. Exit rate

  Exit rate measures the percentage of visitors who leave a specific webpage after viewing it. Exit rate differs from bounce rate in that it focuses on the last page visitors view before leaving the site. A high exit rate should be examined to identify issues with visitors abandoning the specific page. 

  Exit Rate = (# of Exits from a Page / Total # of Pageviews for that Page) * 100

  

  In the Matomo report above, it’s clear that 77% of visits to the diving page ended after viewing it (exit rate), while 23% continued exploring. 

  On the other hand, our products page shows a lower exit rate at 36%, suggesting that more visitors continue navigating through the site after checking out the products.

  How to improve your conversion performance 

  If you’re curious about improving your conversion performance, this section is designed to guide you through that exact process.

  

  Understand your target audience and their behaviour

  You may need to return to the drawing board if you’re noticing high bounce rates or a lack of brand engagement. In-depth audience analysis can unveil user demographics, preferences and behaviours. This type of user data is crucial for building user personas, segmenting your visitors and targeting marketing campaigns accordingly.

  You can segment your website visitors in a number of web analytics solutions, but for the example below, we’ll look at segmenting in Matomo. 

  

  In this instance, we’ve segmented visitors by mobile users. This helps us see how mobile users are doing with our newsletter signup goal and identify the countries where they convert the most. It also shows how well mobile users are doing with our conversion goal over time.

  It’s clear that our mobile users are converting at a very low rate—just 0.01%. This suggests there’s room for improvement in the mobile experience on our site.

  Optimise website design, landing pages, page loading speed and UX

  A slow page loading speed can result in high exit rates, user dissatisfaction and lost revenue. Advanced web analytics solutions like Matomo, which provides heatmaps and session recordings, can help you find problems in your website design and understand how users interact with it.

  Making a website that focuses on users and has an easy-to-follow layout will make the user experience smooth and enjoyable.

  Try Matomo for Free

  Get the web insights you need, without compromising data accuracy.

  Start for free

  No credit card required

  Create compelling calls-to-action (CTA)

  Research shows that a strategically placed and relevant CTA can significantly increase your revenue. CTAs guide prospects toward conversion and must have a compelling and clear message. 

  You can optimise CTAs by analysing how users interact with them — this helps you tailor them to better resonate with your target audience. 

  A/B testing

  A/B testing can improve your conversion performance by allowing you to experiment with different versions of a web page. By comparing the impact of different web page elements on conversions, you can optimise your website with confidence. 

  Key conversion metrics takeaways

  Whether understanding user behaviour to develop a more intuitive user experience or guessing which marketing channel is the most effective, conversion metrics can be a marketer’s best friend. Conversion metrics help you save time, money and headaches when making your campaigns and website as effective as possible. 

  Make improving conversion rates easier with Matomo, a user-friendly all-in-one solution. Matomo ensures reliable insights by delivering accurate data while prioritising compliance and privacy.

  Get quality insights from your conversion metrics by trying Matomo free for 21 days. No credit card required.

• Assembling frames into a video in Node.js using fluent-ffmpeg [closed]

  14 novembre 2024, par Andrei

  I have the original video and it's modified frames in a folder. Now I want to assemble the modified frames into a new video. I also want to take the audio from the original video and add it to the new video.

  


  My latest code is this using fluent-ffmpeg. But it's not working.

  


  await new Promise((resolve, reject) => {
  ffmpeg(path.join(processedFramesDir, "frame-%d.png"))
    .inputOptions(["-framerate 30", "-start_number 1"])
    .input(videoPath)
    .outputOptions([
      "-c:v",
      "libx264",
      "-c:a",
      "copy",
      "-shortest",
      "-r",
      "30",
      "-pix_fmt",
      "yuv420p",
    ])
    .outputOptions(["-map 0:v:0", "-map 1:a:0"])
    .save(outputVideoPath)
    .on("start", (commandLine) => {
      console.log("FFmpeg command: " + commandLine);
    })
    .on("stderr", (stderrLine) => {
      console.log("FFmpeg stderr: " + stderrLine);
    })
    .on("end", resolve)
    .on("error", (err, stdout, stderr) => {
      console.error("Error assembling video:", err);
      console.error("FFmpeg stderr:", stderr);
      reject(err);
    });
});


  


  I get this error even though the frames exist and they are valid pngs :
FFmpeg command: ffmpeg -framerate 30 -start_number 1 -i /tmp/video-processing-CyULOE/processedFrames/frame-%05d.png -i /tmp/video-processing-CyULOE/input.mp4 -y -c:v libx264 -c:a copy -shortest -r 30 -pix_fmt yuv420p -map 0:v:0 -map 1:a:0 /tmp/video-processing-CyULOE/output.mp4 2024-11-13 23:40:27 FFmpeg stderr: ffmpeg version 4.1.11-0&#x2B;deb10u1 Copyright (c) 2000-2023 the FFmpeg developers 2024-11-13 23:40:27 FFmpeg stderr:   built with gcc 8 (Debian 8.3.0-6) 2024-11-13 23:40:27 FFmpeg stderr:   configuration: --prefix=/usr --extra-version=0&#x2B;deb10u1 --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --arch=amd64 --enable-gpl --disable-stripping --enable-avresample --disable-filter=resample --enable-avisynth --enable-gnutls --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librsvg --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzmq --enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opengl --enable-sdl2 --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libx264 --enable-shared 2024-11-13 23:40:27 FFmpeg stderr:   libavutil      56. 22.100 / 56. 22.100 2024-11-13 23:40:27 FFmpeg stderr:   libavcodec     58. 35.100 / 58. 35.100 2024-11-13 23:40:27 FFmpeg stderr:   libavformat    58. 20.100 / 58. 20.100 2024-11-13 23:40:27 FFmpeg stderr:   libavdevice    58.  5.100 / 58.  5.100 2024-11-13 23:40:27 FFmpeg stderr:   libavfilter     7. 40.101 /  7. 40.101 2024-11-13 23:40:27 FFmpeg stderr:   libavresample   4.  0.  0 /  4.  0.  0 2024-11-13 23:40:27 FFmpeg stderr:   libswscale      5.  3.100 /  5.  3.100 2024-11-13 23:40:27 FFmpeg stderr:   libswresample   3.  3.100 /  3.  3.100 2024-11-13 23:40:27 FFmpeg stderr:   libpostproc    55.  3.100 / 55.  3.100 2024-11-13 23:40:27 FFmpeg stderr: [png @ 0x5630fb89a880] Invalid PNG signature 0x52494646F8A20000. 2024-11-13 23:40:27 FFmpeg stderr: [png @ 0x5630fb89a880] Invalid PNG signature 0x52494646C89F0000. 2024-11-13 23:40:27 FFmpeg stderr: [png @ 0x5630fb89a880] Invalid PNG signature 0x524946464EA10000. 2024-11-13 23:40:27 FFmpeg stderr: [png @ 0x5630fb89a880] Invalid PNG signature 0x5249464628A40000. 2024-11-13 23:40:27 FFmpeg stderr: [png @ 0x5630fb89a880] Invalid PNG signature 0x52494646AAA30000. 2024-11-13 23:40:27 FFmpeg stderr: [png @ 0x5630fb89a880] Invalid PNG signature 0x524946467CA10000. 2024-11-13 23:40:27 FFmpeg stderr: [png @ 0x5630fb89a880] Invalid PNG signature 0x52494646AAA30000. 2024-11-13 23:40:27 FFmpeg stderr: [png @ 0x5630fb89a880] Invalid PNG signature 0x52494646BAA10000. 2024-11-13 23:40:27 FFmpeg stderr: [png @ 0x5630fb89a880] Invalid PNG signature 0x52494646ACA30000. 2024-11-13 23:40:27 FFmpeg stderr: [png @ 0x5630fb89a880] Invalid PNG signature 0x5249464670A80000. 2024-11-13 23:40:27 FFmpeg stderr: [png @ 0x5630fb89a880] Invalid PNG signature 0x52494646E8A60000. 2024-11-13 23:40:27 FFmpeg stderr: [png @ 0x5630fb89a880] Invalid PNG signature 0x524946469AA60000. 2024-11-13 23:40:27 FFmpeg stderr: [png @ 0x5630fb89a880] Invalid PNG signature 0x5249464672A90000. 2024-11-13 23:40:27 FFmpeg stderr: [png @ 0x5630fb89a880] Invalid PNG signature 0x52494646B8A50000. 2024-11-13 23:40:27 FFmpeg stderr: [png @ 0x5630fb89a880] Invalid PNG signature 0x52494646AAA80000. 2024-11-13 23:40:27 FFmpeg stderr: [png @ 0x5630fb89a880] Invalid PNG signature 0x52494646A0A70000. 2024-11-13 23:40:27 FFmpeg stderr:     Last message repeated 1 times 2024-11-13 23:40:27 FFmpeg stderr: [png @ 0x5630fb89a880] Invalid PNG signature 0x5249464646A80000. 2024-11-13 23:40:27 FFmpeg stderr: [image2 @ 0x5630fb898a40] decoding for stream 0 failed 2024-11-13 23:40:27 FFmpeg stderr: [image2 @ 0x5630fb898a40] Could not find codec parameters for stream 0 (Video: png, none(pc)): unspecified size 2024-11-13 23:40:27 FFmpeg stderr: Consider increasing the value for the &#x27;analyzeduration&#x27; and &#x27;probesize&#x27; options 2024-11-13 23:40:27 FFmpeg stderr: Input #0, image2, from &#x27;/tmp/video-processing-CyULOE/processedFrames/frame-%05d.png&#x27;: 2024-11-13 23:40:27 FFmpeg stderr:   Duration: 00:00:00.60, start: 0.000000, bitrate: N/A 2024-11-13 23:40:27 FFmpeg stderr:     Stream #0:0: Video: png, none(pc), 30 fps, 30 tbr, 30 tbn, 30 tbc 2024-11-13 23:40:28 FFmpeg stderr: Input #1, mov,mp4,m4a,3gp,3g2,mj2, from &#x27;/tmp/video-processing-CyULOE/input.mp4&#x27;: 2024-11-13 23:40:28 FFmpeg stderr:   Metadata: 2024-11-13 23:40:28 FFmpeg stderr:     major_brand     : isom 2024-11-13 23:40:28 FFmpeg stderr:     minor_version   : 512 2024-11-13 23:40:28 FFmpeg stderr:     compatible_brands: isomiso2avc1mp41 2024-11-13 23:40:28 FFmpeg stderr:     encoder         : Lavf60.16.100 2024-11-13 23:40:28 FFmpeg stderr:   Duration: 00:00:00.62, start: 0.000000, bitrate: 4289 kb/s 2024-11-13 23:40:28 FFmpeg stderr:     Stream #1:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709), 1920x1080 [SAR 1:1 DAR 16:9], 4395 kb/s, 30 fps, 30 tbr, 15360 tbn, 60 tbc (default) 2024-11-13 23:40:28 FFmpeg stderr:     Metadata: 2024-11-13 23:40:28 FFmpeg stderr:       handler_name    : VideoHandler 2024-11-13 23:40:28 FFmpeg stderr:     Stream #1:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 2 kb/s (default) 2024-11-13 23:40:28 FFmpeg stderr:     Metadata: 2024-11-13 23:40:28 FFmpeg stderr:       handler_name    : SoundHandler 2024-11-13 23:40:28 FFmpeg stderr: Stream mapping: 2024-11-13 23:40:28 FFmpeg stderr:   Stream #0:0 -> #0:0 (png (native) -> h264 (libx264)) 2024-11-13 23:40:28 FFmpeg stderr:   Stream #1:1 -> #0:1 (copy) 2024-11-13 23:40:28 FFmpeg stderr: Press [q] to stop, [?] for help 2024-11-13 23:40:28 FFmpeg stderr: [image2 @ 0x5630fb898a40] Thread message queue blocking; consider raising the thread_queue_size option (current value: 8) 2024-11-13 23:40:28 FFmpeg stderr: [png @ 0x5630fb9b7700] Invalid PNG signature 0x52494646F8A20000. 2024-11-13 23:40:28 FFmpeg stderr: [png @ 0x5630fb988dc0] Invalid PNG signature 0x52494646C89F0000. 2024-11-13 23:40:28 FFmpeg stderr: [png @ 0x5630fba3edc0] Invalid PNG signature 0x524946464EA10000. 2024-11-13 23:40:28 FFmpeg stderr: [png @ 0x5630fba40600] Invalid PNG signature 0x5249464628A40000. 2024-11-13 23:40:28 FFmpeg stderr: Error while decoding stream #0:0: Invalid data found when processing input 2024-11-13 23:40:28 FFmpeg stderr: [png @ 0x5630fb8c7900] Invalid PNG signature 0x52494646AAA30000. 2024-11-13 23:40:28 FFmpeg stderr: Error while decoding stream #0:0: Invalid data found when processing input 2024-11-13 23:40:28 FFmpeg stderr: [png @ 0x5630fb9b7700] Invalid PNG signature 0x524946467CA10000. 2024-11-13 23:40:28 FFmpeg stderr: Error while decoding stream #0:0: Invalid data found when processing input 2024-11-13 23:40:28 FFmpeg stderr: [png @ 0x5630fb988dc0] Invalid PNG signature 0x52494646AAA30000. 2024-11-13 23:40:28 FFmpeg stderr: Error while decoding stream #0:0: Invalid data found when processing input 2024-11-13 23:40:28 FFmpeg stderr: [png @ 0x5630fba3edc0] Invalid PNG signature 0x52494646BAA10000. 2024-11-13 23:40:28 FFmpeg stderr: [png @ 0x5630fba40600] Invalid PNG signature 0x52494646ACA30000. 2024-11-13 23:40:28 FFmpeg stderr: Error while decoding stream #0:0: Invalid data found when processing input 2024-11-13 23:40:28 FFmpeg stderr:     Last message repeated 1 times 2024-11-13 23:40:28 FFmpeg stderr: [png @ 0x5630fb8c7900] Invalid PNG signature 0x5249464670A80000. 2024-11-13 23:40:28 FFmpeg stderr: Error while decoding stream #0:0: Invalid data found when processing input 2024-11-13 23:40:28 FFmpeg stderr: [png @ 0x5630fb9b7700] Invalid PNG signature 0x52494646E8A60000. 2024-11-13 23:40:28 FFmpeg stderr: Error while decoding stream #0:0: Invalid data found when processing input 2024-11-13 23:40:28 FFmpeg stderr: [png @ 0x5630fb988dc0] Invalid PNG signature 0x524946469AA60000. 2024-11-13 23:40:28 FFmpeg stderr: Error while decoding stream #0:0: Invalid data found when processing input 2024-11-13 23:40:28 FFmpeg stderr: [png @ 0x5630fba3edc0] Invalid PNG signature 0x5249464672A90000. 2024-11-13 23:40:28 FFmpeg stderr: Error while decoding stream #0:0: Invalid data found when processing input 2024-11-13 23:40:28 FFmpeg stderr: [png @ 0x5630fba40600] Invalid PNG signature 0x52494646B8A50000. 2024-11-13 23:40:28 FFmpeg stderr: Error while decoding stream #0:0: Invalid data found when processing input 2024-11-13 23:40:28 FFmpeg stderr: [png @ 0x5630fb8c7900] Invalid PNG signature 0x52494646AAA80000. 2024-11-13 23:40:28 FFmpeg stderr: Error while decoding stream #0:0: Invalid data found when processing input 2024-11-13 23:40:28 FFmpeg stderr: [png @ 0x5630fb9b7700] Invalid PNG signature 0x52494646A0A70000. 2024-11-13 23:40:28 FFmpeg stderr: [png @ 0x5630fb988dc0] Invalid PNG signature 0x52494646A0A70000. 2024-11-13 23:40:28 FFmpeg stderr: Error while decoding stream #0:0: Invalid data found when processing input 2024-11-13 23:40:28 FFmpeg stderr: [png @ 0x5630fba3edc0] Invalid PNG signature 0x5249464646A80000. 2024-11-13 23:40:28 FFmpeg stderr: Error while decoding stream #0:0: Invalid data found when processing input 2024-11-13 23:40:28 FFmpeg stderr:     Last message repeated 4 times 2024-11-13 23:40:28 FFmpeg stderr: Cannot determine format of input stream 0:0 after EOF 2024-11-13 23:40:28 FFmpeg stderr: Error marking filters as finished 2024-11-13 23:40:28 FFmpeg stderr: Conversion failed! 2024-11-13 23:40:28 FFmpeg stderr:  2024-11-13 23:40:28 Error assembling video: Error: ffmpeg exited with code 1: Cannot determine format of input stream 0:0 after EOF 2024-11-13 23:40:28 Error marking filters as finished 2024-11-13 23:40:28 Conversion failed! 2024-11-13 23:40:28  2024-11-13 23:40:28     at ChildProcess.<anonymous> (/usr/src/app/node_modules/fluent-ffmpeg/lib/processor.js:180:22) 2024-11-13 23:40:28     at ChildProcess.emit (node:events:519:28) 2024-11-13 23:40:28     at ChildProcess._handle.onexit (node:internal/child_process:294:12)</anonymous>

  


  The code used to

  


  ffmpeg(videoPath) .screenshots({ folder: framesDir, filename: "frame-%i.png", size: "?x1080", count: 10, }) .on("end", resolve) .on("error", reject);


  


  The pngs are valid and displaying in windows photos viewer