It's still taking even with Committing quite a while to convert the Ivory track to an audio track, but like you said, that probably is just due to the samples being so huge, and, again, in all fairness, I'm using a 5400RPM drive, so really, I guess I'm kind a lucky it's even working as well as it is.
Chris. ----- Original Message ----- From: Slau Halatyn To: [email protected] Sent: Thursday, November 26, 2015 3:26 PM Subject: Re: Has anyone observed this with Ivory? Hi Chris, Select the instrument track with Ivory on it and either choose Commit from the Tracks menu or simply press Option-Shift-c. You'll be presented with a dialog. Everything in there is pretty self-explanatory. Once you've "committed" an instrument track, the resulting track is an audio version of the MIDI performance. It's just like bouncing but, in one step, all of the routing is done for you and you don't have to create a new track and import audio to it. It's a simple way of converting the MIDI information to audio in one step and, in the process, you can hide and make the instrument track inactive, thus freeing up CPU resources. Bouncing the session at that point will be much faster as the CPU doesn't have to calculate the performance of the instrument track in the process of offline bouncing. Slau On Nov 26, 2015, at 2:45 PM, Brian Howerton <[email protected]> wrote: Chris, This is a new feature in pro tools 12.3. I have read a little about this, but not enough to elaborate. Sent from my iPhone On Nov 26, 2015, at 2:35 PM, Christopher-Mark Gilland <[email protected]> wrote: I guess when you say the track commit feature, I've never heard of that, or at least if I have, never in that termanology. Can you try explaining that process? Maybe what I'm doing isn't the right way of bouncing to start with. Basically, I'm simply just making sure no tracks are armed, then am hitting command+Option+B and just bouncing the whole session to an interleaved 16 bit 48K wave file all in one shebang. Chris. ----- Original Message ----- From: Slau Halatyn To: [email protected] Sent: Thursday, November 26, 2015 2:26 PM Subject: Re: Has anyone observed this with Ivory? 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 [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 [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 [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. -- 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.
