Hi Chris, As Brian mentioned, Ivory is intensive on CPU processing. The plug-in is streaming potentially many dozens of large audio files at any given second not to mention any further internal processing like resonance, ambience, etc. Unlike algorithms that process very efficiently, real-time streaming of multiple audio threads is a CPU challenge. It's a bit of a trade-off in terms of speed but offline bouncing is still generally faster depending on the complexity of the rest of the session. I don't find it to be particularly slow. I use an external Thunderbolt drive chassis with an SSD dedicated to Ivory. While I do notice that bouncing an instrument track with Ivory does take longer than pure audio tracks, it's only noticeably longer but surely not practically as long as a real-time bounce. Again, the track commit feature is a good approach for quicker bounces once the instrument part has been finalized. Even if it's not absolutely complete, one can always reactivate the instrument track, make changes and recommit.
HTH, Slau On Nov 26, 2015, at 1:41 PM, Christopher-Mark Gilland <[email protected]> wrote: > OK, so almost the entire duration of the song in realtime. > Maybe there is something here I am forgetting to understand here, but why is > it that Ivory in general slows things down so much. Slau, I know you made > mention it would be slower, but I'm not exactly understanding the reasonning. > Sorry. I kind a feel like an idiot for asking. > > Chris. > > > -- > You received this message because you are subscribed to the Google Groups > "Pro Tools Accessibility" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Pro Tools Accessibility" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
