Comment 4 for bug 1064118

Revision history for this message
billio (billoldroyd) wrote :

On 32-bit 13.10 the CD used for this test plays without a problem in all applications that play CD tracks..

On amd64 system 13.10, the same CD only plays with significant gaps in the playback and will eventually stop playing.

However, if I Restart the system, and play a CD track by clicking on the file displayed in Nautilus which loads into Totem, the CD track plays fine. Running other software, for example Firefox, has not effect on the playback.

Now, if I run Rhythmbox it will will play tracks from the mucic library normally without a problem, but if I attempt to play a track from the CD then System Monitor shows high IOwait status and the playback has gaps. If I run other software such as Firefox the gaps get longer and eventually the track stops playing.

If then I quit Firefox and run Totem again, Totem will no longer play the track properly and has the same and sometimes longer gaps in playback, with very high IOwaits. Eventually it stops playing the track.

Now, if I Suspend and then Resume, Totem will play the track properly as originally. Running Rhythmbox in the way described above is exactly the same, long gaps in playback.

If I Restart the system and go through this same scenario a second time, but in this case using Soundjuicer instead of Rhythmbox, Soundjuicer has exactly the same effect as Rhythmbox, that is gaps in playback, high IOwait and the same impact on Totem.

The DVD Drive is TSSTCorp CDDVDW SH-S233C
Rhythmbox is 2.991
Soundjuicer is 3.5.0
Totem is 3.8.2

It would seem to me that Rhythmbox and Soundjuicer are having the same impact on the system. Are they somehow loading different software for CD buffering that over-rides the initial load used by Totem ?.

I don't know how to check if something like this has changed. Any advice ?.