see me, promote me! no, really

[xoxos]

i'm glad you moved that file. i want to use these ideas for more complex performance sequencers, it sounds like you get it.

[HiEnergy]

I just transfered my other two circuit demos to soundclick, one with chords and one with drums.

http://www.soundclick.com/bands/page_mu ... dID=563854

Have fun
HiEnergy

[antoine.bertier]

Yet another demo with circuit on drums and miniseries on bass:

http://www.wusiklabel.com/members/82/song_focus_98.php

this time it is not too weird (I think...)

By the way would it be possible to change some parameter via midi CCs ? Here in miniseries I have an lfo on High but the initial value starts at 1 and gradually moves to 4 over time, it would be nice to be able to control it from the keyboard or automate it...

or am I missing something ?

[xoxos]

it's still pretty weird

i generally don't add automation because it seems most hosts apprehend params nowadays.

if you have an lfo at a high rate, it might be ~aliasing with the clock rate.. the lfos go up to ~50Hz so the right side of the rate scale is pretty much for creating harmonic moire-style patterns with the clock. you'll notice if you nudge it slightly you'll get a different output.

also - some of the numeric destinations, eg. increment can be 'counteracted' by the lfo.. if your lfo is at a low amplitude, say swinging from -2v to +2v and your increment value is 1, whenever the lfo is in the -1v range it will counteract the +1 inc value and 'stop' counting. i use the square waveform for these dests, or a high lfo amount to minimise time in the null spot.

[antoine.bertier]

it's still pretty weird

OK, I guess I'm weird that would explain everything

i generally don't add automation because it seems most hosts apprehend params nowadays.

Well I use almost exclusively energy XT 1.4 or 2 so I don't know much about other hosts. But I think midi control is necessary at least the channel mute, and would be nice on the counter parameters.

if you have an lfo at a high rate, it might be ~aliasing with the clock rate.. the lfos go up to ~50Hz so the right side of the rate scale is pretty much for creating harmonic moire-style patterns with the clock. you'll notice if you nudge it slightly you'll get a different output.

I'll try that.

also - some of the numeric destinations, eg. increment can be 'counteracted' by the lfo.. if your lfo is at a low amplitude, say swinging from -2v to +2v and your increment value is 1, whenever the lfo is in the -1v range it will counteract the +1 inc value and 'stop' counting. i use the square waveform for these dests, or a high lfo amount to minimise time in the null spot.

I like the lfo's swinging around a middle value, and I guess I never had them slow enough to be bothered by the result on inc. I'll have to experiment more. For instance on High, the value cannot get below 1 and make the range empty (as far as I can see), so with the sine -2/+2 lfo, and High on 1, it stays on 1 for half a cycle and then goes up to 2 or 3 and back for half a cycle. Then when you increase High the first half cycle start to become less monotone... In the end what I am trying to achieve is increasing High from 1 to 5 over 16 or 32 bars, and having the sine lfo swing around the value much faster.

In any case I'm having fun

[xoxos]

i haven't got eXT 2 yet, i'm sure it's similar(?) to 1.4:

in the top left hand corner of the VST's panel, click [file] > [cc map] > [add]

then 'param' lets you select the gui component to control, and lets you assign a midi cc# to it.

for increment modulation, this (and other releases) are intended to be simple introductions to the ideas, eg. host-synced lfos are a very good idea for all these midi VST, but give the user too much to play with even a 'bias' param on the lfo would help your application. i can't even name another developer that uses 'bias' params on lfos, so for now, that's an "advanced" param.

[antoine.bertier]

i haven't got eXT 2 yet, i'm sure it's similar(?) to 1.4:

in the top left hand corner of the VST's panel, click [file] > [cc map] > [add]

then 'param' lets you select the gui component to control, and lets you assign a midi cc# to it.

Yes it's similar in XT2 (click on the keyboard like icon instead of selecting a menu item). But since there was no mention of automation at all in the documentation I am ashamed to say I did not even try That's a rare case of reading the f.... manual too much !

for increment modulation, this (and other releases) are intended to be simple introductions to the ideas, eg. host-synced lfos are a very good idea for all these midi VST, but give the user too much to play with even a 'bias' param on the lfo would help your application. i can't even name another developer that uses 'bias' params on lfos, so for now, that's an "advanced" param.

That's fine with me. I was just thinking out loud, and already have a lot to play with

[antoine.bertier]

In fact in XT2 it could be even simpler since in the Sequencer view on a midi track assigned to a vst, you can access directly all exposed parameters of the vst to create automation envelopes. So I can indeed access all the parameters of series (but when I play with midi vst I spend all my time in the Modular view, so I never realized it was so obvious ), but series does not seem to like automation enveloppes as it stops sending midi notes as soon as an enveloppe modifies a parameter. At least I couldn't get it to work.

So I had to go through the control map route, assigning a CC to control a parameter, and then adding automation events with the right value on the CC channel. This works fine.

So here is the result with one series driving 3 Mtheory, and automation used to mute the voices and increase the High of counter 1 every 8 bars.

http://www.wusiklabel.com/members/82/song_focus_99.php

[xoxos]

the track goes with the bubble.. red b/g makes it look like christmas.

i'm guessing the sleeping is an XT2 issue if it works normally with the 'legacy' automation technique. i'll try it here (eXT1 and temper) to make sure.

[HiEnergy]

Hi,

I put a new demo up at http://www.soundclick.com/bands/page_mu ... dID=563854

This time it's populus playing some ragtime. Warning: this is quite dissonant!
I used xoxos populus for generating the midi notes, wrapped up in EnergyXT VSTi 1.46.
The sound source is Wusikstation's Dobbert Piano, the host is Ableton Live 7.0.2
Except for some minor tweaking during the playing there's no further influence involved. No prerecorded notes, no external effects, no midi transpose, scaler or arpeggiator. Just populus.

have fun
HiEnergy

[xoxos]

> Warning: this is quite dissonant!

thanks..

i ~see this as the tamagotchi of vsti..

it's better at creating rhythm textures, doesn't do much discretely looping stuff. these ~show how it often repeats phrases and varies them, not often predictably.

http://www.breathcube.com/populus06.mp3
http://www.breathcube.com/populus03.mp3
http://www.breathcube.com/populus01.mp3

if you run it really fast you'll hear the ~'petrie dish culture' effect.. i'd say the most appropriate 'conventional' application would be for bongos. tho convention.. maybe not so big in this forum

[stanlea]

bad links ?

[antoine.bertier]

Here is my new experiment Vox Populi:

http://www.wusiklabel.com/members/82/song_focus_105.php

Two populi drive 5 VOX'd presets in Wusikstations.

For some reason I could not reliably automate the Restart in populus: sometimes it restarts when it receives the CC event, sometime it doesnt. I could not get what the right conditions were to restart... Any hint ?

But clearly I have to spend more time with populus.

Antoine.

[xoxos]

bad links ?

i had '6' instead of '06' - fixed, thanks

restart

?? i looked to make sure i hadn't accidentally deselected any parameters.. the button is connected directly to the pin..

..since it doesn't work with automation, my *guess* is that there's a floating point math translation issue..

..the pin needs a voltage to be at or below 0.0000 on one sample, and above zero on the next to trigger..

..the synthedit button component varies between "0 volts" and "10 volts," however, in your host, you should have no difficulty using automaton to set it at eg. 3 volts..

so if the host has some value translation method that gets the value *close* it won't go below zero to retrigger (it might be rounding to some weird /128 method in your host).

(i know that sounds odd - in se 10 volts = 1.0 float.. because of this, 7 volts rounds slightly low in voltage and will read as a 6 if you simply multiply the float by 10 and store in an integer..)

in the future, i will write my buttons where possible as -10 to +10 to avoid this, i can send you a recompile if required.

thanks for the vox demo, showed the rising/falling nature of some settings.

[antoine.bertier]

it's very early here, i accidentally hit thread admin 'edit post' instead of 'quote'..


the contents of this message, except as noted, are generated by xoxos, not mr. bertier..

next week I'll try to see if I have bongos somewhere in my Wusik sounds

cheeky

if it's dependent on message frequency then it's a 'shell' issue.. your host / synthedit. or maybe both. we can try the -10/+10, and given this, it's probably a good idea anyway.