Re: HostCallback_GetBeatAndTempo
Re: HostCallback_GetBeatAndTempo
- Subject: Re: HostCallback_GetBeatAndTempo
- From: Earl Vickers <email@hidden>
- Date: Fri, 9 Jun 2006 08:42:12 -0700
Title: Re:
HostCallback_GetBeatAndTempo
We've had reports of crashes with our SFX Machine RT AU plug-in
in MOTU Digital Performer 4.6 and 5. The crash appears to be in
MasAUSupportProc::GetBeatAndTempoProc().
For example:
OS Version: 10.4.5 (Build
8H14)
Command: Digital Performer
Version: 4.6 (4.6)
PID: 917
Thread: 0
Exception: EXC_BAD_ACCESS (0x0001)
Codes:
KERN_PROTECTION_FAILURE (0x0002) at 0x00000000
Thread 0 Crashed:
0
<<00000000>>
0x00000000 0 + 0
1
com.MOTU.MAS.AudioUnitWrapper
0x08b5dd38 MasAUSupportProc::GetBeatAndTempoProc(void*,
double*, double*) + 52
2
...sfxmachine.SfxMachinePro.AU
0x10212dac ASfxEntry + 15596
In SFX Machine Pro, we are calling it as follows:
float
ASfx::getHostTempo()
{
#if
TARGET_API_AUDIOUNIT
OSStatus ret;
Float64 tempo = 120.0;
Float64 beat = 0.0;
ret
= CallHostBeatAndTempo(&beat, &tempo);
...
Are we doing something wrong, or is there a known problem in this
area?
Google found a report of a crash in that routine with the UAudio
CS-1 and DP 4.6x:
Posted:
Thu Feb 09, 2006 7:22 pm Post subject:
CS-1 crashes after 4.1 update w/ DP
4.6(.1)
Activating it causes
an instant crash in DP 4.6 and 4.6.1. I've tried all the usual things
to fix but nothing has helped to date. I have a backtrace if it's
helpful to anyone. Is anyone else having this
issue?
Exception:
EXC_BAD_ACCESS (0x0001)
Codes:
KERN_PROTECTION_FAILURE (0x0002) at 0x00000018
Thread 0
Crashed:
0
com.MOTU.MAS.AudioUnitWrapper 0x0ab06e6c
MasAUSupportProc::GetBeatAndTempo(double*, double*) +
72
1
com.MOTU.MAS.AudioUnitWrapper 0x0ab06d38
MasAUSupportProc::GetBeatAndTempoProc(void*, double*, double*) +
52
2
com.uaudio.effects.UAD CS-1 0x11b4d8e0 CUADAudioUnitPluginEntry +
18244
3
com.uaudio.effects.UAD CS-1 0x11b49518 CUADAudioUnitPluginEntry +
892
Robert Grant wrote:
Here's a surprise. Oddity AU is blowing chunks if I
set the BeatAndTempo property on it! Not immediately, put pretty soon
after.
Here's a portion of the call stack - looks
surprisingly shallow:
Thread 3 Crashed:
#0 0x05c25004 in 0x5c25004
#1 0x05bd52b4 in
AUMIDIBase::ComponentEntryDispatch(ComponentParameters*, AUMIDIBase*)
(AUMIDIBase::ComponentEntryDispatch(ComponentParameters*, AUMIDIBase*)
+ 88)
#2 0x05bd5478 in
MusicDeviceBase::ComponentEntryDispatch(ComponentParameters*,
MusicDeviceBase*)
(MusicDeviceBase::ComponentEntryDispatch(ComponentParameters*,
MusicDeviceBase*) + 108)
#3 0x05b72418 in AUMusicDeviceEntry
(AUMusicDeviceEntry + 120)
#4 0x90281a90 in CallComponent (CallComponent +
212)
#5 0x91a90a0c in MusicDeviceMIDIEvent
(MusicDeviceMIDIEvent + 52)
Earl Vickers
--
The Sound Guy, Inc.
email@hidden
http://www.sfxmachine.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden