Project

General

Profile

Bug #351

Audacious hangs while playing files from CIFS volumes

Added by Marco Squarcina over 11 years ago. Updated over 11 years ago.

Status:
Rejected
Priority:
Major
Assignee:
-
Category:
-
Target version:
-
Start date:
October 01, 2013
Due date:
% Done:

0%

Estimated time:
Affects version:

Description

Dear all,

the player becomes unresponsive when I try to move forward the track position slider on a long audio track (e.g. 1h 30') from a CIFS volume. Anyway, the overall performances while playing files from CIFS mounted volumes (on a gigabit link) are really bad. I've found users with similar problems on the web:

https://bugs.launchpad.net/ubuntu/+source/audacious/+bug/1130187
https://bugs.launchpad.net/ubuntu/+source/audacious/+bug/1048270
https://bugs.launchpad.net/linuxmint/+bug/1044923

The mentioned fix of mounting CIFS volumes with the "noserverino" option does not work here. Other players (e.g., vlc) are able to play tracks just fine. I'm using audacious-3.4.1 on gentoo and audacious-3.3.4 on ubuntu and tested the reported issue with different output plugins (i.e. jack, alsa, pulseaudio).

Thanks for this great player.

Kind regards,
Marco

use-fuzzy-seek.diff (1.75 KB) use-fuzzy-seek.diff John Lindgren, October 03, 2013 02:00

History

#1 Updated by John Lindgren over 11 years ago

The output plugin does not matter. What file formats are you playing?

#2 Updated by Marco Squarcina over 11 years ago

John Lindgren wrote:

The output plugin does not matter. What file formats are you playing?

mp3s, like this one: http://www.newcastlebeats.com/static/mixes/Autonomic/Autonomic_Podcast_Layer_01.mp3

#3 Updated by John Lindgren over 11 years ago

Does this patch help?

#4 Updated by Marco Squarcina over 11 years ago

Unfortunately, the patch didn't help. After testing several tracks, I noticed that the reported issue does not depend by the file format: audacious hangs even while seeking wav and flac files.

#5 Updated by John Lindgren over 11 years ago

Hmm, well, it helped immensely here. Apparently you have a different problem that is specific to your network configuration (but don't ask me how, I'm no networking guru).

#6 Updated by John Lindgren over 11 years ago

I've committed that patch. If you have another test case, I'll take a look at it.

#7 Updated by John Lindgren over 11 years ago

  • Status changed from New to Rejected

I'm closing this and #358 since both are unreproducible here and hence probably network configuration problems.

Also available in: Atom PDF