Well, I can't go so far as to say that any specific script lines are causing the problem. I get no error messages whatsoever, only the invalid track ID. It's simply too many, unrelated scripts that trigger the behavior and I'm no programmer, so I can't say that they all have the same string involved, though I suppose it's possible if highly unlikely.
To give you an idea of what I'm talking about, at least one of the scripts works fine by itself but triggers the invalid track ID when paired with another script, which doesn't trigger the behavior on its own. Here's what I've come up with so far as scripts that trigger the behavior:
My Custom Nodes = Always Errors
AutoRateAccurate + MonkeyRok = Always Errors
AutoRateAccurate + Play History = No Errors
AutoRateAccurate + Others = No
AutoRateAccurate = No
MonkeyRok + Play History = No
MonkeyRok + Others = No
MonkeyRok = No
Play History + Others = No
Play History = No
And later I found that Lyrics Viewer also causes the problem but I didn't test it by itself. It was simply one of those I'd installed since I uninstalled MonkeyRok and no longer had a lyrics window in my interface. I was pretty bummed when that wouldn't work either. Note that MonkeyRok by itself causes no issue but when paired with AutoRateAccurate, the invalid track ID returns.
The scripts in my sig all work fine and do not appear to trigger an invalid track ID. I didn't test every one individually, but I did test the big-hitters with these smaller scripts installed and found no problems with them, as described above.
For what it's worth, I don't use WebSearchPanels but I do have WebNodes and Classification and Genre Changer installed and neither gives me an issue.
Well, I can't go so far as to say that any specific script lines are causing the problem. I get no error messages whatsoever, only the invalid track ID. It's simply too many, unrelated scripts that trigger the behavior and I'm no programmer, so I can't say that they all have the same string involved, though I suppose it's possible if highly unlikely.
To give you an idea of what I'm talking about, at least one of the scripts works fine by itself but triggers the invalid track ID when paired with another script, which doesn't trigger the behavior on its own. Here's what I've come up with so far as scripts that trigger the behavior:
[quote]My Custom Nodes = Always Errors
AutoRateAccurate + MonkeyRok = Always Errors
AutoRateAccurate + Play History = No Errors
AutoRateAccurate + Others = No
AutoRateAccurate = No
MonkeyRok + Play History = No
MonkeyRok + Others = No
MonkeyRok = No
Play History + Others = No
Play History = No[/quote]
And later I found that Lyrics Viewer also causes the problem but I didn't test it by itself. It was simply one of those I'd installed since I uninstalled MonkeyRok and no longer had a lyrics window in my interface. I was pretty bummed when that wouldn't work either. Note that MonkeyRok by itself causes no issue but when paired with AutoRateAccurate, the invalid track ID returns.
The scripts in my sig all work fine and do not appear to trigger an invalid track ID. I didn't test every one individually, but I did test the big-hitters with these smaller scripts installed and found no problems with them, as described above.
For what it's worth, I don't use WebSearchPanels but I do have WebNodes and Classification and Genre Changer installed and neither gives me an issue.