Windows Builds: Cannot parse localmotion! #104
Comments
|
Thanks for reporting. This is connected to the new binary file format. Sorry that it causes trouble. |
|
Which hardware do you run it on? |
|
I am using a Lenovo Thinkpad T470s. It has an Intel Core i7-7500U DualCore, 16GB DDR4 RAM, a 512GB SSD and an Intel HD 620 shared graphic card. My friend uses an AMD FX-4300 Quad-Core, 4GB DDR4 RAM and an ATI Radeon 3000. |
|
If I understand it correctly, it should be configurable with a commandline argument, but the argument 'fileformat' is not known by any of the versions I am testing. |
|
The flag is an internal flag that is not exposed to the FFmpeg interface. We need to fix the problem with the new file format. |
|
I‘ve seen the issue also on macOS on M1 (ARM) using a binary build of ffmpeg. |
|
As a note, I am not able to reproduce, tested on windows just now with both a build from gyan and one I just now compiled from the git HEADs of vid.stab and ffmpeg |
|
I am using a build recently compiled from sources on Mac ARM (git-2021-03-26-cad3a5d) and it's not present any more. |
|
I still see the problem in John van Sieckle's ffmpeg static builds for amd64, both release 4.4 and git master from May 1st. It works fine with release 4.2.2 (which is before the change). I'm running this on a Lenovo Thinkpad T450s with an i5-5300U. |
|
I can confirm the problem still there. built from vid.stab f9166e9 exec: result: I don't see any differences between input and output video. |
1480c1
added a commit
to 1480c1/vid.stab
that referenced
this issue
Jun 6, 2021
Currently there isn't a way to set either ascii or binary format in FFmpeg and that causes an issue with FFmpeg on Windows it seems. It will be better to wait until the flag can be exposed through the API or wait until an ABI update to set the binary mode as the default georgmartius#104 Signed-off-by: Christopher Degawa <[email protected]>
|
I'm still getting this error. I built ffmpeg from source, version N-103951-g2b2e9afdd2. Lenovo ThinkPad X260, Linux (Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 8GB RAM) |
|
After 2 years, same error... Version 4.1.4 works, version 4.4 throws "Cannot parse localmotion!" and doesn't stabilize. Same video, same command line, only the ffmpeg binaries are different. Command lines: Error: Build that throws the error: Build that works: |
|
Build v32 from https://www.gyan.dev/ffmpeg/builds/ (ffmpeg 5.1) works on Windows 10 for me. But I had to generate the transforms file with the new version, too (running on a trf file from ffmpeg 4.3.1 I had before was not working). |
|
Dear all, this error is stil unsolved on W10. However, the same ffmpeg version works on W11. So, it is somehow related to the system, it works on W11, does not work on W10. All W.. are with latest updates. |
|
ffmpeg v6.0.1 on Mac M2 suffers from this problem as well. And there's no option to choose the ASCII fileformat, it always generates the new binary fileformat - causing the second pass to always fail with error message "Cannot parse localmotion"
|
|
just to highlight here and help anyone else having this error: basically add fileformat=1 to force saving as old text file format. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I tried to stabilize a video on windows 10. I tested the release and git builds from https://www.gyan.dev/ffmpeg/builds/ and the gpl and gpl-4.3 builds from https://github.com/BtbN/FFmpeg-Builds/releases. All gave me the same error:
Cannot parse localmotion! Last message repeated 236 timesand I could not see any differences between input and output video.I tested it with default options like so:
I did the same in manjaro linux an it worked without any problem.
This is the manjaro version:
These are the windows 10 versions:
and
The text was updated successfully, but these errors were encountered: