wavbreaker-devel Mailing List for wavbreaker
Brought to you by:
tdrobinson,
thp4
You can subscribe to this list here.
2007 |
Jan
|
Feb
|
Mar
|
Apr
(9) |
May
(24) |
Jun
(4) |
Jul
(8) |
Aug
|
Sep
(18) |
Oct
(61) |
Nov
(27) |
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2008 |
Jan
|
Feb
(3) |
Mar
(6) |
Apr
|
May
(10) |
Jun
(10) |
Jul
(17) |
Aug
|
Sep
|
Oct
(2) |
Nov
(1) |
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(6) |
Dec
|
From: Thomas P. <th...@gm...> - 2015-11-27 14:30:33
|
Hi, In order to test wavbreaker on Mac OS X, I've written a small audio output plugin based on libao: https://github.com/thp/wavbreaker/commit/d7c8ef1baf08d7a6b981b3d988201ca74699b4e6 Given that libao supports[1] many different output methods (including OSS, ALSA and PulseAudio, but much more than that, including Mac OS X and Windows), I wonder if having all those plugins around still makes sense - just having a single dependency on libao and removing at least ALSA and PulseAudio support would be a good cleanup; the remaining advantage of OSS is that it just needs Linux development headers and ioctl(), but I'd be for simplifying that down as well and just use libao -- what do you think? Also new: Whenever there is a push to the master branch or a pull request, Travis CI[2] will now build the source on a Ubuntu (Debian-based) VM and see if it still builds correctly, that's kind of nice to make sure the source tree is in good shape. More automated tests would be even nicer (both GUI tests and testing the command-line utilities), but we're not there yet, and it's not a priority at the moment. Thanks, Thomas [1] https://www.xiph.org/ao/ [2] https://travis-ci.org/thp/wavbreaker |
From: Thomas P. <th...@gm...> - 2015-11-17 20:03:46
|
Hi, 2015-11-17 20:47 GMT+01:00 Carl Hetherington <li...@ca...>: > I'll try to add import of CUE, as you suggested, soon. I can send you a > github pull request I suppose. Yes, that'd be great :) > Did you get a chance to test the CUE export changes much? I did test it a bit and noticed that when you save the CUE file to a different folder from the .wav file, then the basename of the .wav file is added to the CUE file without any relative directories. This probably applies to .TOC export as well (haven't checked) but either disallow saving the CUE file in a different folder or make the relative or absolute path of the wav file name in the CUE file so that when opening the CUE file from wherever it is saved will "find" the WAV file (of course, we don't need to account for the user moving the CUE file or WAV file around, although relative file paths would be nice). Thanks, Thomas > On Tue, 17 Nov 2015, Thomas Perl wrote: > >> Hi, >> >> I've done a proper conversion of the SVN history to Git here now and >> merged your changes: >> >> https://github.com/thp/wavbreaker >> >> I can still do file releases on SF.net it seems, but I don't seem to >> be able to change the SCM type from SVN to Git, maybe I don't have the >> right permissions. I will also have to look at whether or not I can >> still change the wavbreaker website. Anyway, if there are more patches >> coming, or if a distro packager wants to have a nice release tarball, >> I can try to do that in the upcoming days - let me know. >> >> Thanks, >> Thomas >> >> >> 2015-11-16 2:09 GMT+01:00 Carl Hetherington <li...@ca...>: >> > Hi all, >> > >> > Great work on wavbreaker! I was glad to have found it. >> > >> > I have made a few small changes to unify the track break export options >> > and add the option to export CUE files. The changes are here: >> > >> > https://github.com/cth103/wavbreaker >> > >> > in case anyone is interested. >> > >> > Best regards, >> > Carl >> > >> > >> > ------------------------------------------------------------------------------ >> > Presto, an open source distributed SQL query engine for big data, initially >> > developed by Facebook, enables you to easily query your data on Hadoop in a >> > more interactive manner. Teradata is also now providing full enterprise >> > support for Presto. Download a free open source copy now. >> > http://pubads.g.doubleclick.net/gampad/clk?id=250295911&iu=/4140 >> > _______________________________________________ >> > wavbreaker-devel mailing list >> > wav...@li... >> > https://lists.sourceforge.net/lists/listinfo/wavbreaker-devel >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> wavbreaker-devel mailing list >> wav...@li... >> https://lists.sourceforge.net/lists/listinfo/wavbreaker-devel >> >> > > ------------------------------------------------------------------------------ > _______________________________________________ > wavbreaker-devel mailing list > wav...@li... > https://lists.sourceforge.net/lists/listinfo/wavbreaker-devel |
From: Carl H. <li...@ca...> - 2015-11-17 19:47:38
|
Hi Thomas, Cool, thanks! I'll try to add import of CUE, as you suggested, soon. I can send you a github pull request I suppose. Did you get a chance to test the CUE export changes much? Regards, Carl On Tue, 17 Nov 2015, Thomas Perl wrote: > Hi, > > I've done a proper conversion of the SVN history to Git here now and > merged your changes: > > https://github.com/thp/wavbreaker > > I can still do file releases on SF.net it seems, but I don't seem to > be able to change the SCM type from SVN to Git, maybe I don't have the > right permissions. I will also have to look at whether or not I can > still change the wavbreaker website. Anyway, if there are more patches > coming, or if a distro packager wants to have a nice release tarball, > I can try to do that in the upcoming days - let me know. > > Thanks, > Thomas > > > 2015-11-16 2:09 GMT+01:00 Carl Hetherington <li...@ca...>: > > Hi all, > > > > Great work on wavbreaker! I was glad to have found it. > > > > I have made a few small changes to unify the track break export options > > and add the option to export CUE files. The changes are here: > > > > https://github.com/cth103/wavbreaker > > > > in case anyone is interested. > > > > Best regards, > > Carl > > > > > > ------------------------------------------------------------------------------ > > Presto, an open source distributed SQL query engine for big data, initially > > developed by Facebook, enables you to easily query your data on Hadoop in a > > more interactive manner. Teradata is also now providing full enterprise > > support for Presto. Download a free open source copy now. > > http://pubads.g.doubleclick.net/gampad/clk?id=250295911&iu=/4140 > > _______________________________________________ > > wavbreaker-devel mailing list > > wav...@li... > > https://lists.sourceforge.net/lists/listinfo/wavbreaker-devel > > ------------------------------------------------------------------------------ > _______________________________________________ > wavbreaker-devel mailing list > wav...@li... > https://lists.sourceforge.net/lists/listinfo/wavbreaker-devel > > |
From: Thomas P. <th...@gm...> - 2015-11-17 19:34:47
|
Hi, I've done a proper conversion of the SVN history to Git here now and merged your changes: https://github.com/thp/wavbreaker I can still do file releases on SF.net it seems, but I don't seem to be able to change the SCM type from SVN to Git, maybe I don't have the right permissions. I will also have to look at whether or not I can still change the wavbreaker website. Anyway, if there are more patches coming, or if a distro packager wants to have a nice release tarball, I can try to do that in the upcoming days - let me know. Thanks, Thomas 2015-11-16 2:09 GMT+01:00 Carl Hetherington <li...@ca...>: > Hi all, > > Great work on wavbreaker! I was glad to have found it. > > I have made a few small changes to unify the track break export options > and add the option to export CUE files. The changes are here: > > https://github.com/cth103/wavbreaker > > in case anyone is interested. > > Best regards, > Carl > > > ------------------------------------------------------------------------------ > Presto, an open source distributed SQL query engine for big data, initially > developed by Facebook, enables you to easily query your data on Hadoop in a > more interactive manner. Teradata is also now providing full enterprise > support for Presto. Download a free open source copy now. > http://pubads.g.doubleclick.net/gampad/clk?id=250295911&iu=/4140 > _______________________________________________ > wavbreaker-devel mailing list > wav...@li... > https://lists.sourceforge.net/lists/listinfo/wavbreaker-devel |
From: zezinho <lis...@fr...> - 2015-11-16 21:09:51
|
Em 16-11-2015 02:09, Carl Hetherington escreveu: > Hi all, > > Great work on wavbreaker! I was glad to have found it. > > I have made a few small changes to unify the track break export options > and add the option to export CUE files. The changes are here: > > https://github.com/cth103/wavbreaker > > in case anyone is interested. > > Best regards, > Carl > I am interested a linux distro packager. If upstream does not cherry pick your work, it would be nice to release on github a numbered tarball. |
From: Carl H. <li...@ca...> - 2015-11-16 01:29:10
|
Hi all, Great work on wavbreaker! I was glad to have found it. I have made a few small changes to unify the track break export options and add the option to export CUE files. The changes are here: https://github.com/cth103/wavbreaker in case anyone is interested. Best regards, Carl |
From: José J. <lis...@fr...> - 2008-11-03 20:15:33
|
A Tuesday 28 October 2008 18:45:41, Thomas Perl escreveu: > At least you will be able to download the official source package from > Debian unstable and dpkg-buildpackage it for yourself on older releases. Hi, it just hitted Mandriva too : https://qa.mandriva.com/show_bug.cgi?id=45392 |
From: Dave M. <dm...@re...> - 2008-10-29 20:21:19
|
On Tue, 2008-10-28 at 18:45 +0100, Thomas Perl wrote: > Hi there! > > Thanks to Free Ekanayaka from the Debian Multimedia Team who uploaded > the package to Debian, wavbreaker 0.10 (released earlier this year) is > now available in Debian unstable (should appear in the repos in a few > days). Just in case you wondered where it was :) > > This obviously won't be in the upcoming Etch (for Debian) and Intrepid > (for Ubuntu), but should be available in Debian testing after Etch and > most likely also Ubuntu 9.04, I guess. > > At least you will be able to download the official source package from > Debian unstable and dpkg-buildpackage it for yourself on older releases. Outstanding .... big congrats! 8) ~Dave |
From: Thomas P. <th...@pe...> - 2008-10-29 07:02:16
|
Hi there! Thanks to Free Ekanayaka from the Debian Multimedia Team who uploaded the package to Debian, wavbreaker 0.10 (released earlier this year) is now available in Debian unstable (should appear in the repos in a few days). Just in case you wondered where it was :) This obviously won't be in the upcoming Etch (for Debian) and Intrepid (for Ubuntu), but should be available in Debian testing after Etch and most likely also Ubuntu 9.04, I guess. At least you will be able to download the official source package from Debian unstable and dpkg-buildpackage it for yourself on older releases. Enjoy, Thomas |
From: Avuton O. <av...@gm...> - 2008-07-30 04:19:43
|
On Mon, Jul 28, 2008 at 1:38 AM, Thomas Perl <th...@pe...> wrote: > Hello! > > On Thu, 2008-07-24 at 14:04 -0700, Avuton Olrich wrote: >> This is probably an old bug, but it's something I just noticed in >> wavbreaker r297. If <CTRL-S> is quickly pressed twice it will try to >> save everything twice and eventually segfault. >> >> The bittrace, it appears, to attempt to close the fp twice (right?). > > Thanks for your bug report. I've fixed this bug in revision 300, which > has just been committed to the wavbreaker SVN repository. Please test if > this works for you. > > Thomas Works perfect, thanks! -- avuton -- "I've got a fever. And the only prescription is more cowbell." -- Christopher Walken |
From: Thomas P. <th...@pe...> - 2008-07-28 08:38:26
|
Hello! On Thu, 2008-07-24 at 14:04 -0700, Avuton Olrich wrote: > This is probably an old bug, but it's something I just noticed in > wavbreaker r297. If <CTRL-S> is quickly pressed twice it will try to > save everything twice and eventually segfault. > > The bittrace, it appears, to attempt to close the fp twice (right?). Thanks for your bug report. I've fixed this bug in revision 300, which has just been committed to the wavbreaker SVN repository. Please test if this works for you. Thomas |
From: Avuton O. <av...@gm...> - 2008-07-24 21:04:49
|
Hello, This is probably an old bug, but it's something I just noticed in wavbreaker r297. If <CTRL-S> is quickly pressed twice it will try to save everything twice and eventually segfault. The bittrace, it appears, to attempt to close the fp twice (right?). #0 0x00002ac175b3c1f7 in _IO_new_fclose (fp=0x7cd800) at iofclose.c:60 #1 0x0000000000408df9 in write_thread (data=<value optimized out>) at sample.c:588 #2 0x00002ac174954e74 in g_thread_create_proxy (data=0x7ca700) at gthread.c:635 #3 0x00002ac1758c6067 in start_thread () from /lib/libpthread.so.0 #4 0x00002ac175ba0edd in clone () from /lib/libc.so.6 #5 0x0000000000000000 in ?? () -- avuton -- "I've got a fever. And the only prescription is more cowbell." -- Christopher Walken |
From: Thomas P. <th...@pe...> - 2008-07-24 07:13:17
|
Hello, Tomek and Dave! On Mon, 2008-07-14 at 15:01 -0400, Dave Maley wrote: > On Fri, 2008-07-11 at 00:04 +0200, Thomas Perl wrote: > > On Thu, 2008-07-10 at 14:47 +0200, pasp wrote: > > > I did a new patch for millisecond boundary align support. Since > using > > > this patch the wavbreaker became useful for me ;) > > > > Thanks for this patch, I'll have a look at it in the upcoming days > when > > I get some free time. I've reviewed the patch and fixed some problems (add a confirmation dialog in the preferences settings instead of a simple information dialog). I've also added the SBE warning dialog when writing tracks (like this: http://khan.thpinfo.com/~thp/images/wavbreaker-sbe-dialog.png). I have not yet implemented the "Fix track breaks" functionality, as I'm not sure how to best switch the boundary align setting and interpolate the track breaks. @Tomek: Maybe you can have a look at the "Fix track breaks" functionality, as you've written the milliseconds code too and probably have a better understanding of it? The new patch is attached. Thanks, Thomas |
From: Thomas P. <th...@pe...> - 2008-07-23 16:45:03
|
Hello! On Mon, 2008-07-14 at 15:01 -0400, Dave Maley wrote: > On Fri, 2008-07-11 at 00:04 +0200, Thomas Perl wrote: > > On Thu, 2008-07-10 at 14:47 +0200, pasp wrote: > > > I did a new patch for millisecond boundary align support. Since using > > > this patch the wavbreaker became useful for me ;) > > > > Thanks for this patch, I'll have a look at it in the upcoming days when > > I get some free time. > > > > @Dave/Timothy: Can you test this patch and tell me what you think of it? > > I hope to have some time this week to do some testing .... If you don't have time, I'll try to review it either tomorrow or on Friday, depending how I can fit this task into my schedule :) Feel free to do the review, too, so we have more feedback for Tomek. > Also providing warnings when writing non-aligned tracks is a nice idea, > but only so long as it doesn't add much overhead in processing the > writes. We might want to add a warning dialog _before_ writing the track breaks and then only once, like this dialog I quickly drafted with Glade: http://khan.thpinfo.com/~thp/images/wavbreaker-sbe-dialog.png This would make it easy for the user to fix sector boundary errors in case they accidentally messed them up, but also allows for "power users" to use "I know what I do" to break the files in milliseconds steps. What do you think? Thomas |
From: Dave M. <dm...@re...> - 2008-07-14 19:01:35
|
On Fri, 2008-07-11 at 00:04 +0200, Thomas Perl wrote: > Hello, Tomek! > > On Thu, 2008-07-10 at 14:47 +0200, pasp wrote: > > I did a new patch for millisecond boundary align support. Since using > > this patch the wavbreaker became useful for me ;) > > Thanks for this patch, I'll have a look at it in the upcoming days when > I get some free time. > > @Dave/Timothy: Can you test this patch and tell me what you think of it? I hope to have some time this week to do some testing .... > > I think I didn't break anything (it works fine for me), but please > > test patch extensively before commit (especially for gape less cutting > > - didn't burn any cds with tracks extracted by wavbreaker, however the > > parts are identical as the parts obtained by previous versions). > > You can use "shntool" (http://etree.org/shnutils/shntool/) to test the > resulting wave file for sector boundary errors (it seems like shntool > can even fix the sector boundary errors by moving data from the > end/start of adjacent wave files to the other file, so the wave files > fill the CD sectors again. > > For wavbreaker, we should by default produce wave files with correct > sector alignment and only allow SBEs when the user has accepted the > warning (I see from quickly looking at the patch that you have > implemented something like that). > > Maybe we can also display the sector boundary warning when writing track > breaks (we should be able to detect SBEs by simply checking for the > modulo result of dividing the track break positions by the CD sector > size (CD_BLOCKS_PER_SEC, I think). I like the idea of forcing the user to accept the warning before allowing non-aligned breaks, makes perfect sense considering sector boundary alignment is 1 of the most fundamental aspects of wavbreaker. Also providing warnings when writing non-aligned tracks is a nice idea, but only so long as it doesn't add much overhead in processing the writes. ~Dave |
From: Thomas P. <th...@pe...> - 2008-07-10 22:05:05
|
Hello, Tomek! On Thu, 2008-07-10 at 14:47 +0200, pasp wrote: > I did a new patch for millisecond boundary align support. Since using > this patch the wavbreaker became useful for me ;) Thanks for this patch, I'll have a look at it in the upcoming days when I get some free time. @Dave/Timothy: Can you test this patch and tell me what you think of it? > I think I didn't break anything (it works fine for me), but please > test patch extensively before commit (especially for gape less cutting > - didn't burn any cds with tracks extracted by wavbreaker, however the > parts are identical as the parts obtained by previous versions). You can use "shntool" (http://etree.org/shnutils/shntool/) to test the resulting wave file for sector boundary errors (it seems like shntool can even fix the sector boundary errors by moving data from the end/start of adjacent wave files to the other file, so the wave files fill the CD sectors again. For wavbreaker, we should by default produce wave files with correct sector alignment and only allow SBEs when the user has accepted the warning (I see from quickly looking at the patch that you have implemented something like that). Maybe we can also display the sector boundary warning when writing track breaks (we should be able to detect SBEs by simply checking for the modulo result of dividing the track break positions by the CD sector size (CD_BLOCKS_PER_SEC, I think). Thanks, Thomas |
From: pasp <pa...@ll...> - 2008-07-10 12:48:44
|
Hi, I did a new patch for millisecond boundary align support. Since using this patch the wavbreaker became useful for me ;) I think I didn't break anything (it works fine for me), but please test this patch extensively before commit (especially for gape less cutting - I didn't burn any cds with tracks extracted by wavbreaker, however the parts are identical as the parts obtained by previous versions). Tomek |
From: Dave M. <dm...@re...> - 2008-07-09 20:23:21
|
On Mon, 2008-07-07 at 00:17 +0200, Thomas Perl wrote: > Hello! > > On Sun, 2008-07-06 at 01:12 +0200, pasp wrote: > > On Sat, 05 Jul 2008 15:08:34 +0200 Thomas Perl <th...@pe...> wrote: > > > Can you please split these changes into separate patches? > > > I'll apply them then. > > > > Patches included. It was boring work ;) > > I can imagine that. But very helpful also! I've merged all your patches > into wavbreaker SVN trunk now :) Great work, these patches! Great to see the contributions, welcome to wavbreaker development Tomek! FWIW I'll second Thomas' acceptance of these, even tho they're already committed ;) ~Dave |
From: Thomas P. <th...@pe...> - 2008-07-06 22:17:13
|
Hello! On Sun, 2008-07-06 at 01:12 +0200, pasp wrote: > On Sat, 05 Jul 2008 15:08:34 +0200 Thomas Perl <th...@pe...> wrote: > > Can you please split these changes into separate patches? > > I'll apply them then. > > Patches included. It was boring work ;) I can imagine that. But very helpful also! I've merged all your patches into wavbreaker SVN trunk now :) Great work, these patches! Thanks, Thomas |
From: pasp <pa...@ll...> - 2008-07-05 23:12:35
|
On Sat, 05 Jul 2008 15:08:34 +0200 Thomas Perl <th...@pe...> wrote: > Can you please split these changes into separate patches? > I'll apply them then. Patches included. It was boring work ;) Tomek |
From: Thomas P. <th...@pe...> - 2008-07-05 18:12:59
|
On Sat, 2008-07-05 at 16:05 +0200, pasp wrote: > On Sat, 05 Jul 2008 15:08:34 +0200 > Thomas Perl <th...@pe...> wrote: > > > I've merged the about box changes. I've removed the toolbar style > > changes from your patch and attached your patch in this mail. > > I must be blind or something, but there were no attachments in > previous mail. Could you send it to me directly? Silly me - forgot it.. Here's the attachment :) Thomas |
From: pasp <pa...@ll...> - 2008-07-05 14:10:36
|
On Sat, 05 Jul 2008 15:08:34 +0200 Thomas Perl <th...@pe...> wrote: > I've merged the about box changes. I've removed the toolbar style > changes from your patch and attached your patch in this mail. I must be blind or something, but there were no attachments in previous mail. Could you send it to me directly? Tomek |
From: Thomas P. <th...@pe...> - 2008-07-05 13:08:45
|
Hello! On Sat, 2008-07-05 at 12:23 +0200, pasp wrote: > On Sat, 5 Jul 2008 13:35:07 +0200 Thomas Perl <th...@pe...> wrote: > > > Since I don't use GNOME I don't know where change the settings. Is it > > > configurable via .gtkrc-2.0 ? > > > > See here: http://bbs.archlinux.org/viewtopic.php?id=45371 > > Ah, I didn't know about it. Thanks! I've removed the toolbar style configuration option from your patch for these reasons. > > See http://wiki.etree.org/index.php?page=SeedingGuidelines - > > especially the section "Tracking at Sector Boundaries". > > > > We can have support for milliseconds if you implement it, although > > the files cut that way can then not be burned onto CD "gapless". My > > idea would be to have an option "Enable cutting at milliseconds" that > > - when clicked - will ask for confirmation from the user describing > > the problems with tracks not cut at sector boundaries. > > Now I understand CD blocks alignment magic :) I like you suggestion, so I > added it to my TODO list. Very good, waiting for your patch :) > > We could always need some help maintaining/improving it. > > By the way, could you commit accepted parts of my patch into trunk? > It would make life easier in preparing next patches :) I've merged the about box changes. I've removed the toolbar style changes from your patch and attached your patch in this mail. Can you please split these changes into separate patches? I'll apply them then. - Main window x/y positioning patch (accepted) - Action select all/none/invert (change to "check" instead of "select) - gtk/glib "sanity" changes (accepted) - Ctrl+Space for jump to cursor (accepted) - The rest This would make my life easier, because I then know which changes in the code reflect which patch/part :) Will merge the "accepted" patches right away and for the select/check patch, simply change the code to read "check" (or something) instead of "select" for reasons described in one of the last mails. Thanks! Thomas |
From: pasp <pa...@ll...> - 2008-07-05 10:28:52
|
On Sat, 5 Jul 2008 13:35:07 +0200 Thomas Perl <th...@pe...> wrote: > Hello! Hi Thomas, > > Ah, I forgot about "standard" meaning of CTRL-Z (I use that shortcut > > because Z key is near CTRL key :) So, what about "CTRL-Space" ? > > Ctrl+Space is fine for me (this means: at least I don't know about > any "standard" behaviour for Ctrl+Space). Nice. I will change it in the next patch. > > Since I don't use GNOME I don't know where change the settings. Is it > > configurable via .gtkrc-2.0 ? > > See here: http://bbs.archlinux.org/viewtopic.php?id=45371 Ah, I didn't know about it. Thanks! > See http://wiki.etree.org/index.php?page=SeedingGuidelines - > especially the section "Tracking at Sector Boundaries". > > We can have support for milliseconds if you implement it, although > the files cut that way can then not be burned onto CD "gapless". My > idea would be to have an option "Enable cutting at milliseconds" that > - when clicked - will ask for confirmation from the user describing > the problems with tracks not cut at sector boundaries. Now I understand CD blocks alignment magic :) I like you suggestion, so I added it to my TODO list. > > Then I'll look into it in the near future :) > > Very good :) Maybe you really want to subscribe to wavbreaker-devel > to keep up with development news and join development of wavbreaker? Subscribed :) > We could always need some help maintaining/improving it. By the way, could you commit accepted parts of my patch into trunk? It would make life easier in preparing next patches :) Greets, Tomek |
From: Thomas P. <th...@pe...> - 2008-07-05 09:35:29
|
Hello! On Jul 4, 2008, at 7:47 PM, pasp wrote: > On Fri, 04 Jul 2008 17:24:32 +0200 > Thomas Perl <th...@pe...> wrote: > >>> * Added CTRL-Z accel for "Jump to cursor marker" >> >> Ctrl-Z is usually the "Undo" key. Is there any specific reason why >> you >> selected this one? I agree that having a accel for the "Jump to >> cursor" >> function is good, but maybe we should think of some other key? > > Ah, I forgot about "standard" meaning of CTRL-Z (I use that shortcut > because Z key is near CTRL key :) So, what about "CTRL-Space" ? Ctrl+Space is fine for me (this means: at least I don't know about any "standard" behaviour for Ctrl+Space). >>> * Three new commands in pop-up menu: >>> "Select All/Select None/Invert Selection" >> >> Very helpful. Maybe we should change the wording from "select" to >> "check", as selecting items is different from checking items. > > I agree. > >>> * An option do change toolbar style (icons / icons+text) >> >> We should probably not make this an option, as GNOME/GTK+ has a >> system-global default setting (in the "Appearance" dialog). I >> think the >> user should set their global toolbar preferences and not deal with >> the >> toolbar appearance per-application. I'd rather not have this as an >> added >> preference. > > Since I don't use GNOME I don't know where change the settings. Is it > configurable via .gtkrc-2.0 ? See here: http://bbs.archlinux.org/viewtopic.php?id=45371 >>> Do you mind if I add an option to choose between of milliseconds and >>> CD_BLOCKS_PER_SECOND ? The former is more intuitive for me - I use >>> your app to split speech samples. >> >> I don't really have an opinion about this, as I do most of my >> cutting by >> listening and trial-and-error. > > Hm, I don't understand what not use milliseconds to point exact > place in > sample. So, if you do cutting by listening and trial-and-error method > then everyone should use the same way? ;) (please forgive me if it > sounds offensive) > I think Wavbreaker has potential and can be used for other tasks than > CD Audio cutting only. Therefore, I thought an option for > CD_BLOCKS_PER_SECONDS vs MS choice (with CD_BLOCKS_PER_SECONDS as > default) should be compromise or I miss something? See http://wiki.etree.org/index.php?page=SeedingGuidelines - especially the section "Tracking at Sector Boundaries". We can have support for milliseconds if you implement it, although the files cut that way can then not be burned onto CD "gapless". My idea would be to have an option "Enable cutting at milliseconds" that - when clicked - will ask for confirmation from the user describing the problems with tracks not cut at sector boundaries. >>> Also, Is anyone already working on automatic segmentation based on >>> intensity, RMS amplitude or noise level? >> >> There is some very primitive code for jumping to silent parts, but >> it's >> not very intelligent and does not have the ability to automatically >> segment audio. > > Then I'll look into it in the near future :) Very good :) Maybe you really want to subscribe to wavbreaker-devel to keep up with development news and join development of wavbreaker? We could always need some help maintaining/improving it. Thanks, Thomas |