search

DISTRHO / Cardinal

Virtual modular synthesizer plugin
https://cardinal.kx.studio/
GNU General Public License v3.0
2.18k stars 149 forks source link

Pitchbend on Host MIDI CC module does not work #193

Closed rafaelferreiraql closed 2 years ago

rafaelferreiraql commented 2 years ago

When using VSTi(2) Cardinal on Reaper on Win8 (not sure about VST3 or VST2), the default Pitch bend output in Host MIDI CC, well, does not output anything. Note that Pitch bending on the regular Host MIDI module works as normal.

falkTX commented 2 years ago

is this with 22.02 release or one of the latest builds? I think this is already fixed on the latest ones.

rafaelferreiraql commented 2 years ago

Oh, I'm using the stable 22.02 release. Great to know that's been worked on.

falkTX commented 2 years ago

Can you try the new builds from https://github.com/DISTRHO/Cardinal/actions/workflows/build.yml ? Would be great to have confirmation that it really works now, thanks!

rafaelferreiraql commented 2 years ago

Embarassingly, I do not know how to run Actions.

falkTX commented 2 years ago

no worries, you can use this link https://github.com/DISTRHO/Cardinal/suites/5702890893/artifacts/188019631 still valid for a few days

rafaelferreiraql commented 2 years ago

Sorry for the delay!

It seems like Host MIDI CC's pitchbend is still broken.

(EDIT: Unrelated but maybe relevant, the Ctrl key is now entirely unresponsive, in the Stable release it was spotty but I could still drag multiple modules with it, but not anymore)

falkTX commented 2 years ago

I tested this myself just now, and cant reproduce. I mean, it is working fine for me. Generating and sending some midi pitchbend events to cardinal I see them in polyscope. And the other way around too, some lfo into midi-cc pitchbend input, checked then externally by a midi monitor tool

PS: Rack 2.1 changed how module movement works, ctrl+drag does nothing now.

dromer commented 2 years ago

I only see an issue with the VST3 (nothing happening, either pitchbend or modwheel). Works fine with VST2 and LV2 (all variants).

MrJC11 commented 2 years ago

I can confirm that with Cardinal v22.05 and while using Reaper v6.57, I too am getting this issue. In fact, no CC outputs work, and no channel pressure.

falkTX commented 2 years ago

I can confirm that with Cardinal v22.05 and while using Reaper v6.57, I too am getting this issue. In fact, no CC outputs work, and no channel pressure.

For VST3 only right? The VST2 variant works fine afaik

falkTX commented 2 years ago

VST3 implementation has been done in efa1eb8a6aa8ec4b0c4ed9f235f024b5945227e6 Closing ticket.