22
edits
(Updated for build 6248) |
(Added error explanation for incorrect file name encoding) |
||
Line 33: | Line 33: | ||
If you modified ''any'' of the required files Avdump2 came with, you will either get a version error or several timeouts and no meaningful error message. So no, you can’t edit the config file either. | If you modified ''any'' of the required files Avdump2 came with, you will either get a version error or several timeouts and no meaningful error message. So no, you can’t edit the config file either. | ||
'''Failed to create MediaInfoProvider''' | |||
<tt>Failed to create MediaInfoProvider</tt> | |||
<tt>Invalid value returned by mil. This error may indicate that your LANG or LC_ALL environment variables are not set to use UTF-8 encoding.</tt> | |||
This error appears if you try to process a file with special characters in its name and your locale settings don’t match the file system encoding. Nowadays almost all file names are encoded with UTF-8 on Linux, so your locale should use that as well. If you work remotely on a server that sets LANG to “C” by default, it won’t work. Try setting LC_ALL=en_US.UTF-8, because that locale is installed almost everywhere by default. LC_ALL takes precedence over LANG. | |||
If you have a file with bogus characters in its name, even changing the locale won’t help. You have to rename the file to something sensible. | |||
== Workarounds == | == Workarounds == |
edits