Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
How to ignore some composers
17-03-2018, 09:29
Post: #21
RE: How to ignore some composers
What exactly do you have in the field when you get the error?
Find all posts by this user
Quote this message in a reply
17-03-2018, 10:26 (This post was last modified: 17-03-2018 10:26 by Uoppi.)
Post: #22
RE: How to ignore some composers
The last I tried was C:\tagUpdate.txt (tagUpdate.txt is correctly in the root folder).
Find all posts by this user
Quote this message in a reply
17-03-2018, 13:25
Post: #23
RE: How to ignore some composers
There is more than one sort of red error message if you enter something wrong in the tagUpdate properties box. What is the exact message you are seeing?
Find all posts by this user
Quote this message in a reply
18-03-2018, 08:00 (This post was last modified: 18-03-2018 08:01 by Uoppi.)
Post: #24
RE: How to ignore some composers
(17-03-2018 13:25)haggis999 Wrote:  There is more than one sort of red error message if you enter something wrong in the tagUpdate properties box. What is the exact message you are seeing?

It's the same one as posted earlier in this thread: "Must be a filename; correct highlighted value and retry". It's always this error.

Not that I mind terribly, because in the case of classical music, the tweak wouldn't result in any fewer navigation steps for me, given the way I've tagged things. It just would have looked nicer to have my main categories of "Classical" and "Rock/pop/jazz" available straight from the first view.
Find all posts by this user
Quote this message in a reply
18-03-2018, 10:10
Post: #25
RE: How to ignore some composers
(18-03-2018 08:00)Uoppi Wrote:  
(17-03-2018 13:25)haggis999 Wrote:  There is more than one sort of red error message if you enter something wrong in the tagUpdate properties box. What is the exact message you are seeing?

It's the same one as posted earlier in this thread: "Must be a filename; correct highlighted value and retry". It's always this error.
It was me that generated the earlier post quoting that error message. In my case, it was caused by accidentally putting my empty tagUpdate file in the wrong location. You appear to have avoided that mistake.

I first hit similar problems when I tried to use a location on my PC rather than on my NAS, where MinimServer is running. Once again, you have confirmed that a PC location is correct in your case, as that's where you run MinimServer.

I've run out of ideas. Simon is now your best bet for a solution, as he is on so many other occasions.
Find all posts by this user
Quote this message in a reply
18-03-2018, 13:36
Post: #26
RE: How to ignore some composers
I tried a few things, yesterday, to provoke the error message and failed. Empty files; utf8 or Unicode endcoded files; no problem. Minimserver appears to simply require a file to exist with the same file name to be satisfied.

Please forgive this suggestion, but it may be helpful if you could provide a screen grab of the tagUpdate.txt properties window, i.e. from right-clicking on the file.

[Image: timestampgood.jpg]

ps - and can you also confirm the Window OS.
Find all posts by this user
Quote this message in a reply
18-03-2018, 15:49
Post: #27
RE: How to ignore some composers
Following on from this suggestion, the file might actually be named tagUpdate.txt.txt. Windows Explorer omits the file extension by default and would show this file as tagUpdate.txt.
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)