Re: [Cdrdao-devel] gcdmaster changes for 2/8/01

[Manuel C. <ll...@ja...>]

Andreas Mueller wrote:
> Manuel Clos wrote:
> Sounds good. I think there are a lot of convienience functions we could
> easily add...

Ok, what ones?

>>Is there any date for the next release?
> Not yet, as a wrote in my last mail I'm currently out of time.

Ok, I will do a redesign of the copy CD interface, and at the time, make 
gcdmaster not close if reading/burning a CD :)

> The progressive showing of the wave form data during scanning should
> be easy. We'll just have to send appropriate guiUpdate() calls 
> whenever the scanning function has worked on a piece of data.
> To avoid scanning of data tracks I'll have to rewrite the scanning
> function to work on a track basis. Currently it uses the reading 
> functions of the Toc object. I can do that in 2 weeks.

Ok, here is my idea. The scanning will be made on a per track basis. 
Then, you don't need to block all the project, just the track you're 
scanning, so you can add new tracks to scan to a queue. I don't know if 
inserting a track before the one we are scanning is a trouble, but you 
can always have the scanning data on a per file basis, this is, 
insertions in the middle of a track won't be possible, but adding 
tracks/files before or after the track we are scanning will have no problem.

I was thinking on a queue of files/tracks to scan and do this scan while 
be work. As you need to block a track/file, then you can abort the 
scanning if this track/file is to be deleted. Or queue it again in some 
other situation. Also, if you can make the scanning data to be 
associated to a track, in some way that you can reorder tracks while the 
scanning is being done (and not restart it).

I would like to implement a "list view" of the Audio CD Project, because 
now is too difficult (or impossible) to change the track order, add a 
simple 2 seconds silence at the end of a track, ... And as every track 
can be composed of various files, we can use a tree view, something like:

CD
+
|---Track One (data1.wav)     <- track one is the name in CD TEXT
|--+Track two                 <- track tow is the name in CD TEXT
    |--data2.wav
    |--date3.wav
    |--silence of 1.5 seconds

The silence at the end should not be there but at the rigth (in the 
interface I have in mind), only silences that are between files or that 
are inside a wav file will be in the tree.

This way, when the tree is collapsed, we get a simple list of tracks 
that can be easily reordered. And if you expand you have the contents of 
the track, on an object view, where there is pretty simple to increment 
a silence or just remove it completely, ...

So, can we get something so that tracks are reordered without any 
problem while we scan them? (including .bin images)

Also, the scanning data cache in .scanning_data files will be great! I 
was thinking of having such files in ~/.gcdmaster, so if you want to add 
"/music/data1.wav" then we look for ~/.gcdmaster/music/data1.wav, 
compare the date (and perhaps some other data like file size) and if it 
valid we get some speed up. A tipical audio CD is 12-20 songs, so the 
speed up can be x12 - x20 :)

-- 
Manuel Clos
ll...@ja...

* Si no puedes hacerlo bien, hazlo bonito (Bill Gates)
* If you can't do it well, do it nice (Bill Gates)