Re: Cannot load nvEncodeAPI64.dll and Cannot run the handbrakecli.exe

The Command Line Interface is just that - something you use from the CMD prompt. Clicking on it won't work, because you aren't telling it what to do.

Now I know how to use it to encode the video with a bat file after watching a video of YouTube(https://www.youtube.com/watch?v=zn6k4YuQR98&t=81s). But I still can't run it with CMD prompt. And I also tried to run it with PowerShell, but it didn't perform better than CMD prompt except not exiting automatically. It seems that you can also encode the video with a ps1 file though I don't fingure it out yet(https://www.youtube.com/watch?v=EVEpjKLXvBo&t=194s). So I still don't know how to use the Command line such as "help". After downloading the nvEncodeAPI64.dll and putting it into the SysWOW64 folder, I couldn't register it because it was invalid. I wonder if it's my NoteBook which can't get or register the nvEncodeAPI64.dll because it's supposed to be there with the update of NVIDIA Geforce Experience(My GPUs are Intel UHD 620 and NVIDIA Geforce MX150).

Re: Cannot load nvEncodeAPI64.dll and Cannot run the handbrakecli.exe

Posted: Fri May 03, 2019 3:13 am

by Woodstock

If you've always worked using a graphic user interface, the command line is VERY different. It doesn't present any way for you to control it, other than what you present to it when opening it. The reward for learning to use it can be great, but the learning is often difficult.

The first part just puts some information in the "title" part of the CMD window the process is running in. The part in this color is the path to the executable, which will vary with where you installed it. This color depicts the "basic" arguments to HandbrakeCLI.exe; -i tells the CLI the path and name of the source file. -o gives the path and name of the output file, and -f says what type of file to use for the output.

The balance of the line is really optional, but it tells the CLI which audio streams to include, parameters about them, which subtitle strings to include, where to find a list of "chapter marker names", and some choices to use for the encoder. These are the things that the GUI and presets can do for you, but the CLI requires you to make choices yourself.

You CAN make use of GUI presets, but you will really want to use the GUI to try those presets out before incorporating them into CLI commands.

I highly recommend picking a portion of a video and try encoding it with different parameters, then viewing the results. You can use the -c command to specify a subset of chapters, like -c 1-2 to only encode chapters 1 and 2 of a longer video.

I find that the same command line, with just a change of the file names, works for "almost everything" published by particular vendors - Funimation usually puts the Forced/Everything subtitle tracks as 2/1, respectively, so most batch jobs I use for Funimation titles have --subtitle 2,1 as part of them.

Oh, and do this command from the CMD prompt to get the CLI help into a file you can view or print:

Re: Cannot load nvEncodeAPI64.dll and Cannot run the handbrakecli.exe

If you've always worked using a graphic user interface, the command line is VERY different. It doesn't present any way for you to control it, other than what you present to it when opening it. The reward for learning to use it can be great, but the learning is often difficult.

The first part just puts some information in the "title" part of the CMD window the process is running in. The part in this color is the path to the executable, which will vary with where you installed it. This color depicts the "basic" arguments to HandbrakeCLI.exe; -i tells the CLI the path and name of the source file. -o gives the path and name of the output file, and -f says what type of file to use for the output.

The balance of the line is really optional, but it tells the CLI which audio streams to include, parameters about them, which subtitle strings to include, where to find a list of "chapter marker names", and some choices to use for the encoder. These are the things that the GUI and presets can do for you, but the CLI requires you to make choices yourself.

You CAN make use of GUI presets, but you will really want to use the GUI to try those presets out before incorporating them into CLI commands.

I highly recommend picking a portion of a video and try encoding it with different parameters, then viewing the results. You can use the -c command to specify a subset of chapters, like -c 1-2 to only encode chapters 1 and 2 of a longer video.

I find that the same command line, with just a change of the file names, works for "almost everything" published by particular vendors - Funimation usually puts the Forced/Everything subtitle tracks as 2/1, respectively, so most batch jobs I use for Funimation titles have --subtitle 2,1 as part of them.

Oh, and do this command from the CMD prompt to get the CLI help into a file you can view or print:

Re: Cannot load nvEncodeAPI64.dll and Cannot run the handbrakecli.exe

It seems that x265_10bit and x265_12bit don't support two-pass mode both in HandBrakecli and HandBrake GUI, and I also hope that HandBrake can support an ass file and pass-through video without conversion as a brilliant video transcoder, because MeGUI, ShanaEncoder and MKVtoolnix can all do so.

Re: Cannot load nvEncodeAPI64.dll and Cannot run the handbrakecli.exe

Posted: Wed May 08, 2019 5:31 pm

by Woodstock

Support for .ssa files being imported is coming (in nightly builds now, waiting for v1.3 to be released).

Re: Cannot load nvEncodeAPI64.dll and Cannot run the handbrakecli.exe

Support for .ssa files being imported is coming (in nightly builds now, waiting for v1.3 to be released).

Support for "video pass-through" is not.

I konw it, and Nightly version adds two more languages—Chinese and French. However, after saving ASS as SSA with Aeguisub, I find that SSA doesn't support some effects which ASS has. Actually, ASS is the advanced version of SSA and it absolutely has more effects. So I have to burn ASS into video with MeGUI. But MeGUI's MP4 muxer can't pass-through E-AC3. In order to pass-through E-AC3 in MP4, I merge(mux) video and audio(E-A3) into MKV. Then I import MKV into HnadBrake GUI, but I have to encode the video again. Thus, I also want video to be pass-throughed without conversion.

Re: Cannot load nvEncodeAPI64.dll and Cannot run the handbrakecli.exe

Posted: Thu May 09, 2019 1:19 pm

by Woodstock

I've processed .ass subtitles that were embedded in the source MKV file for several years. Which "advanced effects" are you referring to, that aren't supported by handbrake? Burned-in .ass subtitles have animation effects that I have been unable to get to display on players that claim to handle Advanced SubStation Alpha files. As long as the fonts needed for that are embedded in the source along with the .ass stream.

Embedded fonts are one thing that importing the file (not embedded in source) isn't supported, though.

Re: Cannot load nvEncodeAPI64.dll and Cannot run the handbrakecli.exe

Embedded fonts are one thing that importing the file (not embedded in source) isn't supported, though.

Hmm, good point. Maybe someone should open an 'enhancement' issue for this.

Re: Cannot load nvEncodeAPI64.dll and Cannot run the handbrakecli.exe

Posted: Thu May 09, 2019 7:20 pm

by DUGUJACK

I attempted to burn ASS file which was embedded in the source MKV file before, but It turned out that the Italic effect could't be processed properly because there were two "<i>" words appearing both in the beginning and the ending of all "Italic" lines of the subtitle. Of course, the rest text of those lines weren't Italic.

Re: Cannot load nvEncodeAPI64.dll and Cannot run the handbrakecli.exe

Actually, you can make it italic simply with ''<i>'' which can be displayed correctly by video players and subtitle editors. However, it may can't be burned properly by video encoders such as HandBrake and ShanaEncoder.