SynthMakerbillv ·
How can I trigger a note to stay on? In other words, I want to simulate the user holding down a note.
Trigger a note to stay on?
From the original SynthMaker forum (2004–2014), with its members’ names and dates.
Xtinct ·
Hi if its just one note try the AHD with a long H eg. 1 gives about 5 secs hold so 1000 is about 83 mins and so on.
tester ·
Check and modify the LED switches in SM toolbox. They switch between 0 and 1 when clicked, thus - you can get your sustain.
Xtinct ·
Heres one for a mono stream hope it helps
billv ·
Xtinct wrote: Heres one for a mono stream hope it helps
That's interesting. Will muck around with it. But need this to happen in the midi section. I need control over note selection as well.
tester wrote: Check and modify the LED switches in SM toolbox. They switch between 0 and 1 when clicked, thus - you can get your sustain.
This was the first thing I tried. Modifying a push button so it just rings true, then connecting to "Note Event". Didn't work. Am I putting it in the wrong place?
Xtinct ·
The midi parts not the problem its the gate time, and the only solution I have found is using a mono envelope that I thinkTrog produced (sorry if not 😊 ) its a wonderful module that can be altered to many different uses like being triggered by LFO, looping itself and having the gate set to on. I'm not at my SM computer now so I can't upload but I'm sure a bit of searching will turn it up. Edit just checked and it was Trog it was part of his GRRRrrr synth download/file.php?id=4699 Edit 2 ignore all that I think you still have use mono streams or the AHD route for it to work. If only we could recreate the -1.#QNAN that the gate puts out, surely its not that difficult or maybe it is and don't call me shirley 😉
oddson ·
Note Event needs a duration after which a note off is issued.
If you want a switch to that sends note on and note off try this:
billv ·
Perfect. Exactly what I'm after. Thanks a lot. The numbers 128 + 144 ? I'm presuming they are Standard midi messages. Will look into those variables later and see what else they can do. Thanks again.
oddson ·
billv wrote: The numbers 128 + 144 ? I'm presuming they are Standard midi messages.
128 = note off 144 = note on
SynthMaker uses the byte value for each event type for the first MIDI channel. * Note Off = 128 * Note On = 144 * Aftertouch = 160 * Controller = 176 * Program Change = 192 * Channel Pressure = 208 * Pitch Wheel = 224
In the rest of the MIDI world the event ID and channel value are two 'nibbles' of the same 'byte' of data.
Here's the MIDI reference in the WIKI for the MIDI Event/MIDI Splitter [old link] (It's for the splitter but the 'event' and 'splitter' use the same conventions.)
In 'real' MIDI 'note off' events are 128-143 or in hexadecimal x80 to x8F but in SynthMaker the channel 'nibble' is excluded so the event types are each 16 integers apart.
If none of this makes sense to you don't worry - it's actually easier just to take the SynthMaker numbers as given and learn MIDI later (or not). 🙂
billv ·
Thanks mate. That's a whole new language for me to look into when time allows. Cheers.
Xtinct ·
Nice one oddson any idea why I can't have more than one of these eg. set up as above and used a LFO to trigger so far so good copied it set different note number and different speed connected up to different osc looked at the output and it had added the note numbers together and triggered at the same speed 😕 any clues?
oddson ·
Xtinct wrote: Nice one oddson any idea why I can't have more than one of these eg. set up as above and used a LFO to trigger so far so good copied it set different note number and different speed connected up to different osc looked at the output and it had added the note numbers together and triggered at the same speed 😕 any clues?
I'm not sure I understand the question... typically if you're adding LFOs you're not connecting them to the frequency info coming from the MIDI2Poly, they're connected to the poly stream that's initiated by a M2P but only from the right-hand-side so they start up when the poly thread for a given note does but the rate of the LFO isn't affected.
More often people are looking to disconnect the LFO from the poly thread so they become free runnings. Search 'free running lfo' if that's what you're after.
Xtinct ·
Hi oddson osm's are so much easier so have a look at this.
Xtinct ·
Solved if you use a seperate amp and combiner for each osc it works. I'd still like to know why but it can wait while I recreate my old soundmaster drum machine. Again thanks for pointing me in the right direction. 😀
attic ·
Thanks mate. That's a whole new language for me to look into when time allows. Cheers.
@billv Just in-case you are going to be looking at the Midi specification a lot this may save you some time. I uploaded this .osm a while back. Look inside you will find a large chunk of the midi spec that you can cut and paste for ease of use.
Midi Spec & Dsp Links Midi Spec & Dsp Links
oddson ·
Xtinct wrote: Solved if you use a separate amp and combiner for each osc it works. I'd still like to know why...
It looks like if you have two M2P modules you need them to connect together in blue and not white or the first of them (whichever is created first) will take over all poly thread creation and the second will do nothing.
billv ·
attic wrote: @billv Just in-case you are going to be looking at the Midi specification a lot this may save you some time.
Got it. Thanks again.
Wrote something here? To have a post removed or your name hidden, write to [email protected].