Re: XMMS plugin maintainer - no response

Christian HJ Wiesner wrote:

> Hi folks,
>=20
> its time we start using this mailing list more often, as using webboard=
s=20
> to discuss things like this can be cumbersome IMO.
>=20
> Frank is currently looking at MPC again, and he was requesting help fro=
m=20
> us on a couple of issues :
>=20
> *1. XMMS Plugin*
>=20
> As long as foobar2000 has not been ported to Linux, its still his=20
> preferred choice for audio playback on Linux, and he is obviously=20
> planning to do development and audio testing with it. Therefore its=20
> necessary that someone who is versed enough with MPC, XMMS and Linux=20
> cares about the plugin. If Frank has to do it himself, his precious tim=
e=20
> will be spent on maintaining the plugin, instead of improving the codec=
.=20
> This cant be in our interest, so i am herewith trying to encourage you=20
> to talk to any developer you know, who fits in the above mentioned=20
> skills range.

Alright. As I told you on the #matroska channel, I'm considering=20
spending all my time for the few coming months to MPC. The CoreCodec=20
video editor project has not really started yet. And my ODJ software is=20
in stalled status right now. Matroska don't need that much work. So that=20
leaves time for an important project like MPC. But I'm not good at=20
coding a codec. I could probably understand it, but there would be a=20
long learning curve that we may not have (unless Frank wants to become a=20
teacher). So I think this 3rd-party thing is the kind of thing I could=20
probably handle easily (as soon as I've reinstalled Linux somewhere). So=20
let's count me in on the XMMS side.

> *3. SV8 alpha encoder listening test*
>=20
> Frank stated more than once that he was disappointed that nobody took=20
> the time to actively test his sample SV8 encoder that time when he=20
> published it. I will ask Frank to make a new release of it soon, and we=
=20
> should ask Case to make a fb2k encoder plugin from it so we can start=20
> testing.

I think I have a decent hardware to test a codec, even though I've never=20
done it so far (ear not trained enough, even though I can recognize bad=20
encodings). So I will work on that too.

What else is left ?

As I also said on #matroska, I think what we need to code is a kind of=20
libmpc that would be able to encode/decode packets of MPC data. The same=20
way you use lame_enc and libmad. That way anyone could work on a plugin=20
for his own system. And even better it could work in Matroska *and* in=20
some portable devices (which is something MPC would be great for) ! I=20
could also use it easily in my ODJ project... and mpcenc end mpcdec=20
would just become basic frontends of the library.


http://mpc.corecodec.org