@Jim DeLaHunt wrote:
I am also seeing the following message in my Firefly log each second:
2007-11-10 16:57:53 (0000a803): timeout in select
2007-11-10 16:57:54 (0012b404): Finished streaming file to remote: 1716748 bytes
2007-11-10 16:57:54 (0000a803): timeout in select
These are the ones I am interested in. The first number (a803 in this case) is the thread id. Can you follow that log backwards and see what that thread is? Or what the last thing that thread did was?
Really there are three things to observe here:
- normal messages about songs starting and stopping.
- the “timeout in select” each second
- other interesting errors, such as “2007-11-10 16:58:13 (0012b804): Write error: Broken pipe … Error copying file to remote…”
The broken pipe may be normal if they played alright. That might be iTunes seeking for the start of music, or it might be iTunes closing the connection before the whole song is played because of a bad header, or something like that.
If it didn’t cause playback problems, it’s not a big deal.
At about 2007-11-10 16:58:17, I created a new smart playlist through Firefly’s web UI, and then in iTunes disconnected and reconnected with Firefly to force the new playlist to appear. I suspect that’s what provoked the messages about “unknown meta code”s.
Yeah, and those are normal. That’s just a reminder to me that I have new metadata fields I need to research and add. Unknown metadata is cheerfully ignored, and iTunes doesn’t really care if i do ignore it.
BTW, Ron, this is my first chance to say thank you for this awesome software. Mostly it’s working wonderfully.
You are welcome, of course. I’ll try and fix the breakage. 🙂