Amazing. Iâve also wanted for a long time the ability to drop a plugin on a cable and automatically have it inserted in the circuit with the cable split and connected to some default pluginâs input/output ports.
Another release is here!
Introduces a few âfactory pedalboardsâ, based on Dwarf ones. For now it is basically the âGuitar Synthâ collection and the âuseful tipsâ one. But this paves the way to have a collection of pedalboards pre-installed with the desktop app, we will add more later on.
Also corrected the case of JACK + PipeWire on some systems, hopefully that works better now.
Enjoy!
PS: Also started generating a âdevice unique idâ thing, to be used later on for the whole plugin store and commercial plugins. But will take a whileâŚ
Eehhm?.. where are this pedalboard?? Nothing is installed with this version⌠my user doc folder is correctly namef MOD Desktop, soâŚ
I installed v0.0.8 for Mac and am able to load the factory pedalboards from the Pedalboards Library.
Sorry, are you speaking about the pedalboards library on internet?
I was thinking that this Guitar Synth pedalboards were inserted in this software release, falkTX speak about factory pedalboards
Well probably Iâm wrong!
(as a side note, opening the synth boards with the default OS mic input makes for a nice noise / ambient soundscape )
Iâm on windows (11)!! Thereâs no factory pedalboards, only the ones I have created (user pedalboards)âŚ
Maybe itâs my faultâŚ
I am trying to have the fun too but so far no luck
I have a Mac Mini Late 2012 running Catalina. Python 3.12.2
This is what I get in the âmod-uiâ log when I start the Mod Desktop 0.0.8:
Traceback (most recent call last):
File âlib/startup.pyâ, line 113, in run
File âlib/Console.pyâ, line 15, in run
File âlib/mod-ui-setup.pyâ, line 91, in
File â/Applications/MOD Desktop.app/Contents/MacOS/mod/webserver.pyâ, line 2500, in run
prepare()
File â/Applications/MOD Desktop.app/Contents/MacOS/mod/webserver.pyâ, line 2471, in prepare
application.listen(DEVICE_WEBSERVER_PORT, address=(âlocalhostâ if DESKTOP else â0.0.0.0â))
File âlib/tornado/web.pyâ, line 1825, in listen
File âlib/tornado/tcpserver.pyâ, line 126, in listen
File âlib/tornado/netutil.pyâ, line 154, in bind_sockets
File âlib/socket.pyâ, line 953, in getaddrinfo
socket.gaierror: [Errno 8] nodename nor servname provided, or not known
ERROR: This system has no python serial support
Using FakeHMI => <mod.development.FakeHMI object at 0x110589250>
cc start socket missing
jack client deactivated NOT
âŚnot only!! Cliking on Open User File âŚit doesnât open the user file⌠but not⌠the directori is correctly named because I can load audio, nam, midi, or any other fileâŚ
Strange!
Thank you for your work; itâs a fantastic piece of software, very powerful.
I have a kind of technical question. I would like to control some settings with the command line (Iâm on Linux, by the way). I found out that mod-host can be controlled with the command line, and I tried to send some commands via the socket. The problem is, I donât know the socket port. I tried the default one (5555), but it doesnât seem to work with mod-desktop.
What would be needed to remove the need to âapproveâ access to mics on MacOS? Is it simply a case of getting hold of an Apple Dev Licence to allow signing?
If so, I would be willing to chip in towards the cost (I think itâs about $300 for organisations).
Sam x
it does indeed use another port, to try to not conflict with other mod-host already running.
this port is not useful by itself though, and connecting through it would make mod-ui state broken and invalid.
The mod-host port on desktop is 18182 by the way.
It needs a code-signing thing to be setup, we still need to setup one for MOD Audio UG as company. It is just something I have not ever dealt with before.
From what I understood it is not complicated, and you can even âad-hocâ and that will do the trick here too.
Thanks for the reply, it seems like itâs not as simple as I hoped. I was asking because Iâm trying to solve this issue:
I really want to figure out a way to change NAM files on the fly using MIDI commands. Right now, the only method I found is to create multiple instances of the NAM plugin, one for each file, and assign a different file to each instance. Then, I can bypass all of them except one using MIDI. The problem is that all these plugins are taking up space on my pedalboard, and I think they might also be using resources even when theyâre bypassed.
Another idea I had is to control either plugin presets or pedalboard snapshots using a MIDI command, but Iâm not sure if thatâs possible.
there is no need to install python when running mod-desktop, it already includes everything it needs to run, it does not use system python at all.
for your error in particular, it comes from here:
application.listen(DEVICE_WEBSERVER_PORT, address=(âlocalhostâ if DESKTOP else â0.0.0.0â))
...
File âlib/socket.pyâ, line 953, in getaddrinfo
socket.gaierror: [Errno 8] nodename nor servname provided, or not known
this means the localhost
address in your system somehow is not being mapped to anything, making mod-ui unable to start.
it seems a very peculiar issue, localhost
should always map to 127.0.0.1
on any regular system, not sure what is going on in yours really.
We have yet another release!
Fixes a few regressions from 0.0.8 and other issues as reported by users.
Enjoy!
I recently saw an issue on macOS where it would first resolve to the ipv6 ::1
before it would resolve to ipv4 127.0.0.1
(this was with nodejs though)
Good point, changed that just now to use the more specific 127.0.0.1
as per Use 127.0.0.1 for desktop instead of localhost ¡ moddevices/mod-ui@214d64d ¡ GitHub
Thanks for pointing me in the right direction.
It turns out my âHostsâ file was empty. I honestly donât know why.
There was another file named âHosts~oldâ, so I renamed it âHostsâ and this solves my problem.
Thanks again !
And yet another release!
Has a new factory pedalboard and some minor tweaks.
Enjoy!
Just downloaded the latest Desktop version, having not used it for a while (maybe a couple of months). Have an issue whereby when the audio interface is set to the iConnectAudio4+, the app wonât Start - i.e. Start button doesnât fire it up. When I choose another, such as the onboard audio or the Syntakt, then it works fine. The iConnect is preferable for the purposes of routing in and out of the DAW.