SynthMaker

Automation...what am i doin' wrong here?

Archive · 2005 9 old posts

From the original SynthMaker forum (2004–2014), with its members’ names and dates.

lalo ·

hi guys!

check this out

http://www.nusic.org/temps/VST_automation_test.rar

it's a simple 'volume' effect just to check the VST automation thing....

but it doesn't seems to work...what am i doing wrong?

thanx

lalo

platinumears ·

whats not working? Is it just not re-drawing maybe? I connected the output of the "preset" module to the "redraw now" trigger on the "RedrawA" module in my plugs, which seems to work ok..

Dan W 🙂

lalo ·

the actual parameter automation doesn't work..... then the redraw too doesn't work... even if the 'Before Change" and "After Change" outlet of DragY are linked to the Redraw trigger inlet.... and the "F" output of the Preset module is linked to the 'Set' inlet of the DragY....

maybe some bug in DragY ?

lalo

malc ·

Hi lalo,

I'll try and have a look for you, might not be until tomorrow as I'm a bit tight for time today.

Malc.

Shifrin ·

Not sure if this is any help, but you could check the 'SimpleSynth' example I posted, all params are automatable (and I tested in EnergyXT - it worked fine.)

Shif.

malc ·

The problem is in the slider itself. It's our fault lalo, we didn't hook thing s up right 😊

Basically the problem is down to the fact that the DragY is giving values between 0 and 7 but presets must be between 0 and 1. There are also some redraw issues.

Try the modifications I made below: [old link]

lalo ·

thanx malc 🙂 i suspected this one...cause i tried an SM vst without GUI but with 'Preset' and it works 🙂

lalo

lalo ·

malc wrote: The problem is in the slider itself. It's our fault lalo, we didn't hook thing s up right 😊

Basically the problem is down to the fact that the DragY is giving values between 0 and 7 but presets must be between 0 and 1. There are also some redraw issues.

Try the modifications I made below: [old link]

yes..there are still some redraw issue...plus...

7 is the value of the slider position at its minimum...so the automation is inverted 🙂

and the cpu is very high ..i suspect is all about redraw issues....

we have to solve this thing...

would be useful to investigate how the VST SDK works in the relationship between the GUI and the sound process in the automation field?

probably the slider redraw too many times...probably we only need it to redraw...25 times in a second (frame rate in a typical video)...

maybe a kind of 'sample and hold' of 1/25 seconds between the preset's F output and the redraw trigger inlet?

let's work on this important issue 🙂

lalo

Tom7777 ·

Maybe make it so theres a Min and Max on the automation modules so you can set whatever is needed for automation.

Wrote something here? To have a post removed or your name hidden, write to [email protected].

Before your first post

A few rules keep this a friendly place. You agree to them once.

Shown next to what you post, here and in the app. It doesn’t have to be your real name: 3–24 lower-case letters, digits or _ (capitals become lower case, spaces become _).

    Then your post goes up straight away.

    Delete this reply?

    Open it in SynthMaker?

    It goes on the track you’re editing there, in place of that track’s sound, and into My sounds. Your other tracks stay as they are.

    Want to keep that track’s sound? Start a new song in SynthMaker first (Song › New song), then open this.

    Report this reply?

    Only the developer reads reports. The person isn’t told who reported them.

    What’s wrong with it?

    Block this person?

    You won’t see their posts and replies here any more. They aren’t told, and you can unblock them at any time.

    People you’ve blocked

    Their posts and replies are hidden from you. Unblock someone to see them again.

    The community rules

    A few rules keep this a friendly place. Everyone agrees to them once, before their first post.