August 2017 - Cocoa-dev - lists.apple.com

Re: Why are some Core Graphics APIs "hidden" from Swift?
by Quincey Morris 30 Aug '17

30 Aug '17

site_archiver(a)lists.apple.com Delivered-To: cocoa-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=teal.net; s=teal; h=received:x-smartermail-authenticated-as:received:from:message-id:content-type: mime-version:subject:date:in-reply-to:cc:to:references:x-mailer; bh=PCXyrkDH3e8LthbzU7pWsmc7clmZQuJ7c6Gj5TY4pJQ=; b=dMR/hpTtXtUvOTcMTqjTFB3amDF4IueK8s6WmO+47J93gJJoux9f2GNHI1ZEOwbsbL7O1/niY4uF1 ZVdqvOrbo2J5uTNZ0n5/SaWGpsVLmH/jGyvkaIrpxGqa8l5XkdAqH19UlRkyEm7r/8IjFN4H/hQP4y k6tjFU+lb3tzcMMg= On Aug 30, 2017, at 14:04 , Rick Mann <rmann(a)latencyzero.com> wrote: > > But the X, Y versions have a double underscore: > > CGContext.__addArc(x1: CGFloat, y1: CGFloat, x2: CGFloat, y2: CGFloat, > radius: CGFloat) > > Why is this? I believe the double-underscore prefix indicates an Obj-C API that is exposed through Swift but not intended for general use. It may be that it’s there for 3rd party developers who insist on using that particular API, or it may be for the Swift compiler to call through to. There is generally a better (simpler) API that does the same thing. In this case, it may be that the x/y plus 1/2 coordinate pattern is an outlier, and Swift standardizes on points instead, in geometrical methods. You can pass CGPoint(x: x1, y:y1) and CGPoint (x: x2, y: y2) into the other API. My guess is that Swift generates the exact same code for the parameters in either case, because it can *always* inline the CGPoint creation methods. You’re not paying a performance or code size penalty, and you are gaining consistency. I don’t know if my reasoning is correct, but it’s an argument that can be made in other similar cases too, so I think it’s something like that. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev(a)lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/site_archiver%40lists.app… This email sent to site_archiver(a)lists.apple.com

1 0

Why are some Core Graphics APIs "hidden" from Swift?
by Rick Mann 30 Aug '17

30 Aug '17

site_archiver(a)lists.apple.com Delivered-To: cocoa-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=fm1; bh=d91pWfBtbn7uJ5NX9Z aO0VgEIon5xTSinF0d83nenbk=; b=LQ32ClRpVRYoDbSu4hNHQODOj8SSr4SzHP N8E0MsjPZdD3mJusiwkvOB/ZW9Y6F58FkbQDolYzQ7iiV3otmu/vuJ7Ej9jGV5eJ wLEDmBFXHVmSy0K1dSIwtXxJEI8x/y7rPcViK+2N7UfJmDoD5aoYiOwUlJBix2Oi fBzBs1ejQ40jlpLQ2GaiVqmWh6+EsIjatdcl8AJ0WqYelbOZunamth7BZsvsWoAQ eauiF+MNVVsZXBdnF4lqEt3pEStrWO0YuiosCTia1ZEhQf8DKz/RELrmJERNUVgH +wHuLU8L/Fp6l1sN/HDpahYBil435ojqZRUjrUKtAqv199dSkP/w== I notice the CGPoint version of APIs map to nice Swift method calls: CGContext.addArc(tangent1End: CGPoint, tangent2End: CGPoint, radius: CGFloat) But the X, Y versions have a double underscore: CGContext.__addArc(x1: CGFloat, y1: CGFloat, x2: CGFloat, y2: CGFloat, radius: CGFloat) Why is this? -- Rick Mann rmann(a)latencyzero.com _______________________________________________ Cocoa-dev mailing list (Cocoa-dev(a)lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/site_archiver%40lists.app… This email sent to site_archiver(a)lists.apple.com

1 0

Re: NSDocument -canCloseDocumentWithDelegate::: not called when terminating
by Jonathan Mitchell 30 Aug '17

30 Aug '17

site_archiver(a)lists.apple.com Delivered-To: cocoa-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mugginsoft.com; s=default; h=Message-Id:In-Reply-To:To:References:Date: Subject:Mime-Version:Content-Type:From:Sender:Reply-To:Cc: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=0fH2of0BDMkhkRWn+9r/5DJyM41B137zVI6g/E8pnwM=; b=a1cQoM/y3YP9vVxLiNnI6c9SB OtQQ5CTqlMyGgyI5Y09pWHOTMFvmgeiqQsoNr8MLUPfLcr295AlqcLzXUi0lOu5xe4YMT+9KavWUu xk9yt7FyByaGwKDv+MykmLAOC9; > On 30 Aug 2017, at 18:30, Quincey Morris > <quinceymorris(a)rivergatesoftware.com> wrote: > > On Aug 30, 2017, at 06:18 , Jonathan Mitchell <lists(a)mugginsoft.com > <mailto:lists@mugginsoft.com>> wrote: >> >> My documents have a lot of variable user cancellable activity that must run >> prior to document closure regardless of whether the document is dirty or not. > >> My solution is to run a termination preflight that processes my clean >> documents prior to allowing actual termination, > > > Instead, the “applicationWillTerminate:” override of your app delegate seems > like the right place, especially because it explicitly permits you to delay > terminate while you do stuff, without having to run the run loop manually. > That’s the *point* of the “applicationWillTerminate:” mechanism. Thanks for the thoughts. Using the applicationWillTerminate is probably a less hacky approach like you say but it would mean refactoring to accommodate this one troublesome situation - I would likely still need to retain the code that handles normal document closing as well. I am not sure that the NSApp -terminate: override is such an issue as the problem only occurs when -terminate: is called. If another termination method appears on the scene it will likely have its own foibles. The doc close logic is quite tricky with copies of the NSDocument instance being sent to both local and remote URLs. Getting it all to hang together at termination in a way that integrates with the NSDocument architecture is challenging. As you say running the loop manually mimics what applicationWillTerminate tries to achieve in the first place. I will keep an eye on how the preflight code works out in the knowledge that I can fall back to an “applicationWillTerminate” style approach. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev(a)lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/site_archiver%40lists.app… This email sent to site_archiver(a)lists.apple.com

1 0

Re: NSDocument -canCloseDocumentWithDelegate::: not called when terminating
by Quincey Morris 30 Aug '17

30 Aug '17

site_archiver(a)lists.apple.com Delivered-To: cocoa-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=teal.net; s=teal; h=received:x-smartermail-authenticated-as:received:from:message-id:content-type: mime-version:subject:date:in-reply-to:cc:to:references:x-mailer; bh=CuFnHPF7FL8w+/qXHHkdYNON9Bhx7PlMBvAfI6DFz9Y=; b=Q2aLCpoLahLXNkSq7A6HV7KJV00LNlPQ3TBnoRM47Hnau+lBU0Z9IFYdTgr4ec5FXaooZZBh/UcjP UDnlWp7kPedGfTRVmTLls9Z/WsJ9XvFBiMLCJN2TT8PvJKBnaALDDnJiMKptJcqc1FYiNRG4VANkCh tHjBTYGy6689i35k= On Aug 30, 2017, at 06:18 , Jonathan Mitchell <lists(a)mugginsoft.com> wrote: > > My documents have a lot of variable user cancellable activity that must run > prior to document closure regardless of whether the document is dirty or not. > My solution is to run a termination preflight that processes my clean > documents prior to allowing actual termination, There’s a difference between your scenario and the one in the thread you linked to. In your case, you don’t need to write anything to the document itself, you say. I think it’s a (slight) conceptual mistake to tie the termination processing to the document machinery, especially as overriding NSDocumentController is a bit hacky even when done right. I also think it’s a mistake to override “terminate:”, because it’s just an action method and you can’t be certain that it’s actually going to be called. (The standard menu item could have a different action method name in the future, or there may be paths within Cocoa that don’t invoke the action method.) Instead, the “applicationWillTerminate:” override of your app delegate seems like the right place, especially because it explicitly permits you to delay terminate while you do stuff, without having to run the run loop manually. That’s the *point* of the “applicationWillTerminate:” mechanism. The consequence of using this override, though, is that documents may already have been closed. So, what I would suggest is maintaining a separate pool of “tasks” (a set of document references would be the simplest approach). In an override of “close”, start the user cancellable activity and remove the corresponding task from the pool. In “appWillTerminate:”, trigger any remaining tasks, and send the termination reply when they’re all done. The reason I’m suggesting “close” rather than “canClose…” is just that it’s simpler, and it avoids getting tangled up in any possible code path where the close is prevented. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev(a)lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/site_archiver%40lists.app… This email sent to site_archiver(a)lists.apple.com

1 0

NSDocument -canCloseDocumentWithDelegate::: not called when terminating
by Jonathan Mitchell 30 Aug '17

30 Aug '17

site_archiver(a)lists.apple.com Delivered-To: cocoa-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mugginsoft.com; s=default; h=To:Date:Message-Id:Subject:Mime-Version: Content-Transfer-Encoding:Content-Type:From:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=pz17gSUBdZZ3s6o36DRSqGhOdjHVvMjIrL+uln8jte8=; b=knS47BqzLUkBkCxgz1oGkni7CJ QKs3gaCqdvZeCLXXOa81DWk36G63+XsuV1V6sXKeAHrO/W6En7NsQ1DBeAeLsTij4E/GnWC+VzjWD k48sEFDIqharwepVYlXZtwTRM; This is one from the archives: https://lists.apple.com/archives/cocoa-dev/2012/Jul/msg00740.html In short NSDocument -canCloseDocumentWithDelegate::: gets called on documents when closing the document window but only for dirty documents when closing the app via NSApp -terminate: (i.e.: the application Quit menu item). My documents have a lot of variable user cancellable activity that must run prior to document closure regardless of whether the document is dirty or not. Trying to fudge the document dirty flag as and when required just sounds like a maintenance headache. My solution is to run a termination preflight that processes my clean documents prior to allowing actual termination, My experience is that intervening in the NSDocument machinery at critical points can be a recipe for disaster if things are not quite right. If anyone has attempted this in the past comments would be appreciated. NSApplication subclass ================== - (void)terminate:(id)sender { // The logic here is quite complex // https://developer.apple.com/documentation/appkit/nsapplication/1428417-term… // The receiver calls NSDocumentController to check if documents can be closed. // If those methods don't handle their callbacks accurately then then this method never returns (even in termination does not occur) // and I think we end up in an inner run loop. // // If the termination process succeeds then this method does not return. // If the termination process is cancelled then this method does return; self.isTerminating = YES; // preflight // see https://lists.apple.com/archives/cocoa-dev/2012/Jul/msg00740.html // when we call terminate: non edited document instances do not get processed like diirty docs hence the preflight BOOL preflight = [[BPDocumentController sharedDocumentController] preflightCloseAllDocumentsOnApplicationTerminate]; if (preflight) { [super terminate:sender]; } self.isTerminating = NO; } NSDocumentController subclass ========================= - (BOOL)preflightCloseAllDocumentsOnApplicationTerminate { // see https://lists.apple.com/archives/cocoa-dev/2012/Jul/msg00740.html // when we call NSApp -terminate: non edited document instances do not get processed like dirty docs hence this preflight BOOL success = YES; // this method is only available if within NSApp -terminate: BOOL appTerminating = [(BPApplication *)NSApp isTerminating]; if (!appTerminating) { return NO; } // we need to preflight non edited documents NSArray *cleanDocuments = [self.documents linq_where:^BOOL(BPDocument * doc) { return !doc.isDocumentEdited; }]; for (NSDocument *doc in cleanDocuments) { self.cleanDocumentTerminateInfo = nil; // this method is called by default on dirty docs but in order to retain our sanity and ensure that the doc close logic // is called in all situations we call it here too [doc canCloseDocumentWithDelegate:self shouldCloseSelector:@selector(onTerminateCleanDocument:shouldClose:contextInfo:) contextInfo:NULL]; // process events until our close selector gets called while (!self.cleanDocumentTerminateInfo) { NSEvent *event = [NSApp nextEventMatchingMask:NSEventMaskAny untilDate:[NSDate distantFuture] inMode:NSDefaultRunLoopMode dequeue:YES]; [NSApp sendEvent:event]; } success = [self.cleanDocumentTerminateInfo[@"shouldClose"] boolValue]; if (!success) { break; } } self.cleanDocumentTerminateInfo = nil; return success; } - (void)onTerminateCleanDocument:(NSDocument *)doc shouldClose:(BOOL)shouldClose contextInfo:(void *)contextInfo { self.cleanDocumentTerminateInfo = @{@"document" : doc, @"shouldClose" : @(shouldClose)}; } _______________________________________________ Cocoa-dev mailing list (Cocoa-dev(a)lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/site_archiver%40lists.app… This email sent to site_archiver(a)lists.apple.com

1 0

Re: XCTest and window restoration
by Samuel Williams 27 Aug '17

27 Aug '17

site_archiver(a)lists.apple.com Delivered-To: Cocoa-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=rWtlLifj/3pbOi9oaAvOxYFW4M0Q4BPBSiDuH0bS6OE=; b=uOEn9g2UaWHD73OZbGQSDZ9uIUnt5qtzonN+bXQA2cqLxCm50HHmmBDcexDdkj/3YI v3rZVh11BqcJ+Uq6wpXZaPNq1tOSihOT0jPSNFZjr5Qua2JmshQfONJW/ecsbG96loEb KYaXAbq+kugn4JDBnKkFyu8R91t194cyuQgx+QPKt7Z2ncrAEXjt63GK4/XGTtQBKt9m kn9z6VmiB76cYR7dR+bLAHi7+beZ0UcxDeCCAfbSrSVBMoaQbhXp979NjcRAhe/RvAxT rqn0b3Jp86ybdNOoXhBjauPolEGh3IxE+6NTdeSp4wsDlikRCaqxo+lyVBmdKa6tbFxq wXUg== I do have that checkbox set so that window restoration is disabled, but it seems like the tests run in their own space and sometimes restore window state between tests. Thanks for your ideas/suggestions. On 26 August 2017 at 07:01, Quincey Morris <quinceymorris(a)rivergatesoftware.com> wrote: > (resent because I forgot to copy the list) > > On Aug 24, 2017, at 17:30 , Samuel Williams <space.ship.traveller(a)gmail.com> > wrote: > > > What am I doing wrong? > > > Nothing wrong, AFAICT. There is a scheme run option for disabling state > restoration. Maybe setting that option for your testing schemes will solve > your problem. > _______________________________________________ Cocoa-dev mailing list (Cocoa-dev(a)lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/site_archiver%40lists.app… This email sent to site_archiver(a)lists.apple.com

1 0

Re: XCTest and window restoration
by Quincey Morris 25 Aug '17

25 Aug '17

site_archiver(a)lists.apple.com Delivered-To: cocoa-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=teal.net; s=teal; h=received:x-smartermail-authenticated-as:received:from:message-id:content-type: mime-version:subject:date:in-reply-to:cc:to:references:x-mailer; bh=xMrDF4fNAbeFmJ0/ciOs+DG3kFdJOImoFuF0tp+YizM=; b=PtPISLrpxorTiRDnvJgw/YCZmczEFX8YcNwb33UcAAMJVs/eA+cupHdswDNk5fO682XI+Bqrq6Exv mVfComlx5ecP8SOxwUye0Rv5We/S9kn0XuklENxMHdBZMDYr6dNBWZCJQc8hIqffjJbtmay0UIGkQg E3z2evPZa+ch7kgs= (resent because I forgot to copy the list) On Aug 24, 2017, at 17:30 , Samuel Williams <space.ship.traveller(a)gmail.com <mailto:space.ship.traveller@gmail.com>> wrote: > > What am I doing wrong? Nothing wrong, AFAICT. There is a scheme run option for disabling state restoration. Maybe setting that option for your testing schemes will solve your problem. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev(a)lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/site_archiver%40lists.app… This email sent to site_archiver(a)lists.apple.com

1 0

XCTest and window restoration
by Samuel Williams 25 Aug '17

25 Aug '17

site_archiver(a)lists.apple.com Delivered-To: Cocoa-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=FqFv7NzOxrvrpWtPdac34/Q22ciDl6PXPlcRFLh2V7c=; b=YgfMMou5dni6ztj2MYxz/927s7NTSDUFPd7bzaXN8eLtKLZuR+/gAFBm8mB7zc3yIZ cBNUmmctRWqFtRCKQ0qG/hQy6ZHAL0Twso3O2F2w2LVmnA9hibGXyEnIi/76msDvYGKt yQwkJyDI7QCplHFW5wAwJXio+goU7gSxXttTHj7bwp7k9dqwdQXTNv/qkrGG7W3InT/M g1RvnX2Qhts0MObgK/G0Kgq+9cJg55NAoe3bLH3qHfGCi6Km7g9JXFs/S7Mz36bbG3bA zQY5uh+xN6dIEsiLUn8LQ0REuZ9NxmumEDOx/ctDEhMxUA6E/bS7fuZmkt5k41s5XJJd BpfA== When running unit tests, the app starts up and restores all windows which causes tests to fail in odd ways. Is there some way to get the UI tests to start with a clean slate every time? What am I doing wrong? Thanks for any advice. Kind regards, Samuel _______________________________________________ Cocoa-dev mailing list (Cocoa-dev(a)lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/site_archiver%40lists.app… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Question about Audio for iOS (SessionCategory?)
by Eric E. Dolecki 24 Aug '17

24 Aug '17

site_archiver(a)lists.apple.com Delivered-To: cocoa-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=WSBWp1xJlGTbM9xtCqTQyR3N+N93Lt4/aTZSjE/QhKs=; b=vS9jGcypiMPzIDTRrLsa6+07RatbbVxL6ldPUvZzmzwyfSiOpHboANpdBrA5qa9Rdu auVUQM1y12q99fIINQWzZqrBJ2RaAWIB9Zvk4ojpLS9iAjlCq9A28vv8efbcd3TO/Lmm VbOr/iDxukZiD6UBbMn00HA1N94N6sns2y/RRBITWDjoi0l8hPYqpOXKzkXmTbmnH745 oXuJoyfRoh68SEXjnhdmw0zSgEe8e6D9SZjR9/R1GagxKRTN5GG8BMuqVloAI6amDf2j m0ZrgrZHelah2i4AxElnxidRjJGDhy/cERQ0R2ksC0hkrBa259pKlFG0cu69C8ZSdAJ0 9Bow== I think I got it. setActive can be called with a second argument and it seems to make all the difference. In all the tutorials I have seen, none made use of it so I didn't know it existed yet - until I read the docs ;) *try theSession.setActive(true, with:[.notifyOthersOnDeactivation])* that tells the Music app to unpause when my audio is done. I put this stuff into a function which seems to be working. Eric On Thu, Aug 24, 2017 at 8:52 AM Eric E. Dolecki <edolecki(a)gmail.com> wrote: > Quick question. > > Am I supposed to set the category, then set a different category while my > audio plays, then when complete go back to the original category? Is that > how I should approach - or are you supposed to set the category one time? > > Eric > > On Fri, Aug 18, 2017 at 3:02 PM Eric E. Dolecki <edolecki(a)gmail.com> > wrote: > >> Where I am at currently. >> >> let audioSession = AVAudioSession.sharedInstance() >> do { >> try >> audioSession.setCategory(AVAudioSessionCategoryPlayAndRecord, with: >> [.duckOthers, .allowBluetoothA2DP, .allowAirPlay, .defaultToSpeaker]) >> try audioSession.setActive(true) >> } catch { >> print("Error. \(error.localizedDescription)") >> } >> >> This doesn't stop Apple Music. This allows me to record audio in the app. >> This ducks Apple Music when I set the category. The defaultToSpeaker allows >> my recorded audio to sound full volume instead of sounding like 0.6 of >> volume (which is weird). The ducking DOES NOT duck Apple Music as needed, >> it seems to duck the audio while my app is running. It also seems to >> degrade the audio somewhat coming to my headphones. >> >> I haven't been banging on iOS 11 beta yet (been holding off). I should >> look to see if they added anything here or not. >> >> Have a great weekend! >> >> On Fri, Aug 18, 2017 at 2:04 PM Eric E. Dolecki <edolecki(a)gmail.com> >> wrote: >> >>> I moved stuff to AppDelegate and it seems a little better. However, when >>> my audio plays, I get Apple Music to duck, and it doesn't come back up in >>> volume. I got a notification during this, and when IT'S audio ping was done >>> playing, Apple Music returned to normal volume. >>> >>> Still playing around... >>> >>> On Fri, Aug 18, 2017 at 1:58 PM Alex Zavatone <zav(a)mac.com> wrote: >>> >>>> There are 4 options you the audio category mode that you can test. >>>> >>>> Apple’s docs suck badly on this topic. I suggest you create the 4 >>>> possible test cases and try them out. >>>> >>>> Also note that one of them will support the silent/mute switch. This >>>> is an item that is worth testing to know what you are getting. >>>> >>>> Cheers, >>>> Alex Zavatone >>>> >>>> > On Aug 18, 2017, at 12:55 PM, Quincey Morris < >>>> quinceymorris(a)rivergatesoftware.com> wrote: >>>> > >>>> > On Aug 18, 2017, at 10:47 , Eric E. Dolecki <edolecki(a)gmail.com> >>>> wrote: >>>> >> >>>> >> I would assume that the audio would come back up. And wouldn't think >>>> my app would pause Apple Music when it starts up... >>>> > >>>> > Unless someone else jumps in with the answer, I’d say it’s TSI time! >>>> > >>>> > _______________________________________________ >>>> > >>>> > Cocoa-dev mailing list (Cocoa-dev(a)lists.apple.com) >>>> > >>>> > Please do not post admin requests or moderator comments to the list. >>>> > Contact the moderators at cocoa-dev-admins(at)lists.apple.com >>>> > >>>> > Help/Unsubscribe/Update your Subscription: >>>> > https://lists.apple.com/mailman/options/cocoa-dev/zav%40mac.com >>>> > >>>> > This email sent to zav(a)mac.com >>>> >>>> _______________________________________________ Cocoa-dev mailing list (Cocoa-dev(a)lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/site_archiver%40lists.app… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Question about Audio for iOS (SessionCategory?)
by Eric E. Dolecki 24 Aug '17

24 Aug '17

site_archiver(a)lists.apple.com Delivered-To: cocoa-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=TZDmf/GNsN7Vp7MGuPNhZ39NFjx+hwYLL8+hbA71Aog=; b=rNNGRLFAfugWQ3qH/+cTAkG7OAhJRnGlspguzaEwpvVcK2VCwnSf70EVWih0+2I0Av 8z6GKTP7x6xEqDvaH3zPzpP3tN31BDVu6+f7PNBTox0NhO6zAWeESvwevWtdYPB3aziC RaWtbsdGGq6bqmdZPl8M3TmVtY1wecgagf+492Dxq101AuRRrCoE79SKjE0yFYFhoTbG sb8cBFfxbQIcFCnI1SWJ6mvoTPihj4LlTiGJsu4Rn9DZEn85FUu7ZHvnZyZJ4qtuFEBd ehblaDujahSh8fiS6FwthJyg7T7gOUIJ2EKGzP/nziWTLO+hWe0n2PaJhHh47mXlP7Rs fyjQ== Quick question. Am I supposed to set the category, then set a different category while my audio plays, then when complete go back to the original category? Is that how I should approach - or are you supposed to set the category one time? Eric On Fri, Aug 18, 2017 at 3:02 PM Eric E. Dolecki <edolecki(a)gmail.com> wrote: > Where I am at currently. > > let audioSession = AVAudioSession.sharedInstance() > do { > try > audioSession.setCategory(AVAudioSessionCategoryPlayAndRecord, with: > [.duckOthers, .allowBluetoothA2DP, .allowAirPlay, .defaultToSpeaker]) > try audioSession.setActive(true) > } catch { > print("Error. \(error.localizedDescription)") > } > > This doesn't stop Apple Music. This allows me to record audio in the app. > This ducks Apple Music when I set the category. The defaultToSpeaker allows > my recorded audio to sound full volume instead of sounding like 0.6 of > volume (which is weird). The ducking DOES NOT duck Apple Music as needed, > it seems to duck the audio while my app is running. It also seems to > degrade the audio somewhat coming to my headphones. > > I haven't been banging on iOS 11 beta yet (been holding off). I should > look to see if they added anything here or not. > > Have a great weekend! > > On Fri, Aug 18, 2017 at 2:04 PM Eric E. Dolecki <edolecki(a)gmail.com> > wrote: > >> I moved stuff to AppDelegate and it seems a little better. However, when >> my audio plays, I get Apple Music to duck, and it doesn't come back up in >> volume. I got a notification during this, and when IT'S audio ping was done >> playing, Apple Music returned to normal volume. >> >> Still playing around... >> >> On Fri, Aug 18, 2017 at 1:58 PM Alex Zavatone <zav(a)mac.com> wrote: >> >>> There are 4 options you the audio category mode that you can test. >>> >>> Apple’s docs suck badly on this topic. I suggest you create the 4 >>> possible test cases and try them out. >>> >>> Also note that one of them will support the silent/mute switch. This is >>> an item that is worth testing to know what you are getting. >>> >>> Cheers, >>> Alex Zavatone >>> >>> > On Aug 18, 2017, at 12:55 PM, Quincey Morris < >>> quinceymorris(a)rivergatesoftware.com> wrote: >>> > >>> > On Aug 18, 2017, at 10:47 , Eric E. Dolecki <edolecki(a)gmail.com> >>> wrote: >>> >> >>> >> I would assume that the audio would come back up. And wouldn't think >>> my app would pause Apple Music when it starts up... >>> > >>> > Unless someone else jumps in with the answer, I’d say it’s TSI time! >>> > >>> > _______________________________________________ >>> > >>> > Cocoa-dev mailing list (Cocoa-dev(a)lists.apple.com) >>> > >>> > Please do not post admin requests or moderator comments to the list. >>> > Contact the moderators at cocoa-dev-admins(at)lists.apple.com >>> > >>> > Help/Unsubscribe/Update your Subscription: >>> > https://lists.apple.com/mailman/options/cocoa-dev/zav%40mac.com >>> > >>> > This email sent to zav(a)mac.com >>> >>> _______________________________________________ Cocoa-dev mailing list (Cocoa-dev(a)lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/site_archiver%40lists.app… This email sent to site_archiver(a)lists.apple.com

1 0