Yes I did compile CRFSuite in Xcode. After compiling it myself I noticed after that Apple actually includes libCRFSuite in the SDK. If you open your Xcode project and choose link framework you can search for CRFSuite and you can link libcrfsuite.tbd in your project. I haven't tried linking against Apple's version myself though (still linking against my own from source). Quickly taking a look though I don't see the header file for libcrfsuite. I imagine crfsuite.h would be in usr/include somewhere. Not sure what's up with that. I was hoping to convert a model to CoreML and use it with NLTagger because I imagine it would use a lot less memory though the CRFSuite model I'm using isn't too big so I'm going to use it as is for now rather than trying to retrain the entire thing with CoreML because I got a million other things to do. As a sidetone, I haven't really been able to do much with CoreML. All the models I'm interested in using in my app don't work with it. Overall I've had a much easier time using ONNX. But for this model I'm sticking with CRFSuite for now.

coremltools doesn't appear to support this. Looks like the answer is no.

I think what I need is to call -playerTimeForNodeTime: in the tap block to get the time relative to the buffer scheduled on the player node.

if (platform.noUIKitOnlySwiftUIAvailable) { abort(); }

Here is a workaround: // In a NSTextField subclass. -(BOOL)sendAction:(SEL)action to:(id)target { if (action == @selector(performClose:)) { return NO; } else { return [super sendAction:action to:target]; } }

Using the tab key to change from editing the multiline text field to the single line text field also causes the window to close so using the mouse is not required to reproduce the bug.

Archiving works. It's when I attempt to submit it to be notarized that it complains about the hardened runtime not being enabled (though it is enabled in my Xcode project but for some reason it must not be enabling it on the embedded executables, which are inside an embedded framework). Haven't had time to retry yet but I assume if I manually do it from the command line it'll work. Will report back when I have a little more time to try.

So I tested converting the AVAudioPCMBuffer I have (which is AVAudioPCMFormatInt16) to a new AVAudioPCMFormatFloat32 and AVAudioEngine plays the float32 pcm buffer. I assumed it was valid to pass in a PCM buffer in other formats (being that -connect:to:format: has a format parameter). Can't seem to get it to play without using float32 format. I think I'll open a new thread asking about this since your question was related but different.

So to play on AVAudioEngine you have to use the same format returned by mainMixerNode.inputFormatForBus? If I have an audio buffer already constructed in with format AVAudioPCMFormatInt16 I can't schedule it on AVAudioEngine?

This particularly app (just for me) embeds the Java runtime. The java runtime is contained within a framework of mine. Xcode complains that the hardened runtime isn't enabled for these prebuilt executables. Is there a way to have Xcode GUI handle this when I archive or do I have use the command line?

Workaround that worked for me: Select one of the apps that is shown in the list (any one). From the details page this app click the down chevron next to the app title and change the app to the app you actually want to update.

Yea I can't update my app. App Store Connect is only showing me a partial list of my apps.

Hm. Maybe it was the Mac App Store version of that same app I was thinking of (that didn't have the Hardened runtime enabled). I know it used to be optional in and outside MAS I guess it changed at some point.

I feel your pain; I've been in the same boat for like two months. They also never responded to my bug report so who knows. It seems to be better on 17.2.1 (but I haven't tested it enough to say confidently that it is fixed). See threads: https://developer.apple.com/forums/thread/737685 https://developer.apple.com/forums/thread/730639?answerId=765237022#765237022 https://developer.apple.com/forums/thread/738048?answerId=768059022 Been working on my own synthesizer for awhile now.

@And0Austria Thanks for sharing that info. I'll have to give AVSpeechSynthesizer another try on iOS 17.2 now and see. It would be nice (if they did fix it) if they included that information in the release notes and/or updated some of our bug reports but if it's fixed that'll be good enough....