This is one area that can be improved. And i have made a start.

My brother doesn't know a or understand the difference between a text file and word document, and is one of those annoying people that would forward a load of pictures to u within the latter.

So, He certainly has no clue how to change from the USB headset to the optical out on the soundcard for listening to music either through the hifi or the headphones when a QLineEdit is presented in the setup dialog, assuming he gets that far.

At first i thought the speaker arrangement box might be the exact thing i was looking for, but it seems to have no effect .. I don't know what this is intended for.

So....

I propose something like the following. Only i don't know enough about the various interfaces to complete this. But i have made a start.

[img]http://www.ds.homedns.org/files/xine-engine.jpg[/img]

The source for which can be found here :

http://www.ds.homedns.org/files/xine-engine.tar.bz2

First i dropped a tab widget in to make some more space by moving all the WW related stuff into a separate tab, Then i went about adding some combo boxes.

I borrowed some code from the xmms alsa input plugin and hacked it some to make a list of devices presented by the alsa api. The name/description is displayed in th QComboBox and the hardware name is stored in a list, the index of the combobox then identifies the hardware name which is saved. On load device name is looked for in the list and if found the corresponding device description set to the active one.

The issue here is i have no idea about all these surround device names etc, or where they come from. so maybe i should provide a line edit also for more advanced users? (it doesn't look as if text can be enteredinto the combox as can be done with some widget sets equivalent).

Anyway. ideas/help/criticism or further input welcomed.

Thanks

Dan

Very interesting. However, I understand that you are querying ALSA directly. FreeBSD and OSX don't have that, and not even all Linux boxen. So it requires conditional compilation and fallback code?

Agreed.

I dont kno anythig about audio system on FreeBSD and Mac however.

Something to research..

I have found that alsa has asound.rc file which holds a list of various device names assigned with plugins. I dont yet know if the api provides a list of these or whether i need to parse the file.

Jack support would be very nice.. but thats something xine does not yet have