Menu
▾
▴
cdrdao-devel
|
From: Manuel C. <ll...@ja...> - 2001-08-03 16:45:34
|
Hi all, I just commited the following changes: * added a "tools" toolbar, it contains select, zoom, zoom in, zoom out, zoom sel and full view. * added a zoomx2 method to AudioCDView to zoom without selections. * created some new icons for the "tools" toolbar * got some icons from eog * select is now the default (was zoom) Next, I will also change the play button to a simple play | stop toolbar. Work on the drag and drop problem (1 file at a time). Zoom out with the third button in the wav view if zoom selected. and select a full track if double clicking with the select tool, ... and so on... Any ideas wellcomed :) Is there any date for the next release? Features I would like to see are progressive showing of the wave as it is read and don't waste time scanning data tracks (not showing data tracks in the wav view would be great also). See you. -- 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) |
|
From: Andreas M. <an...@da...> - 2001-08-07 05:47:27
|
Manuel Clos wrote: > > I just commited the following changes: > > * added a "tools" toolbar, it contains select, zoom, zoom in, zoom out, > zoom sel and full view. > * added a zoomx2 method to AudioCDView to zoom without selections. > * created some new icons for the "tools" toolbar > * got some icons from eog > * select is now the default (was zoom) Great! > Next, I will also change the play button to a simple play | stop > toolbar. Work on the drag and drop problem (1 file at a time). Zoom out > with the third button in the wav view if zoom selected. and select a > full track if double clicking with the select tool, ... and so on... > > Any ideas wellcomed :) Sounds good. I think there are a lot of convienience functions we could easily add... > Is there any date for the next release? Not yet, as a wrote in my last mail I'm currently out of time. > Features I would like to see are progressive showing of the wave as it > is read and don't waste time scanning data tracks (not showing data > tracks in the wav view would be great also). 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. Andreas -- Andreas Mueller Tel: +49 89 67808848 Ramsmeierstr. 1 Email: an...@da... 85579 Neubiberg, Germany |
|
From: Manuel C. <ll...@ja...> - 2001-08-08 00:56:00
|
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)
|
Thanks for helping keep SourceForge clean.
X