i am unable to reproduce this bug in audacity 1.3.9 (latest karmic). can anyone see if they can still produce it?
i am unable to reproduce this bug in audacity 1.3.9 (latest karmic). can anyone see if they can still produce it?