Robert RandolphRobert RandolphRobert RandolphRobert RandolphRobert RandolphRobert RandolphI can edit significantly faster in saw. When handling edits across, and between 50+ tracks, along with adjusting large arrangement portions and adjusting 100s of crossfades in a single session… podium would take weeks. Many of the projects I work on every day are at least 40 tracks or more with hundreds of regions, thousands of automation entries and hundreds of crossfades… let alone everything on various layers!
On a track per track basis, you can move just about as quick. It’s as the projects become larger and more involved that sawstudio becomes easier and quicker. Saw also maintains an amazingly responsive interface under extensive load… and that load is reached later as well.
For small projects I’d rather use podium honestly… it is more ‘fun’ to use, and you can figure something out easier. As the project size grows, sawstudio is more stable, responsive and has more powerful editing options… you just have to not be afraid to reference/memorize the manual 😀
Though in podium, the tool-based interface can cause some slow downs that simply aren’t present in a keyboard based interface. I’m ‘used’ to it having used protools for a good while, but it is still less efficient.
As for reaper… bleh. I’ve tried it with every minor update (.x) and I’ve never liked it. It’s far too generic for my tastes, and the userbase seems to be… ugh. 👿
Robert RandolphRobert RandolphThank’s sam, I’ll give it a try.
I’ve been using podium more and more… but sawstudio still is light years ahead in audio editing and audio handling, which is where the $$ comes from 😀
It is nice to be able to have 2 really well written programs to use. Only so many years ago the choices were pretty slim and depressing.
Robert Randolph@sam c wrote:
instead of hitting control B just hit record on the track (bounce track) and transport bar, hit play and you get a realtime bounce.
Robert from SAW? what brought you to podium?
Hi sam 😀 It is me… I’ve been using podium for a while. I use it in tandem with saw, and I still use saw/sac for all my professional work.
I tried the recording to a bounce track, and nothing records. I figured it was the most obvious solution but when it didn’t work I was rather confused
Robert RandolphRobert RandolphHmmm
How to do a realtime bounce in podium? I don’t see any way other than to do a loopback.
Robert RandolphRobert Randolph@Zynewave wrote:
@Robert Randolph wrote:
I am also seeing strange engine freezes. Hitting the play button does nothing, but the engine still runs ‘as normal’. Turning the engine on and off fixes it.
I hope that is only when you’re using splonki or other problematic plugins.
Without splonki I still get the problem occasionally.
My system is very finely tuned and other hosts I use daily (sawstudio and protools) do not have such issues.
I’ve not narrowed it down yet. It seems to be oddly random.
Is there a reason podium doesn’t send blank buffers to plugins when playback stops? It seems to cause problems with a few plugins that have internal buffer sequencers.
Podium does send blank buffers when playback is stopped. Only when plugins are bypassed/muted will the processing not be called. I’m guessing the problem is how the plugins respond to transport state changes.
It’s possible I guess.. ❓ Splonki does not cause such issues in other hosts that I’ve seen though
Robert RandolphI think it looks fantastic.
You can use inkscape (free) to trace to SVG and use easily found freeware to convert from svg to EPS.
Robert RandolphI’ll try that tomorrow.
I am also seeing strange engine freezes. Hitting the play button does nothing, but the engine still runs ‘as normal’. Turning the engine on and off fixes it.
Is there a reason podium doesn’t send blank buffers to plugins when playback stops? It seems to cause problems with a few plugins that have internal buffer sequencers.