[ardour-dev] Development environment

Paul Davis paul at linuxaudiosystems.com
Mon Apr 9 08:34:04 PDT 2007

On Mon, 2007-04-09 at 15:42 +0000, John Emmas wrote:

> > On 4/9/07, Mike Taht <mike.taht at gmail.com> wrote:
> >
> > Ardour is a realtime process with many threads. It's almost impossible to
> > "step through" anything as there is so much going on at any given point

unfortunately, what mike wrote is not really very accurate. i single
step in ardour all the time. i set breakpoints, i catch exceptions etc
etc etc. it is true, however, that there is a lot of debugging of this
kind app that is best accomplished with debug output.

i would stress again, though, that the AAF work you're planning to do
does not *need* to involve any of this and would be much better for
everyone if it was a completely separate process from Ardour itself. i
understand your curiosity about Ardour internals and your desire to run
it and debug it, but please don't let that cloud the bigger picture:
translating between formats is something that is best done by
translation tools, not by the originator of each format.


More information about the Ardour-Dev mailing list