Webradio player

You can also run the script from Zynthian directly. Install the files into your Zynthian and SSH to the puredata directory where you installed iNetRadio an run the script from there.

In my case, it is as follows:

# cd /zynthian/zynthian-my-data/presets/puredata/generative/iNetRadio/
# ./setup.py
3 Likes

I followed your first suggestion in this way:

after editing the ‘radiostations.txt’ file

  1. in Windows open Terminal (Admin)
  2. type python to install Python
  3. change folder till you arrive in the folder where there is setup.py
  4. type python setup.py to generate the main.pd and the zynconfig.yml files
  5. copy the iNetRadio folder in /home/pi/zynthian-my-data/presets/puredata/generative
  6. enjoy

Hope it helps the dummies like me.

A question @ lexonic: the max number of stations is 22? is it possible to extend rhis limit?

2 Likes

@piattica: the number of stations can be easily exteded:

  1. rename “main.pd.template” to “main.pd.template.pd” and open it with Pure Data.
  2. add more stations and adjust the divisor of ctlin114: (127 / (number_of_stations - 1))
  3. rename “main.pd.template.pd” back to “main.pd.template”
  4. open “zynconfig.yml.template” with a text editor and add more “labels” placeholders under “Stations:”
  5. open “setup.py” with a text editor and adjust variable ‘max_stations = 22’

REMARK: Don’t forget to increment the numbers of the placeholders “STREAM#” and “NAME#” :wink:

2 Likes

too difficult for me

An update to allow customizing the Webradio. Now up to 32 radio-stations can be deployed.

The following config options can be set by setup.py command line arguments:

  • define number of stations to be deployed (default = 32)
  • define radio-station to load on startup
  • speed control by the Zynthian knob can be disabled (removes knob control)

The updated file:
iNetRadio.zip (124.9 KB)

Edit: File re-uploaded. Some timing issues solved, and active play/stop state is now persistent when changing stations.

this is the help-screen for setup.py:

usage: setup.py [-h] [-n N] [-d N] [-a] [-s] [-p] [-v] [stationsfile]

Deploy Radiostations for Zynthian's iNetRadio PD-patch.

positional arguments:
  stationsfile          text-file containing the station names and stream
                        URL's to be deployed. (default=radiostations.txt)

optional arguments:
  -h, --help            show this help message and exit
  -n N, --stations N    number of station slots to deploy
  -d N, --defaultstation N
                        station-number to load on startup
  -a, --altprefix       alternative station prefix (default="[NUM]",
                        alternative="NUM:")
  -s, --speed           enable speed control
  -p, --preview         stations preview only. Does not write out any files
  -v, --verbose         print internals
2 Likes

I have added my internet radio player to chain manager branch so it should be available in the next release. I will look at what has been done here to see what can be integrated, particularly methods to configure stations.

7 Likes

Seems that multiple chains (with different radio stations) can be added, but only last choosen station plays in reality (oram 20240928).

Yeahhh! You are fantastic testers!! :raised_hands:
Always find the issue in the extreme usage!! I love it!!

It seems current radio implementation should be one of the “single chain” processors.
Of course, some of you would like to have several ones running at once, and i understand the motivations, so try to convince the radio engine developers to improve the current implementation :grin:

Cheers!

2 Likes

I just building my (third) zynthian box and one of them plays local Retro FM station in the background. I thought of changing the station without much hassle… :grinning:

1 Like

It should be possible to change station with MIDI program change. This may require savings different ZS3. I think there is an option to direct PC at presets directly but it may be global so not necessarily desirable.

Add a bug report to the issue tracker for the replay problem and I’m sure the “radio engine developer” will take a look. :blush:

3 Likes

Brilliant! Thanks for the Zynthian Webradio and also the pretty good default station list.
I love this Zynthian project :heart:

4 Likes

some more stations:

1 Like

I add in /zynthian/zynthian-my-data/presets/inet_radio my presets.json and now I got my preset but I loose the default presets.

How can I have both?

I have been working on this a little bit that won’t be improved soon. There is a feature request to better manage presets. In Vangelis there is a change that saves the default config if there is no existing user config. That could then be manually edited.

Where can I find the “factory” presets file?

Sorry, I was away from home for a few days without access to zynthian development. I may have mis-remembered the state of development. Looking at the source I see the code to write the default presets to file is commented out so not currently implemented. I also can’t find a feature request I thought I had added to manipulate the presets for internet radio engine. Sorry for the confusion. Please add a feature request so that we can identify some good procedure for manipulating presets.

[Edit] But here is a json with the default stations:

presets.json (18.5 KB)

3 Likes

Webradio player has stopped working on the recent Oram Staging and Vangelis. Neither does it make sound, nor does it show the Vu meters nor any web traffic.
Also playlists do not play any more.

I’ve tried to track it down and I can say inet_radio worked in 2025-06-17-zynthianos-oram-2506-stable.img.xz and Vangelis until recently (some weeks maybe, not used). It now does not work any more. Not when trying to rollback to Oram Staging, not in oram-2511.3.
Maybe some internal player binary had been updated and a true rollback is not there and updated elements of system or ui are kept despite rollback.

Hi @fussl, can you log a bug for this if you haven’t already?

Regards

Bernard

1 Like

Haha, yes sure. Issue #1535 filed. :grin:

Had a 404 the times before, now it worked again. Looks like now it is mandatory to first login to github and then report issue. login while reporting issue does not work any more. Found that out now by conincidence.

1 Like