Problem with overdub...
Forum rules
If you require help using Audacity, please post on the forum board relevant to your operating system:
Windows
Mac OS X
GNU/Linux and Unix-like
If you require help using Audacity, please post on the forum board relevant to your operating system:
Windows
Mac OS X
GNU/Linux and Unix-like
Re: Problem with overdub...
Actually it looks like export selection only exported track 2 there, but that is the one with the "issue" so that should suffice 
Re: Problem with overdub...
Yes indeed it does suffice. You have a bad case of "drop-outs" (skips). I don't know why you are getting it as bad as that with only two tracks. I would have expected that you would be able to run at least a dozen tracks before anything like that. There are some general tips about skips here: http://wiki.audacityteam.org/wiki/Troub ... ings#Skips that you can try, but it seems that something in your system is just not happy.elsigh wrote:that is the one with the "issue" so that should suffice
Why are you killing PulseAudio? Current versions of Audacity should be able to run very well with PulseAudio running.
I have "Edit menu > Preferences > devices" set to "ALSA", "default", "default" "2 (stereo)"
"Edit menu > Preferences > Quality" set to "44100/32 bit/fastest sinc/none/Best sinc/shaped".
I'm currently running Karmic, but I've used the same settings on Lucid.
I use the "PulseAudio Applet" (Pulse Audio Device Chooser) for setting the input and playback settings.
If none of this works for you, would you consider using Jack audio system? Ideally Jack should run on a Real Time Kernel (as in Ubuntu Studio) but I've had Audacity 1.3.12 run well with Jack on a stock Ubuntu installation.
9/10 questions are answered in the FREQUENTLY ASKED QUESTIONS (FAQ)
Re: Problem with overdub...
I run jack in non-realtime mode (I built a RT kernel, but then I had problems building the graphics nvidia driver against it, so I had to go back to the stock non-RT kernel). At the beginning I used to have some occasional xruns which would come noticeable as glitches on listening. I solved my problem by running jackd with the '-s' option (from the manpage: --softmode Ignore xruns reported by the ALSA driver. This makes JACK less likely to disconnect unresponsive ports when running without --realtime). I think the occasional xruns still occur but there's no more noticeable glitches in the hearing.stevethefiddle wrote:If none of this works for you, would you consider using Jack audio system? Ideally Jack should run on a Real Time Kernel (as in Ubuntu Studio) but I've had Audacity 1.3.12 run well with Jack on a stock Ubuntu installation.
Include as much details as you can in your post (Audacity version, Operating System, Equipment used, etc).
Please post your question in the appropriate forum (regarding audacity version and operating system).
Please post your question in the appropriate forum (regarding audacity version and operating system).