Zsolt.
ZsoltHi,
I’ve just had this idea because I’m working extensively with a pretty CPU intensive plugin (Nebula 2) on our demo project.
Bounce tracks are very useful, but I think the idea could be expanded. Here’s what I struggle with.
I bounce tracks because a lot of times I’m reaching 100% cpu and can’t listen to what the result will be after bouncing. So now I’m trying to keep the cpu use below 90% before bouncing. BUT, if I use more instances of the plugin AFTER the bounce track, they will still eat up cpu power. This way I still won’t be able to listen to the affected track.
So my question is; is there a way to implement a feature that disables all effects after a bounce track? Like a bounce button that works ‘backwards’.
Thanks for all your hard work and for an already great DAW
regards,
Zsolt
ZsoltNo thoughts? I’m sure I’m not the only one that’s tired of switching off every plugin because there’s no processing power left 😕 Or am I?
druidWell I have to admit, I’m not really sure what you mean. Don’t know about anyone else.
But if what you mean is bouncing just a synth, and having effects run after it, why not bounce the last effect in the chain? That way, you can turn off the whole chain and just have the bounce.
Or do you mean something else?
H-manYep …I’m with druid on that one.
Assuming you are in Compact Mode, File tab, Arrangement Properties, you can right-click the track header and choose ‘Insert Bounce Track’ however you should note that any effects on the initial track will be moved onto the bounce track automatically.
In your case, doing this will leave Nebula 2 ‘live’ and still eating processor cycles (big-time).
To bounce the whole lot, right click the top track, which is the last effect track in the chain and choose ‘Insert bounce track’ from there.
That will bounce the whole lot and then mute/deactivate all below 🙂
Hope this helps,
Ben
ZsoltThanks for the answers, but it clearly wasn’t a good explanation.
I might not know all the features of Podium yet, but I think what I’m asking for can’t be done without manually disabling plugins.
Let me give you an example with Nebula.
Say I have a guitar track which I want to go through a nice coloured preamp like in the newly released ‘Retro Analog Studio Suite’. This preamp can consume 50-60% of cpu power alone, which I just cannot spare so I’ll have the track bounced. BUT, after this I’ll be inserting more bounce stages for EQ (multiple instances), Reverb (very cpu hungry) and Tape. I want all these stages to be separate to be able to just go back and easily tweak EQ or preamp stage for instance.
So the problem is, when I want to listen to the first stage (preamp), without EQ, Reverb and Tape added, I have to disable all these effects manually. Unless there is a way to disable them easily, which is what I’m asking for. As far as I know, even if you engage the bounce mode for the track closest to the master output, if you would solo the first stage with the preamp effect, all the effects added later in the chain would be activated, therefore eating up cpu power.
I really hope this clears it up. Oh and I’m using expanded mode.
@druid: I hope the example made it clear why I’m not bouncing a whole chain of effects. Podium really slows down to a crawl when using so many instances of Nebula and listening to them in real-time is really impossible. I hope to buy a faster pc in the near future, but even then I won’t be able to use loads of instances.
druidAh I see what you mean.
That could be useful! I haven’t produced much yet so I can’t say I’d use it, but I do wonder if I would at some stage. As for if it is already possible, I agree with you, I don’t think it is, but still… Not knowing enough, I can’t say for sure.
Thanks for clearing that up.
H-manHey Zsolt,
I think this will end up requiring advice from Frits and probably as a feature request after that.
I frequently use the Unload plugins after bounce is activated but of course that only works on child, not parent tracks.
Maybe you’ll have to copy the bounced audio to a new track each time and just leave the work-up tracks muted/de-activeated. I think this could be easier that nesting bounce tracks.
Nebula sounds like a bit of a rig-killa 😯 I’ve never used it, is the quality of the ef-ex worth the restriction on work-flow?
Ben
ZsoltHi druid,
I’m not using all the features of Podium either, because I don’t know them all, that’s why I posted this as a question in the first place; there might have been a clever way to do this who knows.
I really love this program and I want it to be the best it can be, so I made this suggestion/request 🙂
@H-man: my problem is more the listening to the unaffected part before having to render the whole lot. I know I can render just selected parts, but then I have to go and edit the punch-in marker and then edit it again if I want to render the whole song. Sometimes I forget to do that and don’t render part of the song. Then with little adjustments, you just don’t notice it so you can leave mistakes in the mix.
About Nebula; the eq’s, tapes, preamps, (some) effects and reverbs are really unbeatable and are worth the hassle in my opinion. I think you either like it or you hate it, personally I like it 😀
regards,
Zsolt
ZynewaveI’m trying to understand this. Are you asking for a shortcut for bypassing a chain of effects instead of having to bypass each plugin individually with the “X” buttons?
Perhaps it will be easier for me to understand if you could post a screenshot, or send a screenshot/project file to my email.
ZsoltYes, bypassing a chain of effects inserted AFTER a bounce track, but with bounce mode disabled.
Zynewave@Zsolt wrote:
Yes, bypassing a chain of effects inserted AFTER a bounce track, but with bounce mode disabled.
Unless I have misunderstood you, there is no shortcut for this currently. What method do you use to bypass the effect tracks? I would think it is easy to bypass a chain of effects by clicking the X button for each effect in the chain panel. Since you’re using expanded mode, you can probably do it quicker with the X buttons in the inspector group panel. If it sounds like I don’t understand what you want then please post/email a screenshot.
ZsoltSince you’re using expanded mode, you can probably do it quicker with the X buttons in the inspector group panel.
You understand it perfectly and that’s what I’m doing now. But when you have a lot of instances, a bypass button like what I’m suggesting can make it much easier.
It’s really not that urgent to implement it, I just thought it might be a nice feature to have when you’re working with cpu hungry plugins and a lot of instances.