No, Inviska software does not contain anything that could compromise the integrity of your computer, your security or your privacy. If you look at the Softpedia page for Inviska Rename and Inviska MKV Extract you can see they have both been independently verified to "not contain any form of malware, including but not limited to: spyware, viruses, trojans and backdoors." Inviska software contains:
The message you're seeing is because the software is unsigned. The purpose of code signing is to confirm the software author and guarantee that the code has not been altered or corrupted since it was signed. While useful, code signing certificates can be quite expensive and they have to be renewed annually. I only have a few pieces of software with a small user base, so it's hard to justify the cost of a certificate.
The message is actually nothing new, and Windows has warned users about unsigned software since Windows XP. However, the messages used to be rather less alarmist, as you can see in Windows 8.1:
While the old message focused on providing users with factual information, the new Windows 10 message appears more intent on alarming the user, and Microsoft now falsely claim that "Windows protected your PC."
If you click "More info" you're given the option to install the software:
The Windows 10 message seems rather severe and one can't help wonder if it's less about protecting your PC and more about encouraging users to get their software from the Windows Store.
When you use Edge to download a piece of Inviska the below message will be displayed. This reason for this is related to software signing. For a full explanation see the above question.
Inviska applications periodically check for updates so they can notify you when a new version is released. No information is sent from your computer; the software simply reads the latest version number from this file on the Inviska website. If you do not want the software to connect to the internet the behaviour can be disabled entirely (seen next question).
Yes, this behaviour can be disabled in the Preferences dialog under the General settings:
The first option will check for new releases and display a notification once, and only once, each time a new version is released.
The section option will check for new versions, and the latest version information will be displayed in the Help -> About dialog.
The third option disables update checks entirely, so the software will make no attempt to connect to the internet.
Settings are stored in an .ini file which is named after the application (e.g. InviskaFileManager.ini, InviskaRename.ini, etc). The location of the settings file depends on the operating system and version:
|Version||Config File Location|
|Windows Portable||In the application directory.|
|Mac Portable||In the .app bundle under /Contents/MacOS|
|Linux Portable||In the application directory.|
Very few people use 32bit Linux, with one major distribution saying that only 5% of their users used the 32bit version. Some distributions, such as openSUSE and Arch, are no longer offering 32bit versions, and with the vast majority of processors now supporting 64bit, it appears time to move on from 32bit.
It should run on most common distributions, and I've yet to encounter a distribution that it won't run on. The current 3.0 release has been tested to run without additional dependencies(*) on:
(*) The MKV applications are dependent on MKVToolNix, so that will have to be installed.
Inviska Rename uses the TagLib library for reading tags from music tracks. Generally speaking, TagLib works well for reading FLAC tags, as seen in this screenshot. However, there appears to be a small minority of FLAC files where tags are not correctly read. It may be related to this bug, but that seems to have been fixed. At some point in the future I'll ask the make enquires about this with the TagLib team and try to get it sorted out.
There are a small number of rarely used codecs that are not supported for extraction. Any files that contain unsupported codecs will have their names rendered in red. The tracks which use the unsupported codecs will also be coloured red:
The box next to such tracks cannot be checked, and the tracks will not be extracted as part of any batch extraction jobs.
The following codecs are not supported:
|V_MPEG4/MS/V3||Microsoft MPEG4 V3|
|A_PCM/FLOAT/IEEE||PCM Floating Point|
It is unlikely you will encounter these codecs in an mkv file, as they are not commonly used.