Re: [Traverso-devel] csound api introduction

[Nicola Döbelin]

> Hmm, lot's of stuff to do, don't know what you are good at, and getting in
> touch with the code. Well, if you like I could give you a general overview
> how things work. Nicola, you had/have this 'problem' too, getting used to
> the code, anything you can recommend ?

Hm, not really. Most of what I've coded are modules which were written from 
scratch. Your API documentation is very helpful, though. I started with tiny 
things like fixing font alignments in the VUMeters, then I started redesigning 
them, and finally they were largely rewritten ;-).

> At this very moment, after all the lovely GUI improvements Nicola has
> made, we 
> are gearing towards making cvs usable again, finishing the port to 
> QGraphicsView which has it's own set of odities that has to be worked out.
> Certain features either need to be disabled or finished for the 0.40.0.

Remon: Do you have a TODO list for 0.40.0? I know I've sent you lots of 
suggestions in a rather unorganized manner, so I wonder what you really plan to 
do for the next release.

> P.S.
> Before I forget, here is one:
> When importing audio files ( < I > on Track), we store the absolute file
> path 
> to that file, and the peakfile 
> in /project/path/projectname/peaks/audiofilename.peak-channel-0/1
> As Nicola pointed out some time ago, it's quite possible to import another
> file with the same name from another location. The peak file name will
> clash, 
> you get the wrong wave form visualization, or in the worst case a crash.
> What about looking into that routine, and e.g. making the peak file name
> on 
> import more unique ?
> (e.g. grep for the create_id() function which creates a 64 bit id that 
> consists of the timeofday() and random() values., just an idea)
> Related classes: src/commands/Import src/core/Peak src/core/Utils, 
> src/core/ReadSource src/core/AudioSourcesManager

It should also detect if the file was changed by another application, and if 
yes, recalculate the wave form. QFileInfo offers lastModified(), lastRead() and 
created() functions which may be useful. Perhaps created() and lastModified() 
can be stored in the wave form, and if a clip is imported and they don't match, 
the wave form is recalculated.

Regards,
Nic


-- 
"Feel free" - 10 GB Mailbox, 100 FreeSMS/Monat ...
Jetzt GMX TopMail testen: 
http://www.gmx.net/de/go/topmail?ac=OM.GX.GX003K11713T4783a