Zynewave.
Zynewave@H-man wrote:
One question tho Frits, does the record button on the parameter track(s) do anything?
Is it meant to be linked to the device automation record buttons? :-k
1: The parameter track record buttons are useful as indicators. If you have a plugin chain with multiple parameter tracks for each effect in the chain, then record enabling an effect plugin will highlight the record buttons on those parameter tracks that belong to the plugin.
2: If you don’t record enable a plugin track, but record enable any existing parameter tracks, then you can record those parameters and avoid recording changes to other parameters. A sort of selective parameter record. At least that was the idea. I just tested this and I found it did not work for plugin tracks. Now fixed.
Zynewave@Conquistador wrote:
@Zynewave wrote:
includes general optimization and cleanup of a large part of the engine.
Audio engine overall or just automation? What was the clean up? What sort of difference should one notice?
A little overall code cleanup, which will make my work easier in the future. Nothing you should notice in the performance. It was just a comment on what I had been doing the last few days.
Zynewave@aMUSEd wrote:
Just experimenting some more with the automation – how come it records fine if I use the mouse to move a knob or slider but if I use midi learn to assign it to a hardware controller it ignores it?
MIDI learn in a plugin? Please give more details.
LiquidProj3ctExample: Sylenth1 has midi learn. Poise also.
You can link a knob to a physical knob of your hardware controller. Then when you arm the track for recording and turn on record if you move the knob with the physical knob the automation curve isn’t created, but if you move the same knob with mouse then the automation curve is created.
I don’t ask about this before because midi controllers aren’t fully supported yet…
swindusMIDI control change != VST automation
You can record midi controller messages like VST automation. Have a look here:
http://www.zynewave.com/forum/viewtopic.php?p=12407#12407
You need to create the cc message first then it works. Would be better if Podium creates a parameter track on incoming cc messages in record mode automatically.
And there is no mapping between controller messages and VST automation. So a knob controlled by cc messages does not create a VST automation sequence. I think that is what aMUSEd is talking about.
aMUSEd@swindus wrote:
MIDI control change != VST automation
You can record midi controller messages like VST automation. Have a look here:
http://www.zynewave.com/forum/viewtopic.php?p=12407#12407
You need to create the cc message first then it works. Would be better if Podium creates a parameter track on incoming cc messages in record mode automatically.And there is no mapping between controller messages and VST automation. So a knob controlled by cc messages does not create a VST automation sequence. I think that is what aMUSEd is talking about.
Oh right – I don’t really understand why if I move it with a mouse it’s VST automation but if I move it with hardware it’s treated so differently. Ideally I’d prefer to use hardware to tweak knobs where possible (many plugins do have built in midi learn on knobs)
H-man@aMUSEd wrote:
@swindus wrote:
MIDI control change != VST automation
You can record midi controller messages like VST automation. Have a look here:
http://www.zynewave.com/forum/viewtopic.php?p=12407#12407
You need to create the cc message first then it works. Would be better if Podium creates a parameter track on incoming cc messages in record mode automatically.And there is no mapping between controller messages and VST automation. So a knob controlled by cc messages does not create a VST automation sequence. I think that is what aMUSEd is talking about.
Oh right – I don’t really understand why if I move it with a mouse it’s VST automation but if I move it with hardware it’s treated so differently. Ideally I’d prefer to use hardware to tweak knobs where possible (many plugins do have built in midi learn on knobs)
+1
I could have sworn that I was able to do this however it may have been using MC and changing the parameter values using the mixer faders 😕
swindus@aMUSEd wrote:
@swindus wrote:
MIDI control change != VST automation
You can record midi controller messages like VST automation. Have a look here:
http://www.zynewave.com/forum/viewtopic.php?p=12407#12407
You need to create the cc message first then it works. Would be better if Podium creates a parameter track on incoming cc messages in record mode automatically.And there is no mapping between controller messages and VST automation. So a knob controlled by cc messages does not create a VST automation sequence. I think that is what aMUSEd is talking about.
Oh right – I don’t really understand why if I move it with a mouse it’s VST automation but if I move it with hardware it’s treated so differently. Ideally I’d prefer to use hardware to tweak knobs where possible (many plugins do have built in midi learn on knobs)
Because MIDI is MIDI and VST automation is VST automation. They are simply two different things. You don’t need a MIDI cable for VST automation and VST automation works without any MIDI devices/setups.
What is missing here is a mapping between MIDI and VST automation or in other words a MIDI learn function for VST parameters. This has nothing to do with a MIDI learn on a cutoff fader of a VST instrument for example.
Conquistador@Zynewave wrote:
@Conquistador wrote:
@Zynewave wrote:
includes general optimization and cleanup of a large part of the engine.
Audio engine overall or just automation? What was the clean up? What sort of difference should one notice?
A little overall code cleanup, which will make my work easier in the future. Nothing you should notice in the performance. It was just a comment on what I had been doing the last few days.
Ok cool. If it makes your work easier it’s a very good thing. 8)
aMUSEd@swindus wrote:
@aMUSEd wrote:
@swindus wrote:
MIDI control change != VST automation
You can record midi controller messages like VST automation. Have a look here:
http://www.zynewave.com/forum/viewtopic.php?p=12407#12407
You need to create the cc message first then it works. Would be better if Podium creates a parameter track on incoming cc messages in record mode automatically.And there is no mapping between controller messages and VST automation. So a knob controlled by cc messages does not create a VST automation sequence. I think that is what aMUSEd is talking about.
Oh right – I don’t really understand why if I move it with a mouse it’s VST automation but if I move it with hardware it’s treated so differently. Ideally I’d prefer to use hardware to tweak knobs where possible (many plugins do have built in midi learn on knobs)
Because MIDI is MIDI and VST automation is VST automation. They are simply two different things. You don’t need a MIDI cable for VST automation and VST automation works without any MIDI devices/setups.
Sure I get the theory – but in practice if I move a knob I would like the host to record it and draw an envelope – I know why there is a difference but I don’t see why it should make a practical difference in terms of the end result. It’s still moving a knob. My other hosts do not seem to make this distinction in practice – for example if I move a knob with my mouse or with my controller in Live the end result is still an automation lane and envelope. As a musician I’m not interested in the technical details I’m afraid, I just want it to work.
ZynewaveI think what swindus is talking about is support in Podium to link an incoming MIDI message directly to a VST parameter. That is not supported yet, but is on the plan for the future.
When you use the native MIDI learn feature often found in plugins, then Podium has no way of knowing that a certain MIDI message should control a certain VST parameter. Podium then relies on the plugin to parse the incoming MIDI and send VST parameter changes to the host. I just tried this quickly with the Nucleum and Triangle II synths, and they both record proper VST parameter tracks when they are adjusted by MIDI control changes. There may be plugins that report parameter changes to the host differently when controlled by MIDI, and thus the parameter changes will not be recorded by Podium.