huh⌠does anybody know the status of building for DuoX? i did some test builds with my Duo, which worked, but havenât tried with the X, and donât yet have my DwarfâŚ
Yes, maxgen build is broken and itâs in my to-do list. Iâll get back to you soon (but might take a couple days because Iâm moving to a new place).
lilv_lib_open(): error: Failed to open library /root/.lv2/dm-Erbeverb.lv2/dm-Erbeverb_dsp.so (/root/.lv2/dm-Erbeverb.lv2/dm-Erbeverb_dsp.so: wrong ELF class: ELFCLASS32)
canât get lilv instance
resp -102
When I build the plugin following this guide (Max gen~ - MOD Wiki) the build result is <plugin-name>.lv2-duo.tar.gz. Is this supposed to work for all platforms? Shouldnât the plugin for the Dwarf be a different compiled binary?
Youâre running the max gen build manually. So itâs only meant for developers which are looking to use the tools and have control over the process. For typical users itâs much easier than that. Hereâs a video showing the integration between Max Gen and a Duo (it will work seamlessly with any device).
I can confirm it works using the MODwatcher in Max itself. So thanks for that!
Are you planning on updating the manual build process so it will compile for Dwarf too? I am one of those persons that wants a little more control. For the reasons written in the Wiki: add units, knob behavior, a description or even a GUI. (I know I could copy files, edit and copy them back into the MOD as a solution). And also because on occasion I want to edit the exported c++ code, which is only possible when building manually.
Ok. Apologies for not recognizing your hacker intentions
I thought somehow you had landed in the wrong wiki page and was trying to do it the hard way.
Thereâs an easy tweak you can make to download the correct (dwarf) binaries. Under resources/ open file publish.py. Line 83 you have to replace âduoâ with the correct binary architecture. So:
r = urlopen('{0}bundles/{1}/aarch64-a35/'.format(release_process_url, bundle_name))
Let me know how that goes.
Iâll look into changing this package to make the device binary an option to be picked from the command line. For now this should get the hacking goingâŚ
In case somebody with a duox lands here, the value to use would be: aarch64-a53
I gave this a try and came up with this. I added a prompt to select the preferred target (duo,duox,dwarf or all). I made âallâ the default.
I also had some issues with the urlopen function calls in the publish.py file. It started asking for ssl certificates. So I found a way to bypass that. You can find that in the linked github repository aswell.
Itâs just some small tweaks. Hopefully you donât mind me serving these scripts on Github. I thought this might be helpful to others.