-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Is it possible use the Raspberry P0 component in another embedded system (that not is a Raspberry Pi)?
Unfortunately not.
In order to make development and evolution simple, Raspberry P0 uses gpiozero to access the Raspberry Pi pins. Gpiozero only supports Raspberry Pi.
If you need support for another embedded system, I suggest you take a fork of that project and make the changes.
According to the Dr. Sandro Jucá, this risk does not exist.
Yes, it's possible. In the configuration file (.ini), simply include the list of pins in the common_pins configuration. As an example, for three pins:
common_pins = [5, 1, 2]
Or for a single pin:
common_pins = [5]
I noticed that when using Raspberry P0, there is a great use of processing. Is this because of what?
Raspberry P0 uses an unofficial library to control displays of seven sections. The use of more than one display results in the need to use multiplexing. The implementation used to control the displays is deficient.
Changing the current pedalboard is too slow. Is that so? Is there no way to get this process done any faster?
Unfortunately, that's the way it is. Because of the limitations of the technologies used and the way in which audio plugin management has been implemented, it is costly to unload audio plugins from the previous pedalboard and load audio plugins from the current pedalboard.
Some strategies can be taken to facilitate the processing of audio plugins. The company MOD Devices in your Mod Duo device implemented Pedalboard presets, which allow you to swap different parameters settings for the same pedalboard. PluginsManager (Raspberry P0 is included) tries to reuse the already used plugins when occurs current pedalboard change.
A discussion on the subject can be found at https://forum.moddevices.com/t/any-news-about-the-time-gap-when-change-pedalboards/962