Subject: Re: [ecasound] ecasound front end
From: janne halttunen (jhalttun_AT_pp.htv.fi)
Date: Thu Nov 01 2001 - 14:30:48 EET
On Thu, 1 Nov 2001, Luke Tindall wrote:
> I tend to use perl or bash for scripting and have only really glanced at
> python. I've stuck with C for most of my coding days. One of the things we
> need to sort out is the data. Writing a ecs parser in c was a pain in the
> arse, python is probably better for this. If the data was better organised
> the parse routines would be a breeze to develop. The major problem I found
> was that all the ecs files always have the chain as the key. I would rather
> parse for a key say, look out for e options or k options etc. I thought you
> had the right idea with your suggestion for an xml style ecs file.
Yep. What I could do is to objectify the ecsReader and ecsWriter
interface in ecasetupedit and add an xml style output option. ..hmm?
> Personally I hope that we get the emt multi track format that Kai spoke of
> recently. This way you'll get to the data quickly and the parser can be
And then add an emt one, perhaps?
-- To unsubscribe send message 'unsubscribe' in the body of the message to <ecasound-list-request_AT_wakkanet.fi>.
This archive was generated by hypermail 2b28 : Thu Nov 01 2001 - 13:27:32 EET