Popping Sound

Hey All,Well despite the silence from others in here i am still toiling away on this problem.I haved used Atom Inspector to examine 3 different files,A. The working file ie. video only no audio, written via my application using AVFoundation.B. The broken file ie video and audio, written via my applpication using AVFoundation.C. A working file created with FinalCutPro (legacy) and exported using the same settings i am tryint to use for my application.I should also mention that i have tried to use the old dumpster tool/app to open the file but since it is looking at the moov Atom directlyit fails to open my broken file at all.OK so my results...File C appears to be quite different so it has not provided much help, as a comparison tool. (not surprising since it was created differently)BUT, When i examine the broken video file ( ie file B) it ONLY has the following Atoms:ftyp - File Typewide - Wide Atom Headermdat - Media Headerwhereas file A, has many many more, including the moov - Movie Atom

I've been working on a tiled background that I also want to zoom in or out but the problem I'm encountering is that during the zoom in/out action, white space is very noticeable.I'm not entirely sure what you're asking about but I'm almost certain you're in the wrong place (-: It sounds like you're dealing with tiled backgrounds in the context of panning and zooming (kinda like a map view) in which case you might have better luck over in Cocoa Touch. If you agree, you can either start a new thread or move this one there (via the Actions menu, on the right at the same level of the thread title).Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1@apple.com

What you say makes no sense, moreover it sounds like a rant. Without force the same sucking coders writing junk in C++ will just do the same in Swift.Are you referring to C++'s lack of named parameters? Bjarne (and other committee members) directly shooting down any proposal to remedy that ugliness is a huge frustration. But sucking coders writing junk -- the language forces them to write unclear code. It is not the fault of the programmers.You assume that when they move to a language that DOES support named parameters, they will now deliberately omit parameter names because that is what they are used to? And it would have to be deliberate, because the default behaviour is to require the name at the call site. To allow a direct (unnamed) parameter, `_` is necessary.That is absolute nonsense. It is an absurd assumption. A competent programmer uses the available tool set in the best way possible.And one should not obfuscate a new language in order to pander to incompetent people. It is a grave mistake

You don't want to put thousands of entries into either NSUserActivity or CoreSpotlight. If I'm understanding what you have, it sounds like this is effectively static content. If that's the case then your best bet would be to have that content be accessible via a website and let the Apple web crawler index it. That would get it into the public index and would allow the content to be served up to all users when they use iOS Search. NSUserActivity should be used in conjunction with just that, user activity. As the user interacts with your content in the app, it's fine to associate these entries with the activity that the user is doing. If you have an identifier per entry you could associate that with the activity (by way of CSSearchableItemAttributeSet's relatedUniqueIdentifier property, where the attribute set is then attached to the NSUserActivity). If you do this as the user is moving around your app then you would use the same activities for handoff (i.e. with eligibleForHandoff = true). You could a

Can you give a little more information about what you're trying to do? NSUserActivity is intended to be used primarily with exactly what it says, user activity. Because you mentioned deleting content, it sounds like CoreSpotlight might be the more appropriate mechanism for this since that's more in line with indexing of user-generated content. You likely will use both NSUA and CS in conjunction with each other so it might just be a matter of how you're constructing these objects. In either case, having more context about what your content is and how your app works would be helpful.

Sounds like a nice suggestion, though you might have better luck requesting via radar: https://bugreport.apple.com

In the past, the answer has been a flat out no - you couldn't even upload to iTC using beta tools.Now that TestFlight is in the picture it's a little less cut and dried. It sounds like you should be able to upload to iTC using Xcode 7 beta and use TestFlight for testing, though I haven't tried this myself.I think you still cannot use those builds done with beta tools for the public App Store though. For that you need to stick to release versions of Xcode.

Have you read the documentation and watched the WWDC videos on CloudKit? (I'm assuming you mean CloudKit as opposed to iCloud; there's no such thing as iCloudKit.)CloudKit does have both a public (shared between users) and private (only available to that one user) database available. So yes the public database sounds like what you're looking for.

Is the using of Xcode 7 is a solution? What about Swift 2? It differest from 1.2 and I can't continue to develop on machine with Beta OS. That is ridiculous. I don't have 2-3 macs. I'm using one macbook and can't continue and finish a product. Becasue using Xcode 7, I even can't post apps to AppStore.That is sounds very not good.

Before 10.11 Beta 2, 10.6-10 never was a such situation when old tools doesn't work at all. That is sounds very bad from any perspective. Too buggy and bugs are to dumb and stupid.