Positional sensing on megadrum? a dream or a future reality?

[Synthex]

Is it possible to be effective in this forum ?
It is not the war but we try to move in the same direction !

[Marctwo]

You seem to have formed the impression that I only post here as some kind of childish, personal attack on you. I don't understand this???

My intention was simply to offer constructive input and share my ideas where you felt appropriate. However, since you're obviously interested in neither, I'll respect your wishes and keep both to myself in future.

[dmitri]

You seem to have formed the impression that I only post here as some kind of childish, personal attack on you. I don't understand this???

My intention was simply to offer constructive input and share my ideas where you felt appropriate.

If you point me out where you gave your constructive input(s) or shared your idea(s), I'll retract my words.

However, since you're obviously interested in neither, I'll respect your wishes and keep both to myself in future.

I'm very interested in peoples suggestions/inputs/ideas... except yours since there were none.

[Marctwo]

Formulating ideas is generally done through 2 (or more) way communication. The following is how you could have read and reacted to my previous post.

The most important part for me is how you organize your trigger sampling...

How is this important? What options did you have in mind for this?

If you have an efficient system then you should have no problems implementing this on 1 input (snare head)...

Well I'll have to mess around with it a bit to see whether I think the current system is up to handling positional sensing on just 1 input.

If your code is pushed to the limit with normal processing of 22 inputs then your current methods may not be suitable to incorporate this without additional hardware...

Well, The code is pretty much pushed to the limits at the moment so I guess I'll have to think about one or the other. What kind of alternative methods do you have in mind?

Position sensing would be nice on cymbals too (as mentioned) but most cymbal pads would not produce an appropriately variable frequency so may not be worth it...

Yes, it's probablly a good idea just to get 1 working first anyway - maybe then I can look into the possibilities for cymbals, etc.

Thanks for the input.

This to me seems at least reasonable... if not helpful.

[dmitri]

I'm speechless

[Synthex]

Please ...

The subject is : Positional sensing on megadrum !

[elrules]

Please ...

The subject is : Positional sensing on megadrum !

That's right! I started this thread to propose something new and innovative for megadrum. Please, let's talk about technical stuff and share ideas.

What I think is that it could be cool to have an atmega8, for example, for doing only the PS stuff, and then pass a formed MIDI CC value to one input of the atmega32. Then atmega32 only sends this input directly to MIDI out.

It would be nice to use the "Midi log" of a midi tool software to capture all the midi messages when playing the PS snare on a roland td-20 module, and also when playing the PS snare and also the hihat. I don't know about midi specification when you have to send several MIDI CC types of messages. I suppose you can send it all togheter, can't you?

First of all, I will ask a friend to capture midi messages from a TD-20 for me

[dmitri]

Exactly what MIDI messages to send when position of a hit is detected will be the easiest thing to implement and a MIDI log will be helpful here. But it's just 1% of what needs to be done to implement position sensing.

[elrules]

Well, besides the midi log, we can talk about the position detection itself.

How do you detect that a signal is a hit?
Maybe this way?:
"The megadrum samples constantly the inputs taking as inputs sampled quantized values , and when it detects a value higher than the threshold it start comparing values till it finds the highest value (the peak of the wave) and then it creates a midi value from that sample."

If it is how megadrum detect hits, then positional sensing would be somthing like:
"When the value is higher than a threshold it start counting number of samples. When the value is lower than the same threshold (a half wave has happened) it stops incrementing the counter and the value in it is a proportion of the midi cc value it has to send to midi out."

Am I supposing too many "not so obvious" things?

[dmitri]

This is one of the way it can be implemented. The main task will be to find enough free clock cycles to do it reliably and not to effect any other functionality of MegaDrum, then test it and integrate it with MegaDrum menu. As I said I will look into implementing it as I don't see it to be very difficult (if MCU performance permits). Hurrying me up by just bringing this topic up again and again won't help here:)