kdf Wrote: > I'll add a bit more in there hopefully for tomorrow's nightly build, to > track the scan trigger and we'll have to see the logs again.
That sounds good. Unfortunately I'll be away for a week, but it looks like abunn is experiencing the same issue so may be able to provide feedback (assuming his logs look the same to start with). Otherwise I'll be back on to it next Monday. kdf Wrote: > In the meantime, it might be worth trying out MMM 1.1.5, which I believe > has been released a couple days ago. That is what I've been using in > the recent tests. I've upgraded to 1.1.5 and same story - as seen also by abunn. kdf Wrote: > Is this at startup? Yes, that's the beginning of the log onwards. I wasn't able to get the debug settings to save between sessions though, so I don't know what SS is doing on initialise (i.e. between start-up and me enabling the debug). kdf Wrote: > Have you managed to actually complete a scan before? I assume you mean SS scanning the MMM library. Yes - I left it running all day today while I was at work, and it had finished when I got back. Everything worked basically fine (a few CPU peaks causing minor playback interruptions on the SoftSqueeze) until I closed MMM & SS down and restarted them, at which point it seemed to have lost all knowledge and it was back to square 1. -- hunta _______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
