Audacity Bug Summary
••• Introduction •••
••• Keywords •••
    Audacity 3.0.3 development began 19th April 2021

Audacity Bugzilla



Bug 89 - CoreAudio crash when input device's sample rate is 44100 and the output device's sample rate is 48000
CoreAudio crash when input device's sample rate is 44100 and the output devic...
Status: CLOSED WORKSFORME
Product: Audacity
Classification: Unclassified
Component: Application Core
1.3.11
Mac macOS
: P4 Repeatable
Assigned To: Default Assignee for New Bugs
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-01-28 15:28 UTC by James Crook
Modified: 2018-08-20 11:45 UTC (History)
4 users (show)

See Also:
Steps To Reproduce:
???
Release Note:
First Git SHA:
Group: ---
Workaround:
Closed: 2018-08-20 00:00:00


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description James Crook 2010-01-28 15:28:34 UTC

    
Comment 1 Paul L 2016-06-20 17:33:16 UTC
How is this reproduced?
Comment 2 Paul L 2016-06-20 17:33:38 UTC
How is this reproduced?
Comment 3 Gale Andrews 2016-06-20 18:55:59 UTC
It seems to have been transferred from http://wiki.audacityteam.org/wiki/Release_Checklist when we abandoned that tracking method. 

I don't recall being involved with that bug - perhaps Leland found it. I don't know what it means unless it's about overdub recording. It could mean playback to one device, recording from another device, and the devices' sample rates differ in Audio MIDI Setup.

Or it could mean that the playback and recording rates of one device differ in Audio MIDI Setup. If that crashed we would probably know about, it because users of external interfaces often receive wrong-speed or crackly recording if they mismatch rates anywhere. 

Given we are now several PortAudio versions later, I think this should be closed WORKSFORME unless James knows anything more about it.