No, conman, with current EWQL Libraries its not always practical to spend thousands of dollars on computer hardware that may or may not solve the issue I’m having. EWQL’s own computer test system isn’t all that much more powerful than my own. Instead, EWQL/Steinberg could fix their offline bounce flaws and I wouldnt have the impractical demands of bouncing 100 tracks in real time.
Freeze all selected is a simple feature to be added, so I don’t see why steinberg would debate. Just some basic macro programming that Steinberg does so well on hundreds of other features, but occasionally they forget to include it on certain features for some reason.
I have a 5 minute cue with 100 tracks. realtime export takes at least 5 minutes per track. 100 tracks x 5 minutes = 500 = 8.3 hours. I’m not looking forward to spending 8.3 hours to render this stupid project.
So I’ll probably have to use freeze, it just would be a lot quicker with an automated macro, thats all.