MCCgenerator questions

[NTO]

I too have this plug failing for use in Studio One - need instrument def/not effect.
viewtopic.php?f=138&t=547300&p=7800735& ... r#p7800735

Trying it in another environment - Bidule - I can get the midi output to a monitor, but so far all seem to be (some kind of) 14 bit implementation .
In example using CC11 in the plug monitor shows it making 11 & 43. CC2 is 2 & 34.

Watched the Chandler video, and have been browsing the UI.
Often have trouble finding config switches w/Melda plugs.

Anyone know how to get either of these (S1/non 14 bit) to work?

TIA

[sekim]

It will work different in various DAWs depending how they implement VST midi out capture and usage.

In Samplitude it's a total pia. In Reaper it's super easy. In Cantabile it's super easy.

Also, different midi CC have different bit depths. Check the net for a chart of CCs that include resolution.

[NTO]

Also, different midi CC have different bit depths. Check the net for a chart of CCs that include resolution.

Aware of the spec's, examples given are 7 bit definitions.
https://www.midi.org/specifications-old ... ta-bytes-2

[R13]

In example using CC11 in the plug monitor shows it making 11 & 43. CC2 is 2 & 34.

I find it undesirable that MCCGenerator sends out 2 CC messages for certain CC's. It seems to be messages that have a 'course' and 'fine' version (which are different CC numbers). I would prefer it only sends the single CC I have mapped.

[MeldaProduction]

In example using CC11 in the plug monitor shows it making 11 & 43. CC2 is 2 & 34.

I find it undesirable that MCCGenerator sends out 2 CC messages for certain CC's. It seems to be messages that have a 'course' and 'fine' version (which are different CC numbers). I would prefer it only sends the single CC I have mapped.

This is MIDI standard folks. The second message adds precision to the previous one. Yeah, MIDI sucks...

[mabian]

In example using CC11 in the plug monitor shows it making 11 & 43. CC2 is 2 & 34.

I find it undesirable that MCCGenerator sends out 2 CC messages for certain CC's. It seems to be messages that have a 'course' and 'fine' version (which are different CC numbers). I would prefer it only sends the single CC I have mapped.

This is MIDI standard folks. The second message adds precision to the previous one. Yeah, MIDI sucks...

No. Many devices only send - and are ready to receive - the first of the pair.... Why not making it an option per CC?

Thanks,
Mario

[NTO]

This is MIDI standard folks

There's nothing in a spec documents or Developer_Guidelines that says this is the preferred implementation. The CC's listed by name are 7 bit definitions.

Yeah, MIDI sucks...

People have always said this when vendors decide they'll implement it however they wish.

Think anyone is using (i.e.) 16,383 mod wheel (CC1) values?

[MeldaProduction]

Sorry guys, not true. MIDI defines in some latter definition that controllers 32-63 are used as "accuracy" for controlles 1-31. (or something like that). Anyways these values are irrelventa unless you use them of course.

[mabian]

Ok, it's like saying that sidechain cannot be done in VST2 because the specs don't mention it...

My question is: since tons of MIDI devices - hardware and software - support single CC (8 bytes) flow, and this is often beneficial to reduce traffic, would it be feasible to implement an option that allows sending single CCs instead of X, X+32 CC data?

Thanks,
Mario

[MeldaProduction]

Well, it can certainly be done, but honestly who knows, if his controller/VSTi supports that? I mean it only doubles the traffic, which isn't too relevant these days. And the specs DO mention it. To be honest, I was confused too at first though... It's obvious they needed to introduce the higher accuracy somehow, so this is what they came up with