[patch] startBristol process directly use sound device.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
monobristol (Ubuntu) |
Fix Released
|
Medium
|
Stefan Ebner | ||
Maverick |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Binary package hint: monobristol
I think monobristol should open startBristol process with "-audiodev default" option.
Current version of startBristol directly opens sound device (hw(0,0)) without this option, not via PulseAudio. With "-audiodev default" option, startbristol opens default pcm device of ALSA. It's PulseAudio. Then we can see bristol pcm output in gnome-sound window. This is due to ALSA plugin of PulseAudio.
In my opinion, application's direct access to sound device is not good. If one application directly use the sound device, the other application cannot use it and there is no possibility to mix sounds from different appications.
To solve this issue, I attach 03_audiodev.patch.
Thanks to include my patch #660627 and It's my glad if you include this audiodev patch to distributed package.
Regards.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: monobristol 0.60.1-2~maverick1
ProcVersionSign
Uname: Linux 2.6.35-24-generic i686
Architecture: i386
Date: Sat Dec 11 10:00:21 2010
InstallationMedia: Ubuntu-Studio 10.10 "Maverick Meerkat" - Beta i386 (20100902.1)
PackageArchitec
ProcEnviron:
LANGUAGE=
LANG=ja_JP.utf8
SHELL=/bin/bash
SourcePackage: monobristol
Related branches
tags: | added: patch |
Changed in monobristol (Ubuntu): | |
importance: | Undecided → Medium |
Changed in monobristol (Ubuntu Maverick): | |
importance: | Undecided → Medium |
tags: |
added: verification-done removed: verification-needed |
Changed in monobristol (Ubuntu): | |
status: | In Progress → Fix Released |
I'll take a look and talk to upstream the next few days.
Thanks for your work in advance!