Popping Sound

Sounds like an email misfire.

In a thread on the older forums, one of the Apple engineers stated that the reason Float80 is only available on OS X and simulated iOS (not on iOS hardware) is because it isn't built in to the ARM processors.It doesn't sound like they are planning to put much work into Float80 at this point, if it isn't even going to to be availble on iOS devices. Since it It doesn't already have the right methods to conform to the protocol on OS X, it might not be worth the effort to them to make it conform.https://devforums.apple.com/message/1118295------------Swift's current design/policy for floating point types is to expose the capabilities of the processor. This doesn't preclude providing software floating point implementations of other floating point formats, but we cannot comment on future plans (or lack thereof) to add them.One thing I will point out though: Float is much more than just a space optimization. All modern hardware supports SIMD vectors, and using Float instead of Double enables 2x the auto-vect

To really get an idea of how creating a clock using for example CMAudioClockCreate (on iOS) is useful when assigned to an AVPlayer masterClock and used with the method setRate: time: atHostTime: when syncing with user generated audio, it's recommended that you watch the WWDC presentation from 2012 called Real-Time Media Effects and Processing during Playback. Starting at 11 minutes into the presentation the subject Syncronizing Video to Custom Audio is discussed in depth. However, you'll probably want to start at the beginning to experience an excellent explanation of Time and CMTime and clocks in general.You'll find this presentation super helpful and I'm sure it will clear up some of the hazy bits.https://developer.apple.com/videos/wwdc/2012/#517

Ok -- figured out my mistake:My breakpoint was set in the Filter Demo's processWithEvents method. the internalRenderBlock method _was_ being called, but it was erroring out when trying to call pullInput, since the MusicDevice isn't set up to do that (at least by default -- not sure if that's something MusicDevices can do in general).Setting the type to kAudioUnitType_MusicDevice does indeed return a music device type audio unit. Sending a 'startNote' message to the AVAudioUnitMIDIInstrument in the AVAudioEngine does indeed pass all the way through to the kernel's handleOneEvent method.Neat!

56 seconds sounds awfully excessive for that amount of data.I would run the requests through a debugging proxy such as Charles to verify exactly how long the network requests are taking.

About the dummy array + WKInterfacePicker, yeah I also figured that out. Thanks for the info about playing sound via bluetooth that might be interesting.Did you figure out how to respond to TAP events for the WKInterfacePicker? According to the docs:A WKInterfacePicker object presents a scrolling list of items for the user to choose from. Items in the picker may consist of text, images, or a combination of the two. The user interacts with a picker by tapping it, using the crown to scroll through items, and tapping again to select an item. A single interface controller may contain multiple pickers, each with its own set of items.

I read about SpriteKit and texture atlases a bit more, and it looks like the trimming is considered a feature rather than a bug.https://developer.apple.com/library/ios/recipes/xcode_help-texture_atlas/AboutTextureAtlases/AboutTextureAtlases.htmlThose new images are automatically rotated and trimmed to fit the maximum number of images into a single file...So it sounds like you would need to use the 1% alpha workaround you mentioned above, or use the default centered anchor point on the sprite and textures.

Same to me.Using a MacBook Pro Mid 2014. No camera symbol is shown. In Messages->Settings the complete Section for camera / sound is missing.Camera is recognized and working with any other application e.g. Photo Booth and Facetime.Michael

For tiny data (strings, dates, numbers etc.) there is NSUserDefaults or the keychain.For medium sized data (or lots of tiny data) there is Core Data or SQLite (I like SQLite with FMDB) or some other database.For large data like audio files or PDFs I would think individual files on the file system. Take a look at NSFileManager and related guides - there's lots of documentation on the Apple dev site. (File System Programming Guide)