Positional Sensing Multiple Ports CC Conflict

[neumayr]

Hi!

I was unsuccessfully looking for information on this, hope I haven't missed something obvious :S
After using positional sensing for my Snare only without any problems, I today tried to integrate a CY-15R. Now, Megadrum apparently senses the position hit on the Ride, but sends the data using the same CC number as it uses for the Snare.

Addictive Drums 2 does not like this very much, giving me a big "CC Numbers Clashing!" message. Is there a way to set the CC number used for Megadrum's positional data per port?

Best,
Micha

[dmitri]

I cannot advise you on configuring Addictive Drums (or any soft synth) for positional sensing but I can give you the following info:

1. Positional sensing uses only one CC number - CC16.
2. On inputs configured for positional sensing MegaDrum always sends first CC16 and only after that it sends Note On.

Based on the above, any soft synth if capable, should be able to match CC16 positional data to each individual input without a conflict.

[neumayr]

Thank you for your reply. I asked XLN Audio's support, I'll post their answer here.

[angr77]

Hold your horses!

I am the brain behind that we have the MegaDRUM mapping bundled with AD2.

XLN have changed their requirements in AD2 ( since version 2.0.5) it was okey in earlier version to send cc:data on only cc 16.

They don't allow that different sounds (in this case snare, ride1, ride2) communicate ps data on the same cc channel. (Md sends all ps enabled drums on cc 16)

In my delivered MegaDRUM Advanced map settings all three sound slots are set to 16. That's why you get an error in AD2. Easy to change ride 1 to cc 17 and ride 2 to cc 18 to get rid of the AD2 error message. I am going to deliver an update of the md map to XLN on this. But ps data over cc from md will only work for one ad2 sound slot.

But a question which came to my mind...should this be changed in the MD firmware. We can today have several PS enabled pads...should there be a option to be able to set the cc channels individually?

Not just cc 16...

On Roland TD-30 they use cc 16-20.

Last: we have not be able to catch the ps algorithm for CY-15r...so currently cc won't work here.

I will talk to my friend at XLN about why they changed the specs.

Best regards

Angr77

[dmitri]

XLN have changed their requirements in AD2 ( since version 2.0.5) it was okey in earlier version to send cc:data on only cc 16.
...
But a question which came to my mind...should this be changed in the MD firmware. We can today have several PS enabled pads...should there be a option to be able to set the cc channels individually?

Not just cc 16...

On Roland TD-30 they use cc 16-20.

It's possible but I'm puzzled why it now needs separate CC number for separate inputs. What if you (theoretically) want to use Positional sensing on all 55 inputs MegaDrum supports it on?

[angr77]

Thats good!

I have asked that question to XLN. (Why they changed)

Best Regards

Angr77

[neumayr]

Okay, thanks for the additional insight, angr77. XLN support will likely tell me I'm out of luck then, and this won't have any chance of working unless dmitri changes the firmware to allow CC numbers to be set per input. Which would be greatly appreciated

Last: we have not be able to catch the ps algorithm for CY-15r...so currently cc won't work here.

That is a shame.

[angr77]

The PS function on cc:16 for several drums has been working on earlier versions of AD2 than 2.0.5. I have asked my friend why they changed.

Regarding PS on CY-15R...what is your feeling...is it working okey when you look on the MD display and the arrows indicating where the hit has been done? (Something is changing when hitting a CY-15R...but is it consistent?)

We made some job last summer trying to find the algorithm ... Oscilloscope looking on the first half wave when hitting on different positions on the CY-15r. But we felt it got too complex...we could not really see the logics...

However... I have not tested this for a 7-8 months...with a PS enabled input with a rectifier...so it is maybe time?

But I agree...this is a real nice features which we would like to add to the MD!

Angr77

[neumayr]

I spent some time to get this cymbal to at least work correctly without positional sensing - still some way to go. Anyways, you are right. On all three positional level settings, the output isn't consistent at all
I don't have an extra rectifier though, can't tell if that would help here. Do you per chance know if the CY-15R-MG works any better?

[angr77]

Hi!

I have no experience on the CY-15R MG but I am assuming the construction is very similar to the CY-15R. I will give it a new shot in the near future to see if we can solve the algorithm stuff. I have not got any answer yet from my friend at XLN...probably these guys are traveling to the NAMM exhibition this weekend.

Best Regards

ANGR77