rich.herbs wrote: > When the transporter is asked to play a track and doesn't get past the > first second, the status reports mode:play waitingToPlay:1 time:0. The > time:0 confirms that zero seconds have been played (i.e. player > stalled), and the waitingToPlay:1 is, according to the CLI documentation > -"A flag telling whether the player isn't actually playing, but still > waiting for data or something."- All this confirms the symptoms, but > doesn't help much.
Remember player is quite dumb. CLI is LMS giving a version of the Tranporter behaviours. From the slimproto - it is clea rthat data has been sent to Transporter, data has been moved from Transporter input buffer into output buffer (which I think means it has been decoded) but then nothing happens. Since output buffers is full, LMS doesn't send anymore data until output moves, LMS will not generate any display to show track is playing, So Transporter firmware has detected something that tells Transporter processor that output cannot happen (e.g. some sort of DAC input pins say "Not ready"). As I see it, what is required now is somebody with a problem Transporter and a scope or meter to test the circuit (e.g. DAC pins, voltage rails) - they may need advice/guidance from a h/w person such as JoeMuc2009 who has some knowledge of the Transporter innards. As a starting point, I think there are some diagnostics in the Transporter firmware menu - such as test tones. Any test in the firmware menu should be checked. ------------------------------------------------------------------------ bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806 View this thread: http://forums.slimdevices.com/showthread.php?t=110057 _______________________________________________ diy mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/diy
