LiquoricePlayer is released!
Thursday, 26. June 2008, 20:57:41
I thought i should present a hobby project that has just been released in version 1.0 beta!
It is a music player/jukebox, controlled through a web interface directly from within your web browser. It integrates in the Opera web browser using both widgets and panel. So it's easy to control it without ever leaving the browser (or any other maximized application). Just keep the widget on-top, or the panel open
It is small, fast, and handles huge media libraries.
It's called LiquoricePlayer! (Why do i always end up using the "temporary" working name which is always edible stuff for my projects?
)
This project has kept me busy when i've had time over for the last 2 years. Now that i've got it out, i will try to blog a little more frequently than once per year
You can read more about it and download it here.
It is a music player/jukebox, controlled through a web interface directly from within your web browser. It integrates in the Opera web browser using both widgets and panel. So it's easy to control it without ever leaving the browser (or any other maximized application). Just keep the widget on-top, or the panel open
It is small, fast, and handles huge media libraries.It's called LiquoricePlayer! (Why do i always end up using the "temporary" working name which is always edible stuff for my projects?
)This project has kept me busy when i've had time over for the last 2 years. Now that i've got it out, i will try to blog a little more frequently than once per year
You can read more about it and download it here.
WIDGETIZE
kirsten # 26. June 2008, 22:10
Fatimah # 26. June 2008, 23:46
Rijk # 30. June 2009, 00:10
Just tried it for the first time, and it looks quite nice. Unfortunately, it doesn't recognize all the tags that I've painstakingly added to my MP3, Ogg and Flac files.
Emil Segerås # 30. June 2009, 18:53
I don't get it to work though. And it only needs intranet access. If i understand the blog post correctly, the network attribute is only needed if it should have public access.
I'll see if the documentation update mentions something else.
I've noticed before that 127.0.0.1 is blocked for some reason. That's why the player has a ugly workaround (changing the widget that is served to have the local machines ip as a default instead of 127.0.0.1).