PlanetZ forums - scopeusers.com

Hi There,
A new toy to play with.
Its a one note chorder that allows you to setup 12 switchable chords per preset.
If you are like me and do not pocess great keyboard skills this device may be what you are looking for.
I started out to develop a chorder so I could setup guitar like chords, but soon realised it had wider uses.
I have included a short PDF to detail the functionality.
I hope you find it useful.
regards
maus

Wow...yeah!!!!!!!!!!!!!!!!

Very nice

Thanks Guys
There is a couple of things I would like to do but haven't figured how to
- Delay the midi to various notes so we could get a kind of strumming effect; and
- Adjust the velocity of individual notes. This would mean extracting the velocity data from the incoming midi note and then reestablishing the midi data for delivery to each note. Not sure this can be done.
maus

i am not sure how you create the midi events there are several possibiliries but you can use a normal dsp delay line inside an async path to achieve delayed event creation. There is also an async delay module that can be used for simple synchronization of events. velocity can also be controlled when you create your midi event. I will upload a midi module in sdk project form to get an idea of some ways to implement this. -in a couple of days

A midi note on/off button. Here is the sdk module.

Thank you fra77x2,
I will have a play with this module to see if I can achieve something useful.
Your SDK videos got me started with SDK a few years back.
Always been grateful for the tips and tricks I learnt from you
regards
maus

You are very kind. Thanks.

reminder:
There are two types of async modules some of them share the same name like "and", "add" etc.
The ones that are located in the sdk "circuit design" folders are computed on the CPU of the system. Use these only for display /device panels purposes. The ones that are located in the dsp list are computed on the DSPs. These should be used for control signals.
You can resave the dsp modules in a folder easily accesible by adding the module from the dsp list into the project and the saving it with right click / save as module function. If you look at the "module parameters" panel you will see that the modules that are computed on the DSP's are displaying dsp id/ load information but the modules that are computed on the CPU do not.

by using the "async" modules located in the sdk dsp list, the control path is computed on the dsps providing control parameters timing accuracy. Scope hardware midi will retain this accuracy.

Thanks again fra77x2 very useful information
regards
maus