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.
Same here.
You need to sort the automation IDs of the Reaktor instrument.
Open the property panel of the instrument and have a look at the bottom of the property dialog.
As you can see the ‘MAX ID in use’ is greater than the ‘MAX ID’ used for automation. Choose ‘Sort and Compress IDs’ form the IDS menu.
After that the IDs will be sorted and compressed.
Now change the MAX ID to the value showed in MAX ID in use.
Save the ensemble. Start recording in Podium and a knob move in the Reaktor instrument should create a automation track now.
Another way would be using MIDI CC messages. But this does not work in Podium right now. For this you need to activate ‘Panel to MIDI’ for the controls you want to automate.
Maybe you can create a exception in your anti virus software for the file podium.exe. This did the trick for me.
Yes, some anti-virus software can cause this. Had the same experience on a pc.
Thanks!
Printer friendly version of the wiki:
http://www.zynewave.com/wiki/doku.php?id=guide:print&do=export_xhtml
Very nice, thanks!
You can also upload them to the wiki: http://www.zynewave.com/wiki/doku.php?id=colorschemes:index
Then just create a copy before you begin to work on a arrangement.
For me the delay compensation with Nebula 3 on any track works without problems. When using Nebula on the master track I got a delay of 381ms or 16812 samples on all tracks and they are in sync.
@LiquidProj3ct wrote:
However I noticed that when I change programs/banks in Gladiator’s interface, the selected preset/bank of Inspector remain.
There are other plugs like Rayspace from QuikQuak which also behaves like this. The plugin preset management is not reflected in the inspector but there is a workaround for this. Create a ‘Program Library Preset’ in the inspector and make it the active preset. After this this the selected preset in the plugin is saved in the new programm preset and ist also restored after reopening the project. This works for Rayspace.
Sounds like a job for the phantom copy.
The unique copy will create a exact copy of your arangement with all settings, audio files and so on . I use it to save different versions of an arrangement. The phantom copy will only save all settings and no audio files. It needs less memory but does not ‘backup’ the audio files.
For the track copy I don’t know what it does exactly. Maybe Frits or another user can explain it.
You can right click the arrangement and create a unique copy of it. It’s some sort of ‘save as’.