[Ardour-Users] MIDI recording workflow

Nando nandinga at gmail.com
Sun Jul 24 10:57:00 PDT 2011

Hi Paul, what do you mean by freezing? range consolidating? (have no
experience with that) and, can you do that to a MIDI track and a bus?

I've just tried to hit "consolidate range with processing" out of my
newbieness ;p and got

"You can't perform this operation because the processing of the signal will
cause one or more of the tracks will end up with a region with more channels
than this track has inputs.

You can do this without processing, which is a different operation."

so I continued blindly and hit "consolidate range" and got a crash that I
haven't been able to reproduce (will keep trying).


On Thu, Jul 21, 2011 at 3:05 PM, Paul Davis <paul at linuxaudiosystems.com>wrote:

> On Thu, Jul 21, 2011 at 8:51 AM, Brett Clark <brett.clark at zirous.com>
> wrote:
> >> My doubt comes when I assume that muting a track disables all processing
> >> and lighten the CPU load. It's not that crazy right?
> >
> > I cant directly speak for v3, but on the 2.x versions muting a track does
> > not lighten CPU time.  It appears that it still ran all the plugins, just
> > didnt do anything with it after that.  I think its for improved response
> > time when you un-mute the track.  There's probably a more technical
> reason
> > too (eg. calculating latency, etc.).
> correct. however, deactivating a track will change the CPU load. you
> can also freeze a track, which will render it to a new audio file,
> replace the track contents with the result, and turn off all the
> plugins.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ardour.org/pipermail/ardour-users-ardour.org/attachments/20110724/fe480ac2/attachment-0002.htm>

More information about the Ardour-Users mailing list