-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Arturia Instrument Link #7
Comments
"just some random crashes while swapping between plugdata and other instruments." please be a bit more specific: what exactly are you doing to get such a crash? and how does the crash look like? and please show us how we can set it up to verify that it sends/receives midi-clock |
hmm, i don't see these settings. is this screenshot from the standalone version? |
This is the vst3 opened in vvvv |
I have the 1.0.0.314 ,it looks they have done some changes since 2022 |
Regarding MIDI learn: the plugin does not implement |
regarding Midi Clock in/out: could it be the reason they removed this functionality in the vst plugin is that vst3 doesn't support all midi features? here is a list and this does not include midi clock. instead i'd assume they say all timing is the hosts duty and the plugin just takes timing from the host. you can configure this via the TimingSettings node. does this make sense? |
I don't know if it's relevant, but i have a bunch of plugins that react to vvvv TimmingSettings. |
what i was saying: the MicroFreak should also react to TimingSettings and that should replace your desire for it to support Midi Clock input. if not, please explain what's missing. |
Ahh, sorry, when i said MidiClock i didn't make any distintion between it and TimingSettings. and you are right the Timming is not sent as Midi Clock message. Some clarification regarding Timing: |
Regarding my comment on MIDI learn: false alarm, I think the plugin is just buggy in that regard. Doesn't even work in their standalone app. What does work and also mentioned by others (https://forum.arturia.com/t/solved-with-new-version-minifreak-v-generic-controller-now-working-as-expected/4932, https://forum.arturia.com/t/bug-minifreak-v-midi-learn-not-quite-working/2615/16) is to switch away from the generic controller to for example MicroLab, after that it behaves correct. |
- A MIDI program change message now gets routed to program change parameter based on IUnitInfo.getUnitByBus, see comment in https://forums.steinberg.net/t/midi-program-change/201860/5 - Fixes VST event to MIDI message translation - the LegacyMIDICCOutEvent uses some special values to encode MIDI program change and poly pressure. Not sure about quarter frame. Couldn't test this part, not sure which plugin emits such events.
See my commit above, we now translate MIDI program change messages. However it seems to me the demo version of the MiniFreak is missing some MIDI functionality, see page 115 of its manual, therefor I couldn't test the changes there. I did see results however in the Zebralette, I was able to select the presets I put into its "MIDI Programs" folder (can be done in its Preset UI). |
No problems so far, just some random crashes while swapping between plugdata and other instruments.
There are demo versions available for all Arturia Instruments, which i think are quite complete and modern.
This instrument in particular has the ability to send midi cc out when a knob is updated and receives midi cc aswell.
It receives and sends midi clock.
Program change in to change the preset.
https://www.arturia.com/products/software-instruments/minifreak-v/overview
The text was updated successfully, but these errors were encountered: