AudioUnitScheduleParameters with kStereoMixerParam_Volume

Hello everyone I am trying to ramp the input volume for one of the input busses of a stereo mixer unit (part of an AUGraph). Although I don’t get any errors when running my code, nothing happens at all, i.e. no audible volume changes occur. I am unsure what I am missing. Or could it be that the

AudioUnitScheduleParameters with kStereoMixerParam_Volume

Hello everyone I am trying to ramp the input volume for one of the input busses of a stereo mixer unit (part of an AUGraph). Although I don’t get any errors when running my code, nothing happens at all, i.e. no audible volume changes occur. I am unsure what I am missing. Or could it be that the

AudioUnitRender() thread safe?

Hello everyone, I manage a couple of audio units in an AUGraph but pull the graph by calling AudioUnitRender() on the head node’s audio unit. Am I correct in assuming that calling AudioUnitRender() on any node’s audio unit is not thread safe if AUGraph API is being called on the same node, like

Re: AudioUnitRender() thread safe?

:24 schrieb Benjamin Federer : > > Hello everyone, > > I manage a couple of audio units in an AUGraph but pull the graph by calling > AudioUnitRender() on the head node’s audio unit. Am I correct in assuming > that calling AudioUnitRender() on any node’s audio unit is not thre

Re: AudioUnitRender() thread safe?

means you may be using your graph incorrectly, > or you might not need it at all. > > Finally, modifying the graph (adding/removing nodes) while playing > audio is safe according to the documentation. > > Hope this helps a little, > > > -- > Hovik Melikyan > >

Re: AudioUnitRender() thread safe?

> I am pretty sure there is. According to one discussion on this list, > for example AudioOutputUnitStop() waits until a rendering cycle ends > in case it's called from outside of the audio thread. Which means > CoreAudio has proper synchronization mechanisms in place. That is interesting. I’ll t

AudioUnitGetProperty with Swift 3

Hi there, especially the Core Audio team, The documentation for AudioUnitGetProperty() says: public func AudioUnitGetProperty(_ inUnit: AudioUnit, _ inID: AudioUnitPropertyID, _ inScope: AudioUnitScope, _ inElement: AudioUnitElement, _ outData: UnsafeMutableRawPointer, _ ioDataSize: UnsafeMutab

Re: AudioUnitGetProperty with Swift 3

:21 schrieb Matt Grippaldi : > > Try this… > > let nullPtr:UnsafeMutableRawPointer! = nil > > Matt Grippaldi > ma...@kinematicsystems.com <mailto:ma...@kinematicsystems.com> > > > > > > > > > > >> On Oct 19, 2016,

Re: AudioUnitGetProperty with Swift 3

inputData >> bO.mData = inputData >> assert(false) >> } >> >> This came from vgorloff's Swift 3 implementation of a host and audiounit -- >> you can find it on Github. >> >> Sent from my iPhone >> >>

Re: Random Delays occurring with OSX after Mountain Lion

A customer of ours reported having issues with A/V sync where the audio gradually got more and more delayed. This also happened over longer time spans like hours to days. They were monitoring over a USB audio device and tried documenting the A/V sync offset using Quicktime screen recording and

Re: AudioUnitGetProperty with Swift 3

I filed a radar with the Apple Bug Reporter. rdar://28956261 Anyone else having similar issues should file a radar, too, to bring this to Apple’s attention. > Am 21.10.2016 um 18:26 schrieb Lucas Goossen : > > This is what broke it: > SE-0055 > https://github.com/apple/swift-evolution/blob/

Re: AudioUnitGetProperty with Swift 3

That’s what I am currently doing, although AudioUnitGetPropertyInfo reports the *maximum* property size. That is fine in order to stay save, of course. For arrays, as in my case, I am fishing out the relevant data using ioDataSize of the AudioUnitGetProperty call afterwards. > You should be abl

Re: Swift functions in render callback

> I need to re-record mine for them because I presented off an iPad rather than > a Mac, so they couldn’t just turn on QuickTime screen recording to capture it. Well, they could have if they connected your iPad to the Mac and chose the iPad as a camera in a QuickTime video recording. Sorry for

AUGraph deprecation

Last year at WWDC it was announced that AUGraph would be deprecated in 2018. I just browsed the documentation (https://developer.apple.com/documentation/audiotoolbox?changes=latest_major ) but found Audio Unit Process

Re: AUGraph deprecation

problems in that regard? Thanks Benjamin > Am 08.06.2018 um 16:59 schrieb Benjamin Federer : > > Last year at WWDC it was announced that AUGraph would be deprecated in 2018. > I just browsed the documentation > (https://developer.apple.com/documentation/audiotoolbox?changes=latest_

Re: AUGraph deprecation

meeting where the EU director of developer relation was present. According to > him, when Apple announces a deprecation, it WILL happen. My interpretation of > the conversation is that AUGraph is no longer maintained but provided as is. > >> On 11 Jul 2018, at 12:36, Benjamin Federe

Re: AUGraph deprecation

rious to hear if anyone has done/achieved real > stuff here with AVAudioEngine real-time processing and how. > > > Arshia > > >> On 11 Jul 2018, at 15:00, Benjamin Federer > <mailto:benja...@boinx.com>> wrote: >> >> Laurent, >> >>

Re: AUGraph deprecation

> we don't want folks to be seeing warnings until that's done. > > I can say that there is now an availability mechanism so that we can mark > API's as "to be deprecated", and we have marked up AUGraph with that, to > appear ... someday. > >