Sample file locating improvements

[lukas-w]

Consolidating issues about sample file location or missing sample file search.

• Allow several sample paths (Add tha possibility of have several paths to samples directory #2842, Custom/Multiple sample directories #4524)
• Search in project file's directory (Search for samples in Project file's local directory #2982) [Milestone: 1.3]
• Search for sample files with same name but different extension (Look for missing samples with different extension #2825)
• Search on other storage devices (LMMS should look for missing samples #4266)

As long we don't have support for sample bundling (#1257), we should store more information about samples in the project file to be able to locate them better. At the moment, we only store the file name & absolute path. Additional ideas:

• File size
• File hash
• Acoustic fingerprint (would help relocation even if the file was re-encoded)
• A flag indicating whether the sample is a factory sample shipped with LMMS
• Other metadata?

[Spekular]

Related: Missing files for sample tracks don't show up in the LMMS Error report. ( Full email quote removed by @lukas-w )

[musikBear]

In regard to "LMMS should look for missing samples" an intermedia option would be, that the user either input a direct path, and LMMS will then load that file, or user inputs a directory, and LMMS then scan that. The latter is used by sonys tracker sw.
Even thoug i am somewhat reluctant to let programs make HD changes, LMMS could either make a copy of the located file or move the located file, into the Setting defined path, so that this relocating would be a one off.
Writing this, i also see a design for packed-projects