Roland CY-14c Xtalk: Hits to edge triggers bow peizo

[airflamesred]

Have you tried with the dynamic threshold?

[dmitri]

As per viewtopic.php?p=26726#p26726, can you please post the video for me to see the severity of the problem so that I could address it properly?

[dmitri]

Also, when I have a test firmware, will you be able to test it promptly?

[dmitri]

Here is a test firmware version:

megadrum_test_20140828.zip

It has a modified algorithm for general false triggering suppression and this algorithm applies even stronger suppression on edge hits of piezo/switch(/switch) cymbals.
This modified algorithm is activated when Retrigger is set to an odd number (1, 3, 5 ...). For your cymbal please set Retrigger on the head and the edge to an odd number and test it again.

[mdefiore]

Thanks Dmitri...that was fast! I'll test it tonight and advise tonight.


[quote...="dmitri"]Here is a test firmware version:

megadrum_test_20140828.zip

It has a modified algorithm for general false triggering suppression and this algorithm applies even stronger suppression on edge hits of piezo/switch(/switch) cymbals.
This modified algorithm is activated when Retrigger is set to an odd number (1, 3, 5 ...). For your cymbal please set Retrigger on the head and the edge to an odd number and test it again.[/quote]

[mdefiore]

New firmware is better than previous. Can get TD-30 level sensitivity on the bow and hit the edge slowly without triggering the bow. Faster edge hits, however, still trigger the bow as per image:



Video showing TD-30 with cy14c. You can see the trigger meter showing a green light whenever i hit the cymbal lightly with my finger. You can also see the red "rim" light light up when I hit the edge.

https://www.youtube.com/watch?v=sGxzMFPdD8w
e][/quote]

[dmitri]

So, we're in the right direction, aren't we? Before I make further changes to the firmware, can you test it with MinScan on the Bow set to 35 and on the Edge set to 30?

[mdefiore]

Yes, certainly in the right direction, thanks Dmitri. I've already tried several combinations of minscan—all the way up to 50 for edge and bow—with the new firmeware. Still same problem, so I put it back to 20. The main reason why I want to move from the TD-30 to the Megadrum is to decrease latency; it's not bad with the TD-30, which, based on my readings and angrs wwebsite, has about 4 ms of latency between mesh pad hit and midi note. This means I'd like to keep the minscan on the Megadrum at a max of 20 if I can.

So, we're in the right direction, aren't we? Before I make further changes to the firmware, can you test it with MinScan on the Bow set to 35 and on the Edge set to 30?

[dmitri]

The main reason why I want to move from the TD-30 to the Megadrum is to decrease latency; it's not bad with the TD-30, which, based on my readings and angrs wwebsite, has about 4 ms of latency between mesh pad hit and midi note. This means I'd like to keep the minscan on the Megadrum at a max of 20 if I can.

I understand that. The suggested test was to have a better understanding of what is causing the issue with Roland CY-14c since I myself don't have this issue with Yamaha PCY-135S. It was not a suggestion to keep it with high MinScan.

[mdefiore]

Hmmm..that gets me thinking. I'm tempted to just replace my Roland cymbals with Yamaha cymbals if Yamaha cymbals work better with the Megadrum right now. Does the PCY155 work the same as the PCY135 with the Megadrum?

The main reason why I want to move from the TD-30 to the Megadrum is to decrease latency; it's not bad with the TD-30, which, based on my readings and angrs wwebsite, has about 4 ms of latency between mesh pad hit and midi note. This means I'd like to keep the minscan on the Megadrum at a max of 20 if I can.

I understand that. The suggested test was to have a better understanding of what is causing the issue with Roland CY-14c since I myself don't have this issue with Yamaha PCY-135S. It was not a suggestion to keep it with high MinScan.