Hi. I just got a spare RPi3+ to test MODEP and proceeded to flash the latest image on a SD. Everything is ABSOLUTELY vanilla. Just the RPi. No addituonal soundcard or whatever. I tried to power up and login with SSH. No problem. I tried to connect to http://172.24.1.1 with various browsers and d…

Hello, yes, you have to configure the output audio card to use - the image is preconfigured for use with Pisound. See https://blokas.io/modep/docs/Sound-Card-Setup/ If you plan to use the analog output of Raspberry Pi, use hw:0, 44100 for sampling rate and you’ll have to increase the buffer size to…

Thanks. Of course I plan to get an external sound card after my first trials to get accustomed to the system. I suspected I had to configure something in regards to audio, but I was surprised that the interface didn’t show up at all.

I tried changing the configuration file as suggested. The reboot semed successful, and jack and all audio stuff seems loaded correctly. I can see the MODEP wifi endpoint after boot and I can login via SSH. Still I’m unable to connect to 172.24.1.1

What is the output of sudo systemctl status mod-ui? Did you connect to the MODEP WiFi before connecting? You may run ifconfig and try using other IPs listed for http:// address (especially ones that start with 192. for example)

Output is code=exited, status=1/failure I guess there’s something wrong, maybe in the config. Is there a log I can check?

The essential services are ‘jack’, ‘mod-host’ and ‘mod-ui’. If one of them is not running, the web interface won’t work. See the following link for commands to query their status and access their logs: https://blokas.io/modep/docs/Troubleshooting/ Hit the ‘end’ key on your keyboard to go to the ver…

Thank you for you help. I double checked my changes to the service and remembered that I did not change the -p parameter to 512 for the jackd command. I thought the change was needed only to avoid xruns, but it seems it prevents the daemon to start altogether. After setting it to -p 512 everything…

There will be an update to MODEP which will make this easier. :slight_smile:

Since the MODEP update is announced quite long time ago, may I ask you if there’s a fast and easy way to update the mod-ui of the actual 2018 MODEP to the newest version from GitHub ? I’m interested in the advanced Midi functions. Thank you.

No, there’s no easy way to do that, if there was, the update wouldn’t be taking this long. :wink: Anyway, some very good progress was made on the update, stay tuned for release, we want to make sure everything works smoothly out of the box. Btw, which advanced MIDI functions do you have in mind?

Test with newly installed MODEP

Patchbox OS MODEP

Giedrius March 17, 2020, 10:51am 16

Hey, the updated MODEP is available via Patchbox OS img: [Beta] Patchbox OS image 2020-03-14 (and MODEP) - it now has the MIDI settings too.

What programs on Patchbox OS are softsynths?

Topic		Replies	Views
[SOLVED] Connecting to Server Issue MODEP	4	1784	November 2, 2018
GUI setup for MODEP? MODEP	5	1484	March 29, 2020
Can I install MODEP without Patchbox? MODEP	35	1912	October 1, 2023
MODEP with Berryboot MODEP	2	676	May 4, 2019
Trouble getting started with modep [SOLVED] MODEP	5	1738	April 2, 2019
MODEP on raspi5 MODEP	15	1287	January 3, 2025
[Release] MODEP 2018-09-11 MODEP	25	4934	March 17, 2020
MODEP- how to access via browser on RPI	4	32	June 9, 2026
MODEP not booting, MODEP-MOD-UI disabled Support	12	180	September 2, 2024
What am I missing? MODEP	4	579	January 14, 2021

Test with newly installed MODEP

Related topics