Ok it looks like with a project open, you go to File, then Close Arrangement Editor. Then you can access the project-specific plugin database.
Good point, though I record without a metronome
I’ve found it’s possible to input the value into the sampler’s plugin interface while recording the parameter track. So I can set a loop a bit before a MIDI note and it is not at perfect points in time, but can get the value assigned that way.
Any update on where you’re at in the above mentioned to-do list Frits?
OK I figured out how to set up multitimbral instruments, though could someone please help me figure out how to use more than one multimbral instrument?
Say I have one instance of Kontakt with 16 MIDI channels pointed to it. Now I’d like to create further instances of Kontakt, each also with 16 MIDI channels. I can set this up, but is there a way to switch my single MIDI keyboard to various MIDI inputs (as created in the project device list)?
Thanks king. Any response to this Frits? Could you also explain or point me to the relevant Podium Guide section for how to set up tracks so that one instance of Kontakt can be loaded with multiple instruments, then corresponding tracks can be created with MIDI connected to each instrument? I’m a little at a loss for how to set this up instead of having to create an instance of Kontakt for each single instrument. Thanks!
Hello again,
Do you foresee near-future implementation of having the control surface channel record arm act as a toggle for simulated fader touch rather than having to hold it?
It is currently extremely difficult to simply sit and listen to a looping song section while making EQ tweaks. Having multiple parameter tracks all set to ignore previously recorded data and overwrite it (without having to hold buttons for each while mixing multiple parameters at once) would make a major difference.
Thank you
Thanks a ton for your help Levendis – much appreciated!!! Something came up and I’m unable to make time to experiment just yet but will definitely go over this in detail at some point and give it a shot.
I’ve been playing around with this, and it sort-of works, but I’ve noticed two things.
To have one channel panned L and one panned R, I need to set up a track and TWO sends so that Return 1 and Return 2 can be panned separately. If I pan the parent track hard left and create just one return track, it can’t be panned hard right because the bus is only sending through a left channel. This makes sense, but requires that the parent track’s fader is brought to 0.
The only way to get the return tracks working with the parent track fader at 0 is if an effect is loaded on the parent track so that the Send busses can be dragged below the Gain slider in the effects rack. With no effect added, the busses won’t move. This isn’t a big deal, just a workaround, and the effect can be removed from the parent track after the send busses are moved below the horizontal gain slider.
#2 is more of an actual issue – if I add the pitch effect on a Return track, the latency jumps from 1ms up to 54ms which is expected, BUT the latency on the parent track jumps from 2ms up to 55ms even with no effect on. Is it possible to keep the parent track at 2ms while the effected Return track is at 54?
Thanks!
Thanks Levendis!!! I wasn’t aware the busses could be dragged and placed anywhere within the fx chain!
Yeah that would be an amazing feature, but I understand it can’t be implemented soon. That is ok. What you have done already is amazing and so simple to get going, and I especially appreciate not having to restart the program to recognize MIDI and control surface devices!
I’ll play around with what you have some more now knowing what I can’t accomplish, and I hopefully will find a different way to make my workflow easier.
Ok, that’s fine. Could you make note of it or should I submit it as a request somewhere? I am surprised a change like that wouldn’t be quick, but I understand. I really look forward to the change though, because otherwise, I’m limited to one or two faders at once whereas it would make a huge difference to my workflow to be able to balance drum sounds for example, where I have room mics, ambient mics, overheads, many close, etc. and really need to move them all at once since the sounds interact.
Sorry to sound so negative.. I’m finding Podium amazing (intuitive, simple but powerful, lightweight, aesthetically great), but this aspect isn’t working for me. I also noticed that when I switch presets, the motorized faders don’t update to reflect the setting. Would there be an issue with locking faders to the actual parameter settings instead of the recorded automation data, and then having recording optional? It’s like audio.. sometimes I’d like to have it play while I monitor a guitar coming through, but don’t necessarily want it to record, especially if I’m looping a section and having a player practice a part over and over.. I don’t want it to record and then play back the next time over.
With parameter tracks, I’m always looping clips and dialing in sounds, so things are still always going to jump back to what’s recorded at the beginning when the clip loops, so no matter what I have to make note of the settings at the end of the clip and then manually dial them in individually at the start of the clip and delete all the automation.
just each parameter tracks individually, not the actual track they are under. If I have 3 faders that aren’t right next to each other, I’ve got to use one hand to hole three buttons and my remaining hand won’t be able to move all three faders if they aren’t real close. This is all even assuming that I’m able to change the record to a single button because right now on the BF2000 MCU it’s like a shift function, where I have to use one hand for the shift so the button becomes the record button, then my other handle holds that record button and I can really only use one single other finger to move the fader.
Yes, but does it matter if it’s toggle on/off rather than hold for on?
This is working for me, but it constricts use to one hand. I’d like to control 4-5 faders at once. Would you consider changing this to when record is enabled on a parameter track? Presently I see no impact when record is enabled or not since parameters always respond to faders.