Reply To: Bounce crash and stuck plugin

I 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. 👿