n8n-nodes-ffmpeg-wasm 1.2.6 → 1.2.8

package/dist/nodes/FFmpegWasm/FFmpegWasm.node.js

@@ -960,6 +960,13 @@ class FFmpegWasm {
     async execute() {
         const items = this.getInputData();
         const returnData = [];
+        try {
+            require.resolve("@ffmpeg/core");
+        }
+        catch {
+            throw new Error("FFmpeg.wasm core module (@ffmpeg/core) is not installed. " +
+                "Please uninstall and reinstall the n8n-nodes-ffmpeg-wasm community node.");
+        }
         let corePath;
         try {
             const credentials = await this.getCredentials("ffmpegWasmApi");
@@ -979,7 +986,22 @@ class FFmpegWasm {
             ...(corePath ? { corePath } : {}),
         });
         try {
-            await ffmpeg.load();
+            const globalAny = globalThis;
+            const savedFetch = globalAny.fetch;
+            try {
+                delete globalAny.fetch;
+                await ffmpeg.load();
+            }
+            catch (loadError) {
+                const msg = loadError instanceof Error
+                    ? loadError.message
+                    : String(loadError);
+                throw new Error(`Failed to initialize FFmpeg.wasm: ${msg}. ` +
+                    `Ensure the n8n instance has sufficient memory (512MB+ recommended).`);
+            }
+            finally {
+                globalAny.fetch = savedFetch;
+            }
             for (let i = 0; i < items.length; i++) {
                 try {
                     const binaryPropertyName = this.getNodeParameter("binaryPropertyName", i);
@@ -999,7 +1021,10 @@ class FFmpegWasm {
                     if (operation === "metadata") {
                         lastLogOutput = "";
                         try {
-                            await ffmpeg.run("-i", inputFilename, "-hide_banner");
+                            await Promise.race([
+                                ffmpeg.run("-i", inputFilename, "-hide_banner"),
+                                new Promise((resolve) => setTimeout(resolve, 10000)),
+                            ]);
                         }
                         catch {
                         }
@@ -1738,7 +1763,10 @@ class FFmpegWasm {
                             const outputName = `${outputFilename}${outputExt}`;
                             lastLogOutput = "";
                             try {
-                                await ffmpeg.run("-i", inputFilename, "-hide_banner");
+                                await Promise.race([
+                                    ffmpeg.run("-i", inputFilename, "-hide_banner"),
+                                    new Promise((resolve) => setTimeout(resolve, 10000)),
+                                ]);
                             }
                             catch {
                             }
@@ -1826,7 +1854,12 @@ class FFmpegWasm {
             }
         }
         finally {
-            ffmpeg.exit();
+            if (ffmpeg.isLoaded()) {
+                try {
+                    ffmpeg.exit();
+                }
+                catch { }
+            }
         }
         return [returnData];
     }

package/node_modules/@ffmpeg/ffmpeg/.gitpod.Dockerfile

@@ -0,0 +1,2 @@
+FROM gitpod/workspace-full
+RUN sudo apt-get update && sudo apt-get install -y libgtk-3-0 libx11-xcb1 libnss3 libxss1 libasound2

package/node_modules/@ffmpeg/ffmpeg/.gitpod.yml

@@ -0,0 +1,7 @@
+image:
+  file: .gitpod.Dockerfile
+tasks:
+- init: >
+    wget https://github.com/jeromewu/docker-workspace/raw/master/vim.zip -O /tmp/vim.zip &> /dev/null &&
+    unzip /tmp/vim.zip -d /home/gitpod &> /dev/null &&
+    npm install

package/node_modules/@ffmpeg/ffmpeg/.yarnrc.yml

@@ -0,0 +1,4 @@
+packageExtensions:
+  "@ffmpeg/ffmpeg@*":
+    peerDependencies:
+      "@ffmpeg/core": "*"

package/node_modules/@ffmpeg/ffmpeg/CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+ advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+ address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+ professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at jeromewus@gmail.com. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

package/node_modules/@ffmpeg/ffmpeg/CONTRIBUTING.md

@@ -0,0 +1 @@
+WIP

package/node_modules/@ffmpeg/ffmpeg/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2019 Jerome Wu
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/node_modules/@ffmpeg/ffmpeg/README.md

@@ -0,0 +1,202 @@
+<p align="center">
+  <a href="#">
+    <img alt="ffmpeg.wasm" width="128px" height="128px" src="https://github.com/ffmpegwasm/ffmpeg.wasm/raw/master/docs/images/ffmpegwasm-icon.png">
+  </a>
+</p>
+
+# ffmpeg.wasm
+
+[![stability-experimental](https://img.shields.io/badge/stability-experimental-orange.svg)](https://github.com/emersion/stability-badges#experimental)
+[![Node Version](https://img.shields.io/node/v/@ffmpeg/ffmpeg.svg)](https://img.shields.io/node/v/@ffmpeg/ffmpeg.svg)
+[![Actions Status](https://github.com/ffmpegwasm/ffmpeg.wasm/workflows/CI/badge.svg)](https://github.com/ffmpegwasm/ffmpeg.wasm/actions)
+![CodeQL](https://github.com/ffmpegwasm/ffmpeg.wasm/workflows/CodeQL/badge.svg)
+![npm (tag)](https://img.shields.io/npm/v/@ffmpeg/ffmpeg/latest)
+[![Maintenance](https://img.shields.io/badge/Maintained%3F-yes-green.svg)](https://github.com/ffmpegwasm/ffmpeg.wasm/graphs/commit-activity)
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
+[![Code Style](https://badgen.net/badge/code%20style/airbnb/ff5a5f?icon=airbnb)](https://github.com/airbnb/javascript)
+[![Downloads Total](https://img.shields.io/npm/dt/@ffmpeg/ffmpeg.svg)](https://www.npmjs.com/package/@ffmpeg/ffmpeg)
+[![Downloads Month](https://img.shields.io/npm/dm/@ffmpeg/ffmpeg.svg)](https://www.npmjs.com/package/@ffmpeg/ffmpeg)
+
+Join us on Discord!
+
+[![Discord](https://dcbadge.vercel.app/api/server/NjGMaqqfm5)](https://discord.gg/NjGMaqqfm5)
+
+ffmpeg.wasm is a pure Webassembly / Javascript port of FFmpeg. It enables video & audio record, convert and stream right inside browsers.
+
+**AVI to MP4 Demo**
+<p align="center">
+  <a href="#">
+    <img alt="transcode-demo" src="https://github.com/ffmpegwasm/ffmpeg.wasm/raw/master/docs/images/transcode.gif">
+  </a>
+</p>
+
+Try it: [https://ffmpegwasm.netlify.app](https://ffmpegwasm.netlify.app#demo)
+
+Check next steps of ffmpeg.wasm [HERE](https://github.com/ffmpegwasm/ffmpeg.wasm/discussions/415)
+
+## Installation
+
+**Node**
+
+```
+$ npm install @ffmpeg/ffmpeg @ffmpeg/core
+```
+
+> As we are using experimental features, you need to add flags to run in Node.js
+
+```
+$ node --experimental-wasm-threads transcode.js
+```
+
+**Browser**
+
+Or, using a script tag in the browser (only works in some browsers, see list below):
+
+> SharedArrayBuffer is only available to pages that are [cross-origin isolated](https://developer.chrome.com/blog/enabling-shared-array-buffer/#cross-origin-isolation). So you need to host [your own server](https://github.com/ffmpegwasm/ffmpegwasm.github.io/blob/main/server/server.js) with `Cross-Origin-Embedder-Policy: require-corp` and `Cross-Origin-Opener-Policy: same-origin` headers to use ffmpeg.wasm.
+
+```html
+<script src="static/js/ffmpeg.min.js"></script>
+<script>
+  const { createFFmpeg } = FFmpeg;
+  ...
+</script>
+```
+
+> Only browsers with SharedArrayBuffer support can use ffmpeg.wasm, you can check [HERE](https://caniuse.com/sharedarraybuffer) for the complete list.
+
+## Usage
+
+ffmpeg.wasm provides simple to use APIs, to transcode a video you only need few lines of code:
+
+```javascript
+import { writeFile } from 'fs/promises';
+import { createFFmpeg, fetchFile } from '@ffmpeg/ffmpeg';
+
+const ffmpeg = createFFmpeg({ log: true });
+
+(async () => {
+  await ffmpeg.load();
+  ffmpeg.FS('writeFile', 'test.avi', await fetchFile('./test.avi'));
+  await ffmpeg.run('-i', 'test.avi', 'test.mp4');
+  await fs.promises.writeFile('./test.mp4', ffmpeg.FS('readFile', 'test.mp4'));
+  process.exit(0);
+})();
+```
+
+### Use other version of ffmpeg.wasm-core / @ffmpeg/core
+
+For each version of ffmpeg.wasm, there is a default version of @ffmpeg/core (you can find it in **devDependencies** section of [package.json](https://github.com/ffmpegwasm/ffmpeg.wasm/blob/master/package.json)), but sometimes you may need to use newer version of @ffmpeg/core to use the latest/experimental features.
+
+**Node**
+
+Just install the specific version you need:
+
+```bash
+$ npm install @ffmpeg/core@latest
+```
+
+Or use your own version with customized path
+
+```javascript
+const ffmpeg = createFFmpeg({
+  corePath: '../../../src/ffmpeg-core.js',
+});
+```
+
+**Browser**
+
+```javascript
+const ffmpeg = createFFmpeg({
+  corePath: 'static/js/ffmpeg-core.js',
+});
+```
+
+Keep in mind that for compatibility with webworkers and nodejs this will default to a local path, so it will attempt to look for `'static/js/ffmpeg.core.js'` locally, often resulting in a local resource error. If you wish to use a core version hosted on your own domain, you might reference it relatively like this:
+
+```javascript
+const ffmpeg = createFFmpeg({
+  corePath: new URL('static/js/ffmpeg-core.js', document.location).href,
+});
+```
+
+For the list available versions and their changelog, please check: https://github.com/ffmpegwasm/ffmpeg.wasm-core/releases
+
+### Use single thread version
+
+```javascript
+const ffmpeg = createFFmpeg({
+  mainName: 'main',
+  corePath: 'https://unpkg.com/@ffmpeg/core-st@0.11.1/dist/ffmpeg-core.js',
+});
+```
+
+## Multi-threading
+
+Multi-threading need to be configured per external libraries, only following libraries supports it now:
+
+### x264
+
+Run it multi-threading mode by default, no need to pass any arguments.
+
+### libvpx / webm
+
+Need to pass `-row-mt 1`, but can only use one thread to help, can speed up around 30%
+
+## Documentation
+
+- [API](https://github.com/ffmpegwasm/ffmpeg.wasm/blob/master/docs/api.md)
+- [Supported External Libraries](https://github.com/ffmpegwasm/ffmpeg.wasm-core#configuration)
+
+## FAQ
+
+### What is the license of ffmpeg.wasm?
+
+There are two components inside ffmpeg.wasm:
+
+- @ffmpeg/ffmpeg (https://github.com/ffmpegwasm/ffmpeg.wasm)
+- @ffmpeg/core (https://github.com/ffmpegwasm/ffmpeg.wasm-core)
+
+@ffmpeg/core contains WebAssembly code which is transpiled from original FFmpeg C code with minor modifications, but overall it still following the same licenses as FFmpeg and its external libraries (as each external libraries might have its own license).
+
+@ffmpeg/ffmpeg contains kind of a wrapper to handle the complexity of loading core and calling low-level APIs. It is a small code base and under MIT license.
+
+### Can I use ffmpeg.wasm in Firefox?
+
+Yes, but only for Firefox 79+ with proper header in both client and server, visit https://ffmpegwasm.netlify.app to try whether your Firefox works.
+
+![](https://user-images.githubusercontent.com/5723124/98955802-4cb20c80-253a-11eb-8f16-ce0298720a2a.png)
+
+For more details: https://github.com/ffmpegwasm/ffmpeg.wasm/issues/106
+
+### What is the maximum size of input file?
+
+2 GB, which is a hard limit in WebAssembly. Might become 4 GB in the future.
+
+### How can I build my own ffmpeg.wasm?
+
+In fact, it is ffmpeg.wasm-core most people would like to build.
+
+To build on your own, you can check build.sh inside https://github.com/ffmpegwasm/ffmpeg.wasm-core repository.
+
+Also you can check this series of posts to learn more fundamental concepts:
+
+- https://jeromewu.github.io/build-ffmpeg-webassembly-version-part-1-preparation/
+- https://jeromewu.github.io/build-ffmpeg-webassembly-version-part-2-compile-with-emscripten/
+- https://jeromewu.github.io/build-ffmpeg-webassembly-version-part-3-v0.1/
+- https://jeromewu.github.io/build-ffmpeg-webassembly-version-part-4-v0.2/
+
+### Why it doesn't work in my local environment?
+
+When calling `ffmpeg.load()`, by default it looks for `http://localhost:3000/node_modules/@ffmpeg/core/dist/` to download essential files (ffmpeg-core.js, ffmpeg-core.wasm, ffmpeg-core.worker.js). It is necessary to make sure you have those files served there.
+
+If you have those files serving in other location, you can rewrite the default behavior when calling `createFFmpeg()`:
+
+```javascript
+const { createFFmpeg } = FFmpeg;
+const ffmpeg = createFFmpeg({
+  corePath: "http://localhost:3000/public/ffmpeg-core.js",
+  // Use public address if you don't want to host your own.
+  // corePath: 'https://unpkg.com/@ffmpeg/core@0.10.0/dist/ffmpeg-core.js'
+  log: true,
+});
+```

package/node_modules/@ffmpeg/ffmpeg/_config.yml

@@ -0,0 +1 @@
+theme: jekyll-theme-cayman