Can someone build a polyphonic midi sequencer using M3 ?

[musurgio]

I wonder if it can be done with M3 a midi sequencer to drop the cubase just for midi !
I only need to be able to record my midi notes played driving Pulsar only synths
Regards,
Dimitrios

[musurgio]

Thanks.
I have checked.
These are step sequencers.
So I am sure that someone can come up with a killer sequencer where you can record real chords progressions in realtime .
A 16 channel sequencer would be great for a start.
Every channell should be polyphonic and there should be quantizing options too.
An editor would be a must.
Even archaic Commodore 64 had a nice Stenberg Pro16 with editor why not Pulsar !!
Regards,
Dimitrios

[hubird]

If I'm right this is not (good) possible on a DSP based system (as opposed to native).
DSP is realtime and doesn't uses buffers necessory to handle Midi.
Someone will correct me if I'm wrong, but that's what I remember from replies to the same question in the past here
Alas...

[astroman]

...Even archaic Commodore 64 had a nice Stenberg Pro16 with editor why not Pulsar !!...

because it was programmed in 8-bit machine language which is the same format as the original midi data bytes
A DSP can process such stuff, but it's as reasonable as transporting a six-pack by truck - you don't start your car to go to a restaurant just around the corner, though I know Greek persons that would if 'just around' exceeded 200 m...

anyway, there is not a single reason to NOT use native processing on midi - it's about 100 times more efficient (depends a bit on how it's programmed) than Scope processing.
Scope has a very high level of abstraction - which has some advantages.
It allows very short programming times and is MUCH more forgiving than a tradional C environment, as it catches most errors that otherwise would constantly crash the machine.

on the other hand you cannot access arbitrary data at low level (like midi) and you have significantly less control over the GUI.
There are things possible in native programming that Scope will NEVER be able to do, but if it WOULD allow access at that level - which in other words simply means you HAVE TO deal with it, 90% of the (Scope) developers would either give up or fail on it
That is not kidding or dissing anyone - just write your own control of whatever, but don't copy it from an internet page...

If you look at you Scope app folder you'll find a ton of libraries that are written in X86 (or PPC) code - there is no difference in performance of an internal .DLL versus an external .EXE

cheers, tom

[musurgio]

HI,
The main reason is perfect timing.
What if scope took midi notes and turned them in something pulsar oriented that has nothing to do with midi so overcome the above mentione problems ?
I know Samplers use ram for sampepool so could a pulsar sequncer use ram for buffering.
I am not convinced that scope cannot come up with a recorder that will use midi as trigger...
Regards,
Dimitrios

[UsedManateeSalesman]

Not meant to deter your quest at all, but just an observation that I've been thinking about lately: How perfect does timing need to be to be musical? As an example, for all the complaining people do about Cubase SX being so "horribly out of time", last night I noticed that a wave I'd just exported out at 120bpm was playing perfectly in sync over the course of many minutes with the (non-synced) blinking LED on a nord modular (which happens to blink at 60bpm). For me anything beyond that is just wasting time being a technician, and I'm sure that whatever you've got is at least as tight.

Now go make some music.