Thanks Fritz for the fast reply and the modifications. Without this, these plugins just couldn´t be used. It´s a shame they don´t do anything about it, being such a big company 😕 Good to know that some developers listen 🙂
Hi,
thank you for this very fast response, don’t know if there’s any other place where the support is this good 🙂
I’ve also read the manual, but of course I don’t know Podium as well as you do and I expected 2 hosts to behave in a similar way. Thanks for the explanation, at least I know what’s going on. And it’s a mastering eq; I won’t use it in a mix, so no real problems there.
Regards,
Zsolt
Since 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.
Yes, bypassing a chain of effects inserted AFTER a bounce track, but with bounce mode disabled.
Hi 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
Thanks 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.
No 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?
How about pressing ‘E’ when the track is selected? I always do that and it works well for me.
But double clicking could be a good addition too.
Thanks, nice update. Can live with how the inspector works as I don’t use it really often (almost everything you need is included in compact mode 🙂
Looking forward to the next update 😉
I think what sets Podium apart is its sleek and attractive design and looks, which would surely change if skinning was an option.
I do wonder how I could turn off that brushed steel look or where that texture can be found so I could change it. Just to see how that would look, not really a fan of brushed steel 😉
Great update. Workflow is so much better using compact mode. Thanks for this 🙂
Thanks very much. I’m sure it was posted somewhere in this thread; I must have missed it. 🙂
Am I missing something or doing something incorrectly? Whenever I try a new beta (just by replacing the 1.94 build .exe with the new one) I get this.
There are some differences, like the look of the track lane, but the panning and gain faders are the same 😕 Do I need to do anything else? Or do I have to start a new project? I’d think replacing the executable is all that needs to be done. So what’s happening?
Thanks in advance.
Zsolt
I knew it would be this simple :s. And I could swear I tried it. 🙂
Thanks for your help.
Cheers
Zsolt
I’m still pretty much a newbie with Podium, but I think it means when changing something (midi or audio), both the original and the phantom copy change.
Might be wrong though 🙂