piz midi plugins (windows/linux/mac)

[insertpizhere]

i really like the simple lfo... its great and i think i wont even need a more complex one....

just one detail that i miss a lot, so i can delete all the other lfo plugs:

-there should be more triggering modes (that dont depend on midi notes) .... it could be triggered / synced to bar start (like the lfo in z3ta+ or psp nitro) .... then using the phase knob you could sync any lfo phase to the bar start

i'm planning to let it be triggered on bar start. i guess that would be enough to keep it mostly in sync.

another important thing are the synced freqs... 2 Bars is not enough....sometimes really slow modulations are required..... 8 bars ?... 16 would be nicer though... eheh

no problem, i'll add more long sync modes.

ive also found a problem while using ext1 .... when i open the simplelfo gui in ext the plug stops sending cc msgs... maybe this is related to the fact that ext1 has problems with vst plugs which are guiless... (the problems ive found in most guiless vsts is that the native gui is not refreshed when you load presets or automate the plugs parameters)

edit : the above testing was done in the vsti version of ext... i dont know if it behaves the same in the standalone version....ill have to check

i only tested it in the standalone, and i haven't experienced that problem. it could be my fault though. i'll check it in the vsti version... i know energyXT 1.4 does have problems with updating the parameter displays (XT2 is much better about this), but i don't think that should stop it from sending out the CCs...

also...it would be nice if the phase values were shown in degrees

all right. not radians?

[insertpizhere]

ok, i added a "Bar Start" trigger setting to the LFO, which might be kind of weird. in "tempo" mode it will retrigger on the selected beat division. in "Hz" mode, it'll retrigger every bar. the weird part is that for saw and ramp waveforms, it stops after one cycle, even if it's longer than one bar, and then waits for the next bar before it starts again. this is an experiment. i could always add more options, but this is supposed to be the simple version... i think if anyone needs stranger triggering options than this, they can trigger it with midi instead.

if you adjust the phase, it won't change until the next time it's retriggered, except in "free running" mode, where changing the phase will cause the LFO to be retriggered (i don't know how well that will work, but it didn't used to do anything).

also added 3, 4, 8, and 16-bar sync modes and changed the phase to display degrees (to do: make it easier to get 90, 180, and 270?).

it should now work with other time signatures, if the host reports it correctly. it doesn't seem to work in energyXT 1.4.1.

[Optomadic]

piz hows about a simple & quick MIDI note looper..

fs:
Sync to host tempo
Selectable bar record length
Play and Stop button (stop button actually stops cycles)
Either autostop,autoplay or (maybe) dub record after length
Reset button to clear recording
(Possible but not essential) save recording to file

I've tried one called MIDIzoid looper but it does not sync properly. The dev says it's more of a delay than a recorder. arrggg..

Can you help with this?

[maki]

piz hows about a simple & quick MIDI note looper..

fs:
Sync to host tempo
Selectable bar record length
Play and Stop button (stop button actually stops cycles)
Either autostop,autoplay or (maybe) dub record after length
Reset button to clear recording
(Possible but not essential) save recording to file

I've tried one called MIDIzoid looper but it does not sync properly. The dev says it's more of a delay than a recorder. arrggg..

Can you help with this?

this one exists and is called MidiPart in EnergyXt 1.4 and midilooper in Bidule. What we do not have is a midi looper that does buffer lenght quantization on bit or bar and midi controll of recording start and stop. This would be good inovative tool for liveperformance.

[Optomadic]

Yea I realise it can be loaded in another 3rd party app! I was just looking for something real real simple like.. Buffering the length buffer and ctrl of start stop would be other essential feats Insertpizhere you up for this ?

[insertpizhere]

it would be a great thing to have. since energyXT1 and Bidule aren't available for Linux, someone should do it anyway. i'm going to add it to my list. if you feel like it, explain exactly what it should do, and how you would control it.

[insertpizhere]

i updated midi2qwerty. now you can access any key on the keyboard (US English keymap, anyway), even in XT2, and you can make it respond to a CC value of 127 or 0.

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

[-PIKU-]

regarding midi looper... i used phrazor. the star\stop points have to be fixed previously but it's not a big problem for me... i think it is usable live. for each track you can record up to 128 loops with different lenght and they always sync with host tempo, jumping from a clip to another is very simple. the midi data can be quantized live.

it can be of inspiration for a future live midi loop recorder\player

sonicbytes era2 is very good but with fixed loop lenght

[Optomadic]

Has Phrazor been discontinued?

[-PIKU-]

yes... but the actual version works well

[Optomadic]

arrg.. So how would I go about getting my hands on it now.. Just to try this out??

[soma]

Holger is working on Kore now as far as I know. Can't wait to see what he does with it.

[-PIKU-]

some ideas for a midi loop live tool:

loop lenght: it is selectable with a slider or menù. if a specific mode i on the loop lenght is automatically cutted when record starts and stops (some options about the quantization of this cutting can be added)

many loops can be recorded and stored in memory. so those lopps can be triggered and played in various ways. i really like the pattern triggering of sonicbytes era and liveslice.
using era2 with a touchscreen is the same of using a hardware groovebox seq!!!

two or more loops can be played together and can be sent to different midi ports(is it possible with vst3??) or to different midi channels.

different loops can be organized in groups. every group has color. it can be choosen if one only or more loops can play together or the next triggered loop stops the previous.

trigger mode: in phrazor and era2 when you change loop it does not start from the beginning, but plays the portion of loop that is related to the host tempo. it could be set as an option. loops could be triggered with theyr start point aligned with the trigger... loops could be used as arpeggio patterns.

recodr mode: overdub or replace. a nice idea is an automatic loop slicer... il i press recors and a lenght of 4 measures is set, the seq continues to record and every 4 measures it saves a loop in memory.
if you stay without playing anything no empty loops are stored.
i think that 127 as maximum recordable loops could be sufficent but this value could be increased.
all the recorded loops could be stored in a slot with infinite positions, with a scrollbar(similar to the piz midimonitor one).
they can be selected one by one or in groups pressing ctrl, then deleted dragged, copyed and so on...
right click on loopname to access play options and various others... the loops can be dragged from that slot to the live triggerer(era2 like but with piz pads!!) where i can associate lopps to external midi triggers (midi channel 16 could be reserved to that use) and organize them in groups (drum,synth,sampler...)

autoquantize: phrazor like.

edit pianoroll wiev: phrazor like but resizable, it can be used live with a touchscreen.
the interface has to be as accessible as possible, with resizable elements and selectable colors. it was great to use the energyxt seq as midi editor... dragging loops from this plug to the ext seq and viceversa...

[Lagrange]

many loops can be recorded and stored in memory. so those lopps can be triggered and played in various ways.

This seems like a good idea! Maybe a bunch of buttons from 0 to 9.

two or more loops can be played together and can be sent to different midi ports(is it possible with vst3??) or to different midi channels.

different loops can be organized in groups. every group has color. it can be choosen if one only or more loops can play together or the next triggered loop stops the previous.

A tad complex for a simple plugin. Maybe eXT would be better for this level of complexity..

L

[Lagrange]

Guys, heres a mockup of the SML plugin. Piz I'll add more specific info soon...



Let me know what you think plz!

Thanks

L