Thanks for the long comments. We are reading it; it may take
us a while to respond to most of your points...
Haas Wernfried wrote:
> On Mon, Jul 22, 2002 at 12:30:22AM -0500, Tim Jackson wrote:
>>is, how well will it be able to handle a 85-90minute 48000hz sound file
>>with lots of other tracks coming in and going out the entire time? The
>>system that I'm doing this editing on is pretty hefty, its an Athlon 1800+
>>w/ 1GB of PC2700 (DDR333). This is all running under Debian too. Anyone
>>out there using Audacity to undertake anything this big? If so, how well
>>is it working? Any little glitches or anything to be aware of?
> i've tried editing files up to 90 minutes with audacity (cut beginning, end,
> envelope(fade in/out) and stuff like this). i had some problems with it, so
> let's see.
> BUT: i just tried version 1.0 not any newer and i haven't yet filed any
> bugreport / feature request about this because i was too lazy, so i can't
> really blame the developers for not solving my problems ;)
> so let's write down a bugreport and feature request right now:
> first i'll try to compile version 1.1. but it fails:
> ./configure --without-libmad --without-vorbis --without-id3tag (some stuff
> missing on my system)
> make: Leaving directory `/home/mud/audacity-src-1.1.0/lib-src/allegro'
> cd portaudio/pa_unix_oss && make
> make: Entering directory
> gcc -c -g -I../pa_common ../pa_common/pa_lib.c -o ../pa_common/pa_lib.o
> gcc -c -g -I../pa_common pa_unix_oss.c -o pa_unix_oss.o
> pa_unix_oss.c: In function `PaHost_CanaryProc':
> pa_unix_oss.c:551: void value not ignored as it ought to be
> pa_unix_oss.c: In function `PaHost_WatchDogProc':
> pa_unix_oss.c:597: void value not ignored as it ought to be
> make: *** [pa_unix_oss.o] Error 1
> make: Leaving directory
> make: *** [portaudio/pa_unix_oss/portaudio.a] Error 2
> make: Leaving directory `/home/mud/audacity-src-1.1.0/lib-src'
> make: *** [audacity] Error 2
> gcc version is 2.95.2, kernel 2.4.18, anything else you need to know?
> (i guess so, but what?)
> so, i'll just bugreport and request features for 1.0 and i'll be very pedantic
> and i'll complain about almost everything and it will be very annoying for
> every developer. so i just want to say that i've looked quite long for some
> software to edit big sound files under linux and that audacity is definitely
> the best :)
> it is also quite possible that i overlooked some features which i complain
> to be missing are already in audacity and that i was too dumb to find it
> in the docs ;)
> just to explain what i want to do with audacity most of the time: i record
> some stuff from the radio and it is splittet into several files (one per
> hour). now i want to e.g. take the last 20 minutes of the first file, append
> the second one and delete the last 30 minutes of the second and save.
> alright, i start audacity and resize it to fit my display. after closing
> and restarting, window size is small again. could audacity remember it,
> now file #1 is loaded, works fine, although i'd prefer to have it zoomed to
> fit the window by default, too.
> now i am searching the beginning of the stuff i want to keep. this means
> setting cursor at different points and playing the file. pressing stop and
> play all the time is too much work for me, could just pressing the
> play-button start playing at the point where the cursur is set? would be
> i usually zoom in while searching to find the starting point more exactly,
> a "zoom-into-selection" feature (like in cool edit) would be great.
> if i finally have found the point of interest, i select everything from
> the starting point (means 0 seconds) to the actual point (let's say 5
> minutes). problems here:
> - shift-mouse-left works fine for extending selections, but could this please
> be done with mouse-right, too? it's unused anyway in the select function.
> - if i extend my selection to the left (0 seconds) and i do not go to the
> very lift, i don't get to 0 seconds, but 5 seconds. if i click too far on the
> left (actually out of the spectrogram onto the "titlebar", the focus is no
> longer on this track and i the selection seems to be lost :-/ there
> are some workarounds using existing functions of audacity, but a "select
> from here to the beginning/end" feature and/or a way to select things better
> would be great. in cool edit is some space before and after the spectrogram,
> clicking there selects to the beginning/end, seems quite useful to me. if
> you select in one click, audacity even scrolls and it is possible to move
> just to the beginning, but with shift-click, this does not work.
> now the beginning is finally cut and now it is time to append the second part
> exactly at the end of the first.
> as i did not find a way to append file #2 directly after #1 i just import #2,
> select and cut the whole track, cut it, set cursor after the end of #1 and
> paste it. the to tracks are now appended without any gap, which is great.
> now i just want to fade out the ending, which works fine, too. even if i
> select some seconds beyond the ending of the track, audacity fades out
> exactly to the ending and not the virtually selected point somewhere in
> time :)
> the whole thing is exported as wav file, done.
> now the really funny thing:
> i installed audacity some weeks ago, played a bit around, audacity always
> crashed somewhere after importing the second file. now i have done the
> dings described up there three times without a crash. of course this is
> great, but i don't really understand why. is it possible, that something
> was not installed right at first, but was solved in between (maybe a missing
> ldconfig or something like this? i installed wxGTK-2.2.9 as root and
> including make install and just compiled audacity, but did not use make
> install. i'm quite sure i installed something else in between, maybe
> this has solved the problem. other theory: i just didn't do things that
> crash audacity right now).
> now for some more random stuff:
> - the selected time is shown in the info-window below the spectrogram, it says
> something like "Selection 1000s - 400s", what about showing lenght of
> selection too ("Selection 1000s - 400s = 600s"). a preffered unit (always
> show time in minutes/seconds would be nice, too.
> - after zooming in via selecting an area by holding down the mouse button,
> right mouse button zooms in instead of out
> so, to finally answer Tim Jackson's questions:
> apart from the fact, that i have had some no longer reproducible crashes
> (which i hope will never ever appear again) and some problems with the
> interface (maybe i'm just too dumb to switch from cool edit to audacity),
> i think that audacity is quite capable to edit really big files.
> dear developers: good work!
> PS: whoo, this post really got long...
> PPS: on this list, the reply address is not the one of the list, but of the
> person who sent it. intenton? feature? bug?