For me, the Pi MusicBox is mainly an internetradio tuner. So I was wondering… Things like categories etc. in the Streams section, (and saving to streamuris.js from the browser), will they ever be? If so, is there a roadmap when such might happen?
The plan is to remove streamuris.js entirely and use Mopidy’s m3u playlist functionality to provide this. This will then allow you to save streams directly from the browser and have them available on any client. I was thinking of just having one nominated m3u playlist which will then appear under the ‘Streams’ page.
I like your idea of categories but I’m not sure if this approach would easily extend to provide categories. Perhaps if this nominated playlist became a user configurable list of playlists then we could achieve this; the added functionality would also help to make the ‘Streams’ idea worth keeping as otherwise it’s nothing more than a slightly special playlist.
Thanks for the bonus pic - that is a very smart setup.
What I’m looking for is something like I have in TuneIn right now. Over there I have categories/groups called ‘News’, ‘Dance’, ‘Classics’ and ‘General’. This just to sort the streams.
In streamuris.js all those streams are in the same list. A long list. Feels a bit cluttered. I need for it to be organized. I like organized.
I like what you say here: ‘The plan is to remove streamuris.js entirely and use Mopidy’s m3u playlist functionality to provide this. … Perhaps if this nominated playlist became a user configurable list of playlists then we could achieve this.’
One other option might be to have the TuneIn categories/groups from ones own TuneIn account display directly in Pi MusicBox. But I have no idea if there is a TuneIn API that allows for such a thing. (Or, if so, how to build such.)
About this removing streamuris.js in favor of Mopidy’s m3u playlist… Apologies for seeming to be impatient… But are we talking weeks, months, years, or, ‘don’t know’? Just so I know
(And something else… Do you maybe have any idea on why my link to the photograph insists on using httpS, instead of the regular http that I set?)
I have a mostly working version at https://github.com/kingosticks/mopidy-musicbox-webclient/tree/streamuris-v2 but I’ve been busy with other things lately and not fixed the remaining bugs (wow, that was 3 months ago…!). There will be a release which includes that soon (weeks) since it’ll be going into musicbox v1.0.
New/different approach to the same “problem”…
I still want to divide/split up/separate the different streams I have in my streamuris.js. Now I know that it won’t be long before the new version of Pi MusicBox arrives, where streamuris.js will become obsolete, but for now, streamuris.js is still very much alive in my very smoothly running 24/7 setup
This is a coding question…
Is it possible to enter data in between two streams in streamuris.js, so it would look like a header of some sorts? Something like this:
[PHP code for a group name for stations below this line];
streamUris.push(['Slam!', 'tunein:station:s67814']);
streamUris.push(['Slam! The Boom Room', 'tunein:station:s253880']);
streamUris.push(['538 Dance Department', 'tunein:station:s75171']);
[PHP code for a group name for stations below this line];
streamUris.push(['BBC Radio 1', 'tunein:station:s24939']);
It’s a javascript structure that’s simply read in and iterated over. Every item is assumed to be a stream so you put in dummy items, maybe like: streamUris.push(['My Group 1', 'null']);
These dummy items will still look just like regular streams but if you click them they show an error rather than play.