And why is the file names important ? it's the tagging thats important
.Do you resort to untagged files and have LMS guesing artist etc from
the file names ?
Another case of case sentive vs not case sensitive are *.cue files .LMS
on Win find the corrsponing flac,mp3 or wav vs on *nix the case
mherger wrote:
>
> Your initPlugin method might be called before the FTS plugin is
> initialized. Use the postinitPlugin sub instead.
>
Thanks!!! - that was spot on. I'll change my code accordingly.
sternenjaeger's
To make sure that it's not my code that causes the problem i used the
init routine of the HelloWorld plugin. When issuing a search for a
playlist by name:
Code:
sub initPlugin {
my $class = shift;
myDebug("Initializing the plugin");
my
frank1969 wrote:
> So I don't understand what happens there:
> If windows sees both as the same file, scanner (who is case sensitive)
> should just see "changed file", (example 1) remove the old artist "Abba"
> and insert the new artist "ABBA". I don't understand why it keeps the
> old spelled
mherger wrote:
> The short answer to your subject: the scanner is case sensitive, but
> Windows is not.
I'm aware of this fact - but just therefore I thought it wouldn't
matter, if the file is called "Ich liebe Dich" or "Ich liebe dich" - or
"ABBA" <=> "Abba" - for Windows is case insensitive
When working on my "BookmarkHistory" plugin i noticed a possible issue
with the "playlists" CLI command when the full-text search feature is
enabled.
To make sure that it's not my code that causes the problem i used the
init routine of the HelloWorld plugin. When issuing a search for a
playlist
