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

[dmitri]

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.

Not before we sort out the issue with the Roland cymbal, will you?:)

Does the PCY155 work the same as the PCY135 with the Megadrum?

Yamaha PCY135 and PCY155 cymbals are 3 zone cymbals and as far as I know are as good (if not better) as Roland cymbals and cost less. Though being 3 zone they use only one stereo jack instead of two as Roland 3way cymbals do. Besides they have a built-in trim pot to adjust piezo output level.
As far as I can judge they work perfectly with MegaDrum.

[dmitri]

I just realized that you MegaDrum is with the Positional sensing addon built-in and you use your cymbal on an input with the Positional sensing. Can you please test it on any other input except inputs 4, 6, 8, 10 and 12?

[dmitri]

And here is another test version with head suppression level increased:

megadrum_test_20140829.zip

[mdefiore]

Sure Demtri, I'd be happy to work this out before switching to Yamaha cymbals (if I do).

I have tried the cymbal on inputs both with and without positional sensing. The cymbal works much better on inputs with positional sensing.

I'll try it shortly and get back to you tonight.

Thanks.

And here is another test version with head suppression level increased:

megadrum_test_20140829.zip

[mdefiore]

I tried the new firmware with the same settings, but the response is similar: slows edge hits do not cause bow notes, but fast edge hits do trigger bow notes.

I'm also noticing some strange behavior with bow rolls: there is a delay in megadrum registering fast rolls on the bow intermittently...then it catches up....then there is a delay, then it catches up. This behavior is more pronounced in this last firmware update.

Sure Demtri, I'd be happy to work this out before switching to Yamaha cymbals (if I do).

I have tried the cymbal on inputs both with and without positional sensing. The cymbal works much better on inputs with positional sensing.

I'll try it shortly and get back to you tonight.

Thanks.

And here is another test version with head suppression level increased:

megadrum_test_20140829.zip

[dmitri]

I tried the new firmware with the same settings, but the response is similar: slows edge hits do not cause bow notes, but fast edge hits do trigger bow notes.

Are you sure that every edge hit, when doing fast edge hits, actually makes the edge switch? Those edge switches are not always perfect - some edge hit misalignment may actually not make the switch.

I'm also noticing some strange behavior with bow rolls: there is a delay in megadrum registering fast rolls on the bow intermittently...then it catches up....then there is a delay, then it catches up. This behavior is more pronounced in this last firmware update.

Are you sure it is delaying MIDI data and not actually missing some hits due to too heavy false triggering suppression in the new algorithm? Delaying would be very puzzling, whereas I would understand why it is missing hits.

[mdefiore]

Dmitri: Are you sure that every edge hit, when doing fast edge hits, actually makes the edge switch? Those edge switches are not always perfect - some edge hit misalignment may actually not make the switch.

The rolls are fast, so I can't know for sure. However, I think the switch is being triggered for two reasons 1) Watching the megadrum manager while hitting seems not to miss notes, rather replace edge hits with bow hits. 2) The same roll on the TD-30 does not produce bow hits (not just when listening to it, but also when looking at the rim led on the TD-30 itself: the rim led never goes off when I'm doing an edge roll).


Dmitri: Are you sure it is delaying MIDI data and not actually missing some hits due to too heavy false triggering suppression in the new algorithm? Delaying would be very puzzling, whereas I would understand why it is missing hits.

That's possible, but I don't think so. If it were missing notes than the the graphical Megadrum manager midi log (the graph) would simply pause when doing a roll. Thats not what I'm seeing. I see the graphical display slows down for a bit—then speeds up a lot— then slows down again. The speed changes are enough to be noticeable.

[dmitri]

Dmitri: Are you sure that every edge hit, when doing fast edge hits, actually makes the edge switch? Those edge switches are not always perfect - some edge hit misalignment may actually not make the switch.

The rolls are fast, so I can't know for sure. However, I think the switch is being triggered for two reasons 1) Watching the megadrum manager while hitting seems not to miss notes, rather replace edge hits with bow hits. 2) The same roll on the TD-30 does not produce bow hits (not just when listening to it, but also when looking at the rim led on the TD-30 itself: the rim led never goes off when I'm doing an edge roll).

With fast rolls the rim led on TD-30 may actually not have enough time to go off when missing some rim hits. Can you actually capture a MIDI output from TD-30 showing a steady flow of rim MIDI notes without any intermittent bow MIDI notes when doing fast rim rolls?

Dmitri: Are you sure it is delaying MIDI data and not actually missing some hits due to too heavy false triggering suppression in the new algorithm? Delaying would be very puzzling, whereas I would understand why it is missing hits.

That's possible, but I don't think so. If it were missing notes than the the graphical Megadrum manager midi log (the graph) would simply pause when doing a roll. Thats not what I'm seeing. I see the graphical display slows down for a bit—then speeds up a lot— then slows down again. The speed changes are enough to be noticeable.

This is in fact a misbehavior in MDM MIDI Log graphical repaint algorithm which I've never had time to fix yet.