hi, in the attached photo input 1 (bass guitar) goes to output 1, but when I use a distortion in input 2 (guitar) even the sound of input 1 changes and becomes distorted… (input 2 go to output 2). it happens to me with all the pedalboards I’ve built… I need the input 1 sound to remain clean, how do I do it?
Wow… Amazingly strange 
Which firmware version is installed on your device ?
1.13.1.3122
now work… i don’t know what happened… but work. on the other hand the 2 control chain devices has disconnected. i try to switch off and on
1 Like
oh… cool, but it may be interesting for the development of the firmware to understand what happen here. If it happen again could you try to share the pedalboard ?
That I believe is simply because the plugins are quite heavy for the MOD Duo (together). The MOD Duo CPU capacity is quite limited at this point and some of the plugins that you are using may be quite heavy.
I would suggest you to start with a simple (and almost “painless”) replacement. I see that you are using a lot of instances of the TinyGain, try to replace it with the more simple Gain plugin. Hopefully, that will save you some CPU, I’m not sure if enough, thou.
what the difference by Tiny gain and simply gain??
Check (and update) this page to help you finding the less CPU consuming plugins
https://wiki.mod.audio/wiki/Plugins_CPU_Usage
2 Likes
using Gain in place of Tiny Gain and the CPU usage is decrease to 80% but i thing a big CPU usage is made by the head simulator… my problem is to have a good distorsion sound and i see that i need to use the head simulator to get a good sound… do you know other idea??
Holà,
I see these things that can improve you CPU usage :
- since you use the Duo to have 2 mono signals you don’t need to use stereo on the stereos plugins (reverbs and rakkarrack). It may cause the CPU to do more calculs for nothing.
- if you use the same way the 2 reverbs I think you can us only one of those two (the input 1 path goes through the reverb’s left channel and the output 2 through the right channel of the same plugn)
- if the Duo accepts this portal beta plugin (you have to allow beta plugins in the webUI to check this) you can send the time plugins through. It will let the CPU one cycle more to calculate the reverb and delay.
- you have parallelised the TUBE DRIVER and the Rakarakk, you can add do the same with the phaser.
If you share your pedalboard through the webUI and put the link here, I can do these optimisations for you and share a link back here.
1 Like
here my pedal board:
can you explain me this passage please?: " * if the Duo accepts this portal beta plugin (you have to allow beta plugins in the webUI to check this) you can send the time plugins through. It will let the CPU one cycle more to calculate the reverb and delay.
1 Like
Done !
With portal plugin (48% of the Dwarf’s CPU) :
And without (57% of the Dwarf’s CPU) :
After going back to you original pedalboard, the solution without portal is exactly the same CPU consuming as yours. But you have a better way to control your sends to the reverb/delay.
Yep… I can try but I think falkTX did a pretty good job here : Introducing Portal
2 Likes
thank you very much!!!
1 Like
in practice is only the UI on the WebGUI
