Hi guys, we have built a new version of MODEP, at the moment we consider it a beta version, so please test it and let us know how well it works for you, if all goes well, we’ll promote this build to release version.
I installed it but had some problems because I could not find my power supply and the only one I had was underpowered. Just got a new one and will be testing this weekend, I will leave some comments here as soon as I have done so.
Just noticed that there is a conflict between the pisound-hotspot service and the dnsmasq service because the hotspot starts a separate dnsmasq. It causes the dnsmasq service to fail without further problems, but to be safe, it would be wise to disable the dnsmasq service in the image. I did it manually on my pi and it works fine. It also help that systemctl status will not show a degraded state.
I found an interesting bug that I am able to reproduce 100% of the time, but I am not sure how to debug further. Here are the steps to reproduce:
Create a new pedalboard
Disconnect left and right channels
In the Simulator category, add a CAPS Cabinet IV
Connect the Cabinet IV output to both outputs
Connect the Inputs to the Cabinet IV input
Validate that you get sound
From the simulator category, add a CAPS AmpVTS
Connect the output of the AmpVTS to the input of the Cabinet IV
Sound stops
Delete the AmpVTS
Still no sound, turning the Cabinet off makes the sound work, but the plugin does not work anymore. The only way I found for the plugin to work again is to delete it and put it back again.
I am not sure if this behaviour occured on the older version of the image, but I never noticed it myself.
The culprit seems to be the AmpVTS, if I try other effects instead of the Cabinet IV, I get the same issue. The AmpVTS alone also does not make any sound.
Caps plugins don’t work for me too.
First : - They can’t work upper than 48kHz (written in the caps internet site).
and : - They compile on debian but some of them don’t work.
also : - there is a problem with the plug in itself and we (under librazik team / trebmuh / sub26nico / jp Cima) have a solution and the creator is informed of the patch to apply.
The CAPS Cabinet IV works for me however, it just stops working as soon as I connect it to CAPS AmpVTS and needs to be reset.
It is not only the CAPS Cabinet IV that stops working, all other plugins I have tested from other sources also stop working once connected to CAPS AmpVTS.
Do you have a link to the patch? Maybe I can test it on my side.
Using this patch broke Cabinet IV on my side. I get the following error:
mod-host: /usr/include/boost/math/special_functions/detail/bessel_i0.hpp:105: T boost::math::detail::bessel_i0(T) [with T = long double]: Assertion `x >= 0’ failed.
Hello, I’m the patch author for the fix of caps plugins.
Please take the version from the PR 14, and not another outdated version which I have created in haste.
As patch file: https://github.com/moddevices/caps-lv2/pull/14.diff
I’ve sent this to Tim Goetze, he has answered me he will either integrate it, or get rid altogether of the faulty Kaiser window code in coming releases.
Hi, there’s no automatic script to do the update. The OS image generation scripts are here: https://github.com/BlokasLabs/modep/tree/modep/ - you may try going through stages 3 - 5 and figure out what’s necessary to manually update the image, but I would recommend you to better just flash the new image instead.
