I use Kaspersky which usually is pretty transparent about what it does and haven’t seen any warnings… Anyway, I’ll try to disable it and reinstalling MOD desktop… Thanks for the heads up!
Just checked kaspersky’s register and sure enough you were right! Those files were flagged as trojan and deleted even though kaspersky didn’t show any notifications about it. Thanks a lot!
3 Likes
This is pretty awesome, my only problem is that I’m on an ARM laptop running linux. I see that the source is available on github but there are no build instructions for it. Is there a chance that it can be added?
1 Like
It seems that it no longer works on Linux since Pipewire was updated to 1.2.0.
Does anyone know if the Mod plugin version for DAW’s is under construction yet?
And is there an estimated time when it would be ready?
Updated to ubuntu 24.04.1 from 22.04 and CPU usage has increased a lot in pipe/wire and direct to interface (mod jack) configuration. Not sure why it’s happening but I have some xruns now.
Found the problem, CPU Governor
3 Likes
Is Mod Desktop supposed to support integrate [dot] moddevices [dot] com?
If not, is this on the roadmap?
it does not support it yet, but it is in the plans yet.
though first it needs to support integration with the plugin store, and that first needs having desktop builds online.
so realistically not happening this year, but hopefully we see advances for that in the next
1 Like
The Desktop version is running nicely on my Macbook Pro. CPU load is reasonable, lots of fun incorporating it into my guitar rig.
I have some issues using Midi though. CCs for controlling certain plugins work like charm. But I cannot figure out how to do Pedalboard Changes.
According to the wiki, it should be able to do so using PC commands. I tried everything with different settings in the Midi Setup, but I cannot get Pedalboard or Snapshots to change. Should this work on version 0.0.12?
It’s also kind of lost because the Logging doesn’t show anything suspicious, and also I cannot find any plugin that would support monitoring incoming MIDI messages.
Help would me much appreciated here.
I checked again, all I see in the logging are these entries whenever I send CC commands:
DEBUG: effects_output_data_ready() UI is ready to receive more stuff (code 0)
DEBUG: RunPostPonedEvents() START
DEBUG: RunPostPonedEvents() Queue is empty
DEBUG: PostPonedEventsThread() looping (code 1)
PROTOCOL: response 'resp 0'
DEBUG: RunPostPonedEvents() START
DEBUG: RunPostPonedEvents() Before the queue iteration
DEBUG: RunPostPonedEvents() Sending 'param_set 0 :bypass 1.000000'
DEBUG: RunPostPonedEvents() After the queue iteration
DEBUG: RunPostPonedEvents() Sending 'data_finish'
DEBUG: RunPostPonedEvents() END
DEBUG: PostPonedEventsThread() looping (code 1)
Whats odd is that I cannot see such entries when I try to send PC commands - regardless of the channel I am using. I tried with another software and confirm that PC commands are properly sent (e.g. C0 00, where I would assume that the first pedalboard is being loaded). “MIDI Program Channel for pedalboard” is set to 1.