Playback error - can't read from source

Bug #736402 reported by Rizlaw
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gmusicbrowser (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Running latest ppa version of gmusicbrowser (1.1.6). Playback output settings are "alsa" and alsa device = "hw:0,1" in advanced settings in order to obtain bit perfect digital output to external DAC. The OS is Ubuntu 10.04.2 LTS.

During playback of music I get random pauses with the pop up notification that player can't read from source. Music stops playing, sometimes pressing play button restarts playback, sometimes it doesn't.

The attached screenshot of the error shows the exact message displayed.

Tags: playback
Revision history for this message
Rizlaw (rizlaw) wrote :
Revision history for this message
Simon Steinbeiß (ochosi) wrote :

thanks for taking the time to report the bug.
does this happen in the beginning of a song or in the middle?

and: could you check whether other gstreamer-based players expose the same/ a similar behavior with these settings?

(you could try e.g. parole or totem-gstreamer or exaile)

another test: could you try to get two instances of gmusicbrowser playing back at the same time or alternatively gmusicbrowser and one of the above mentioned gstreamer-based players?
(for two gmusicbrowser instances you have to start it from a terminal with the options "-nofifo -nodbus")

Revision history for this message
Rizlaw (rizlaw) wrote : Re: [Bug 736402] Re: Playback error - can't read from source

On Wed, 2011-03-16 at 23:27 +0000, Simon Steinbeiß wrote:
> thanks for taking the time to report the bug.
> does this happen in the beginning of a song or in the middle?
>
> and: could you check whether other gstreamer-based players expose the
> same/ a similar behavior with these settings?
>
> (you could try e.g. parole or totem-gstreamer or exaile)
>
> another test: could you try to get two instances of gmusicbrowser playing back at the same time or alternatively gmusicbrowser and one of the above mentioned gstreamer-based players?
> (for two gmusicbrowser instances you have to start it from a terminal with the options "-nofifo -nodbus")
>

Simon,

As I recall, it happens at the beginning of a track change.

Revision history for this message
Simon Steinbeiß (ochosi) wrote :

again:

 * could you check whether other gstreamer-based players expose the same/ a similar behavior with these settings?
 * another test: could you try to get two instances of gmusicbrowser playing back at the same time or alternatively gmusicbrowser and one of the above mentioned gstreamer-based players?

Revision history for this message
Rizlaw (rizlaw) wrote :

On Fri, 2011-03-18 at 17:42 +0000, Simon Steinbeiß wrote:
> again:
>
> * could you check whether other gstreamer-based players expose the same/ a similar behavior with these settings?
> * another test: could you try to get two instances of gmusicbrowser playing back at the same time or alternatively gmusicbrowser and one of the above mentioned gstreamer-based players?
>

I don't use/like exaile so I can't comment.

I do use totem-gstreamer but I can't play it simultaneously with
gmusicbrowser. I did try playing totem and gmusicbrowser alternately.
When I stop GB and start totem and then stop totem and try to restart
GB, I do get the same error message popping up. Usually, a second click
on the GB "play" button will get it to start playing again.

Revision history for this message
Simon Steinbeiß (ochosi) wrote :

sorry, i still can't reproduce your bug.
can you reproduce this at all with totem-gstreamer? (e.g. playing a longer playlist of files that exposed that problem with gmusicbrowser and seeing whether they play flawlessly)

did you activate any additional gstreamer-functions like gapless? (that's still pretty experimental/unstable btw)

Changed in gmb-shimmer:
status: New → Triaged
Revision history for this message
Rizlaw (rizlaw) wrote :

On Tue, 2011-04-05 at 08:37 +0000, Simon Steinbeiß wrote:
> sorry, i still can't reproduce your bug.
> can you reproduce this at all with totem-gstreamer? (e.g. playing a longer playlist of files that exposed that problem with gmusicbrowser and seeing whether they play flawlessly)
>
> did you activate any additional gstreamer-functions like gapless?
> (that's still pretty experimental/unstable btw)
>
> ** Changed in: gmb-shimmer
> Status: New => Triaged
>

In Ubuntu 10.04.1, Totem (Movie Player 2.30.2 using gstreamer 0.10.28)
does not have any setting or plugin that I can find to enable gapless or
alsa device = hw:0,1 to the obtain bit perfect playback settings
identical to those I enabled in gmusicbrowser, Quodlibet, Guayadeque and
gmpc/mpd. The "AC3 passthru" option does not pass bit perfect digital
output. I have also looked at gconf-editor and found no Totem Movie
Player settings that would allow me to enable gapless or alsa hw:0,1
settings.

Consequently, I can't play a longer playlist with the necessary type of
HD music files that triggers the problem in gmusicbrowser when I am
playing a mix of 16/44, 24/88, 24/96. 24/192 files.

All I can report is that, of the players that allow me to set and play
bit perfect HD music files (gmusicbrowser, Quodlibet, Guayadeque and
gmpc/mpd), only gmusicbrowser exhibits the problem previously described.

It's unfortunate you can't replicate my problem, and I'm not sure that I
can provide any further useful feedback, but I do appreciate the effort.

Pasi Lallinaho (knome)
Changed in gmusicbrowser (Ubuntu):
status: New → Triaged
no longer affects: gmb-shimmer
Revision history for this message
Jackson Doak (noskcaj) wrote :

Please re-open this bug if you find it on a currently supported release

Changed in gmusicbrowser (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for gmusicbrowser (Ubuntu) because there has been no activity for 60 days.]

Changed in gmusicbrowser (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.