[ubuntu-mono] [Bug 688847] Re: [patch] startBristol process directly use sound device.
Takashi Sakamoto
688847 at bugs.launchpad.net
Thu Dec 23 13:32:29 UTC 2010
Now works fine in my maverick. Thanks and have a good year!
--
You received this bug notification because you are a member of Ubuntu
CLI/Mono Uploaders, which is subscribed to monobristol in ubuntu.
https://bugs.launchpad.net/bugs/688847
Title:
[patch] startBristol process directly use sound device.
Status in “monobristol” package in Ubuntu:
In Progress
Status in “monobristol” source package in Maverick:
Fix Committed
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
ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8
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)
PackageArchitecture: all
ProcEnviron:
LANGUAGE=ja_JP:ja:en
LANG=ja_JP.utf8
SHELL=/bin/bash
SourcePackage: monobristol
More information about the Ubuntu-mono
mailing list