Hello @Pablo ,
please tell us how you fixed this, because we all don’t want to stay dumb, too.
Greetings and God bless, Marius
4 Likes
Gosh. Just a mis-match of midi channels (a bit embarrassed to admit).
I thought I it was cardinal as the native mod sequencers were triggering the synth just fine. However on fiddling with the synths midi settings everything fell into place.
I have to say this is really good!!! I can hardly contain my excitement.
It takes some getting used to since once deployed to the Mod device setting up a cardinal patch is like working blindfolded but the combination of the Duo X and Cardinal is pretty fantastic! Well done folks!
7 Likes
I’ve been fiddling around with Cardinal for most of today. Mostly just trying to learn the different modules and what not.
Right now, figuring out how to use the HOST parameter plugin to control clock in cardinal using the “Ice Tray” delay / looper module as the final touch. (which is really fantastic for mangling samples longer than 20-30 secs, with a lot of melodic content. I’d love to be able to set up for a live performance next month.
(or if anyone can point me towards where i could change the clock from host would be lovely)
However the sound quality doesn’t really seem to be there yet compared to how it processes sound in the DAW as a plugin.
It kinda jumps, and is pretty mangled up. It coughs up a bit tidbits of sound, and i’m wondering if there’s any documentation or other an IRC channel for people that are testing and comparing their experiences with the different modules on the MOD devices (I’m using the dwarf for reference), as to be able to discuss what works on the devices, and what doesn’t.
I’m gonna be playing around a lot more the coming weeks
5 Likes
@falkTX does the trick of “view → limit rate → 4x” work also when you port the patch to the MOD device? Maybe this is what @DupeSupreme needs.
1 Like
Why not use Host Time module, or do you want to have a completely separate/unrelated clock source inside the cardinal patch?
Why not use Host Time module, or do you want to have a completely separate/unrelated clock source inside the cardinal patch?
I’m running different time signatures for different units in my setup.
Setup so far:
1010 Blackbox (sampler) (Host Clock)
Fred’s Lab Toôro, (Polysynth) - Wired monophonically into one of the inputs in Dwarf. (L)
Electric Guitar (R) input of the dwarf
The pedalboard consists basically of reverb/delay(host synced) for the guitar and synth
and an internal media file playing different soundscapes and textures that i’m currently trying to mangle up with different cardinal patches which is independent. from the rest of the setup.
From a performance standpoint, it still doesn’t seem like i can get the media filer player + cardincal patches up and running in Mod dwarf.
might be easier to just bring the computer instead.
1 Like
Hi! You are probably all busy with the reboot 
, but here goes;
I am trying to deploy a midi MPE patch from Cardinal 22.10 to my Mod Duo X 1.12 RC3 using the Cardinal plugin, but so far without success. Not even a rise in CPU. Also tried other patches inwhich MDX responded and made strange sounds. Tried both in Native and Vst3 and vst2 plugin in ableton, but no success.
Do the Cardinal plugin(s) need an update to keep up with Cardinal 22.10?
Or is the failure somewhere else?
1 Like
Cardinal plugin (on MOD side) needs an update, yes.
Cloud is sorta back up (only missing HTTPS/SSL certificate setup), as soon as that is setup I will push the updated Cardinal releases.
7 Likes
Plugin updates can finally be pushed (a few more cloud setup details finalized).
Did one with Cardinal as a test, which was successful, so we got 22.10 release on the MOD Plugin Store now.
8 Likes
I’m very excited about Cardinal and I had a go at sending a few patches to my Duo X.
I not sure what to expect regarding CPU usage, but it seems a bit more demanding than I thought it would be.
I tried recreating a patch composed of Mod plugins I had from before using Cardinal modules, and the CPU usage was peaking a lot higher. CPU usage was also a lot more erratic.
I was not structured enough when trying things out to save pedalboards and patches in comparable states. But I probably could do so if there is an interest.
I tried running this pedalboard and the CPU was mainly around 70%.
I’m on 1.11.6.2908 and Cardinal 22.10-4
2 Likes
Not bringing much to the main topic, but…
Now you are 
You can edit the previous post if you’d like
2 Likes
Store version updated to 22.11 as per latest release
An important change for MOD builds is the use of simde instead of sse2neon, following what VCV Rack chose to use for the official ARM builds.
How this affects performance still has to be tested, with a quick check myself I don’t notice much difference at all.
9 Likes
Store version update to 22.12 as per latest release again
The Surge-XT modules are in, among a few other things.
7 Likes
This does not appear to work on a Mac w/Chrome. I have the v22.12-6 plugin installed, I click connect to MOD on the CardinalNative App, menu then shows push to MOD, but when selecting that nothing happens. The plugin does not get updated, there is no “screenshot” showing in the plugin, no sounds and there is no confirmation in the Native app that anything has happened.
Also a minor issue, there are two menus, one at the top of the app window and the main Mac OS window. Selecting “Quit” from the Main Mac OS menu does not do anything.
1 Like
Have you tried to refresh the browser window with the MOD Webgui?
1 Like
I have (I also tried switching browsers etc). I did notice that after clicking Push to MOD, there is an increase of CPU usage shown on the little meter, but no sound and the plugin does not change visually (the screenshot etc). I have also tried both Cardinal and Cardinal mini (installing, re-installing etc).
Btw- A couple days ago, I had loaded the Cardinal plugin to see what it was about and it did indeed show a sample patch in the preview and it had sound. Then I removed it shortly afterwards until today.
Update: I have gotten a couple of the demo patches like Etherpad and Interverb to work only in Cardinal Mini, not Cardinal (why are there two?). But it’s still pretty sketchy because if I try to push another patch it may do nothing, it may get stuck on the previous one etc. A couple of the other patches- I am unable to determine what is required to “start” them.
This really needs more documentation- like mentioning to add a Cardinal “Host Params” module to setup the knobs in the plugin etc.
Update 2: As I mentioned, I have a few of the demo patches running, but the sound quality is pretty awful. Loads of crackling, high CPU usage. Cardinal also doesn’t show the name of the current patch that’s open, so I keep opening up the same one thinking it is a different one because I don’t remember the name of what I just loaded ha!
This could be like what Clavia was doing with the Nord Modular 20 years ago and the MDX with it’s knobs could make it a great host for such. I don’t think VCV would be the right vehicle for it though because it’s not exactly optimal CPU performance-wise. Thus it would put limits on everything. If this is hitting the roof on the MDX I think the Dwarf would certainly have an even bigger issue.
1 Like
Need to investigate the connection issues on macOS, but for performance indeed we cant expect much here.
The example patches are likely not going to work cpu-wise, that is what the “awful sound” comes from, they are probably just always hitting cpu limit and causing xruns.
For the semi-short term I plan to try to make the interaction better. Reducing the time that a patch is automatically sent to the remote instance, and also listen for knob changes and immediately send those over so we dont have to wait until we hear the change in the audio.
And a bit further down the line I want to have a proper version, with only a few select modules, where the GUI is directly shown on the browser. The idea is to have only things known to work well, in an effort to have a version that can be pushed to the stable part of the store.
5 Likes
I think (for me anyway) the Cardinal plugin may be better used as a “fill-in” for times when I need a certain module/plugin (or a combination of a couple) that is not within the current MOD ecosystem. Like a flexible sample player for example. Or a source of randomness like what a “M.I. Marbles” type module can make.
Btw- why the two different Cardinal plugins? Which should I be using?
1 Like
one is audio/midi, the other has 10 optional CV ports. use the mini if you dont care to route CV signals
4 Likes
Hi! Thanx for opening this universe 
Currently trying to use the Voxglitch Grain Engine with expander to do some live sampling with MDX, But no luck so far. I tried both plugins? What could I be doing wrong? Should it work?
1 Like