“Popping Sound”

Or, is this a case where it will still be there for legacy apps, but if I target iOS 9 for my builds, I can't use OpenAL? It was still there on the audio slides from WWDC 2015.Anyone have any more information? Looks like I may spend my Christmas vacation moving all my apps to AVAudioEngine.

Using a set of Turtlebeach USB headphones, and it progressively degrades over time, to a point where it doesn't work, just dead air with popping in the background. Worked fine on 10.10.x, works on Windows. 10.11b2: newp.

I hear the old saw Languages live and change a lot. It's often used by people too lazy to learn proper grammar in the first place. I expect Apple's prose to be as professional as possible. At a minimum their usage should be consistent, which in this example, they clearly are not.Hey, I'm no prescriptivist. But those words ****, and somebody has to carry the English grammar torch. I get emails from people all the time asking me to revert back to them. ***? Sounds like I'll need a teleporter or a human genome scrambler.BTW - I found the word roll used somewhere in the Xcode Docs. The writer meant role. Maybe that's evolution, too. Why not?

This is a routing issue, the A2DP output route will currently not be available to you in AVAudioSessionCategoryPlayAndRecord.See < http://forums.developer.apple.com/message/8370 > for more details. To confirm this you can either use MPVolumeView which will display available outputs or add a few lines of code to your app.For example, using AVAudioSessionCategoryPlayback and asking the AVAudioSession for the currentRoute.outputs will give you something like this - in this case, it shows output via A2DP to a Jambox.( <AVAudioSessionPortDescription: 0x17000b610, type = BluetoothA2DPOutput; name = JAMBOX by Jawbone; UID = 00:21:3C:65:41:CE-tacl; selectedDataSource = (null)> )Doing the same when in the AVAudioSessionCategoryPlayAndRecord category and asking for availableInputs from the audio session and inputs/outputs from the currentRoute produces the following. A2DP is gone as the current output and will not be avalable as an output choice with MPVolumeView.Available Inputs: ( <AVAudioSess

Nope, just looks like the document needs to be updated. You can submit Feedback directly on the documentation page with the the missing information. Note that kAudioFormatMPEG4AAC is from CoreAudioTypes.h giving you an idea of which technologies are built on top of others.Thanks, Core Audio isn't confusing at all...😕

> OK, I think I am still a bit confused about this. It sounds like you are> saying that there is no way for the phone and watch to share a keychain with> accessGroup.>Yes, that's correct.> This would seem to imply that the user would have to log into each the> watch and the phone separately for the same app, that seems wrong.>Yes, that's correct. The phone and watch apps can now be completelyindependant entities with their own login credentials. You can leverage thephone app to improve the onboard-ing process for the watch app, butfundamentally they are independant devices with their own data stores.> However, I don't see any other way to securely do this if the keychain> can't be shared. Am I missing something? Sorry for the confusion....>You'll need to build your own authentication infrastructure here. My firstpass advice would be to have your phone app log into your service and generateyour authentication token to use for future communication (the same way mostmodern

Oddly no - my games use OpenAL and they seem to run fine (music and sounds).

My Sound Blaster X7 USB DAC also works again in beta 2, although the popping has appeared now. Unplugging and re-plugging the USB cable didn't help in my case.

Well, one of the common symptoms in the two threads I linked you to was the hang with the progress bar at 3/4, so the kernal was loaded, the file-system checked out; my reading was that it got stuck waiting for one of the system services to finish initiating. Sounds like yours may not be making it that far.If it turns out to be unrelated to iCloud account (as is sounding increasingly likely), I'd suggest you do a NVRAM and SMC reset (if you haven't already) and boot with Verbose Mode (cmd+v). That should provide a clue. Once things get to that stage though, it's almost always quicker to rescue whatever is important via Target Mode, erase, and start again.

Rich, you wrote:1) You might have seen the alert when a purchase attempt occurs - 'You've already purchased this. Tap OK to download it again for free'...... This alert will occur whenever a user with a new device requests to 'buy' an IAP rather than to 'restore' it. At this point in the dialog (i.e. the user is already at the App Store with a purchaseRequest) the user will have added the transaction observer whether they do it your way or mine so any unfinished transaction will already have come through to updatedTransactions.2) Something else to consider. If there is an incomplete transaction and the restoreCompletedTransactions method is called to restore previous transactions, the incomplete transaction will not appear in the array of prodict identifiers to restore. Using my approach of adding the transaction observer only when necessary the code will addTransactionObserver when it executes a restoreCompletedTransaction. 3) As to the recommendation to calling addTransactionObserver in the didFinishLaunchi

LCS wrote:After messing around a bit more, the bug seems to be related to how the compiler is interpreting the type. /.../ If it sees the explicit type of the parameter as its actual Type which conforms to SomeProtocol, it calls the correct T:SomeProtocol version.But if it sees the explicit type of the parameter as the protocol-based Type, it incorrectly calls the unrestricted T:Any version instead.Yes, this seems like a reasonable explanation. I wonder if this is a known and prioritized issue or what would be a sufficiently small/elegant/clear demonstration of it. I don't like filing bug reports, especially complicated ones that are bound to be misinterpreted.Eridius wrote:For any non-@objc protocol type Foo, Swift does not allow you to pass a value of the existential type Foo (i.e. a value typed as Foo, as opposed to a value whose type is bound by Foo) to a function that expects a generic type T bound by Foo. /.../ This is why Swift is resolving the overloads the way it does.So the question becomes: Why doe

There's been a couple of posts recently regarding Time units for audio playback and how they affect overall sound quality.http://forums.developer.apple.com/message/16043 & http://forums.developer.apple.com/message/13026In your case an AVAudioPlayer is being used - that's great - what this really means is that you're using Audio Queue Services for playback because AVAudioPlayer is using Audio Queue Services on your behalf.What AVAudioPlayer is doing is setting the kAudioQueueProperty_TimePitchAlgorithm property of the playback queue object to kAudioQueueTimePitchAlgorithm_TimeDomain and because it doesn't expose this property to you, you can't change it -- you get what you get.The header comment for this setting indicates the following hint about quality Modest quality, less expensive. Suitable for voice and messing around with sample rates isn't really going to get you anywhere in this context. If you want to higest quality available you'll need a different way to ask f