I think it may be specific to your system/CDROM drive. The plugin is very simple - it passes the parameter (in this case -t 4 ) directly to cdda2wav and it tries to retrieve the audio from that track.
This plugin is a hack and there are a number of things that can go wrong - such as. 1. cdda2wav was not intended to do realtime playing so perhaps something with you system/drive is making it buffer data and it stalls. 2. cdd2wav is "upsetting" your drive. 3. SC timeouts waiting for data from cdda2wav. I suspect the CDROM drive buffering is kicking in and that the drive is spinning up for a big buffer read and SC timeouts. To SC the "cdplay:" device looks like a radio station URL so perhaps increasing Radio Station timeout (see Settings/Advanced/Network ) might help. With one DVDROM drive I found cdda2wav could only play one track. To play another track I had to re-read the CD's Table of Contents. When I updated the DVDROM drive firmware - evrthing was OK. So cdda2wav/CD driver can upset some drive hardware in unexpected ways. You could use cdd2wav to rip a track4 to a file and then play track 4 to verify. If that worked then you know the issue is probably buffering/timeouts - a log with player.source set to INFO might show somehting. -- bpa ------------------------------------------------------------------------ bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806 View this thread: http://forums.slimdevices.com/showthread.php?t=42106 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
