[ubuntu-mono] [Bug 688847] Re: [patch] startBristol process directly use sound device.
688847 at bugs.launchpad.net
Mon Dec 20 15:12:46 UTC 2010
I tested it from maverick proposed and get unexpected behaviour. Then i
review my patch and found my mistake to the patch...
In advanced mode, the value in "adriver" item should be valuated but in
my patch "easyariver" is still valuated (at 21st line in previous
patch). This is due to my miss-operation to create the patch, maybe
subtle copy mistake...
I'm sorry for package mentainers to take more time just before your
** Patch added: "Modified patch for audiodev issue"
You received this bug notification because you are a member of Ubuntu
CLI/Mono Uploaders, which is subscribed to monobristol in ubuntu.
[patch] startBristol process directly use sound device.
Status in “monobristol” package in Ubuntu:
Status in “monobristol” source package in Maverick:
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.
DistroRelease: Ubuntu 10.10
Package: monobristol 0.60.1-2~maverick1
ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 18.104.22.168
Uname: Linux 2.6.35-24-generic i686
Date: Sat Dec 11 10:00:21 2010
InstallationMedia: Ubuntu-Studio 10.10 "Maverick Meerkat" - Beta i386 (20100902.1)
More information about the Ubuntu-mono