Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 549 by icyfi...@
gmail.com: per_frame_options bug
https://bugs.chromium.org/p/webp/issues/detail?id=549I don't know where the bug is supposed to be filed for this; from reading the docs:
https://developers.google.com/speed/webp/docs/img2webpthe "Synopsis" says: img2webp [file_level_options] [files] [per_frame_options...]
which to mean; means the correct commandline for what i'm running is this:
libwebp-1.2.2-rc1-windows-x64\libwebp-1.2.2-rc1-windows-x64\bin\img2webp.exe -o ScreenCapture\20220104T211619.webp ScreenCapture\Capture-20220104T205004.jpg ScreenCapture\Capture-20220104T205005.jpg -d 2048
When I run this though; the duration between frames is only 100 milliseconds.
If I read the example at the bottom of the documentation it shows the [per_frame_options...] ahead of the [files] and when I replicate my command line like that , the output is as expected
libwebp-1.2.2-rc1-windows-x64\libwebp-1.2.2-rc1-windows-x64\bin\img2webp.exe -d 2048 -o ScreenCapture\20220104T211619.webp ScreenCapture\Capture-20220104T205004.jpg ScreenCapture\Capture-20220104T205005.jpg
So I guess the question is, is the documentation wrong in that [per_frame_options...] go at the end, is the program wrong for not recognizing the [per_frame_options...] after the files.
Thank you
Dennis Rutherford
--
You received this message because:
1. The project was configured to send all issue notifications to this address
You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings