Subject: audacious input plugin

From: mld/uade team
Date: Mon Jan 9 19:55:41 2006

To: UADE-Developer-discussion
Hi folks,

just commited an audacious media player input plugin to cvs. (audacious -&gt; http://audacious.nenolod.net/Main_Page)

since the default modplug engines chokes on some for old amiga mods I thought it could be useful ;)

have fun

Michael

---

From: shd
Date: Mon Jan 9 22:19:52 2006

To: UADE-Developer-discussion
[quote:78b66d1663="mld/uade team"]Hi folks,

have fun

Michael[/quote:78b66d1663]

Excellent! I just got mail two days ago that audacious plugin is needed. :)

---

From: mld/uade team
Date: Mon Jan 9 22:37:30 2006

:) Wasn't me...

---

From: mld/uade team
Date: Mon Jan 9 22:45:40 2006

To: UADE-Developer-discussion
err.... wasn't me bugging for the audicous plugin I want to say...

btw. Updated the web page in that respect as well...

Michael

---

From: shd
Date: Mon Jan 9 22:46:54 2006

To: UADE-Developer-discussion
[quote:26bd9ba506="mld/uade team"]:) Wasn't me...[/quote:26bd9ba506]

Nice port. How did you get the time? Btw. you may add your name to xmms/plugin.c copyright headers too =)

---

From: shd
Date: Mon Jan 9 22:48:16 2006

To: UADE-Developer-discussion
[quote:10da519840="mld/uade team"]err.... wasn't me bugging for the audicous plugin I want to say...

Michael[/quote:10da519840]

Care to update uade-www too? Man page?

---

From: Guest
Date: Mon Jan 9 22:56:10 2006

To: UADE-Developer-discussion
[quote:5b77d71ef2="shd"][quote:5b77d71ef2="mld/uade team"]err.... wasn't me bugging for the audicous plugin I want to say...

Michael[/quote:5b77d71ef2]

Care to update uade-www too? Man page?[/quote:5b77d71ef2]

regarding build requirements? I'll see to it...

basically: 
audacious + dev headers... :)

---

From: shd
Date: Mon Jan 9 23:00:09 2006

To: UADE-Developer-discussion
[quote:560f65ba9b="Anonymous"][quote:560f65ba9b="shd"][quote:560f65ba9b="mld/uade team"]err.... wasn't me bugging for the audicous plugin I want to say...

Michael[/quote:560f65ba9b]

Care to update uade-www too? Man page?[/quote:560f65ba9b]

basically: 
audacious + dev headers... :)[/quote:560f65ba9b]

We should also mention audacious as we mention others. You can remove beep media player among the support frontends because it's not supported by us or their developers.

Perhaps the list of supported frontends should be made more clear on the page. Now it's hidden inside a block of text :)

---

From: mld/uade team
Date: Mon Jan 9 23:15:27 2006

To: UADE-Developer-discussion
ok. see if it's better now :)

---

From: jraitala
Date: Tue Jan 10 05:30:48 2006

To: UADE-Developer-discussion
I think it would be better to list libao/uade123 with other frontends and state that it is a command line client.

---

From: mld/uade team
Date: Tue Jan 10 16:34:45 2006

To: UADE-Developer-discussion
[quote:e7141339c0="jraitala"]I think it would be better to list libao/uade123 with other frontends and state that it is a command line client.[/quote:e7141339c0]

good idea!

commited the changes to cvs. Removed the obsolete screenshots as well...

Heikki if you like please update/edit or whatever *g*

---

From: shd
Date: Tue Jan 10 17:01:39 2006

To: UADE-Developer-discussion
[quote:335fc7460c="mld/uade team"]
Heikki if you like please update/edit or whatever *g*[/quote:335fc7460c]

Done. Removed all old binary package links as being obsolete. Changed wording and a bit of style.

---

From: nenolod
Date: Sat Jan 14 02:20:44 2006

To: UADE-Developer-discussion
Hi! I'm glad that you ported the plugin, but there are some issues you need to resolve before the 0.2 release of Audacious...

Admittedly, I have only taken a small look at this code, so I'm unsure how much of this applies.

* Firstly, the plugin cannot write directly to the output plugin due to some seriously needed model changes. In 0.2, doing so will result in no audio being produced. You should use produce_audio() instead as it is thread safe, reentrant, and allows for a more sane I/O model.

* Secondly, be sure to convert the code over to ConfigDB! Without this change, your plugin will soon not build (under 0.2, we require all plugins to use the ConfigDB. Use of the old xmms stuff is deprecated.)

Past that, things should be dandy. If there's anything important we may be able to provide you all with a patch, but it will mainly matter on the amount of time that is available to us. 0.2 is a pretty big release, and 0.3 will cause even more changes to the model (such as removing legacy functionality that your plugin currently depends on.)

I'm sure a lot of people will be pleased to hear of this port, however.

---

From: shd
Date: Sat Jan 14 02:37:56 2006

To: UADE-Developer-discussion
[quote:b3bbfe62e1="nenolod"]
* Firstly, the plugin cannot write directly to the output plugin due to some seriously needed model changes. In 0.2, doing so will result in no audio being produced. You should use produce_audio() instead as it is thread safe, reentrant, and allows for a more sane I/O model.

[/quote:b3bbfe62e1]

Michael, you need to upgrade to latest SVN version to use produce_audio(). Message me when done.

---

From: mld/uade team
Date: Tue Jan 17 20:24:26 2006

To: UADE-Developer-discussion
I'll see if I get the svn version to compile with my b0rked autoconf/automake/libtool setup, otherwise I wait for a stable "tarball with configure" release ;)