all the needed definitions are already set from mod-plugin-builder.
3 Likes
Hi @falkTX,
Thanks.
I had removed readline by defining SKIP_READLINE.
The sizes I am getting are way off the installed binaries though so I thought I would try to add that into bootstrap as well, bootstrap works fine and installs the package.
I’m getting build errors on mod-host now though.
Should the Dwarf mod-host include readline?
Edit:
these are the size differences:
mine:
[root@moddwarf ~]# ls -ltrh mod-host.so
-rwxr-xr-x 1 root root 170K Jan 1 00:21 mod-host.so*
installed:
[root@moddwarf ~]# ls -ltrh /usr/lib/jack/mod-host.so
-rwxr-xr-x 1 root root 365K May 12 2022 /usr/lib/jack/mod-host.so*
1 Like
size difference likely due to missing hylia as lib which is a static one so the entire code gets merged in.
you only need it for ableton live, so can be skipped too.
1 Like
Ah super I will have a look at this…
2 Likes
Hi @falkTX,
I seem to be having some coms troubles with my mod-host:
mod-ui.run[613]: WARNING:tornado.general:Connect error on fd 38: ECONNREFUSED
Have you any ideas what might be missing or causing this?
(I still have readline removed)
Cheers
Andy
1 Like
arguments that start mod-host have changed, if you are on v1.11 you need mod-host hotfix-1.11 branch
2 Likes
Hi @falkTX
Out of curiosity what version is the master branch?
Is that the one for 1.12?
Cheers
Andy
1 Like
Hi @falkTX,
I have a working version on the Dwarf now for 1.11 that has bidirectional midi CCs from the ui knobs, snapshot loading and pedalboard loading.
Currently I have one midi_out in mod-host which I am connecting manually via jack_connect mod-host:midi_out mod-midi-broadcaster:in
The next step is to do automatic connections.
I am wondering if you would ever want to merge this code into your mod-host?
If not for me I am happy to just connect the midi_out to the aggregated port or all hardware ports.
If you do want it I am going to have to think of something a bit smarter as really for the separated ports the message should only be going to the originator.
Let me know?
Cheers
Andy
6 Likes
just open a PR against mod-host project.
hard to say if/when it will be merged, but having it public is the first step for anything.
regarding the auto-connection, you can just use jack_connect function in the C code, with special attention needed for the separated / merged mode.
6 Likes
Thanks.
I looked more deeply at the midi stuff, without major changes (multiple midi ins) I can see no way of seeing what the originator was.
So I guess sending the CC to all midi devices is the only way forward. I will add in connections like this.
One question though what is the g_raw_midi_port_list for?
4 Likes
for plugins that request raw midi access, typically for handling midi clock internally.
that list is the midi ports to keep track of in case another hw device appears, so mod-host makes the connection automatically
2 Likes
Hi @falkTX
Thanks for the info.
I’m struggling to get my linux setup the same as the dwarf, the in process clients mod-midi-broadcaster and mod-midi-merger are not loading from mod-host or the command line on ubuntu 22:
$ jack_load mod_midi_merger
could not load mod_midi_merger, intclient = 0 status = 0x 1
I have tried the normal /usr/lib/jack install and also /opt/usr/lib/jack, the files are there fine.
I know bugger all about jack and have not found much help on the internet, do you have any ideas?
Cheers
Andy
3 Likes
on debian systems, due to multiarch, path is like /usr/lib/x86_64-linux-gnu/jack/
1 Like
Nice one thanks, will look at that in the morning…
1 Like
10 Likes
Added another pr: Midi cc out nrpn by AndrewCapon · Pull Request #62 · moddevices/mod-host · GitHub
Adds NRPNs, also bi directional.
8 Likes
Hi! I’m sorry I couldn’t tell if this hotfix was actually merged into the code. So… Is it available in the Dwarf firmware already? Thanks!
@falkTX, @gianfranco Hi! Three years later I just want to check in with this question, maybe generalize it a bit: is MOD audio going to revert some focus from MOD desktop back to physical devices? There are not only outstanding requests, but (supposedly) working pieces of code in the pull requests that have never been merged.
It’s so frustrating to be one step from having a good thing made into a great thing and not seeing in happening for years (my first marriage doesn’t count, looking back, it was doomed from day 1).
If I’m not mistaken, I think I saw the message that MOD went open source. I’m not sure to what parts of the MOD portfolio that open source approach was/is applicable, but I would expect more attention to the suggested solutions to the firmware.
I understand the lack of resources (@falkTX you often say you’re the only developer in the company), but even more so I would expect you guys paying attention to whatever help offered by the community.
I wouldn’t even mention ControlChain idea, this was buried long time ago, I guess bu now nobody wants to dig this out. Help us at least to implement the workarounds that we’re suggesting.
I’m sorry I’m letting my frustration out, but I kinda invested my own time and resources into the periferals to my MOD Dwarf that I’m not getting the full value from.
Sorry missed this message, it was never merged unfortunately.
1 Like