Hi, I have been working on a simple curses-based textmode frontend for
cdrdao until I just discovered your excelent GUI... But there are a
couple of things that could be improved: (don't get upset now ;)
As it is now, you can't see what parts are from different files. It
would be nice if each boundary between files/parts of files, and
silences was shown. A simple lightgray line would do it. It would also
be very nice if you could see what the actual filename is for each part!
(it could be shown in the statusbar when the mouse points at each part).
A special color could be used for silence.
There is also no way to be sure that you've selected exactly one
part/file! A double-click in one part should select exactly that part.
Double-click on a track-mark should likewise select everything from that
mark until next mark or end, this way it would be more easy to move the
order of tracks.
Another nice thing would be if shift-click would let you extend the
current selection, or select everything between the one-sample-marker
and the place you shift-click if there was no selection... by the way,
there is no "select none" or "unselect"!
I think that the player should play from the marker and not only the
selected range, but this could also depend if there is any selected
range or not, (if you could unselect that is!)
There should be a Copy, not only Cut.
The trackmarks should show their exact time, in a read-write textwidget
so that you could write in a new value manually...
It would also be nice with a "align trackmark with start of file/part",
or maybe just "add trackmark at start of file/part".
I didn't get the scanbus-button ("rescan") to work, i had to manually
run "cdrdao scanbus" in a shell and paste the information in...
And now some extra ideas:
what if you inserted/appended a whole file, and cut out a part of it,
and then realized that you want to change it? A really cool thing would
be if you could bring up a "selected part of file" window where you see
the WHOLE file and gets to edit the used range..
another cool feature would be fade in/out, and maybe crossfade... this
would not be hard to do, if you fade a selected range, that faded range
will later be stored in a tmp-file together with the resulting .toc
file, but only first when you save or record it, so that you could
experiment with how much or which part you're fading. The extra
information could be saved in comments in the .toc, so that when you
load such a project again it will not use the temporary fade-files but
the real files... anyhow, this was just a thought, not important!
I hope I didn't scare you with all those feature requests! =) I would
gladly help out with the coding, but the problem is that I have no
experience in C++, only C... But maybe I could learn and help out a
little anyhow, if I get some hints where to start... The most important
stuff (I think) is showing the boundaries between parts and letting you
select the total part (so that deleting it would really delete it from
the .toc, but without changing the other files/parts in the .toc!)
| __ ____ _ ____
|__/__ _____ _____||___ (_) ____ _____|
| )(_____|( | )(_____||_____ | (______(_____|