<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: PulseAudio in openSUSE</title>
	<atom:link href="http://blogs.gnome.org/rodrigo/2008/06/05/pulseaudio-in-opensuse/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.gnome.org/rodrigo/2008/06/05/pulseaudio-in-opensuse/</link>
	<description>From lost to the river</description>
	<lastBuildDate>Sun, 08 Jan 2012 15:47:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Livio</title>
		<link>http://blogs.gnome.org/rodrigo/2008/06/05/pulseaudio-in-opensuse/comment-page-1/#comment-679</link>
		<dc:creator>Livio</dc:creator>
		<pubDate>Thu, 19 Jun 2008 13:31:16 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/rodrigo/2008/06/05/pulseaudio-in-opensuse/#comment-679</guid>
		<description>Wow. What a emotions...

PA replaced ESD - takes less resources and support per-app volume setting. It is crap? I don&#039;t think so...</description>
		<content:encoded><![CDATA[<p>Wow. What a emotions&#8230;</p>
<p>PA replaced ESD &#8211; takes less resources and support per-app volume setting. It is crap? I don&#8217;t think so&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Laney</title>
		<link>http://blogs.gnome.org/rodrigo/2008/06/05/pulseaudio-in-opensuse/comment-page-1/#comment-678</link>
		<dc:creator>Laney</dc:creator>
		<pubDate>Thu, 19 Jun 2008 11:17:23 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/rodrigo/2008/06/05/pulseaudio-in-opensuse/#comment-678</guid>
		<description>PulseAudio is a crap. First thing I&#039;ve done to delete this buggy rubbish from the almost fine oS11. I hope the pulseAudio will disappear soon from Linux and never come back, I don&#039;t need one more bad designed &quot;wannabe&quot; sound server which is not compatible to any audio app.</description>
		<content:encoded><![CDATA[<p>PulseAudio is a crap. First thing I&#8217;ve done to delete this buggy rubbish from the almost fine oS11. I hope the pulseAudio will disappear soon from Linux and never come back, I don&#8217;t need one more bad designed &#8220;wannabe&#8221; sound server which is not compatible to any audio app.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Srini</title>
		<link>http://blogs.gnome.org/rodrigo/2008/06/05/pulseaudio-in-opensuse/comment-page-1/#comment-661</link>
		<dc:creator>Srini</dc:creator>
		<pubDate>Mon, 09 Jun 2008 04:07:17 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/rodrigo/2008/06/05/pulseaudio-in-opensuse/#comment-661</guid>
		<description>Awesome. But any links/info on how to get pulseaudio working with Bluetooth headset? Im on RC1 and Im not able to do much.</description>
		<content:encoded><![CDATA[<p>Awesome. But any links/info on how to get pulseaudio working with Bluetooth headset? Im on RC1 and Im not able to do much.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jones Lee</title>
		<link>http://blogs.gnome.org/rodrigo/2008/06/05/pulseaudio-in-opensuse/comment-page-1/#comment-660</link>
		<dc:creator>Jones Lee</dc:creator>
		<pubDate>Sat, 07 Jun 2008 10:56:29 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/rodrigo/2008/06/05/pulseaudio-in-opensuse/#comment-660</guid>
		<description>I do not believe that using pavmeter is a good decision because it looks too complicated compared for a normal user, they use some jargon like sink, server, etc. I think SuSE instead should start a project to develop a new volume meter for gnome-media, I just hate to wait till 2.26 to see this feature.</description>
		<content:encoded><![CDATA[<p>I do not believe that using pavmeter is a good decision because it looks too complicated compared for a normal user, they use some jargon like sink, server, etc. I think SuSE instead should start a project to develop a new volume meter for gnome-media, I just hate to wait till 2.26 to see this feature.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Livio</title>
		<link>http://blogs.gnome.org/rodrigo/2008/06/05/pulseaudio-in-opensuse/comment-page-1/#comment-659</link>
		<dc:creator>Livio</dc:creator>
		<pubDate>Thu, 05 Jun 2008 18:38:21 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/rodrigo/2008/06/05/pulseaudio-in-opensuse/#comment-659</guid>
		<description>You need to register yourself in there to report.

Please, report in there because Lennart Poettering doesn&#039;t use openSUSE neither Novell&#039;s bugzilla and will notice no bug report.

Upstream bugs should land upstream, unless it&#039;s not about packaging ;) .</description>
		<content:encoded><![CDATA[<p>You need to register yourself in there to report.</p>
<p>Please, report in there because Lennart Poettering doesn&#8217;t use openSUSE neither Novell&#8217;s bugzilla and will notice no bug report.</p>
<p>Upstream bugs should land upstream, unless it&#8217;s not about packaging <img src='http://blogs.gnome.org/rodrigo/wp-content/mu-plugins/tango-smilies/tango/face-wink.png' alt=';)' class='wp-smiley' />  .</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: garrett</title>
		<link>http://blogs.gnome.org/rodrigo/2008/06/05/pulseaudio-in-opensuse/comment-page-1/#comment-658</link>
		<dc:creator>garrett</dc:creator>
		<pubDate>Thu, 05 Jun 2008 18:28:37 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/rodrigo/2008/06/05/pulseaudio-in-opensuse/#comment-658</guid>
		<description>I had to search around on the pulseaudio website for where to report a bug for upstream, and found the link to &quot;add a new ticket&quot; at this link:
http://www.pulseaudio.org/newticket

Then, it immediately gives me this error:

Forbidden
TICKET_CREATE privileges are required to perform this operation

I&#039;ll just report it in the Novell bugzilla against openSUSE for now, I guess.</description>
		<content:encoded><![CDATA[<p>I had to search around on the pulseaudio website for where to report a bug for upstream, and found the link to &#8220;add a new ticket&#8221; at this link:<br />
<a href="http://www.pulseaudio.org/newticket" rel="nofollow">http://www.pulseaudio.org/newticket</a></p>
<p>Then, it immediately gives me this error:</p>
<p>Forbidden<br />
TICKET_CREATE privileges are required to perform this operation</p>
<p>I&#8217;ll just report it in the Novell bugzilla against openSUSE for now, I guess.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Livio</title>
		<link>http://blogs.gnome.org/rodrigo/2008/06/05/pulseaudio-in-opensuse/comment-page-1/#comment-657</link>
		<dc:creator>Livio</dc:creator>
		<pubDate>Thu, 05 Jun 2008 18:02:01 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/rodrigo/2008/06/05/pulseaudio-in-opensuse/#comment-657</guid>
		<description>Garett, add your thoughts as bugs in PA bug tracker, so developer can see them.

Personally, I&#039;m curious why making good things with KDE is always abandoned...

We had many great things implemented in GNOME, but even they&#039;re desktop agnostic, they are not implemented/used in/by KDE...

I use mostly KDE, but that&#039;s kind of discrimination...</description>
		<content:encoded><![CDATA[<p>Garett, add your thoughts as bugs in PA bug tracker, so developer can see them.</p>
<p>Personally, I&#8217;m curious why making good things with KDE is always abandoned&#8230;</p>
<p>We had many great things implemented in GNOME, but even they&#8217;re desktop agnostic, they are not implemented/used in/by KDE&#8230;</p>
<p>I use mostly KDE, but that&#8217;s kind of discrimination&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: garrett</title>
		<link>http://blogs.gnome.org/rodrigo/2008/06/05/pulseaudio-in-opensuse/comment-page-1/#comment-656</link>
		<dc:creator>garrett</dc:creator>
		<pubDate>Thu, 05 Jun 2008 12:28:04 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/rodrigo/2008/06/05/pulseaudio-in-opensuse/#comment-656</guid>
		<description>Overall, good work.  I like to see things progressing forward technically.

However, just at a quick glance, it looks like there are a number of UI/UX issues in each dialog.

Here&#039;s a quick list:

* Why is each dialog branded as PulseAudio, in a huge, useless header?

* &quot;playback stream&quot; and &quot;output device&quot; are pretty jargony, plus, I don&#039;t understand why a person would want to right-click and move them around (referring to the tip).

* Most people want to adjust both the right and left channels at the same time.  I don&#039;t see an obvious way to lock them together (to adjust both at once).  Perhaps a better UI metaphor would be to have one volume slider for both the left and the right and then a little widget (probably another slider) to adjust the left/right balance.

* The mute icon should probably be a mute button, with the word &quot;mute&quot;, perhaps.

* I don&#039;t understand the speaker layout in the speakers tab.  Is that supposed to be a dropdown?  Why is it so wide?  Shouldn&#039;t there be a label to the left of it too?  Can you do any auto-detection, so the list only presents what is available as valid options (and probably greying out the rest)?  What happens if I set up 7.1 when I only have computer speakers attached?

* Why are playback, output devices, and input devices separate?  Sure, they&#039;re different technically, but I think the user wants to be able to control the overall volume of computer&#039;s sound, the input volume, and application volume in once place.  Can the UI be simplified to optimize for the 90% case?  I think the fine-grained audio output UI (front left and right, back left and right, etc. can be either changed into volume + balance + fade, like a car radio, or have one overall volume with either details/advanced settings in a dialog or disclosure widget).  I&#039;d opt for a UI similar to what people already know, such as the car or home stereo setup (the volume + balance + fade approach).

I realize that your blog is not the appropriate place for official bugs on this sort of thing... and that bugzilla is, but since you&#039;re talking about it, it is under development, and I&#039;m referring to your screenshots, I decided to post here quickly.

Hopefully my feedback is useful.

Also, I should upgrade my laptop running an openSUSE 11 beta to the latest to see how it all works first-hand.  (:</description>
		<content:encoded><![CDATA[<p>Overall, good work.  I like to see things progressing forward technically.</p>
<p>However, just at a quick glance, it looks like there are a number of UI/UX issues in each dialog.</p>
<p>Here&#8217;s a quick list:</p>
<p>* Why is each dialog branded as PulseAudio, in a huge, useless header?</p>
<p>* &#8220;playback stream&#8221; and &#8220;output device&#8221; are pretty jargony, plus, I don&#8217;t understand why a person would want to right-click and move them around (referring to the tip).</p>
<p>* Most people want to adjust both the right and left channels at the same time.  I don&#8217;t see an obvious way to lock them together (to adjust both at once).  Perhaps a better UI metaphor would be to have one volume slider for both the left and the right and then a little widget (probably another slider) to adjust the left/right balance.</p>
<p>* The mute icon should probably be a mute button, with the word &#8220;mute&#8221;, perhaps.</p>
<p>* I don&#8217;t understand the speaker layout in the speakers tab.  Is that supposed to be a dropdown?  Why is it so wide?  Shouldn&#8217;t there be a label to the left of it too?  Can you do any auto-detection, so the list only presents what is available as valid options (and probably greying out the rest)?  What happens if I set up 7.1 when I only have computer speakers attached?</p>
<p>* Why are playback, output devices, and input devices separate?  Sure, they&#8217;re different technically, but I think the user wants to be able to control the overall volume of computer&#8217;s sound, the input volume, and application volume in once place.  Can the UI be simplified to optimize for the 90% case?  I think the fine-grained audio output UI (front left and right, back left and right, etc. can be either changed into volume + balance + fade, like a car radio, or have one overall volume with either details/advanced settings in a dialog or disclosure widget).  I&#8217;d opt for a UI similar to what people already know, such as the car or home stereo setup (the volume + balance + fade approach).</p>
<p>I realize that your blog is not the appropriate place for official bugs on this sort of thing&#8230; and that bugzilla is, but since you&#8217;re talking about it, it is under development, and I&#8217;m referring to your screenshots, I decided to post here quickly.</p>
<p>Hopefully my feedback is useful.</p>
<p>Also, I should upgrade my laptop running an openSUSE 11 beta to the latest to see how it all works first-hand.  (:</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: iain</title>
		<link>http://blogs.gnome.org/rodrigo/2008/06/05/pulseaudio-in-opensuse/comment-page-1/#comment-655</link>
		<dc:creator>iain</dc:creator>
		<pubDate>Thu, 05 Jun 2008 11:27:07 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/rodrigo/2008/06/05/pulseaudio-in-opensuse/#comment-655</guid>
		<description>Looks really good :)
Would it be possible to have a nicer way to pick speaker layout, rather than just a list of layouts? Some sort of images maybe?</description>
		<content:encoded><![CDATA[<p>Looks really good <img src='http://blogs.gnome.org/rodrigo/wp-content/mu-plugins/tango-smilies/tango/face-smile.png' alt=':)' class='wp-smiley' /><br />
Would it be possible to have a nicer way to pick speaker layout, rather than just a list of layouts? Some sort of images maybe?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- This Quick Cache file was built for (  blogs.gnome.org/rodrigo/2008/06/05/pulseaudio-in-opensuse/feed/ ) in 1.28481 seconds, on Feb 10th, 2012 at 11:52 pm UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on Feb 11th, 2012 at 12:52 am UTC -->
