Re: What could cause error -4 in Logic validation?
Re: What could cause error -4 in Logic validation?
- Subject: Re: What could cause error -4 in Logic validation?
- From: Howard Moon <email@hidden>
- Date: Fri, 26 Sep 2014 10:34:45 -0700
I'm not sure what in the plist would cause a render failure. It passes everything up until that point, when I get this:
RENDER TESTS:
Implements: AudioUnitProcess, AudioUnitProcessMultiple
Input Format: AudioStreamBasicDescription: 2 ch, 44100 Hz, 'lpcm' (0x00000029) 32-bit little-endian float, deinterleaved
Output Format: AudioStreamBasicDescription: 2 ch, 44100 Hz, 'lpcm' (0x00000029) 32-bit little-endian float, deinterleaved
Render Test at 512 frames
ERROR: -4 IN CALL AudioUnitRender
* * FAIL
--------------------------------------------------
AU VALIDATION FAILED: CORRECT THE ERRORS ABOVE.
--------------------------------------------------
From that "implements" line above, it looks like the following code is causing it (from CAAudioUnit.cpp):
OSStatus CAAudioUnit::ProcessMultiple (AudioUnitRenderActionFlags & ioActionFlags,
const AudioTimeStamp & inTimeStamp,
UInt32 inNumberFrames,
UInt32 inNumberInputBufferLists,
const AudioBufferList ** inInputBufferLists,
UInt32 inNumberOutputBufferLists,
AudioBufferList ** ioOutputBufferLists)
{
#if defined(__MAC_10_7) || defined(__IPHONE_4_0)
return AudioUnitProcessMultiple (AU(), &ioActionFlags, &inTimeStamp, inNumberFrames,
inNumberInputBufferLists, inInputBufferLists, inNumberOutputBufferLists, ioOutputBufferLists);
#else
return -4/*unimpErr*/;
#endif
}
That implies to me that __MAC_10_7 is not defined. But the wrapper library code, the wrapped vst plug-in, and the wrapper itself all have their Base SDK set to 10.7. So shouldn't that symbol be defined? If not, what the proper way for me to make sure it IS defined?
(Could it be related to the Deployment target? I have mine set to 10.6.)
Thanks,
Howard
On Sep 26, 2014, at 9:55 AM, Oli Larkin <email@hidden> wrote:
> i've had some issues with the plist file and the extra bits steinberg define for the wrapper... maybe double check those
>
>
> On 26 Sep 2014, at 17:45, Howard Moon wrote:
>
>> I finally found a listing that says that is "unimpErr", which means an "unimplemented core routine". Perhaps the auwrapper from the VST 3 SDK does not implement something that is required in Mavericks but not i previous OSes? Does anyone know what that might be, or how to find out? There's no other details in the validation listing from Logic.
>>
>> Thanks,
>> Howard
>>
>> On Sep 26, 2014, at 9:30 AM, Howard Moon <email@hidden> wrote:
>>
>>> Does anyone know what might cause "error -4 in AudioUnitRender" during the render tests when validating a plug-in? I am seeing this error in Logic's AudioUnit validation tests, but ONLY in OS X 10.9.x, NOT in 10.8.x. What does -4 mean? If you enable the AudioUnit anyway, it seems to work fine. It just fails validation for some reason, and only in 10.9. Any ideas?
>>>
>>> Thanks,
>>> Howard
>>>
>>>
>>> _______________________________________________
>>> 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
>>
>>
>> _______________________________________________
>> 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
>
_______________________________________________
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