MIDI modules

Fpr my projects, I need to develop some MIDI modules. They are like: external MIDI In/Out, MIDI to CC and CC to MIDI, (N)RPN to and from MIDI.
If someone else is also interested in such modules, please make suggestions (like 1 Module for cc/RPN/NPRN), or 1 Module for CC, with all ＣＣｓ as array. At the moment nearly anything is possible.

a simple midi keyboard would be great , the default one have hanging note issue

Hi I would like to to have a button or two or 10 where I can fire a few Midi commands. A button can be programmed before with one or a whole bunch of Midi commands.

With this little Midi device I could control e. G. My Hardware devices. My FX machine fire a program change #78 or a synthesizer k5000 e. G. Midi channel 5 bank 4 program number 96.

Each Button can be named. And the whole device can be named so it could be used as a group.
The type of command can be easily selected for none programmer persons

Guitar players could use this as a floorboard substitute. Means easy programming of there real floorboard, they fire from their hardware floorboard one command into scopes new Midi device e. G. Program changes #34 and the new Midi button is translating this into a preprogrammed bunch of Midi commands, e. G. Preamp program change #5 on Midi channel 7 and FX machine program change #65 on Midi channel 3 and a program change on Midi channel 9 to a scope mixer number 3 to set the mixer into recording mode. The button can use scopes Midi learn function for remote control.

This device could also be used to recall stacked synthesizer sounds, e. G. 3 or 4 scope synth or external synths recall presets as one sound with one button in your project. Or combinations of synthesizer mixer and FX settings to experiment with different stacksounds.

The possibilities are endless.

The device could have 2 or more programmable Midi inputs and outputs.

The device could be dynamic, adding buttons or killing and build them into groups or ungroup them again. . Colorize the way you want and having a good overview.

If you need a graphic designer, ask me.

a midi kill or "all notes off" switch would be nice.

Hi I would like to to have a button or two or 10 where I can fire a few Midi commands. A button can be programmed before with one or a whole bunch of Midi commands.

With this little Midi device I could control e. G. My Hardware devices. My FX machine fire a program change #78 or a synthesizer k5000 e. G. Midi channel 5 bank 4 program number 96.

Each Button can be named. And the whole device can be named so it could be used as a group.
The type of command can be easily selected for none programmer persons

Guitar players could use this as a floorboard substitute. Means easy programming of there real floorboard, they fire from their hardware floorboard one command into scopes new Midi device e. G. Program changes #34 and the new Midi button is translating this into a preprogrammed bunch of Midi commands, e. G. Preamp program change #5 on Midi channel 7 and FX machine program change #65 on Midi channel 3 and a program change on Midi channel 9 to a scope mixer number 3 to set the mixer into recording mode. The button can use scopes Midi learn function for remote control.

This device could also be used to recall stacked synthesizer sounds, e. G. 3 or 4 scope synth or external synths recall presets as one sound with one button in your project. Or combinations of synthesizer mixer and FX settings to experiment with different stacksounds.

The possibilities are endless.

The device could have 2 or more programmable Midi inputs and outputs.

The device could be dynamic, adding buttons or killing and build them into groups or ungroup them again. . Colorize the way you want and having a good overview.

If you need a graphic designer, ask me.

Interesting ideas. One question: do you know how to add/remove pads dynamivally? AFAIK pads are allocated at the module loading time and can't be changed. I can't use PEP, where it seems to be possible. Do send a stream of MIDI data, the MIDI data can be stored in an ini-file and picked up at run-time.

Im not a programmer, Im a musican, I can play several instruments, but no I dont know how to make it dynamic. Maybe it is good enough to have a set of dev.modules e.g. 5 Buttons or 10 Buttons, I guess this is the easy way.

Hi, Dragon !

I hope you feel fine and have good succes with Scope development !
I imagine you are working on some Scope devices and by reading your posts on Z, I guess they are going to be unique and special !

I also hope you found a solution to all the issues with your device development and SDK...

Do you know when we, poor Scope users, will discover the result of your hard work ? On what kind of device are you working on ? You don't have to answer if you prefer to surprise us !

I'm impatient to try that !

Cheers !

I have different projects in the fire, but regarding MIDI, I'm working on:
- ext. MIDI-IN and out
- convert MIDI-CC into control voltages and vice versa
- same for RPN and NRPN values
- MIDI keyboard (virtual) with options like you have on a real MIDI controller (sliders, knobs, pushbuttons) etc.

Regarding real Scope work, I'm waiting for the Dongle. I working on a multiple harmonics generator (resynthesis). The current device usess too muich DSP power, only 2 voices are available. With a new DSP osc design, I'm expecting at least 4 voices.

Nice to hear.

Great !

Hi, a bit late to reply but for midi, an easy way to handle MPE

looking forward to the new devices

Excellent idea as MPE is really starting to mature.
Not into the Roli stuff, but Continuum and Lin are grabbing my attention.

Hi, a bit late to reply but for midi, an easy way to handle MPE

looking forward to the new devices

So, here is the 1st device: MIDI to CV, 16 CC values can be handled with teaching button: Press the button, apply up to 16 different CCs and press button again. The state will be saved, so next time, you don't need to teach again. The ini file will be automatiically generated in the app directory. The dll goes the usual dll dir (for ex. C:\Program Files\SCOPE SDK XITE\App\Dll). You need the VS 2013 runtime dir too (https://www.microsoft.com/en-us/downloa ... x?id=40784.
Example pro (incl):

midi2cv.png (60.2 KiB) Viewed 9308 times

At the moment, only one instance is useful. If someone needs more than one, just reply and ask for it. I might have an idea, to make each module unique.

Looks great!
Can you give me an example of how I would use this ?
What's it's purpose?
Sorry but I'm not familiar with CV stuff.
Just wondering if there's a use for me in my setup that I might overlook.
Thanks and keep up the great work.

Looks great!
Can you give me an example of how I would use this ?
What's it's purpose?
Sorry but I'm not familiar with CV stuff.
Just wondering if there's a use for me in my setup that I might overlook.
Thanks and keep up the great work.

If you got a MIDI keyboard controller, it might have some CC controller as well (buttons, sliders, pots etc). If any of these can produce CCs (Continuous Controls), you can use these outputs to control any potentiometer in Scope. It can be volume, frequency, time - whatever comes to mind. AS exmaple, you can control the frequency of a LP Filter like a Wah-Wah from your keyboard. If you keyboard controller allows a foot pedal: her you have your wah control connect the Midi2CV out to the LP Filter F control, push the T button, move the pedal, push T again and you're done.

Looks very interesting, and thanks for the example use. I look forward to trying this out, and congrats on your first device.

Wow, DragonSF, great device!

Is there any filtering or interpolation to smooth 7bit MIDI to 32bit CV?

Wow, DragonSF, great device!

Is there any filtering or interpolation to smooth 7bit MIDI to 32bit CV?

I can do that. But you'll always have a step, because there is no in-between state. Value is either 54 or 55, but never 54.6. On the other side, if you have an idea, I'm open to suggestions. Another way would be using 14-bit (N)RPN input. I can do that too.

A new module: external MIDI IN. If uou encounter note-hanging, push the off-button. To selct the Midi In device, push show and select the device from the combobox. Enjoy!

ext midi in.png (20.4 KiB) Viewed 9196 times

If you encounter hanging notes, please tell me. There is a speed limit within Scope, which gives problems at BPM > 160. I might need to increase the buffer.

Thanks for the explanation but I'm still puzzled.
I understand cc assignments so what's the difference when you use midi in, on a synth and assign cc's normally under scope.
Is this for modular?
Or are these sdk modules for developers?
Sorry for my ignorance.

I can't understand it too, I have no idea why cv

CV comes from the analog world. It's just a value, to control anything instead of a pot. And yes, all these modules are for SDK.

Ok got it!
So with this module could you not implement something in a mixer to maybe have osc
Hui, Mackie control for scope?
Just a thought
Thanks for your efforts in keeping the platform alive with new modules, ideas.

Ok got it!
So with this module could you not implement something in a mixer to maybe have osc
Hui, Mackie control for scope?
Just a thought
Thanks for your efforts in keeping the platform alive with new modules, ideas.

There are no implementation limits: wherever there is a pot, you can replace it with one of the outputs. Even switches should work (think of pads).

Top stuff, a real boon. Thank you

Wow, that midi in idea deserves a device, that's HUGE. No need for routing through a DAW just to get midi into scope anymore!!

Wow, that midi in idea deserves a device, that's HUGE. No need for routing through a DAW just to get midi into scope anymore!!

And no more Midi-Ox fiddling. And you can have as may MIDI-Ins as you like.

Wow, DragonSF, great device!

Is there any filtering or interpolation to smooth 7bit MIDI to 32bit CV?

I can do that. But you'll always have a step, because there is no in-between state. Value is either 54 or 55, but never 54.6. On the other side, if you have an idea, I'm open to suggestions. Another way would be using 14-bit (N)RPN input. I can do that too.

But when you convert midi --> CV a lot of values can be added between 2 CC values, no ?
On the other way, I understand there is no reason...

Looks great!
Can you give me an example of how I would use this ?
What's it's purpose?
Sorry but I'm not familiar with CV stuff.
Just wondering if there's a use for me in my setup that I might overlook.
Thanks and keep up the great work.

Have a look at Expert sleepers Silent Way : a collection of vst's that generate audio rate modulation signal you can use inside Scope via asio. And you'll use digital CV signals ! No more midi jitter ! Amazing possibilities !

Dragon !
The ext. midiinput looks really useful ! I hope you'll release it as a module...!
When I load it into my Xite, I don't have any gui ! .... .... I guess you are still working on it ...

Dragon !
The ext. midiinput looks really useful ! I hope you'll release it as a module...!
When I load it into my Xite, I don't have any gui ! .... .... I guess you are still working on it ...

Actually, I wanted to finish the basic stuff =SDK device)first, but in that case, I'll make module.

Actually, I wanted to finish the basic stuff =SDK device)first, but in that case, I'll make module.

This is a great development, looking forward to this very useful module. Many thanks

Excellent ! Computer soundcard driver are available in Scope (but doesn't always work perfectly...) and now, we are going to be able to choose any mini input directly in Scope !

Dragon, you're making very inovative stuff ! Great !

Do you think it would be possible to make a midi delay ?
I believe it doesn't exist as far as I know... Not even a modular module.

A simple device that delays all midi data on its input with time settings, of course ! Let's say ... Hhhh ... Up to 1s maxi !?

This would be useful for sending exactly the same midi CC modulation to any other parameter but with exactly 150ms delay..!

It's not device ideas I miss but rather time to build them..!

Dragon !
The ext. midiinput looks really useful ! I hope you'll release it as a module...!
When I load it into my Xite, I don't have any gui ! .... .... I guess you are still working on it ...

Some obstacle is happeing here: As soon as I make a module or putting the device into a surface, I can't connect the MIDI out anymore (and this is not my MIDI-out, it's the MIDI-out of a standard Scope module (Fifo to MIDI).

ArrrGh ! Very unfortunately, I can't help you at all about this !

Maybe some other developers could ?

Or you could ask on the sdk forum, I'm not sure it's pretty busy...

So ... This message is absolutely useless for you.... Hin hin .. Sorry !

ArrrGh ! Very unfortunately, I can't help you at all about this !

Maybe some other developers could ?

Or you could ask on the sdk forum, I'm not sure it's pretty busy...

So ... This message is absolutely useless for you.... Hin hin .. Sorry !

Thanks for recognizing my problems. I think the only one can help is Holger. But maybe I find a way around.

Dragon,

Can you include support for polyphonic aftertouch/pressure?

This is a very neglected aspect of MIDI. Especially useful with Modular.

Eric

Dragon,

Can you include support for polyphonic aftertouch/pressure?

This is a very neglected aspect of MIDI. Especially useful with Modular.

Eric

My MIDI modules are completely transparent. I just pass everything the driver supplies to the output (with some clever buffering of course ). But nothing is filtered out.

thx+bookmarked

a suggestion: maybe put such atoms in their own topic? maybe in a bundle, and a descriptive topic will make them a lot easier to find! i've only now stumbled across this topic, for example. and i'm sure many SDK users do not sift through every post to find such additions..
cheers, and thanks for those!