<?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: Audio profile configuration for the masses</title>
	<atom:link href="http://abock.org/2007/01/06/audio-profile-configuration-for-the-masses/feed/" rel="self" type="application/rss+xml" />
	<link>http://abock.org/2007/01/06/audio-profile-configuration-for-the-masses/</link>
	<description></description>
	<lastBuildDate>Sun, 07 Mar 2010 08:30:50 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: hard core sex clip</title>
		<link>http://abock.org/2007/01/06/audio-profile-configuration-for-the-masses/comment-page-1/#comment-67752</link>
		<dc:creator>hard core sex clip</dc:creator>
		<pubDate>Mon, 25 Jun 2007 19:51:15 +0000</pubDate>
		<guid isPermaLink="false">http://abock.org/2007/01/06/audio-profile-configuration-for-the-masses/#comment-67752</guid>
		<description>&lt;strong&gt;hard core sex clip...&lt;/strong&gt;

hard core sex clip...</description>
		<content:encoded><![CDATA[<p><strong>hard core sex clip&#8230;</strong></p>
<p>hard core sex clip&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: old school hardcore punk</title>
		<link>http://abock.org/2007/01/06/audio-profile-configuration-for-the-masses/comment-page-1/#comment-63772</link>
		<dc:creator>old school hardcore punk</dc:creator>
		<pubDate>Tue, 05 Jun 2007 21:45:32 +0000</pubDate>
		<guid isPermaLink="false">http://abock.org/2007/01/06/audio-profile-configuration-for-the-masses/#comment-63772</guid>
		<description>&lt;strong&gt;old school hardcore punk...&lt;/strong&gt;

old school hardcore punk...</description>
		<content:encoded><![CDATA[<p><strong>old school hardcore punk&#8230;</strong></p>
<p>old school hardcore punk&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Techwriter&#8217;s den &#187; Blog Archive &#187; Exporting profiles</title>
		<link>http://abock.org/2007/01/06/audio-profile-configuration-for-the-masses/comment-page-1/#comment-32379</link>
		<dc:creator>Techwriter&#8217;s den &#187; Blog Archive &#187; Exporting profiles</dc:creator>
		<pubDate>Tue, 23 Jan 2007 00:51:21 +0000</pubDate>
		<guid isPermaLink="false">http://abock.org/2007/01/06/audio-profile-configuration-for-the-masses/#comment-32379</guid>
		<description>[...] Reading Aaron&#8217;s posting on audio profiles in Banshee, I wonder over and over again, if we could have such profiles/presets in GIMP for exporting. I rarely see people using all of available export filters all the time, besides, users are still presented with extra dialogs with exporting options. So why not have a nice UI to save most often used options as profiles and use them in Save/SaveÂ As/SaveÂ AsÂ Copy dialogs? [...]</description>
		<content:encoded><![CDATA[<p>[...] Reading Aaron&#8217;s posting on audio profiles in Banshee, I wonder over and over again, if we could have such profiles/presets in GIMP for exporting. I rarely see people using all of available export filters all the time, besides, users are still presented with extra dialogs with exporting options. So why not have a nice UI to save most often used options as profiles and use them in Save/SaveÂ As/SaveÂ AsÂ Copy dialogs? [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stefan Kost</title>
		<link>http://abock.org/2007/01/06/audio-profile-configuration-for-the-masses/comment-page-1/#comment-29743</link>
		<dc:creator>Stefan Kost</dc:creator>
		<pubDate>Wed, 10 Jan 2007 21:36:54 +0000</pubDate>
		<guid isPermaLink="false">http://abock.org/2007/01/06/audio-profile-configuration-for-the-masses/#comment-29743</guid>
		<description>@Ronald,

I was also thinking about another GParamSpecFlag, we already have &#039;Controlable&#039; which flags run-time chanable properties, likewise we could have &#039;Editable&#039; which marks properties that make sense to be set by the user initialy (and remain that way for the whole processing).</description>
		<content:encoded><![CDATA[<p>@Ronald,</p>
<p>I was also thinking about another GParamSpecFlag, we already have &#8216;Controlable&#8217; which flags run-time chanable properties, likewise we could have &#8216;Editable&#8217; which marks properties that make sense to be set by the user initialy (and remain that way for the whole processing).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ronald S. Bultje</title>
		<link>http://abock.org/2007/01/06/audio-profile-configuration-for-the-masses/comment-page-1/#comment-29708</link>
		<dc:creator>Ronald S. Bultje</dc:creator>
		<pubDate>Wed, 10 Jan 2007 17:31:46 +0000</pubDate>
		<guid isPermaLink="false">http://abock.org/2007/01/06/audio-profile-configuration-for-the-masses/#comment-29708</guid>
		<description>The current gnome-audio-profiles already does the availability check (2.17.2). A disadvantage of being framework-agnostic is that you can no longer do that, unless you either want to link to all frameworks or want to resort to ugly hacks like calling gst-inspect on the commandline.

Doesn&#039;t xml have provision for internationalization (see e.g gconf schema files, which are essentially xml)?

My idea for &quot;which properties should be exposed&quot; was to actually introduce a private GstParamSpecFlag (like readable/writable) flag for gstelements.</description>
		<content:encoded><![CDATA[<p>The current gnome-audio-profiles already does the availability check (2.17.2). A disadvantage of being framework-agnostic is that you can no longer do that, unless you either want to link to all frameworks or want to resort to ugly hacks like calling gst-inspect on the commandline.</p>
<p>Doesn&#8217;t xml have provision for internationalization (see e.g gconf schema files, which are essentially xml)?</p>
<p>My idea for &#8220;which properties should be exposed&#8221; was to actually introduce a private GstParamSpecFlag (like readable/writable) flag for gstelements.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stefan Kost</title>
		<link>http://abock.org/2007/01/06/audio-profile-configuration-for-the-masses/comment-page-1/#comment-29164</link>
		<dc:creator>Stefan Kost</dc:creator>
		<pubDate>Mon, 08 Jan 2007 12:44:29 +0000</pubDate>
		<guid isPermaLink="false">http://abock.org/2007/01/06/audio-profile-configuration-for-the-masses/#comment-29164</guid>
		<description>hi Aaron,

looks great! I am the buzztard developer and have the same issues with the gnome-audio-profiles like the jokosher guys. The things I had in my mind was:
* why are the in gconf (they aren&#039;t settings)
* which gobject properties in the pipeline should be settings
* figure out which profiles can be used (element availabillity check)

This seems to match the things you fixed. Some questions still:
* why do you include the GParamSpec limits in the xml profile (like min max value, or enum values)?
* any idea of how to get profiles ready for i18n?
* for the element availability check, it might be a good idea to show profiles with missing elements as grayed items and use the libgimmi-code approach once its established

I&#039;d like to see this replacing the current audio profiles once, as generic media encoding profiles.

Stefan / ensonic</description>
		<content:encoded><![CDATA[<p>hi Aaron,</p>
<p>looks great! I am the buzztard developer and have the same issues with the gnome-audio-profiles like the jokosher guys. The things I had in my mind was:<br />
* why are the in gconf (they aren&#8217;t settings)<br />
* which gobject properties in the pipeline should be settings<br />
* figure out which profiles can be used (element availabillity check)</p>
<p>This seems to match the things you fixed. Some questions still:<br />
* why do you include the GParamSpec limits in the xml profile (like min max value, or enum values)?<br />
* any idea of how to get profiles ready for i18n?<br />
* for the element availability check, it might be a good idea to show profiles with missing elements as grayed items and use the libgimmi-code approach once its established</p>
<p>I&#8217;d like to see this replacing the current audio profiles once, as generic media encoding profiles.</p>
<p>Stefan / ensonic</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard</title>
		<link>http://abock.org/2007/01/06/audio-profile-configuration-for-the-masses/comment-page-1/#comment-29066</link>
		<dc:creator>Richard</dc:creator>
		<pubDate>Sun, 07 Jan 2007 20:15:34 +0000</pubDate>
		<guid isPermaLink="false">http://abock.org/2007/01/06/audio-profile-configuration-for-the-masses/#comment-29066</guid>
		<description>This is totally great. :-)

I just ran into this profile dialog a couple of days ago in Sound Juicer, and was, well &quot;surprised&quot;.

Cheers
-Richard</description>
		<content:encoded><![CDATA[<p>This is totally great. <img src='http://abock.org/wp-includes/images/smilies/face-smile.png' alt=':-)' class='wp-smiley' /><br />
I just ran into this profile dialog a couple of days ago in Sound Juicer, and was, well &#8220;surprised&#8221;.</p>
<p>Cheers<br />
-Richard</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jan Schmidt</title>
		<link>http://abock.org/2007/01/06/audio-profile-configuration-for-the-masses/comment-page-1/#comment-29053</link>
		<dc:creator>Jan Schmidt</dc:creator>
		<pubDate>Sun, 07 Jan 2007 16:54:18 +0000</pubDate>
		<guid isPermaLink="false">http://abock.org/2007/01/06/audio-profile-configuration-for-the-masses/#comment-29053</guid>
		<description>Nice work Aaron - it looks awesome. It&#039;s exactly the sort of love that the audio-profiles UI has needed for a long time now.</description>
		<content:encoded><![CDATA[<p>Nice work Aaron &#8211; it looks awesome. It&#8217;s exactly the sort of love that the audio-profiles UI has needed for a long time now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fiercely</title>
		<link>http://abock.org/2007/01/06/audio-profile-configuration-for-the-masses/comment-page-1/#comment-29048</link>
		<dc:creator>fiercely</dc:creator>
		<pubDate>Sun, 07 Jan 2007 15:41:06 +0000</pubDate>
		<guid isPermaLink="false">http://abock.org/2007/01/06/audio-profile-configuration-for-the-masses/#comment-29048</guid>
		<description>This is the kind of usability love GNOME must continue to get. What needs to be done to make this standard for GNOME?</description>
		<content:encoded><![CDATA[<p>This is the kind of usability love GNOME must continue to get. What needs to be done to make this standard for GNOME?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christian Schaller</title>
		<link>http://abock.org/2007/01/06/audio-profile-configuration-for-the-masses/comment-page-1/#comment-29034</link>
		<dc:creator>Christian Schaller</dc:creator>
		<pubDate>Sun, 07 Jan 2007 13:09:29 +0000</pubDate>
		<guid isPermaLink="false">http://abock.org/2007/01/06/audio-profile-configuration-for-the-masses/#comment-29034</guid>
		<description>Great stuff Aaron! The audio profiles have long been a half done project so its nice to see some serious progress in the area. Hopefully it can evolve into  generic audio profile system that others, like Jokosher also can hook into.</description>
		<content:encoded><![CDATA[<p>Great stuff Aaron! The audio profiles have long been a half done project so its nice to see some serious progress in the area. Hopefully it can evolve into  generic audio profile system that others, like Jokosher also can hook into.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
