From the original SynthMaker forum (2004–2014), with its members’ names and dates.
nix ·
Hey,
I had another bash at a midi sequencer recently and was surprised to find it works! ie. timing is workable even up to 300 bpm(as fast as I have tried). You may have caught the thread in help.
Here is version 0_1->
Here is a kick played with it and the same kick played with Orion drumrack after 5 min @ 300 bpm->
Here is the audio->
http://www.sendspace.com/pro/dl/6lodb3
No railroad tracks
Please test for me if you like.
It is based in green yet, as the midi events are, so maybe it only works good for me coz my system is quick.
Hope this solves some issues for people, I imagine it could be polyphonic?
Cheers, good health
DigitalWhiteByte ·
HeHe, 😉
I do not know if it happens to me only, but when the last note is played,the first fails. 😮
yep 😀
trogluddite ·
Impressive stuff.
I've only tested on my weedy Atom netbook, so far (30% CPU, very low for an SM schematic) - and apart from dropouts when using the GUI, the sequence stays pretty stable, I can see why it would be tight on a decent quad core.
Definitely the best performance I've seen yet from a 'Green' sequencer - keep up the good work!
nix ·
Oh yeah DWB,
I noticed that too. Will try for a fix.
That's great it doesn't entirely go to pieces on a weedy(heh) system.
Thanks for the encouragement 8D
I'll maybe try polyphonic and vector gui in time.
Also like 64 pattern slots and a way to sequence them perhaps.
+ arp hmm.
We'll see 🙂
ohmanwhat ·
Hi..
It seems there's something wrong with the note off mechanism.
It will work (i.e. turn off sound) only if it will come immediately after the same note on.
No idea why it's like that.. I have tried plugging the seq into a synth, waveplayer, anything... with the same result.
However, it's not a SM bug since using a midi input (rather the seq) follows the midi spec.. that is, any note that was turned on can be turned off in a later time.
Anyone got an idea?
Thanks!
nix ·
Here is a fix for the last note/first note problem->
Here is a screen of the interface->
Hey ohmanwhat,
I think what happens is the midi event forgets what notes have been played. if you trigger note on 60, and the note on 72, 60 will hang. The on/off must follow each other. I think it's the behaviour of the midi event module.
Cheers folk, best
PS- added transpose
ohmanwhat ·
Hi nix thanks for the reply!
I'm just a SM tryout noob and might be babbling (and if so then please forgive me) but from what I understand the inside of the seq is split to two triggers, one for note-on and on for note-off. It seems that the note-off is passing the note-on as well. Please look at the pic.
If I'm completely off hook, then please explain what do you mean "it's the behaviour of the midi event module" ?
where's that module? I mean, if I connect a midi-in (keyboard or whatever) then it's allowed to on-60, on-72, off-60, off-72 (60 won't hang) however, if I try to do that with the sequencer, the 60 will hang.
Can you help me find the problem?
Thanks a lot! (and also for your update!)
ohmanwhat ·
btw nix, just checked your update
(and maybe it happens in previous versions too, I didn't notice)
but first time first note doesn't play, does it happen on your side as well?
p.s.
are the midi input and audio output necessary or can we remove them from now on?
thanks!
nix ·
no worries,
hmm
The second midi event module from top is note off. They are parameters 144(note on) and 128(note off). If they are fired sequentially the on/off will happen. If you have a note on, then another note on the first will hang. The triggers are twice from the bool switch. The first (bool true) is note on and the second (bool false) is off.
hmm hope helps
No need to forgive!
I'll up a pic of the midi event, one alternative to using 2 midi event modules is to use 1 and switch between 144 and 128 as the message type.
I'm not sure why a controller would be different, maybe there is some sort of hidden voice management. I'll try it too, I have an old keys controller
The midi and audio outputs are dummies so that you can export as VSTi
Hmm I'll try for a fix on that first note too
nix ·
Here is the fix for first note on->
Cheers
ohmanwhat ·
hi nix.
I think I found the culprit. Here's the old switch:
and here's my suggested switch (probably can be simplified by eliminating the internal switch 🙂)
of course this will only give explicit control over note on (when the triangle is marked) and note off (when the triangle is not marked).
If we want a different kind of behavior, i.e., to note-off the last note automatically when moving to the next slot, then we need to do something else.
let me know what you think.
btw - you can use a midi in with the pc keyboard, no need for a controller to check this (it works the same except no velocity and aftertouch info)
Thanks a lot!
nix ·
hey man,
That's cool it's working for you now, would you like to post your mod so the sequencer can be played by midi?
I'd definitely try it myself.
Cheers!
edit- oops, i think i have misinterpreted what your mod is for. I will try the switch mod you have posted.
nix ·
Is this the mod you were trying for?->
Now the note off glitch is fixed.
The design isn't as elegant, but the performance is the same.
I come back with a screen of the mod.
Cheers
ohmanwhat ·
Hi Nix,
Sorry for the late reply..
I push play button but this time the sequencer doesn't run.
How do you make it tick?
Thanks!
nix ·
Do you have your soundcard selected in the 'ASIO out'? It turns on the mono stream.
That was about all I could think of, I just downloaded and tested the _0_13 version which I have upped here and it work fine here.
hmm let me know if there's still something wrong with it, and I endeavour to fix 🙂
The fix which is in the latest version is just using two booleans per note, one to pass note on and one to pass note off. I found that if you pitched 2 sequential notes differently, the first would hang. So it worked fine when all were note 60, but if you played one 72, the 72 would ring out for the length of env. It's fixed now.
ohmanwhat ·
nix you are right... i blush 😮 i didn't turn on the asio out.
I found 2 more challenges for you 🙂
1. when stopping the seq, it will play the first note if it's marked on
2. if first note is not marked on, on first play, the notes that come first will hang
Thanks!
nix ·
Try this->
Thanks a bundle for testing!
Cheers =))
nix ·
OK,
Here is a hack I made with MAX/msp.
It is a 4096hz trigger, which I understand is about the 30,000 bytes allowed over MIDI.
It should be a lot better now.
If you want to try it you need 'MIDI Yoke'->
http://www.midiox.com/index.htm?http:// ... /myoke.htm
Or MIDI cable with an out and in.
And MAX Runtime->
http://cycling74.com/downloads/
The Runtime is on the right.
Here is the MIDI tick and my DreamSequence sequencer->
So route the MAX patch to the MIDI in in the .osm, and press the speaker and little button.
The MIDI out and soundcard can be set in the MAX patch by double clicking the DAC~ and MIDI out buttons.
The 4096hz should stream now.
It can go faster, but cpu issues.
I own this clock, it is my copyright, so please ask if you wish to distribute it 🙂
Cheers, Nick
MIDI Yoke and the MAX Runtime are free
nix ·
I figured ou how to get max to compile an .exe,
so here is tick 4096hz as app, so you can shell execute on load if wish.
I also found that 'Maple' virtual midi cable works best(ie. it use no cpu).
I think the device use no cpu, it does here. Only have to worry about your application of it in SM.
2 essential modules are integer changed and integer sample and hold. With these you can block the ticks from the rest of the schematic so CPU doesn't soar, and the links don't redline. Bear in mind that this has the capability to use alot of cpu depending on how you apply it, wise to keep task manager up.
Here it is->
http://www.sendspace.com/pro/dl/jpem0i
You need to set the midi out in the toolbar dialog only once. Just make the one you want to use 'a'.
Cheers
I'll be back with a poly midi seq later today prolly(.dll) 🙂
AngularMomentum ·
I was able to test it now on a laptop and on my main DAW, and on both I have severe timing issues. Also the notes do not play the length correctly. With interacting the timing issues are bigger, or even notes dropping. Tested both on ASIO4ALL, EMU ASIO and Direct X on a Turion 64 x2 and a Phenom2 920 x4, I might be able to test tonight on my Q6600, this one has the fastest GPU. Although the timing issue becomes smaller with ASIO, it is very apparent. I love the sequencer setup, it looks very promising.
aliasant ·
Im not sure why you guys keep persisting?
I am working on an Arp / Seq that works perfectly fine in poly. Timing is perfect.
nix ·
Oh OK AM, damn.
Hmm, it work at very high bpm here flawless. Like 300 again.
Hmm, I have intel quad 3.
Aliasant, it is a midi quest, i guess.
I would like to alleviate SM MIDI timing issues with MAX, and work in my preffered environment, SM.
Yeah, I have sample accurate timing too in stream. So quick!
Glad you like the sequencer build AM, I pm you my poly one.
hmmph,I am dissappointed that the MAX device does't perform on other's systems.
I dunno I think what to try to replicate the killer performance I have here at your end, AM among.
Cheers nonetheless 🙂
trogluddite ·
He he he, that's very close to being on-topic ...
Nixon wrote: Searching for cheap car hire from Avis, Budget, Europcar, Hertz and Thrifty. Book online - No hidden fees
...well, close for a spammer anyway!
But taking Nix's name in vain is really below the belt! 😠
Maybe I invoked the wrath of the 'bots with my comments earlier today?... 😉
infuzion ·
Thanks for keeping SM-land bot-free Trog!
nix ·
Yeah, that's funny trog!
'Thine botteth shalt not take my name in vain!'
Wrote something here? To have a post removed or your name hidden, write to [email protected].