[ardour-dev] jack/ardour application extension(s)

[Paul Davis]

On Tue, 2007-02-20 at 18:40 +0100, Robin Gareus wrote:

> 
> Why on ardour-dev ?
> 
> I'd like to get the current zoom-range from ardour (either query or
> notify) - AFAIR ardour's menu can be customized, too (hook to change
> video-file path of xjadeo or gjvidtimeline). - is there doc around for
> that?

pretty difficult to figure that out, but we could add it to OSC. i don't
think we've done any OSC query support yet, but i think that liblo makes
it pretty easy to support. what do you want to do with the zoom range?

> where to start best? - Is it welcome to "integrate" external software
> into ardour like this? -

very welcome, except that we need to "evolve" some good generic
mechanisms for it.

> slightly OT: I'd like to request a new Feature in ardour: Lock
> audio-files or chunks to a fixed timeline-position on the audio-track
> they are dragged or pasted - best if ardour could even use/set the
> offset-value in the file's header.

it will go in post-MIDI-merge (post2.0) when you will be able to lock
regions to BBT or audio sample time or timecode time.

> and a final ardour-extension question: What is the status of the
> ardour's EDL import/export?

non-existent. there are nibbles at handling AAF and OMF, but nothing
substantive or even look-at-able.

> It's kind of easy to parse the audio-file-name and offset from an EDL,
> and I've done it to for some FCP projects with awk. - but I'd prefer a
> proper EDL parser [lib] (that issues warnings and allows customized
> filter to plugin mapping etc); if anyone want to start such a project
> I'll gladly contribute. - meanwhile I could come up with a perl script
> that will work for >95% off all projects, but I'd rather not :)

i have moved away from the whole "EDL" nomenclature, because an ardour
session (as well as that of any other capable DAW) is *so* much more
than an EDL. 

the formats in other DAWs are all proprietary, except when they use AAF
which is incredibly complex; ardour itself uses XML so you just need an
XML parser and some semantic information on how to use the nodes.

--p