#660 closed defect (fixed)
x264opts does not accepts options without values
Reported by: | burek | Owned by: | Michael Niedermayer |
---|---|---|---|
Priority: | normal | Component: | undetermined |
Version: | git-master | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Reproduced by developer: | yes | |
Analyzed by developer: | no |
Description
one of them is "thread-input", which has got no value, but ffmpeg's parser requires options to be in "key=value" format..
there are other options without value required, like:
--no-scenecut
--intra-refresh
--open-gop
--no-cabac
etc..
Change History (6)
comment:1 by , 13 years ago
comment:2 by , 13 years ago
Component: | FFmpeg → undetermined |
---|---|
Priority: | important → normal |
Do you believe this is a regression?
comment:3 by , 13 years ago
Well, actually khali (from the ffmpeg IRC channel) detected that bug, not me, but he has got problems with registering on this trac, so I placed a bug report instead. However, I don't know how to check if that's a regression or not, but if you can give me a link or something, I could answer that. Khali says he has got no reason to believe it is a regression, though.
comment:4 by , 13 years ago
Hi there ;) I didn't really have "problems with registering", rather I did not realize that it was possible to register myself. This is done now. Thanks burek for creating the ticket meanwhile.
So I can only confirm that this isn't a regression as far as I am concerned. I only started using ffmpeg for encoding x264 video recently so I have no comparison point.
comment:5 by , 13 years ago
Reproduced by developer: | set |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Locally fixed, will be in mainline in a moment
comment:6 by , 13 years ago
Testing with 0.9.1, I am able to pass no-cabac as -x264opts but not thread-input:
[libx264 @ 0x645360] bad option 'thread-input': '1'
does not accept* (sorry)