n5200 pro - squeezecenter responsiveness

[sparkle999]

Has anyone had any problems with the responsiveness of the squeezecenter software hosted off a thecus?

I ask because I've just upgraded from slimserver 6.x, have moved to the latest firmware, installed slimcenter. Rescanning etc very quick - circa 3 and a half minutes, however operating/navigating from a pc via web browser from album to album (adding a song, removing a song from a playlist etc) is taking ages (>30secs) - web browser is always waiting on the server. cpu loading on the thecus is 0%... Music seems to stream okay to the two SB3 devices - one wired, one wireless.

Only installed today, so am hoping it's something really stupid, e.g. is it caching some info or whatever, or user error. However, I feel as though something is wrong. The NAS box is happily xferring big files to the same pc very quickly, so I don't think it's the network.

Operating the SB3s using the remote seems fine.

Any things I could check? I've not tweaked any settings away from the default.

Thanks
sp.

[sparkle999]

More information. Managed to dig out the log file, which is screaming that there is a permissions problem. I am not sure what to do - I would be grateful if someone could cast their eye over the errors. I have just provided the top part of the log file as the rest of it is large, and seems to repeat the same errors.

Many thanks
sp.

[funkstar]

Have you re-booted your N5200?

I think a few of us were having similar problems with album art (although I wasn't getting _exactly_ the same error as that) and a re-boot sorted it out.

I think this returns after a clear and re-scan.

[sparkle999]

Have you re-booted your N5200?

Yes, I did that shortly after the first post... read on...

I think this returns after a clear and re-scan.

Ahhhhhhhhhhhhhh... Now that is very helpful indeed. Thankyou. Things had improved momentarily after the reboot, however I did a full rescan and the problems started again. I hadn't realised it was the rescan that was causing the problem...

That's a result, many thanks - I can workaround rebooting every now and again. Do I need to log a problem anywhere, or is it logged already?

Cheers sp.

[funkstar]

The guy that put the module together is aware of it i think, but he's away on business at the moment, so re-booting is the only work around right now.

I used to always do a complete clear and rescan when adding music to my library, but with 7.0 the look for new music option has worked a lot better for me than it did in 6.5.x.