search

lisamelton / video_transcoding

Tools to transcode, inspect and convert videos.
MIT License
2.39k stars 160 forks source link

HandBrakeCLI Problem #230

Closed asheimo closed 6 years ago

asheimo commented 6 years ago

Not sure what I'm missing, I updated to the latest version of transcode video and HandBrakeCLI.

c:\bin>transcode-video HandBrakeCLI: unknown option -- auto-anamorphic unknown option (--auto-anamorphic) C:/Ruby22-x64/bin/transcode-video: transcoding failed:

khaosx commented 6 years ago

Can you run the command from the directory that transcode-video lives in and paste the output back here?

asheimo commented 6 years ago

C:\Ruby22-x64\bin>transcode-video --quick HandBrakeCLI: unknown option -- auto-anamorphic unknown option (--auto-anamorphic) C:/Ruby22-x64/bin/transcode-video: transcoding failed:

lisamelton commented 6 years ago

@asheimo Sorry I took so long to respond. I've been away all day.

The problem is that you're using an old version HandBrakeCLI. You need to be using version 1.0.0 or later.

You can test which version you have installed by issuing this command:

HandBrakeCLI --version

What does that output of that command look like?

asheimo commented 6 years ago

I thought that too but this is the output I get:

c:\bin>HandBrakeCLI.exe --version [20:15:12] hb_init: starting libhb thread [20:15:12] thread 5517020 started ("libhb") HandBrake 1.1.2

lisamelton commented 6 years ago

@asheimo OK, that is very weird. That's normally version issue if you get the --auto-anamorphic error.

What does your whole command line look like, i.e. which options and arguments are you passing to transcode-video?

asheimo commented 6 years ago

well embarrassment strikes again... I searched for HandBrakeCLI and found a copy in the C:/Ruby22-x64/bin directory. When I deleted that TranscodeVideo began working as normal. Please feel free to mark closed and note it was an issue between the keyboard and floor.

lisamelton commented 6 years ago

@asheimo No worries! I'm glad you solved the problem.

I'll close this now but never be shy about opening a issue.