piz midi plugins (windows/linux/mac)

[soma]

i fount it very useful in general. and primarily for live applications.
i would like to find a way to
to improve the quality of life in studio work
to save precious seconds for common operations
without loosing instinctiveness

Never take your hands off the keyboard unless you have to. Then beg and plead for that function to get a shortcut
that's my strategy.

[-PIKU-]

regarding midi looper: 2
user frienly interface: ok, but the plug has to be flexible and comlete... not the last childish useless plugin
live usability: only 10 patterns, ok but ad a 11th pad to allow infinite recording with autoslice. so infinite loops will be created (the lenght can be fixed or decided by midi external triggering of rec\stop function), numbered\named and stored. those can be accessed, played and dragged to the main pads if wanted. a little box with scrollbar will contail all the recordings

midi drag and drop: to use midi collections like "groove monkee", to drag midi loops direcly to a midi seq like se energy xt seq. so there is no need of a pianoroll to edit loops.

*autoquantize option.

--- different record modes can be choosen with simple visual symbols.
*fixed lenght record - with a slider to choose the lenght value

*midi triggered lenght -good for live using pedals or others

*autoslice mode - the recording continues and autoslices loops whose lenght can be fixed or midi triggered (first trigger=start record, second trigger=sets lenght, then the utoslice will continue to create loops nd store them in memory)
if the poor number of 10 main patterns is increased to a minimum of 16, the autoslice could be used to record in the main patterns. so it will be easy to choos the better one and save it (i think not only to live but even to studio work)

* replace\ovredub, if i continue to play beyond the end, the notes will be recorded on the same loop. if i record a cc motion over a midi note loop in overdub, it will automatically replace the same cc on the recording...

--- anyway, the most important point for me are:
autoslice of a continuous recoring
controllable rec\lenght\stop
midi drag&drop to\from ext editor or another plug instance!

[Lagrange]

not the last childish useless plugin...

If you were referring to my mock up, its just a simplified outline with no GUI.

that looks good to me. if i do it, it'll be simple like this....

Piz seems to be ok with it.. I was just adding my input and trying to help out here.. Not just sitting around making a bunch of demands on the dev and expecting him to lay a golden egg .

L

[insertpizhere]

well, i want it to be simple enough that i'd want to use it live, but hopefully all the useful features will still be there. the way i'm imagining it, it works out great... i think i'll be ready to start working on it soon. maybe i'll write up my plan for this and post it here sometime.

[maki]

regarding midi looper: 2
user frienly interface: ok, but the plug has to be flexible and comlete... not the last childish useless plugin
live usability: only 10 patterns, ok but ad a 11th pad to allow infinite recording with autoslice. so infinite loops will be created (the lenght can be fixed or decided by midi external triggering of rec\stop function), numbered\named and stored. those can be accessed, played and dragged to the main pads if wanted. a little box with scrollbar will contail all the recordings

midi drag and drop: to use midi collections like "groove monkee", to drag midi loops direcly to a midi seq like se energy xt seq. so there is no need of a pianoroll to edit loops.

*autoquantize option.

--- different record modes can be choosen with simple visual symbols.
*fixed lenght record - with a slider to choose the lenght value

*midi triggered lenght -good for live using pedals or others

*autoslice mode - the recording continues and autoslices loops whose lenght can be fixed or midi triggered (first trigger=start record, second trigger=sets lenght, then the utoslice will continue to create loops nd store them in memory)
if the poor number of 10 main patterns is increased to a minimum of 16, the autoslice could be used to record in the main patterns. so it will be easy to choos the better one and save it (i think not only to live but even to studio work)

* replace\ovredub, if i continue to play beyond the end, the notes will be recorded on the same loop. if i record a cc motion over a midi note loop in overdub, it will automatically replace the same cc on the recording...

--- anyway, the most important point for me are:
autoslice of a continuous recoring
controllable rec\lenght\stop
midi drag&drop to\from ext editor or another plug instance!

Yes, this is how my Christmas Wish List looks like!

[-PIKU-]

Piz seems to be ok with it.. I was just adding my input and trying to help out here.. Not just sitting around making a bunch of demands on the dev and expecting him to lay a golden egg .

i don't makea bounch of demands... i try to explain my concept. there are only two demands: autoslicing and drag&drop midi.

midipads is very simple, but even flexible! it can be used as a live midi controller, mixer, converter\remapper.

i like your layout for the midi-looper. i only hope that it will be useful for many applications, not only for live. "childish"is referred to midizoid looper an things like this

[insertpizhere]

another update to the simple LFO:

now when in beat sync and tempo mode, it'll hopefully always be right, even in weird time signatures (for example, in Reaper, i tried it with a time signature of 83/45). it won't wait until a bar starts to be in phase.

i also renamed the beat-based frequencies. anywhere it said "beats" before was actually quarter notes, which is not always equal to the beat length. if anyone needs frequency in beats which will correctly follow time signature changes, let me know... i don't know which (note values or beat divisions) is musically "better," so i just picked the easier one.

anyway, i think this is done now, unless i find more bugs.

http://thepiz.org/xt/midiSimpleLFO20071026.zip

[Optomadic]

Thanks piz will try now..

[-PIKU-]

midipads- could you add an option switch to make the plugin window not to stay always on top?
sometimes it's not wanted, like in cubase\nuendo docking

[runagate]

My "touchsreen player" and I had a lot of fun with GUI imagery last night.

She

1) doesn't know PCs, just Mac

2) had never seen a VST

3) hasn't the slightest idea what most DSP terms mean (flanger, for instance)

But we're making great headway in explaining things to one another. I have a real keyboard player, too, but I'm really interested in getting people who haven't the slightest idea of any electronic instrument involved in "all you need is creativity" sort of involement in music. Always have, and now it's pretty feasible.

She went off to ponder weird GUI knobs, sliders, X-Ys, etc.
She makes some seriously friggin' weird band posters for groups around here, too.

[maki]

It's about midi looper...
I have been thinking about what was written before and everything looks fine. I am glad that Piz is interested so I will just put a new demand because before or later this is going to be an isue (and has been an unforgettable issue last 15 years, since Zyklus MPS disapeared).
I am thinking about many, many patterns istead of just ten. I am thinking about a database with 16 SONGS of 16 PARTS and 16 PATTERNS per PART. In addition I dare to suggest that every of those 16 patterns per PART can be recorded and playedback in its own midi channel and that individual PARTS and BANKS can be loaded with just one controlltrigger on a midi controller.
Yes, this means a multitimberal midi looper with 4096 midi loops and an extra computer keyboard on the desk to serve as a midi controller! Maybie this sounds complicated but actually it is necessery for following setup:
In "live" situations while playing with more than one midi master keyboard a musician should be able to record several midi loops on his midi keyboards and all those loops together should be treatet as PARTS of a SONG: intro, strophe, refrain, variations, different fill-inns and ending. It is expected that an live performer could need place for 16 SONGS to preload on
stage.
A separate computer keyboard or even better, something like x-key 128 keys device could be divided in 16 vertical collumns and every of its 8 keys could be hardware triggers for different commands in midi looper while existing computer keyboard could be used to call differnt PARTS and SONGS.
http://www.piengineering.com/xkeys/xk12884.php

Many possibilities with something like that. I have even more ideas but I would be very happy if Piz makes just the simple midi loper described earlier in this thread.

[insertpizhere]

small midipads update:

- now you can put an fxb named "midipads.fxb" in the same directory as the dll, and it will be the default bank when you load the plugin. the included one is the same as the built-in bank, but the first preset is brown.

- increased the number of programs to 32

- fixed a bug where if you had more than one copy of the plugin running, a random number of pads would be triggered when you opened the GUI.

http://thepiz.org/xt/midi16Pads20071027.zip

[runagate]

The link is broken, piz.

And what a strange bug. Sounds kinda fun.

Great idea for the default bank.

[insertpizhere]

you must have downloaded it while i was uploading it again... i increased the number of programs and re-uploaded.

[runagate]

Hmm that bug gives me a really fun idea for a Usine patch...