ZynewaveZynewaveI 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.
ZynewaveOuch #-o
I’ll fix that tomorrow.
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.
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@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@Zynewave wrote:
@LiquidProj3ct wrote:
The last stretch of the curve hasn’t slope in sequencer. Curve editor snap is 1/16, while sequencer snap is set to 1/1.
It’s not a bug, but perhaps a bit confusing. It’s because the snapped point at bar 2 is actually beyond the end of the curve sequence event. When the end of a sequence/sound event is snapped at bar 2, it will stop playing events/audio just before the bar 2 start.
Maybe I should change this behaviour for track automation curves, and actually include point events snapped on the end of curve sequence events?
There is a new beta5 where point events snapped on the sequence end is included in the track curve.
Beta5 also has a new “transform to grid aligned points” command in the curve editor. The old “digitize spline curve” is renamed to “transform points to spline curve”. Next I’m going to add a “transform spline curve to lines” command.
I’m not home during the weekend, so I may only be able to respond to your feedback late on monday.
ZynewaveAlright. You’ll need to do some manual setup of a set of Bidule mappings:
On the project start page, devices panel, right-click the Bidule mapping and select “new copy”. In the properties dialog that appear:
Name the mapping e.g. “Bidule 1-2”, select the “link to global instance” option, select “stereo” in the plugin input and output combo boxes. Click ok.
Now right-click the new mapping you just created, select “new copy” and:
Name the mapping “Bidule 3-4”, increase the two “first channel” settings to 3. Click ok.
Repeat for as many stereo pairs you need.
Once you have set up the mappings, you can assign them on separate tracks to treat them as individual stereo effects.
ZynewaveHi,
Before I can give a detailed answer I need to know: Are you using Bidule as a single multichannel fx (meaning surround sound), or as multiple mono/stereo pairings of the I/O channels?
ZynewaveZynewaveZynewave@LiquidProj3ct wrote:
The last stretch of the curve hasn’t slope in sequencer. Curve editor snap is 1/16, while sequencer snap is set to 1/1.
It’s not a bug, but perhaps a bit confusing. It’s because the snapped point at bar 2 is actually beyond the end of the curve sequence event. When the end of a sequence/sound event is snapped at bar 2, it will stop playing events/audio just before the bar 2 start.
Maybe I should change this behaviour for track automation curves, and actually include point events snapped on the end of curve sequence events?
ZynewaveBeta4 is up. This fixes all the bugs I am aware of, and includes general optimization and cleanup of a large part of the engine. I also implemented close to real-time response to edits made in the curve editor. Previously curve editor changes would only be audible with almost one second delay.
Please try beta4 with your old and new projects and let me know if you find problems. I’m going to test it thoroughly over the coming days. If all goes well, I’ll release 2.15 next week.
Zynewave@druid wrote:
If you mean a host that supports rewire, then yes. But I don’t believe it can actually host rewire connections, only slave to them.
If you are talking about Podium then I am confused about your remark. Podium can act as host for other ReWire slave applications (such as Reason). Podium can not slave to other ReWire hosts.
Zynewave