[Alsaplayer-devel] Update and future direction

[oliver oli]

Andy Lo A Foe wrote:
> * A lightweight stable audio playback core.
> * A pretty good API to the core.
> * A miserable user interface.
> 
> I started work on a GTK2 interface but after years of scripting and Java 
> coding I just don't find it interesting to write a GUI in C/C++ against 
> gtk2's API. So it dawned upon me, why not improve the API/CORE and leave 
> the GUI to seomeone else? I suck at it anyway. Or at least I think I can 
> do a much better job doing the UI in Python, Ruby or even (gasp!) Java...
>
> What do you think?

A GUI in Python, Ruby or C# would be fine. I don't want to use Java on 
Linux, I feel there are too much versions and it runs not very well 
(from a users perspective).

What I really would like to see is an Opensound Control interface for 
Alsaplayer as many people are using Alsaplayer for artistic use.

I don't know if anyone improved resampling. It sounded quite cheap some 
time ago. Alsaplayer could make use of the SoundTouch library (which 
also can do time-stretching).

I would vote for improvements to the core engine and ignoring the GUI. 
For me a language independent control interface would be the most 
important feature (for example OSC). Support for other file formats 
would be cool, too (wavepack, musepack, aac, speex,...)