On Tuesday 11 February 2003 01:05 am, Dominic Mazzoni wrote:
> In a nutshell, yes, Audacity is totally tuned for working on a local dr=
> However, you may be able to get better results by changing the
> block size. I'm not even sure whether larger or smaller blocks
> would give you better performance - it depends on whether
> throughput or latency is the main bottleneck with NFS, and I'm
> not sure.
Um, I'm working on it. My CVS snapshot is from December 1st of last year=
this going to have the blockfile rewrites that you guys did, or is it jus=
> Open Sequence.cpp and change sMaxDiskBlockSize to some other
> power of two. Try drastic changes, like 65536 and 8 MB.
> The Run Benchmark command in the Help menu will also help with
> this. Try it on your local drive first, to get an idea of
> how it performs. Then try it on your network drive, and see
> what sorts of block sizes give you the best performance. I'd
> be very interested in hearing your quantitative results.
> - Dominic
> Dave Fancella wrote:
> > On Monday 10 February 2003 10:29 pm, Dominic Mazzoni wrote:
> > Um, while we're on the subject of full disks, I thought I'd bring thi=
> > up. I was experimenting with an older cvs snapshot earlier today (I'=
> > still waiting for alsa, remember :) ), and here is what I experienced=
> > First, my sound workstation (so to speak, it's also the tv, the stere=
> > etc.) has a 4GB hard drive in it. I mount up 100GB worth of space fr=
> > server (locked up from the kids) over NFS.
> > Using a project stored in my home directory that's piped in over NFS,
> > with a couple of tracks, I get a lot of popping and clicking. The ki=
> > of noises that make you think "hmm, the buffer's not filling fast
> > enough". NFS is supposed to be pretty slow for this type of applicat=
> > but I've not had noticeable problems that were nfs-related with ecaso=
> > Of course, ecasound manages the hard drive space totally differently
> > than audacity in that it doesn't manage anything.
> > So I repeated the operation on my local hard drive. The operation
> > amounted to importing 6 tracks that were recorded this weekend on a h=
> > drive recorder and exported as wav files to CD. Now I import them in=
> > audacity. 2 tracks combine as a single stereo drum track. Two guita=
> > tracks (I combined them and thought better of it), a bass track, and =
> > singer. I applied an effect to the singing at one point (slight phas=
> > On the local hard drive the popping and clicking goes away most of th=
> > time. I managed to get it to come back by playing all 6 tracks at onc=
> > with the phase effect applied. On NFS the popping and clicking comes=
> > with one track and gets geometrically worse as you add tracks. I did=
> > even try to apply effects when I ran it over NFS.
> > The conclusion, then, is that your BlockFile classes are optimized fo=
> > working on local hard drives, which means they would probably perform=
> > I experienced over NFS.
> > Now the qeustion. (Always with me it's a long explanation and a shor=
> > question that gets one or two words answer ;) ) Is this the intende=
> > behavior? Is Audacity *supposed* to be used only on local hard drive=
> > and not across the network as I have been attempting to? If so, is t=
> > any plan or intent to try to make it work better under certain condit=
> > over NFS? (I have tried tweaking NFS for performance and found the
> > default settings were better than any tweaks I did)
> > Dave
> >>OK, I went ahead and implemented a recording time indicator in the
> >>status bar. It only shows up while you're recording, and it only
> >>shows up if you're idle for at least 3 seconds - that way it doesn't
> >>get in the way of the tooltips and other things in the status bar.
> >>Another thing we need to do is have Audacity just gracefully stop
> >>recording when the disk is full (ideally a few seconds earlier!).
> >>- Dominic
> >>Tino Meinen wrote:
> >>>Op ma 10-02-2003, om 21:43 schreef Anthony Airon Oetzmann:
> >>>>>Status bar. :)
> >>>>Is there still room ?
> >>>>How about "Rectime left h:mm:ss"
> >>>Please try to avoid using abreviations, they're (nearly) impossible =
> >>>translate correctly and there are already too many of them in audaci=
> >>>If space on the statusbar is sparse, just show the time, and use a
> >>>tooltip to explain the meaning: Recording time left before all free
> >>>space on the drive is used up.
> >>>(or somthing similar)
> >>>--Tino Meinen
> >>>This SF.NET email is sponsored by:
> >>>SourceForge Enterprise Edition + IBM + LinuxWorld =3D Something 2 Se=
> >>>Audacity-devel mailing list
> >>This SF.NET email is sponsored by:
> >>SourceForge Enterprise Edition + IBM + LinuxWorld =3D Something 2 See=
> >>Audacity-devel mailing list
> This SF.NET email is sponsored by:
> SourceForge Enterprise Edition + IBM + LinuxWorld =3D Something 2 See!
> Audacity-devel mailing list
"I slipped inside the oval office,
I slipped in oh so fast,
Grabbed the president by the necktie
And wiped my funky ass, hey"