Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot use lut3d .cube filter #851

Open
3 tasks done
flow-dev opened this issue Oct 8, 2018 · 0 comments
Open
3 tasks done

Cannot use lut3d .cube filter #851

flow-dev opened this issue Oct 8, 2018 · 0 comments

Comments

@flow-dev
Copy link

flow-dev commented Oct 8, 2018

I'd like to apply ”lut3d" using my .cube file,
but the .cube argument is not given anymore.

I thought there was a problem with the path of the. cube file,
I tried changing the location but did not change...

".on('start', function(commandLine) {"
log is " -filter_complex lut3d="SLog3_SG3c_.cube" " Accurate command.

If ffmpeg alone, I can use lut3d without problems,
but node-fluent-ffmpeg cannnot this cmd ...

Please tell me how to write the code.

Version information

  • fluent-ffmpeg version: 2.1.2
  • ffmpeg version: 4.0.0
  • OS: Windows10

Code to reproduce

var proc = ffmpeg(input_name)
        .complexFilter([
            {
                "filter":lut3d,
                //"input": "SLog3_SG3c_.cube"
            }
        ])
        .on('start', function(commandLine) {
            console.log('Ffmpeg with command: ' + commandLine);
        })
        .on('end', function() {
            console.log('file has been converted succesfully');
        })
        .on('error', function(err) {
            console.log('an error happened: ' + err.message);
        })
        .save(output_name);

(note: if the problem only happens with some inputs, include a link to such an input file)

Expected results

an error happened: ffmpeg exited with code 1: Error initializing complex filters.
Invalid argument

Observed results

Checklist

  • I have read the FAQ
  • I tried the same with command line ffmpeg and it works correctly (hint: if the problem also happens this way, this is an ffmpeg problem and you're not reporting it to the right place)
  • I have included full stderr/stdout output from ffmpeg
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant