Page 3 of 3

Re: Listers don't work with *.ts files

Posted: 2020-01-17, 16:21 UTC
by DrShark
ghisler(Author) wrote: 2020-01-17, 16:05 UTCIt doesn't because multimedia file tend to be HUGE, and passing them to a plugin which doesn't declare that it supports them could take a LOT of time. For example, when you pass a 2 GB video to a text plugin, it can block the viewer for several minutes.
But some (in theory any/all) files with file types Lister recognizes as multimedia may also be used for different purpose (e.g. *.ts files are also script programs=plain text files). If Lister plugin is designed to show a script program it will normally load itself only for plain text *.ts files and will skip media *.ts files anyway.

And again, it's impossible to demand plugin authors to declare "MULTIMEDIA" in detect string because neither plugin authors nor plugin users know what file extensions Lister recognizes as multimedia file types on particular system!

EDIT: maybe TC should also store the list of all extensions it recognizes as multimedia in currently running environment in some wincmd.ini parameter, and with some other wincmd.ini parameter (like notmultimedia=) to let user to add the extensions from first list which Lister must NOT recognize as multimedia?

Re: Listers don't work with *.ts files

Posted: 2020-01-18, 05:33 UTC
by Usher
I think there won't be such problems, if multimedia *.ts filetype is defined with magic numbers (file signature).
You can add magic numbers also for other multimedia files or other known file extension conflicts.
See Wikipedia list: https://en.wikipedia.org/wiki/List_of_file_signatures
Note: Wikipedia lists only 0x47 for ts stream, but all files I have tested start with 0x4740.

Re: Listers don't work with *.ts files

Posted: 2020-01-22, 20:44 UTC
by DrShark
BTW, in TC 9.50 should be possible to solve the problem without any ini editing using new Default view method by type Lister feature.
At least here on Vista 32-bit it works with PNG and Imagine.wlx without MULTIMEDIA detect string: I just added Image plugin as a default view method for *.png and it works.
Can someone try the same for *.ts on Windows where there was a problem using plugins without MULTIMEDIA detect string for this extension?

2ghisler(Author)
For complete solution of a problem, I still suggest to make TC show somewhere (in wincmd.ini parameter, or some dialog) all the extensions Lister recognizes as multimedia, so user at least could know it may be a reason Lister doesn't load some plugin and it worth trying Default view method by type for problem extension and plugin in that case.

Re: Listers don't work with *.ts files

Posted: 2020-01-23, 10:16 UTC
by ghisler(Author)
It depends on the configuration. TC calls
GetProfileString('mci extensions',...
to get a list of multimedia extensions. This is redirected by Windows to the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\WINDOWS NT\CURRENTVERSION\MCI EXTENSIONS
btw, this redirection is defined here:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\IniFileMapping\win.ini

Re: Listers don't work with *.ts files

Posted: 2020-01-23, 13:31 UTC
by DrShark
ghisler(Author) wrote: 2020-01-23, 10:16 UTC It depends on the configuration. TC calls
GetProfileString('mci extensions',...
to get a list of multimedia extensions
Thanks for information. I suggest to add it to newer edition of listplugin.chm so plugin developers could use it too to check whether extensions of files formats viewed by their plugins need MULTIMEDIA in plugin default detect string.
ghisler(Author) wrote: 2020-01-23, 10:16 UTCThis is redirected by Windows to the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\WINDOWS NT\CURRENTVERSION\MCI EXTENSIONS
btw, this redirection is defined here:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\IniFileMapping\win.ini
It's good that for users it's possible to see that extensions list too in Registry (or maybe in win.ini file directly in older Windows), but I think more user friendly way is to show that list in some TC dialog (maybe in Software tab of cm_SysInfo or in cm_About dialog).