This is weird, Host CV module on desktop should definitely look different.
the cv ports are hidden on the ânativeâ variant, as to not confuse users who might think they are usable ports.
but yeah that breaks this usecaseâŚ
Ah, right for non-Jack users.
Well one can run the plugin version as well and that should be able to connect right? (it does here)
AU would make sense, since it doesnât support anything pretty much.
Try VST3/LV2/Clap instead, these 3 should all have Host CV
module available.
Cardinal FX VST3 doesnât work - nothing visible as before.
The main Cardinal VST does show ports but not working in the Cardinal plugin on MOD environment - FX or the main Cardinal one.
Any idea of LV2 hosts for Mac?
Carla, Kushview Element, Reaper, Ardour, Harrisson Mixbus, Tracktion Waveform, Zrythm. Cardinal.
(yes, Cardinal can host itself. see the Ildaeil
or Carla
modules)
Oh cool - was going to try Reaper, good to know
Sorry @dreamer - LV2 not working in Reaper either, tried with all iterations and no joy,
I donât this setting up this CV is possible at all right now - guessing something needs to be enabled on the MOD environment for this to work?
Huh, this is strange.
For me on Linux in Reaper I can use VST3, LV2 and CLAP of Cardinal
(so not Mini
, Synth
or FX
) that load the Host CV module.
My bad - Monday brain hadnât properly connected the CV in MOD.
SPECTRAL now working a treat on the MOD DUO X - all mapped and good to enjoy here folks.
More to follow - VERY happy about this
This one actually works
why the many control to cv? the âhost paramsâ module provides the knobs as a cv source to patch in to other things.
Ah - didnât know that! Only had this thing a few days
A few others up there now - the time stretcher and resonator options didnât work out.
Still - theyâre there an mapped to knobs on the MOD DUO X so hope people have some fun sonic mangling with them
@falkTX Understand what you mean now - Iâd tried that but that feature doesnât seem to work on the MOD version of Cardinal, whereas using CV does.
Except thatâs exactly what I showed in my screenshot and it works great for me.
Odd - tried it again with a more complex setup today and worked fine.
SOLVED: turned out it was mainly a performance issue. See at the bottomâŚ
I hope thatâs also the right place to ask for help on using Cardinal on the Dwarf?
I am trying top deploy a Synth patch made in Cardinal to my Dwarf, using the description here:
https://github.com/DISTRHO/Cardinal/blob/23.10/docs/MODDEVICES.md
First thing that I found confusing was that I could only find a âCardinal FXâ in the Plugin store, no synth or mini, despite on the web plugin catalogue this exists: Cardinal - MOD Audio
But as I saw the FX has midi in, I assumed I can try to deploy a Cardinal synth patch.
After finding the right menu item (minor documentation inconsistency - see below) and clicking the âconnect to remoteâ, I wondered how I can see that itâs successful, but I assumed when the menu changes to say âdeployâŚâ it must be connected
After chosing deploy I wondered again how I can now see that the deploy was successful. The documentation ends there, so i clicked around a bit. There is no new preset in the Cardinal plugin, were i thought I might get a preset named as the patch that i uploaded.
At some point i realized there is a difference:
The Dwarf is running continuously at 100% CPU now⌠I logged in via ssh, and see that jack is the one who uses a lot of cpu the whole time. I see some things happened related to Rack / Cardinal and alsop with the modules I used in the deployed patch, but no error.
After I deleted the plugin from my pedalboard, cpu usage goes down.
Is this a bug or is this just a sign that my Cardinal patch is too much for the Dwarf?
Another minor thing is that the wording of the description is incorrect - it says I should click on âConnect to MODâ - bit the menu item is âConnect to remoteâ - before creating a bug I looked in the source code and actually found there is a switch that makes it being one or the other at compile time, but i dont understand why that exists and why the normal Cardinal calls it âremoteâ and what other devices could be remote.
Let me know if I can debug that furtherâŚ
Update:
A smaller Cardinal patch worked.
One time in the process the knobs functionality on the dwarf appeared to be crashed - it didnt react on any of the physical buttons anymore but the web UI and also redeploying worked.
But the buttons only worked again after a reboot.
One thing that is less nice than with pure mod patches is that the buttons all are labeld just with âparameter 1â etc so it has to be remembered. Would be perfect if it could be identified from within the patch what the knob does but thats probably complicated or impossible.
In that case free manual naming would be good.