aMUSEd's Forum Page

No I suppose strictly speaking it’s not a “bug” (though I thought it was at first) but I would describe it as needing “fixing” all the same in the sense that it is not working properly – it may be working as “intended” but it is not “fit for purpose” imho. I’m pleased it will be addressed, I just hope it will not be too long as the workaround is impractical for my purposes.

I can’t see a way to add other graphics and it looks like the grain is embedded in the exe. I’d really prefer a plainer look.

Pity. I can’t understand why this isn’t seen as more of a priority. Is no-one else using automation with softsynths apart from me?

It would be great if you do, thanks. I don’t understand why it should have this behaviour in the first place though – it seems a very strange way to create automation if it doesn’t follow the instrument/effect setting as left by the user. I don’t know any other host that does automation this way. The workaround you suggest is doable if I just have 1 or 2 envelopes but if I have a more complex piece I can see it becoming a turn off.

I’ve never used that because I don’t know what punch in is. My guess was that it means recording starts when I start playing? If so as you can see I had already played several bars before touching the knob but they end up silent.

I’ll try the new beta thanks

That would be great thanks

@Zynewave wrote:

Questions:

If you change the VSTi patch after you created this automation lane, will this host change the starting point of the curve to match the value of the parameter in the new patch?

No if you change the patch the cutoff jumps to the recorded position rather than retaining the patch position – but I would expect that.

@Zynewave wrote:

Can you grab the first point on the automation lane and drag it to the right on the timeline? In that case, what will the curve look like up to the first point?

This

But note even then it does not start at zero – it starts at the patch’s value of 49%
(The host is Energy XT 2 btw but this is what I expect as standard behaviour regarding automation of plugin values – it should always record exactly what is played)

@Zynewave wrote:

The problem here is in the way that automation is designed in the VST spec. When a VST parameter is automated it will change the loaded patch directly. Stopping playback during automation will thus leave that parameter/patch at the last automated value. If you then restart playback at a point before the first recorded automation, it would result in a random patch (= random sound) depending on where you last stopped playback. That is why Podium always sets the parameter value at playback start.

I’m sorry but I don’t understand this at all – if this is in the VST spec then how come no other host I know of sets the cutoff or other param to zero at the start and end? Surely the “default” starting point should be the position the instrument is set to at the start of recording, not zero? Just as a comparison look at how this is handled in another host:

Note the cutoff value for this patch “kickass drone” is at 49% and even though I don’t actually touch the knob to change the cutoff value till halfway through the sequence (marked in red) the host correctly starts the envelope at the 49% position and ends at the point where I let go of the knob.

In Podium I can make the same sequence but it will drop to the cutoff to zero at the start of the track right up until the point I tweak the knob and again at the end – making the sequence silent right up until the point where I touch the knob even though I am playing notes before that. And this is just a simple sequence – imagine how this would affect a more complex sequence with lots of params being moved at different times – nothing would sound the same on playback as it did when I recorded it. That can’t be right.