Triode wrote: > This looks like another thread for multiple people to have opinions > on.... Let me comment on my views on the architecture and the software I > am looking at: > > 1) Playback should be a small self contained application which is able > to be deployed on multiple devices with a minimal memory footprint. It > will be optimised for real time performance and low memory footprint. > This is what squeezelite is - its a C only implementation of a > squeezebox playback implementation which is reasonably efficient for > deployment on small footprint linux devices. At present it supports > most major codecs with the exceptions of wma and alac and is being run > by quite a few people already. Squeezelite is already at release 1.0 > and I believe most of the bugs are already resolved with this... (YMMV) > > > 2) User interface can and should be a separate application and is > probably best mainly written in a higher layer scripting or other > language. What I propose for this is jivelite which is a cut down > version of squeezeplay and support applets and scripting to extend its > capabilities. Initially my focus is to create the framework for this as > I am making some significant internal changes to the jive code for this. > I am currently using the Logitech icons as they are all part of the > development tree which has a BSD license, but I would like to replace > the icons with ones which we generate. My primary target for this will > be to get to a new skin which works on a 1080p display. > > I did look at xbmc but was concerned that for just rendering a user > interface it looked to be overkill and specially on the platform I > tested on it seemed to use high cpu load to continuously render the > display. For an audio device which would ideally not do any display > activity unless there is something to show and would allow us to disable > the display completely I took the view that we would be better to have > direct control over this. > > 3) I am assuming at least in the medium term LMS remains as the server > application. However longer term its possible to do more in applets > scripted as part of jivelite and possibly creating direct control of > squeezelite from jivelite (for instance I'm thinking of a spotify > applet) > > 4) IR control and other user interface devices need to be integrated > with jivelite as this is how it will be controlled. This will require > us to work on getting a common set of user interface options for it. > (Jivelite is sdl based so we need to provide input to sdl which should > be reasonably well supported) > > 5) Specific audio output drivers - this bit is the only bit which I > think needs to be specific to the wandboard based community squeezebox > hardware. This will require us to develop whatever is necessary to > drive the hardware John is planning. [I think John and Clive have been > talking on this] > > > Jivelite is very early days at present - I'll post more on the linux > thread when I have more for people to test... I would be interested in > anyone who has graphics art skill who can create some more icons for us > at some point.
This jivelite suppose it's also for other interfaces than hdmi ? I'm not particularly interesed in TV based UI (some are ) I would not really want to turn on a tv for controlling the player , I do have iPad and iPhone for control . Or are there suitable touch screens and other small screens that uses hdmi ? screensavers could be cool in some applications . ------------------------------------------------------------------------ Mnyb's Profile: http://forums.slimdevices.com/member.php?userid=4143 View this thread: http://forums.slimdevices.com/showthread.php?t=98179 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/discuss
