One more MegaDrum firmware to test

[dmitri]

I'm inclined to think that the amount of feedback on this test firmware speaks for itself.

[r0bbie]

I'm inclined to think that the amount of feedback on this test firmware speaks for itself.

Not yet.... we’ve been enjoying nice Easter holydays! ( I hope)...
I was actually awaiting an update for MCT to change the firmware to your test version.
I will use Midi-Ox now, I will post results for 10" 12" and 14" DIY pads in a few days.
Would oscilloscope pictures of the piezo's output extra help you?

Regards,

Rob.

[dmitri]

I'm inclined to think that the amount of feedback on this test firmware speaks for itself.

Not yet.... we’ve been enjoying nice Easter holydays! ( I hope)...
I was actually awaiting an update for MCT to change the firmware to your test version.
I will use Midi-Ox now, I will post results for 10" 12" and 14" DIY pads in a few days.
Would oscilloscope pictures of the piezo's output extra help you?

Not really. Too many pictures will be need.

[Ken Forgettable]

I'm inclined to think that the amount of feedback on this test firmware speaks for itself.

ARGUUH where's my PAYPAL. Some people need a holiday about now and others are finding MCT firmware updates are problematic at the moment, anyway there's no rush but you could make it easy for us. May I again suggest sending the test data by MIDI so instead of fooling about with the LCD we can use MIDI-OX. Right clicking for the menu on the Input monitor window you can do a 'Copy All' (then Paste into your favourite editor)- instead of:

TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT
708984 1 -- 185 16 47 10 --- Control Change (Bottom right - data sent in CC messages. 0 - for centre, 127 - close to rim)
708990 1 -- 153 38 92 10 D 2 Note On
709190 1 -- 153 38 0 10 D 2 Note Off


...you could get a post like:

Medium tight 14" Pearl single ply.

TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT
708972 1 -- 185 16 5 10 --- Control Change (Top left - raw value)
708976 1 -- 185 16 5 10 --- Control Change (Top right - value adjusted for low hit levels)
708980 1 -- 185 16 31 10 --- Control Change (Bottom left - raw hit levels without 'Curve' adjustment)
708984 1 -- 185 16 47 10 --- Control Change (Bottom right - data sent in CC messages. 0 - for centre, 127 - close to rim)
708990 1 -- 153 38 92 10 D 2 Note On
709190 1 -- 153 38 0 10 D 2 Note Off

NB. This data is garbage.

But it's working for me nearly as well (if not better) than your velocity routine for light hits and I insist on using a 14" snare. I had an acoustic only drummer around to play with this 'test' firmware and ended up missing work the next day. We used BFD2 but they only do two 'zones' so we switched to Battery 3 and had some cool stuff happening by mapping the CC onto the modulators.

I suggested positional sensing was like 3D but my dear friend came up with 'MegadrumSKI'.
Sorry, but Golden Mangle awards are not for nothing. Pike wants to use it with acoustic heads and Dmitri's brain is now known around these parts as the Megadrum Surface Kontrol Interface.

I've also modified Dinamic Threshold algorithm in this version and in my tests rejection of false triggering is much better. I'd like to here feedback on this as well.

Tentatively agree with you.

[elrules]

Wow! I cannot believe that finally, positional sensing will be becoming a real feature in the near future.

Sincerely, I am very positively surprised

[r0bbie]

So here are my results.

I have tested with 4 different pads,

All DIY pads have the same construction, Ice-hockey puck glued to wooden cross-bar with a 25mm high foam donut.
On top of the puck a 27mm piezzo with Roland style cone made from a sanding block.
Cone height is about 3mm above the shell edge.

Mesh head is a single layer Tama.
All pads are Hot! so I have tempered them with different resistor configurations noted above each table.
I have recorded data for each velocity 3 times for center, half way the head and close to the rim.

Before recording the data I have set Highlevel for each pad about 50 below the value detected bij HighlevelAuto.

I noticed when I started recording medium velocity hits that the data on the display changed in a split second to a different value, changing retrigger to 70 cured this problem.

Dmitri, if you make a other test firmware, would it be possible to leave the data a few seconds longer on the display?

[dmitri]

Thanks, r0bbie! Picture is quite different from my Pintech - less consistency and different numbers then in my tests.

[elrules]

Is this feature forsaken or is it still a work in progress.

I am back in Amsterdam so again I have to build my megadrum before testing this.

How is it going

[dmitri]

Is this feature forsaken or is it still a work in progress.

I am back in Amsterdam so again I have to build my megadrum before testing this.

How is it going

It is shelved at the moment mostly for the lack of interest and partly due to lack of a "measure stick" for comparison.

[kurtus420]

If we wanted to still give you some input would that be a was of time or would it possibly re-hash this subject? I started to look for this info but didn't have much luck finding it, as stated before it would be great if the post had positional detection written on it. I just got my megadrum up and running and have some diy 10" x 4" taye toms c/w beatnik crossbar, 10" roland mesh head and poron roland style diy cones with 35mm piezos on head and rim on all the toms. I have a 12" x 5" sonor force 3007 snare cw with beatnik crossbar, 12" roland mesh head, poron diy roland cone 35mm piezo head and rim. My pads currently have a pot installed on the heads but the rim piezos do not, will this cause an issue? I will definately take part in this as soon as I figure out how all of the megadrums parameters work and I get good triggering, I want to have a good understanding on how to dial my megadrum in first.

Is this feature forsaken or is it still a work in progress.

I am back in Amsterdam so again I have to build my megadrum before testing this.

How is it going

It is shelved at the moment mostly for the lack of interest and partly due to lack of a "measure stick" for comparison.