ZynewaveZynewaveZynewaveZynewaveYou’ve really thought this out haven’t you?
Yes. Even though Podium has been commercial only about two years, it has been in development since 1990, so I’ve had plenty of time to think things through.
Darcy, I don’t know how far you have gotten with Podium, but I have just updated the getting started tutorial. You may find some useful hints in there.
ZynewaveBased on the feedback I have received on this forum, I have now rewritten the Getting Started page with new sections. It’s closer to a proper tutorial now. Comments are welcome.
ZynewaveIs there a reason why POdium does not automatically load plugins when the arrangement is opened?
If you open extra browser windows, you can actually have more than one arrangement open simultaneously. Useful if you want to copy stuff from one to the other.
ZynewaveThanks for the help Max.
With Podium, Jamstix is in the project but doesn’t load until you hit the play button. You then have a bit of a delay while it loads the samples before it goes.
As Max said, monitoring must be activated with the power button to load the plugins. If not already activated, then pressing play will activate monitoring, causing the delay. The power button acts like a kind of arrangement load command. A project can contain a large number of arrangements and it would not be practical if they all had their plugins loaded when the project is loaded. Only one arrangement can be active at a time.
ZynewaveWhat Max said. The value is mostly for diagnostic purposes. The largest latency value is deciding for the amount of delay there is when you start playback. E.g. the SIR convolution reverb adds a latency of 8192 samples, which is a noticeable latency.
ZynewaveIs that difficult to implement?
No, but it will take some time, with little benefit to most users. Since you have found the the problematic plugin, I prefer to continue work on some of the major features, which yields more bang per manhour I put into it.
ZynewaveExcellent post, suges
ZynewaveIf there was a switch for ‘Create Audio event with Bounce Wrapper Track creation’ that I could switch off, but others could leave on if they wanted, then that would save me about three button clicks.
You can save two button clicks. If you use the ‘wrap in new bounce track’, you can press undo afterwards, which will undo the event creation, but not the bounce track creation. A further undo command will undo the track creation.
Zynewavedisregard everything i’ve said above… it’s irrelevant now i know how to use Podium properly
Will do 😉
Zynewave@super_crunchy wrote:
@Zynewave wrote:
@super_crunchy wrote:
Something you may want to consider changing eventually, and this goes for realtime bounce as well… once a bounce track has finished recording (ie stop is pressed after recording) make the bounce track automatically turn off “Enable audio bouncing”
I’m not sure I understand. Do you mean that once you have bounce-recorded a track, either realtime or rendered, that you want the track to be converted to a regular audio track without the bounce button in the track header?
yes Frits, that would be good – because at the moment the bounced audio does not play back until “Enable audio bouncing” is turned off
Say what!? That’s the whole point of the bounce track. Once the B button is activated (and R button is deselected), the bounced audio track should play. This is indicated by muted subtracks and the audio event on the bounce track is drawn in unmuted color.
Another nice thing about the new bounce rendering, is that you don’t have to record arm the bounce tracks if you just want to render one bounce track at the time. The B button then behaves more like the freeze feature of other hosts.
Frits
ZynewaveBy the way, you wrote that the punch in/out markers tell Podium what to render.. I still have to draw an event in the bounce track. Is this on purpose?
Yes. It allows you to restrict the track time range that you want to bounce. Note that the punch in/out markers are only used if the punch in/out buttons are selected. Good idea about the missing event warning. I’ll add that for the next release.
Zynewave@super_crunchy wrote:
Something you may want to consider changing eventually, and this goes for realtime bounce as well… once a bounce track has finished recording (ie stop is pressed after recording) make the bounce track automatically turn off “Enable audio bouncing”
I’m not sure I understand. Do you mean that once you have bounce-recorded a track, either realtime or rendered, that you want the track to be converted to a regular audio track without the bounce button in the track header?
Seems to be a few extra steps every time you bounce when realistically after you bounce, you’d only want to play the bounced audio. Well, this is the case for me, to save CPU cycles
When I have bounced an instrument track, I often switch off the bounce mode when composing, to make changes to the MIDI data or to rearrange sequences on the timeline, and then redo the recording. The track bounce feature was designed for quick switching between playing bounced audio and the live plugins.