Maverick: Kino plays too fast, sound is not passed through pulseaudio

Bug #436248 reported by Daniel Ellis
66
This bug affects 13 people
Affects Status Importance Assigned to Milestone
kino (Debian)
Fix Released
Unknown
kino (Ubuntu)
Confirmed
Undecided
Unassigned
Nominated for Jaunty by Nigel Stewart
Nominated for Karmic by Nigel Stewart
Nominated for Lucid by Nigel Stewart
Nominated for Maverick by Nigel Stewart

Bug Description

Binary package hint: kino

When playing back a video, the sound will cut out if another application plays a sound. As far as I understand, all applications need their audio routed through pulseaudio for them to work nicely together.

The author notes that kino does not directly support pulseaudio, but padsp may be used to redirect the output. [http://www.kinodv.org/article/view/173/1/13/]

I have tested this by changing the menu item of kino from 'kino %F' to 'padsp kino %F'. This fixes the issue and I don't notice any increased latency on the audio.

Revision history for this message
Nigel Stewart (nigels) wrote :

When playing back video, and pulse audio active, no audio and video playback is too fast.
And lots of output:

Could not open ALSA device "/dev/dsp": No such file or directory
ALSA lib pcm.c:2211:(snd_pcm_open_noupdate) Unknown PCM /dev/dsp

The padsp workaround improves video playback, but the audio sounds choppy.

The workaround that works well for me (and others) is to use pasuspender
to suspect pulse audio and allow direct audio hardware access.

Further discussion:
http://ubuntuforums.org/showthread.php?t=1334403

Revision history for this message
Nigel Stewart (nigels) wrote :

The workaround I suggest for Jaunty, Karmic, Lucid and Maverick is to adjust the Kino menu item to prefix kino with pasuspender in order to bypass pulse audio.

Revision history for this message
Stefan Divjak (stefan-divjak) wrote :

Same issue here, with the only difference that kino so far worked fine in Jaunty, Karmic and Lucid. After the update to Maverick I have exactly the above symptoms, so i would see this as a regression.

Changed in kino (Ubuntu):
status: New → Confirmed
tags: added: regression-release
summary: - Karmic: Sound in Kino is not passed through pulseaudio
+ Maverick: Kino plays too fast, sound is not passed through pulseaudio
Revision history for this message
Olivier Berger (olivierberger) wrote :

May I suggest to have a look at the workaround suggested in : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=526655#10

Hope this helps.

Changed in kino (Debian):
status: Unknown → New
Revision history for this message
Ian (ifreecarve) wrote :

i've tried the following combinations (command, audio device) with no success:

kino, default
kino, /dev/dsp
padsp kino, default
padsp kino, /dev/dsp
pasuspender kino, default

using pasuspender also breaks sound on my system, which forces me to "killall pulseaudio && /etc/init.d/pulseaudio" to get it working again.

Revision history for this message
Timokl (timokl) wrote :

Yesterday, Kino worked fine. Today, I imported an Mpeg-2 file - and after that I have the same problems: Accelerated playback and no sound.

Revision history for this message
Timokl (timokl) wrote :

Turing off sound in Kino produces playback at normal speed - but no sound. :-/

Revision history for this message
arkmundi (rkerver) wrote :

Ubuntu 11.10 (Oneiric Ocelot), same problem as outlined
padsp kino:: command works OK
adding my voice that it would be good if Kino authors, working with Debian & Cannonical, would get it all working with pulseaudio, and reincarnate the app into present tense
many thanks!

Revision history for this message
Michael Franzl (michaelfranzl) wrote :

Same problem here on Ubuntu 11.10 as outlined.

The following workarounds did NOT work for me:

* padsp kino
* pasuspender -- kino
* entering "default" as audio device
* entering any other existing audio device which is in /dev/snd/

I had the same problem in Ubuntu 10.10 on a completely different computer. Apparently this bug exists since 2008. I'm asking myself why this program is even in Ubuntu?

Revision history for this message
Chris (cmavr8) wrote :

padsp kino command works OK for me too.
Ubuntu 11.10 64-bit fully updated.

Revision history for this message
charles.fox@gmail.com (charles-fox-gmail) wrote :

This is still present in 12.04 (Ubuntu studio), but the previously suggested fix of running with
   $ padsp kino
makes both the sound playback and correct video speech work.

(This works because kino is using the old fashioned dsp audio API. It's been superseeded by ALSA,Pulse and others, but the padsp command provides an emulation of the API from Ubuntu's standard pulseaudio desktop sound system. The Kino developers or maybe ubuntu packagers could easily fix by testing if pulse is running, and automatically switching to this command for the launcher. It could be done with a wrapper script rather than changing kino itself.)

Revision history for this message
charles.fox@gmail.com (charles-fox-gmail) wrote :

(if padsp doesn't work for some users, they may need to install the padsp program first of course.)

Revision history for this message
Kirils Solovjovs (linux-kirils) wrote :

This is still the case with kino version 1.3.4-1.3
padsp workaround works.

please fix.

Changed in kino (Debian):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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