Playback interruption on Rasperry PI

General
1

Hey all, I’m having continuous playback interruption while listening gmusic allaccess songs on Mopidy 0.19.5 running on raspbian.
Mopidy is the only service running on pi, mopidy cpu usage is ~20% and ram usage is ~45%
Problem seems related to audio buffer size (log attached) but I can’t find any way to change it’s configuration. Can you please help me?

Marco

mopidy.conf:
[logging]
config_file = /etc/mopidy/logging.conf
debug_file = /var/log/mopidy/mopidy-debug.log

[local]
enabled = false

[audio]
mixer = software
mixer_volume = 90
output = alsasink
visualizer =

[http]
enabled = false

[mpd]
enabled = true
hostname = 192.168.1.101
port = 6600

[gmusic]
username = xxxxxxxxxxxxxxxx@gmail.com
password = xxxxxxxxxxxxxxxx
deviceid = xxxxxxxxxxxxxxxx

mopidy.log:
----------------- music stop here -----------------
2015-01-17 18:08:21,739 DEBUG [5934:MainThread] mopidy.audio.actor: Buffer 5% full
2015-01-17 18:08:21,755 DEBUG [5934:MainThread] mopidy.audio.actor: Triggering event: state_changed(old_state=playing, new_state=paused, target_state=playing)
2015-01-17 18:08:21,760 DEBUG [5934:MainThread] mopidy.listener: Sending state_changed to AudioListener: {‘old_state’: u’playing’, ‘target_state’: u’playing’, ‘new_state’: u’paused’}
2015-01-17 18:08:22,003 DEBUG [5934:MainThread] mopidy.audio.actor: Buffer 13% full
2015-01-17 18:08:22,007 DEBUG [5934:MainThread] mopidy.audio.actor: Buffer 19% full
2015-01-17 18:08:22,011 DEBUG [5934:MainThread] mopidy.audio.actor: Buffer 26% full
2015-01-17 18:08:22,016 DEBUG [5934:MainThread] mopidy.audio.actor: Buffer 32% full
2015-01-17 18:08:22,475 DEBUG [5934:MainThread] mopidy.audio.actor: Buffer 39% full
2015-01-17 18:08:22,484 DEBUG [5934:MainThread] mopidy.audio.actor: Buffer 46% full
2015-01-17 18:08:22,489 DEBUG [5934:MainThread] mopidy.audio.actor: Buffer 53% full
2015-01-17 18:08:22,493 DEBUG [5934:MainThread] mopidy.audio.actor: Buffer 59% full
2015-01-17 18:08:22,777 DEBUG [5934:MainThread] mopidy.audio.actor: Buffer 62% full
2015-01-17 18:08:22,785 DEBUG [5934:MainThread] mopidy.audio.actor: Buffer 69% full
2015-01-17 18:08:22,789 DEBUG [5934:MainThread] mopidy.audio.actor: Buffer 75% full
2015-01-17 18:08:22,793 DEBUG [5934:MainThread] mopidy.audio.actor: Buffer 81% full
2015-01-17 18:08:23,293 DEBUG [5934:MainThread] mopidy.audio.actor: Buffer 88% full
2015-01-17 18:08:23,300 DEBUG [5934:MainThread] mopidy.audio.actor: Buffer 94% full
2015-01-17 18:08:23,322 DEBUG [5934:MainThread] mopidy.audio.actor: Buffer 100% full
2015-01-17 18:08:23,361 DEBUG [5934:MainThread] mopidy.audio.actor: Triggering event: state_changed(old_state=paused, new_state=playing, target_state=None)
2015-01-17 18:08:23,377 DEBUG [5934:MainThread] mopidy.listener: Sending state_changed to AudioListener: {‘old_state’: u’paused’, ‘target_state’: None, ‘new_state’: u’playing’}
----------------- music continue here -----------------

2

Strange, currently we don’t have anything exposed to control the sizes of the various buffers, but I’m working on a branch which will be adding something like this which hopefully would help for this case.

3

Is there any update on this scenario? I’m seeing exactly the same thing, unfortunately…