I returned to use your VTM after many years because my experience with it from many years ago was exceptionally good and the present version looks promising, except that... see below
I am using ver 15. of your VTM under windows 10 64-bit with the default code page for the Polish language. I have no problems with using the software in English and I do not need to have it localized. However, when it comes to reading files and folders with extended character sets in their names, your program fails to recognize cartain characters even so commonly used as "–" (cf "-") that other applications can handle without any issues.
The problem described is a nasty surprise and for the time being makes VTM unviable and actually – useless. It is still more surprising that your former versions (ex. ver. 4) worked like a charm under XP 32 bit and did not have any problems with extended character sets.
I will appreciate your advice how to overcome this disadvantege. Needless to say, renaming files and folders to make them readable for VTM is not a viable option at all.
Best regards
Marek
Code page issues?
Thanks for your reply. I know, that VTM works fine on a machine running Windows 10 with West-European code page, but it apparently refuses to work on Win10 with the East/Central European code page. That’s, of course, my guessing, because I am not a professional IT specialist and all I can do is to report the issue. My experience shows that whenever a folder or file name (imported from a disc file by option available in VTM) contains "–" or some other characters from the extanded character table, then the program cannot identify the file, whilst other files, i.e. free from "weird" characters are processed smotthly and perfectly. I’ll try to use the latest version and may be it will help. I’ll get back to you if the problem persists. However, if there is no "cure" to this "illnes" then I will (quite reluctantly) have to seek some other measures to produce thumbnails for my video clips. Cheers!
Hi, Sorry to have been tacit for such a long time due to my road accident and long recovery. Now, I am back here with my answers.
Now, I am using VTM ver 18.0.0 under Win 10 64-bit. The MS system configuration (region, etc.) is typical of machines and MSW systems traded in in the Central European Countries (former Russian zone of "socialist republics") with 1250 codepage and utf-8. In everyday tasks I use Total Commander 10 as my file browser. I have not encountered any problems with the recognition of most commonly used multimedia file formats by VTm when the file is opened via "Add File" or "Add Folder" function.
However, I encounted nasty problems with loading files to VTM with the use of txt file lists. As I found after seval tests, a number of programmes (except, Total Commander, Everything of VoidTools to mention, but a few) generate filelists in file formats other than win 1250 in utf-8. But I managed to develop a simple VB6 code with ADODB.Stream to have those "unfortunate" and misformatted files readable for your VTM.
Therefor, hereby I report, Sir, that the problems formerly reported are gone. I have one more question but I will put it in a separate thread.
Thanks for your co-operation and assistance.
Cheers, Marek
Now, I am using VTM ver 18.0.0 under Win 10 64-bit. The MS system configuration (region, etc.) is typical of machines and MSW systems traded in in the Central European Countries (former Russian zone of "socialist republics") with 1250 codepage and utf-8. In everyday tasks I use Total Commander 10 as my file browser. I have not encountered any problems with the recognition of most commonly used multimedia file formats by VTm when the file is opened via "Add File" or "Add Folder" function.
However, I encounted nasty problems with loading files to VTM with the use of txt file lists. As I found after seval tests, a number of programmes (except, Total Commander, Everything of VoidTools to mention, but a few) generate filelists in file formats other than win 1250 in utf-8. But I managed to develop a simple VB6 code with ADODB.Stream to have those "unfortunate" and misformatted files readable for your VTM.
Therefor, hereby I report, Sir, that the problems formerly reported are gone. I have one more question but I will put it in a separate thread.
Thanks for your co-operation and assistance.
Cheers, Marek