10 May
2011
10 May
'11
3:04 p.m.
On Tue, May 10, 2011 at 07:36:46AM -0400, Paul Davis wrote :
On Tue, May 10, 2011 at 6:15 AM, Arnold Krille
<arnold(a)arnoldarts.de> wrote:
> On Tuesday 10 May 2011 12:00:56 Aurelien wrote:
>> Second question, is there a way to do a "non-realtime" export, I mean
an
>> offline export, like when rendering 3D images, and so on.
>
> That is how export generally works in ardour. So, yes, there is a way to
> export offline, in ardour its called "Export" :-)
OK. Thanks.
in addition, ardour has no concept of different "quality levels" for
export. what is exported is precisely the same data as would be
generated during playback. there is no "high quality" or "low
quality"
option. the only thing that is different is whether or not JACK is
continuing to use an audio interface (or network interface) for timing
- during export, Ardour tells JACK to stop doing that which means that
it no longer matters how long the process of generating the data and
writing it to disk will take. since the same code path is used for
data processing, the only real difference is that we're also writing
to disk (but unlike the case when doing normal recording, this is done
directly without elaborate buffering to make sure that things are
real-time safe - we don't need that because export doesn't need to
meet real time requirements).
OK.
Then, I would have one question: why can I come to different results for
several exports of the same session?
I mean, I already had cases in which my master finally end up to +1.0
dB, and the export after to -0.1dB (without changing anything), and so on.
I'm not speaking of big differences, but enough to make it hard to
optimize my dynamic before mastering.
I really thought that it was linked to realtime processing, but if not,
I'd be interested in understanding what is behind all of this.
--p
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
--
Aurélien