[Ardour-Dev] waveform display for master track
torbenh at gmx.de
torbenh at gmx.de
Fri Nov 21 11:12:30 PST 2008
On Fri, Nov 21, 2008 at 08:02:03PM +0100, Kjetil S. Matheussen wrote:
> On Fri, 21 Nov 2008, Kjetil S. Matheussen wrote:
>> On Fri, 21 Nov 2008, torbenh at gmx.de wrote:
>>> On Fri, Nov 21, 2008 at 06:34:36PM +0100, Kjetil S. Matheussen wrote:
>>>> On Fri, 21 Nov 2008, torbenh at gmx.de wrote:
>>>>> now jackless ardour actually IS a weird concept ;) i admit that.
>>>>> But it would at least be a very good test for the new Port
>>>>> Needs some thought, where to put the decision which ports to use etc.
>>>>> But its not a HUGE change.
>>>> But wouldn't it be enough just to let the GUIless ardour work on a
>>>> jack server?
>>> yeah. that might work out also.
>>> hmmm... but its not so cool anymore ;)
>>> heh.... it might be even cooler:
>>> we might be even able to jack_snapshot the whole jack graph in this case
>>> we have an environment Variable that overrides default server name IIRC.
>> Hepp, and by furthermore using a dummy X server (I'm sure such a thing
>> exists), and fork() (in libjack) all jack programs connected to
>> ardour (usually jamin) and then autoconnect the fork's jack
>> connections to the new jack server, all problems are solved. Easy!
> Heh, infact, there's not even any reason to make an export function,
> just fork ardour, and reconnect the fork's jack port to the new
what happens to the X connection upon fork ?
its either shut down, or interferes with the parents connection.
both cases are bad ;P
creating a GUIless ardour is easier than you might think.
all relevant non GUI code is inside libardour, and the GUI hooks into
it, by connecting itself to sigc++ signals.
its along the lines:
Session s( argv );
while( s.transport_frame != s.end )
There must even be a signal which gets triggered, when the export is
done. so we can connect to that, and run g_mainloop();
http://galan.sourceforge.net -- The graphical Audio language
More information about the Ardour-Dev