SynthMaker

BETTER KNOW YOUR TOOLBOX P02 - -=MIDI=-

Archive · 2005 9 old posts

From the original SynthMaker forum (2004–2014), with its members’ names and dates.

skOre ·

The Midi Group holds a couple of modules to get, use, change, filter, create or send midi data.

These are the most used modules, the Midi In, to receive Midi Data, just like receiving Audio Data (samples) from an Audio In. The Midi to Poly creates a Poly Stream that you can use within your schematics. Since oscs are controlled by frequency, you will want to use the frequency output of your MidiToPoly component to let them receive the pitch you provide through your Midi Input. The Midi Out, off course, will send midi data to the device you choose.

Notice that you can choose the Input just like in the asio panel, yet with this, you can select more than one source. You can also use the PC keyboard as a rudimentary input device (you'll figure out the layout yourself 😉)

These modules receive Aftertouch and PitchBend values from the midi connector and convert them into Integrers that you can use in your schematic.

Note that the range in which these are put out is shown at the connector.

The Midi CC is a component that lets you choose a Midi Controller to convert its output into a Synthmaker Integrer. This is most likely used for Midi-Controlling knobs or sliders.

The Midi Split will receive the latest midi transmission and output its data, the Status, the Channel, the CC and its value, as well as a trigger for each new event. Foreshadowing the use of Arrays, you could use the midi split for a simple midi-event table:

(What happens: the data is added into a string - connecting values to a string one after the other will add them into one, I also used commas to seperate the values - and this is given to an array. There is a counter that goes up every time it receives a new event from the Splitter and will reset if the value reaches the set maximum. Connecting an Array to a text field [shortcut: A] will show you the whole array at once.)>>Schematic<<

- Can anybody tell me why I need a new line component here? -

The same way, just the other way round - connect values to its inputs and trigger it to send a midi message.

Again the same as the last one, just designed for Midi Note messages

This is a filter to monitor just one note.

This is the mono equivalent to the MidiToPoly.

Everybody is invited to find typos&errors or provide more indepth knowledge!

Shifrin ·

Just wanted to say nice one 😉

Shif.

Shimmer ·

I'm still trying to get to grips with this program, looks like this could be a big help. Cheers. 😉

angstrom ·

I'm not utterly sure that the MMon is the equivalent of Midi To Poly.

I thought it was more of an R&D voice management module whose name was pulled out of a bag. Note that it is called "Midi Mono" rather than "Midi to Mono" and that it outputs to green data types rather than mono streams.

Waaay back I had a thread where malc stated something about it being mis-named, but didn't really fill in what an appropriate name might be.

skOre ·

Hmm, interesting point angstrom.

I guess from the definition of mono, this surely is a module that gets just the last note and outputs its data. But thanks for pointing me to this, will investigate 🙂

angstrom ·

If it's any help, here's the thread where it was mentioned in passing .. there's probably others

really, really basic question

he component is R&D and as such not much thought has gone into the name yet but it's purpose is to show you the number of voices that are playing.

I am guessing Malc is busy writing documentation himself right now, other wise he might cut in with the answer ...

*cough*

*waits* 😉

infuzion ·

Cool stuff skOre; will def help me get up to speed when I get ready for MIDI things.

BTW, could you provide the schematics you use pretty please? Just 1-2 components are no biggy, but like that array would be handy. Not a biggy; I'm just lazy.

skOre wrote: Can anybody tell me why I need a new line component here?

Seems Array fields are like SQL tables or even database sheets (eg Excel), delimited my a NewLine. So, each row would represent one instance of an item (in this case, a single MIDI transmission), & each column (delimited here with a comma) is an item in such event.

caco ·

Hi skOre

This is a fantastic idea and a great help

Thank you

skOre ·

Schematic added (link above)

Thanks for the comments!

Wrote something here? To have a post removed or your name hidden, write to [email protected].

Before your first post

A few rules keep this a friendly place. You agree to them once.

Shown next to what you post, here and in the app. It doesn’t have to be your real name: 3–24 lower-case letters, digits or _ (capitals become lower case, spaces become _).

    Then your post goes up straight away.

    Delete this reply?

    Open it in SynthMaker?

    It goes on the track you’re editing there, in place of that track’s sound, and into My sounds. Your other tracks stay as they are.

    Want to keep that track’s sound? Start a new song in SynthMaker first (Song › New song), then open this.

    Report this reply?

    Only the developer reads reports. The person isn’t told who reported them.

    What’s wrong with it?

    Block this person?

    You won’t see their posts and replies here any more. They aren’t told, and you can unblock them at any time.

    People you’ve blocked

    Their posts and replies are hidden from you. Unblock someone to see them again.

    The community rules

    A few rules keep this a friendly place. Everyone agrees to them once, before their first post.