Re: [Audacity-devel] Project Announcement and Help seeking

[Dominic M. <do...@au...>]

On Feb 24, 2004, at 6:27 PM, Arturo "Buanzo" Busleiman wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Tue, 24 Feb 2004, Dominic Mazzoni wrote:
>
>> Hi, thanks for writing.  Sounds like a great project!
>
> Well, as most projects/inventions, it was made after the need :P
>
>> Audacity projects ("sessions") are XML files.  As a first step, you
>> might want to see if it's possible to convert a CoolEdit session to an
>> Audacity project file.  Then later you could build that directly into
>> Audacity.
>
> Yes, that's my idea. Anyway, how's the Audacity development team taking
> the "plugins", "conversors" [ import / export stuff ] into account? I
> mean, is there any specific API / guidelines an "external" developer
> should follow when writing an add-on like this?
>

We don't have a plug-in interface for importers and exporters yet.

Given how well-integrated this project needs to be, I think it only
makes sense to integrate it directly into Audacity.  A plug-in interface
would have to be quite complicated indeed if it supported something
as complicated as this.

One thing you might want to look at is ImportLOF.cpp - this was 
contributed
a while back as a "list of files" importer.  You could use it as a guide
to write your CoolEdit importer.

>> But I don't know much about CoolEdit sessions - how much information 
>> do
>> they contain?
>
> Well, Take a look by yourself. In URL [1] you can download the output 
> of
> the Audio::CoolEdit module applied to a .ses file of mine.

Cool, it looks like all of the relevant info is there.

> On the other hand, today I checked into Audacity when I had a little 
> time.
> It was real nice to see XML :) - WHen I saw it, I remembered I had
> *already* seen it some months ago, but I just forgot. :P
>
> Anyway, one of the most important differences is that CoolEdit uses 
> byte
> offset position for beginning of a waveblock instead of, what it would
> seem, a time offset in audacity. I believe a convert method is referred
> from the perl module. (Audio::CoolEdit).

Yeah, you'll have to account for that change somehow.

Actually I originally thought you could just write an Audacity XML file,
but it's not quite that simple - Audacity expects to find a .auf file
for each "block", containing the summary data (min, max, and average
waveform values), and there isn't an easy way to dump these files
outside of Audacity.

This seems like a shortcoming, though, so I'd be happy to work with you
to make it possible for Audacity to open XML files that leave out
.auf files (which could be created on the fly).

- Dominic


> - --
> Arturo "Buanzo" Busleiman - www.buanzo.com.ar - GNU/Linux Documentation
> GNU's es_AR Team Leader - PGP/GnuPG Key available at 
> horowitz.surfnet.nl
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.6 (GNU/Linux)
> Comment: For info see http://www.gnupg.org
>
> iD8DBQFAPAf6HSuFHeH64foRAotgAJ9P4lYoWdPgOuALwf7q+rz5wPI+/ACeKADF
> Yl2G5yV8fKoytf5fBvFxnXg=
> =ujoI
> -----END PGP SIGNATURE-----
>
>
>
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> _______________________________________________
> Audacity-devel mailing list
> Aud...@li...
> https://lists.sourceforge.net/lists/listinfo/audacity-devel