Change Tempo Effect Crashes

[Brian Smith]

I can't find this reported anywhere so I hope I haven't duplicated. The Change Tempo effect on an hour-long project crashes all open Audacity screens. On reopening recovery seems to work properly without data loss. This has happened three times in succession.

[waxcylinder]

This is a known regression issue for 3.0.0 (affects all Nyquist effects) - this has been fixed for the soon to be upcoming 3.0.1 release.

Peter.

[steve]

affects all Nyquist effects

Different bug. "Change Tempo" is not a Nyquist plug-in, it's a built-in effect.

This has happened three times in succession.

Does the problem occur with one specific project, or is it a general problem that occurs in any project when the selection is more than an hour?

Which version of Audacity are you using? (look in "Help menu > About Audacity")

[waxcylinder]

affects all Nyquist effects

Different bug. "Change Tempo" is not a Nyquist plug-in, it's a built-in effect.

OOPS

I just tested Change Tempo with a one hour stereo chirp and it worked just fine with 3.0.0 on W10

Peter

[steve]

I'm not able to reproduce the problem either, indicating that we need more information to proceed.

[Brian Smith]

Thanks for your responses. I'm using Windows 10 Home v.20.H2.

The crash happens whenever I apply the Change Tempo function, even on short stretches. I installed v.3.0.0 and as my first session imported three one hour .aup files. They've been saved as .aup3 files but I notice distortion spikes have crept in. Could they be corrupted as a result of the file format conversions?

Tomorrow I'll reinstall v.3.0.0 and try to rebuild my projects.

[waxcylinder]

... I installed v.3.0.0 and as my first session imported three one hour .aup files. They've been saved as .aup3 files but I notice distortion spikes have crept in. Could they be corrupted as a result of the file format conversions?

I did a LOT of extensive QA testing importing old AUP files from earlier Audacities (even as far back as 1.2.6) and I nevere encountered such distotyion or spikes.

Peter.

[steve]

but I notice distortion spikes have crept in. Could they be corrupted as a result of the file format conversions?

It's possible that the tracks already had some invalid sample data, which would go some way to explaining the crashes, and would also explain the spikes in the converted project.

How big are these projects? (total size of the "_data" folder).

Please zoom in very close on one of the spikes in the AUP3 version and take a screenshot to show us.
See: https://manual.audacityteam.org/man/screenshot.html
and: viewtopic.php?f=49&t=64936

[Brian Smith]

UPDATE:

I reinstalled v3.0.0 and resumed work; pleased to say I've not experienced any nasty spikes since I rebuilt the damaged projects. I forgot to mention that as well as the spikes and distortion, the sound levels rose to unacceptable levels. I've created 9 small projects in v.3.0.0 of 17-18 minutes each (compared with the hour projects converted from v.2.4.2) and all seems well. I applied the Change Tempo effect to one of those and it worked without crashing.

@Steve: the _data folders were in the region of 1¼Gb, each representing an hour of music. With so many small files I can see the scope for corruption.

I'll report if anything changes, otherwise thanks Steve and Waxcylinder for your input.

CONCLUSION: After 35 years at the IT coalface nothing surprises me about computers. My guess is the first v.3.0.0 installation didn't complete properly, otherwise Windows or a program running concurrently somehow corrupted it. Had the problems persisted I would have regressed to v2.4.2 and awaited a stable v.3. If the reinstalled version continues to work I won't lose any sleep on it!

[steve]

Thanks for the update.

There is a new version of Audacity scheduled for release later this month (Audacity 3.0.1). It contains some bug fixes so it is highly recommended for all Audacity 3.0.0 users to update to the new version as soon as it is available.