Accéder au contenu principal

Streaming mp3 fromVLC / Icecast to Android

Here are some tips for streaming music to android mobile devices from a PC.

Platform which has been used fo test:
  • Ubuntu 11.10 oneiric + a NAS for storing music (windows can fit as well)
  • Videolan VLC 1.1.12 (providing mp3 flow)
  • icecast 2.3.2 (shoutcast radio)
  • Winamp 1.2.12 for Android mobile(music player)
  • Android-vlc-remote for Android (remote control for VLC)
Start icecast server
icecast2 -c icecast.xml
The icecast xml config file is the original one. don't modify anything at this stage. 












Setup VLC in order to stream mp3 instead ogg format














Close VLC

Prepare a playlist (ie: scarlatti.m3u)

with Banshee or whatever.

Launch VLC in command line

vlc scarlatti.m3u --sout '#standard{access=shout,mux=ogg,dst=source:hackme@192.168.0.3:8000/scarlatti}' --sout-keep --extraintf=luahttp --fullscreen --http-album-art 

 












 Check that icecast is displaying a mount point for the new radio














Check the HTTP access to VLC interface  (port8080)
















Connect Winamp Android Mobile to the Icecast server


Control VLC remotely with VLC Remote
















Drawback:  the name of current song is not displayed. It seems that something has to be developed at VLC level in order to push the song title to icecast.

Others players for Android: RealPlayer is OK, but very beta.
The shoutcast station address is not stored for next usage.

A Nokia phone E51 with Nokia Internet radio does the job. 

Other tests
Streaming directly from VLC in http mode:

vlc -vvv scarlatti.m3u --sout '#standard{access=http,mux=mpeg1,dst=192.168.0.3:8080}'

Players on Ubuntu: Banshee ok, VLC ok,
Players on Android: Not very useful because few player on Android can manage to read the output: winmap: Nok, RealPlayer Nok.

Commentaires

Enregistrer un commentaire

Posts les plus consultés de ce blog

Oracle Documents Cloud Service - Using Upload File REST API

If the Upload File sample given in ODCS documentation is used "as is", we get a http 400 error. The syntax is strict and every blank line must be empty (no space character for instance). If we cust and paste the sample, there are residual space characters which must be removed. So, use this pattern instead: -----1234567890 Content-Disposition: form-data; name="jsonInputParameters" { "parentID": " " } -----1234567890 Content-Disposition: form-data; name="primaryFile"; filename="example.txt" Content-Type: text/plain Hello World! -----1234567890-- instead the original one: -----1234567890 Content-Disposition: form-data; name="jsonInputParameters" { "parentID":"FB4CD874EF94CD2CC1B60B72T0000000000100000001" } -----1234567890 Content-Disposition: form-data; name="primaryFile"; filename="example.txt" Content-Type: text/plain -----1234567890-- Tests can be...
3 commentaires
Lire la suite

Oracle Sites Cloud Service - Adding authentication to a site

With Oracle Sites Cloud Services, access to any site is Public, by default. If you have to add authentication, there is a very simple way to achieve it: First, we assume that authentication will be against the existing Identity Domain provided with the tenant. In a dedicated page of a site, called Login for instance, we add an App component which embeds an URL to any folder of Documents Cloud Service. ie: App URL =  https://documents.XX.oraclecloud.com/documents/ embed /home/nameasc Note that the URL will be called with the EMBED keyword . Then we add the App component is a region, and  we setup a height=1 and a width=1 (almost invisible). That's all. Each time a user will navigate to this custom   Login Page, and if the user is not yet authenticated, a new page will splash on the screen, asking for credentials. Once login and pasword are provided by the user, the page disapears and return to custom Login page. Optionnaly it's possible to add a dedicate...
Enregistrer un commentaire
Lire la suite