Explore the integration of media technologies within your app. Discuss working with audio, video, camera, and other media functionalities.

All subtopics
Posts under Media Technologies topic

Post

Replies

Boosts

Views

Activity

Camera app best practices
As a reminder, the recommended approach to monitor camera rotations, including on upcoming hardware, is to use the AVCaptureDevice.RotationCoordinator / AVCaptureDeviceRotationCoordinator API. In many common scenarios on iPhone Duo, proper use of the rotation coordinator is the only way to ensure that your camera previews and captures use the orientation expected by the user. AVCaptureVideoOrientation has been deprecated as of iOS 17.0 and iPadOS 17.0. When switching cameras in your app, make sure to create a rotation coordinator for that device. To ensure that your app has implemented the rotation coordinator API correctly, you should test different orientations and sizes of your app on an iPad with Stage Manager enabled. Additional information: Sample Code: Supporting device rotation in your camera app Tech Talk: Build a great camera experience for iPhone Duo WWDC23 session: Support external cameras in your iPadOS app
0
0
493
Oct ’26
3D scanning and 3D model with texture mapping
I am new here and would appreciate help in coding or an explanation what to use in swift for an app which will be able to capture LiDAR scanning and RGB data from taken pictures, generate a 3D mesh, and create .OBJ, .MTL, and .JPEG file set for further manipulation of 3D model. I am able to create from LiDAR scanning 3D mesh and .OBJ file but can not generate .MTL and .JPEG for a texture of 3D model.
2
0
975
14h
Hi-Res Lossless audio output on Apple TV 4K for third-party apps (tvOS 27)
Hello, I'm reaching out on behalf of Qobuz, a music streaming service that supports Hi-Res audio on all platforms. We have just released our Apple TV app, and we need to confirm the audio output limits that apply to third-party apps on tvOS. Here is our current understanding: Up to tvOS 26, audio output is limited by the system to 24-bit/48 kHz on all Apple TV models. Higher sample rates are resampled by tvOS. Starting with tvOS 27, Apple TV 4K (2021 and 2022 models) supports Hi-Res Lossless output up to 24-bit/192 kHz when connected over HDMI to compatible audio equipment (AV receiver or DAC). On our side, Qobuz streams and decodes audio up to 24-bit/192 kHz on Apple TV, and we don't restrict the resolution of our catalogue. Could you please confirm: Whether Hi-Res Lossless output up to 24-bit/192 kHz on tvOS 27 is available to all third-party apps, or only to Apple Music. If it is available to third-party apps, which APIs or configuration (e.g. AVAudioSession preferred sample rate, AVPlayer vs. AVSampleBufferAudioRenderer, entitlements) are required to get bit-perfect output at the source sample rate. Whether our understanding of the limits above is correct, including the supported Apple TV models. Thank you in advance for your help. Best regards, Jérémie Senior iOS Developer, Qobuz
0
0
116
21h
Media Extension format reader for MKV/WebM in several apps of one developer – appropriate use and conflicts?
I'm preparing several sandboxed macOS apps (macOS 26 and later) for the Mac App Store and would like to add Matroska/WebM support through a Media Extension format reader. Before implementing it, I'd like to clarify a few points. The apps work only with local video files the user opens or adds: a player for many videos at once (video wall), a practice player with loops and markers, an app for precise trimming and export, and a catalog of the user's video library with thumbnails and duplicate detection. None of them is network-facing. Plan: one format reader for Matroska and WebM (own implementation of RFC 9559, no third-party code), embedded as an ExtensionKit bundle. Video is decoded by the system decoders (H.264, HEVC, VP9 after VTRegisterSupplementalVideoDecoderIfAvailable, AV1 where available); no own video decoder. Each app calls MTRegisterProfessionalVideoWorkflowFormatReaders() and VTRegisterProfessionalVideoWorkflowVideoDecoders() at launch and shows a notice with a link to System Settings when the extension is disabled (AVErrorMediaExtensionDisabled). Questions: MTProfessionalVideoWorkflow.h and VTProfessionalVideoWorkflow.h say the registration functions are intended for applications supporting professional video workflows. Is it acceptable to call them from apps like these, which serve video editing, review and library management, but not a broadcast or camera workflow? Users may buy only one of the apps, so I'd embed the same format reader (same ClassImplementationID and CFBundleVersion, bundle identifier prefixed by each host app) in every app. Is that supported? When are AVErrorMediaExtensionConflict and kVTExtensionConflictErr returned, and how can they be avoided? Does the enable switch in System Settings apply per ClassImplementationID or per host app? Would a user who installs a second app have to enable the extension again? Is there a supported way to open System Settings directly at General > Login Items & Extensions > Media Extensions from an app? Are there App Review requirements specific to apps that embed Media Extensions, beyond guidelines 2.4.5 and 4.4? Thanks in advance.
3
0
404
22h
Camera preview rotated 90 degrees on initial presentation on iPadOS 27.2.1, corrected after returning from Control Center
Dear Apple Support Team, We are investigating a camera preview orientation issue on an iPad and would appreciate guidance on the relevant UIKit and AVFoundation behavior. Our app uses Flutter and the third-party Regula Document Reader SDK for passport MRZ scanning. We understand that third-party SDK internals are outside Apple’s support scope. Our question concerns the relationship between the active interface orientation, presentation lifecycle, and camera preview connection orientation. Environment Device: iPad (A16), hardware identifier iPad15,7 iPadOS: 27.2.1, as reported by the device and diagnostic export App distribution: TestFlight App version in the diagnostic log: 2.0.14, build 7 Flutter plugin: flutter_document_reader_api 9.8.1718 Runtime Regula SDK API version: 9.8.6944 Runtime Regula SDK Core version: 9.8.20492 Steps to reproduce Hold the affected iPad in landscape orientation and open the app. Open the passport scanner. The scanner interface appears in landscape, but the camera image appears rotated by 90 degrees. Open Control Center, then dismiss it and return to the app. The preview can then appear in the correct orientation. Close and reopen the scanner; the issue may recur. Physically rotating the device does not consistently resolve the issue. Expected: The preview should match the current interface orientation from initial presentation. Actual: The preview initially has an orientation mismatch and may recover only after leaving and returning to the app. Diagnostic observations We collected initial-entry and app-resume observations within the same scanner session: Before scanner presentation, the active UIWindowScene.interfaceOrientation is landscapeRight. The SDK’s presenting view controller belongs to the active application window. The scanner controller has landscape dimensions of approximately 1180 × 820. The third-party SDK’s supported interface orientation is configured for landscape right. However, the initial preview connection reports videoOrientation = portrait and videoRotationAngle = 90. Updating supported interface orientations and requesting layout updates did not resolve the initial mismatch in this test. A subsequent app-resume observation reports videoOrientation = landscapeRight and videoRotationAngle = 0. This change is recorded before our app’s delayed layout refresh. We recognize that interface orientation and capture rotation are different concepts, and that connection metadata alone does not establish the displayed pixel orientation. We are providing these observations alongside the visible symptom rather than treating a particular angle as universally correct. Scope and investigation status Our separate QR scanner and receipt camera work normally on the same device. The passport scanner also works normally on many other iPads. We have not established that this affects all devices running this iPadOS version. An app-side orientation enum comparison issue was corrected before collecting the build 7 log, but the preview mismatch remained. We have not isolated the cause to iPadOS, our presentation code, or the SDK’s capture initialization. We do not yet have a focused standalone Xcode reproduction project. We are also preparing an inquiry to the SDK vendor. Questions Are there known circumstances in which a camera preview initially uses portrait orientation despite being presented in a landscape UIWindowScene? What is the recommended lifecycle point for determining the initial interface orientation and configuring the preview connection, particularly while presentation or rotation transitions are in progress? Which supported APIs should be used to keep preview rotation synchronized with interface changes on this iPadOS version? Could the recovery after dismissing Control Center indicate an initialization or lifecycle ordering issue? What additional observations would help distinguish these possibilities? What should we include in a minimal native reproduction or system diagnostic collection to make this issue actionable? We can provide a symptom video and an application diagnostic export. These were collected in separate tests on the same affected device and are not time-synchronized. The application export is not an Apple sysdiagnose. Thank you for any guidance on how to investigate this further. With Best Regards, GTF_Japan_Service
0
0
21
22h
Supported diagnostics for a natural playback transition failure in a WKWebView hosting music.apple.com
We are evaluating an unreleased iPhone app that embeds the complete official music.apple.com page in WKWebView. The official website displays its own lyrics. Our app retains an independent website sign-in and local listening tools. A JavaScript bridge observes playback metadata and provides explicit transport commands through the page's existing MusicKit instance. It does not create a developer-owned MusicKit instance or extract lyrics, credentials, protected audio addresses, or DRM data. On an iPhone 14 Pro Max running iOS 27.2.1, a foreground track can play to its natural end, after which the queue position advances but the next track remains stopped at time zero. A filtered error observation reports MKError with reason NETWORK_ERROR. This identifies the SDK error category, not the underlying cause or request owner. The failure was observed before Safari inspection was attached as well as during inspection. Safari Web Inspector can connect to the app's main page. Our metadata-only observations include a fetch row with HTTP 200 and several subsequent fetch rows with no displayed HTTP status. We have not captured request addresses, headers, cookies, response bodies, HAR files, lyric text, or raw stacks. These rows cannot currently be linked to the SDK error. An earlier actual-zero-user-script control with the full native model and layout completed one foreground transition and continued playing the next track for 51 seconds. This is not a current matched comparison and does not identify a specific bridge operation. The complete bridge can also complete transitions in a separate Mac host. We have no deterministic minimal reproducer establishing an Apple or WebKit defect. The official-website branch leaves Media Session and audio-session ownership to the website and does not issue automatic next-track commands. No proposed global fetch wrapper has been installed, because adding Promise rejection handlers changes observable rejection behavior. We are seeking guidance before expanding instrumentation or requesting more real-device test time. Questions concerning this single transition failure: Is full music.apple.com playback in a third-party WKWebView, alongside observation and explicit transport through the page's existing MusicKit instance, a supported integration pattern? If not, which supported integration preserves a website account independent of the iPhone's Media & Purchases account? Which public diagnostics can distinguish cancellation from transport failure at this transition without exposing protected resource addresses, authorization values, response content, or raw stacks? Are there documented event-listener reentrancy, WKWebView lifecycle, or audio-session constraints that this host should follow when observing the existing player? Environment: iPhone 14 Pro Max; iOS 27.2.1; macOS 27.2.1; Xcode 27.2 (27B52). Experimental app version 0.65, build 67, not submitted. The existing public version is unchanged. Attachments: None. This draft contains no account identifiers, device identifiers, real-session logs, signing material, or source attachments.
1
0
103
1d
403 / 40300 "Invalid authentication" on every /me request, even with a new key and Media ID
My MusicKit setup worked for about a week, then every request that uses a Music User Token started failing with 403, code 40300, "Invalid authentication". That includes GET /v1/me/storefront. Catalogue requests with the same developer token still work. What I've tried, none of which helped: Signing in again through MusicKit JS (the sign-in itself succeeds) A new MusicKit key, twice A new Media ID with a new key tied to it Accepting the latest program agreements, then signing in again MusicKit JS in Safari gets the same refusal right after sign-in, so it isn't my server code. My Apple Music subscription is active, and I'm signing in with the account that holds it. Has anyone seen user tokens rejected like this and found the cause? I've seen a suggestion that an Apple Account password change can trigger it, but nothing about how to recover. Feedback filed as FB25575398
1
0
276
1d
Let Audio Units read the project's whole tempo and signature map (FB25609451)
I've filed FB25609451 and I'm posting it here so other Audio Unit developers can add their own feedback if they need the same. What I'd love in Logic Pro (and any AU host) is what REAPER already does for plug-ins: you insert the plug-in and it immediately knows the whole song, every bar's time signature and tempo, without playing anything, and it updates right away when you change a signature or tempo. In REAPER this works through its host interface (IReaperHostApplication): the plug-in calls TimeMap_GetMeasureInfo to read the start, time signature and tempo of any bar. For Audio Units today, HostCallback_GetBeatAndTempo / HostCallback_GetMusicalTimeLocation (AUv2) and musicalContextBlock / transportStateBlock (AUv3) give the current tempo and time signature, but nothing about the other bars. So a time-aware plug-in has to hear the song played through once, or the user pastes the Signature List into it and redoes it after every edit. Suggestion, read-only: A way for an Audio Unit to read the project's tempo and signature map (Signature track and Tempo track), for example a host callback for AUv2 and a block or property on AUAudioUnit for AUv3, returning every event with its position, time signature and tempo. A notification when the user edits them. Also useful: the current bar number in musicalContextBlock / HostCallback_GetMusicalTimeLocation, and the playback rate during Varispeed. It would help click and count-in tools, arpeggiators and sequencers, tempo-synced effects, and notation or visual displays. If you need this too, filing your own feedback that mentions FB25609451 helps. Leo Margarit, Margarit Audio (OddClick)
0
0
32
2d
Is Apple Music artwork allowed in a music discovery app without playback?
Hi Apple Developer Community, I'm developing an iOS app focused on music discovery and social interaction. Users can share songs with people nearby, and I'd like to use the Apple Music API to retrieve song metadata and album artwork. The artwork would appear on map markers, shared song cards, and user music profiles. The app is not primarily a music player, and users would be able to open songs in Apple Music. I'd like to clarify: Is this use of Apple Music metadata and album artwork permitted under the MusicKit / Apple Music API terms, even without in-app music playback? Would displaying artwork in these social discovery contexts require additional licensing or permission? If additional permission is needed, which official Apple team or licensing channel should I contact? I want to ensure the app complies with Apple's terms before release. Thank you for your guidance!
0
0
161
2d
MusicKitJS | Cannot play explicit songs | CONTENT_RESTRICTED
[Ticket on Feedback Assistant FB12353357] Hi there, We’re experiencing issues playing explicit songs using MusicKitJS for the Web (tested on both stable v1 and beta v3). Upon calling the SDK’s “play()” function, the following error gets logged in the console “CONTENT_RESTRICTED: Content restricted” and playback doesn’t begin. The Storefront we’ve tested in is “it”, but very likely all of them are impacted with the issue, here’s a few Adam IDs of affected tracks: 1681182396, 1683117248, 1669607876. A quick check with the REST APIs reveals indeed that the relevant thing all 3 of them have in common is "contentRating" being "explicit”. The bug isn’t however easy or predictable to replicate because it seems that it can be somewhat solved by fiddling with both the “Screen Time” restrictions settings within an iOS/iPadOS device (of course logged in with the same Apple account), as well as with the “Parental Controls” dashboard located in the Web version of the Apple Music’s settings page. We’re still not 100% sure what exactly “triggers” the fix, but both mentioned dashboards above are essential in attempting to solve it by trial and error. Specifically: in the “Parental Controls” dashboard what helps is actually turning ON the restrictions with the toggle, and then easing them up the most by specifically setting the less restricted available option in all 3 dropdown menus (pretty baffling); in the “Screen time” dashboard what helps is simply enabling/disabling the feature itself altogether, as well as the “Content & Privacy restrictions” toggle, and changing the level of allowed content between “Clean” and “Explicit”; I also want to highlight the fact that during the entire process, for the issue to be actually solved, users every time had to to restart their iPhone/iPad multiple times after changing a setting in “Screen time”, along with deauthorizing/authorizing (logging out and back in) their Apple Music account from the MusicKitJS SDK. The issue seems to always affect freshly created Apple accounts right from the start, we’re not aware of methods that can lead to the bug “coming back” and starting to happen again after being solved manually with the process above (meddling “randomly” with dashboards). It’s a pretty serious one because many of our users do not posses an Apple device and only use their Apple Music subscription on the Web and/or their Android device, meaning that the “Screen time” dashboard isn’t available for them. We’ve never been able to solve the problem on an Apple ID account solely by fiddling with the “Parental Controls” dashboard located in the Web version of the Apple Music’s settings page: tinkering with the “Screen time” settings was essential every single time, meaning owning an Apple device is essential to solve it. Last thing I’m adding is that the issue doesn’t seem to also affect listening to these explicit songs directly with the various first-party Apple Music clients (tested on the iOS native app, Android native app, and on the Apple Music WebApp). Steps to reproduce: on the Web, create a new Apple ID account and activate an Apple Music subscription (do not login with said account on an Apple device); go to the Apple Music WebApp settings page at music.apple.com/account/settings and make sure that the “Parental Controls” restrictions are turned OFF; open any explicit song in the Apple Music WebApp and confirm that playback is allowed; login and authorize the newly created account using any website/application integrated with the MusicKitJS SDK (v1 or v3, doesn’t matter); open the same explicit song as before (or any other) in said third-party client that uses the SDK and verify that playback doesn’t begin and an error “CONTENT_RESTRICTED: Content restricted” is logged in the console upon playing. Additional infos: Apple ID account region and language: Italy - Italian; Storefront affected: IT but possibly all of them; MusicKitJS versions affected: both v1 and v3; Browser where the issue was reproduced: Chrome v114. Attached you’ll find some informational screenshots. Thanks!
3
0
2k
2d
iOS ScreenCaptureKit: background frame processing and capture scope
I’m evaluating ScreenCaptureKit for an explicitly user-initiated, on-device text-recognition workflow on iPhone. Apple’s “Capturing screen content on iOS” sample currently describes iOS 27 full-display capture and capture continuing while the app is backgrounded. Before building a minimal prototype, I’d like to clarify: Can screen frames continue to be delivered and processed locally using Vision for text recognition while another app is foregrounded? What background configuration and processing limitations apply? Can capture on iPhone be restricted to a specific third-party app, or are the available scopes full-display capture and the capturing app’s own content? Is there a supported way to detect that the user has left the intended capture source and stop capture? Are there documented restrictions on capturing system apps, particularly Messages? The intended configuration has explicit system authorization, a visible capture indication, stop/cancel controls, no audio or camera capture, no network transmission, and no retained screen recording. Temporary recognition results would expire and be discarded; only explicitly user-selected output would be retained. This is a capability investigation, not a report of an observed failure. I haven’t run a device prototype yet.
0
0
138
2d
Mouse/Window Lag 4K Display
Hi, all! I recently redid my set up and bought a 44" 4K Samsung TV to mirror the display on my Macbook air. I connected everything using a Hyper Display HDMI hub. Everything is connecting ok, but I'm noticing that there is a slight lag in my mouse and display. The refresh rate is set to 60 and my display is set to 1920x1080. I've tried looking up everything and have had no luck. Any help would be appreciated!
0
0
27
2d
AUHAL input callback teardown: when is inputProcRefCon safe to release?
I am developing a macOS application that captures audio through an AUHAL input AudioUnit. The application registers an input callback using kAudioOutputUnitProperty_SetInputCallback. The callback receives an application-owned context through inputProcRefCon and obtains input audio using AudioUnitRender. The intended shutdown sequence is: Close application-level callback admission. Call AudioOutputUnitStop. Remove the callback using AudioUnitSetProperty with a zero-initialized AURenderCallbackStruct. Wait for callbacks already entered by the application to finish. Call AudioUnitUninitialize and AudioComponentInstanceDispose. Release the application-owned callback context. We use an atomic active-callback counter, covering all context accesses made by callbacks that have entered the counted region. However, this counter cannot account for a callback that Core Audio may have already dispatched but that has not yet executed its first instruction. My question: Is there a supported AUHAL teardown sequence that guarantees no previously scheduled, dispatched, or executing input callback can subsequently access inputProcRefCon? Specifically, does successful return from AudioOutputUnitStop, callback removal, AudioUnitUninitialize, or AudioComponentInstanceDispose provide such a guarantee? Is passing an AURenderCallbackStruct with both fields set to NULL a supported way to remove the input callback, and does removal have any documented completion semantics? If none of these operations provides the required guarantee independently, what is the recommended lifetime-management pattern for safely releasing the application-owned callback context? I have prepared a small standalone AUHAL test project that compiles the relevant Core Audio operations and passes deterministic offline lifecycle tests. Physical AUHAL activation and native callback teardown have not yet been executed, so I am not claiming a reproduced crash or verified native behavior. I am primarily seeking clarification of the supported Core Audio API contract, rather than a diagnosis of an observed crash. Thank you.
0
0
92
3d
AVSpeechSynthesizer pulls words out of thin air.
Hi, I'm working on a project that uses the AVSpeechSynthesizer and AVSpeechUtterance. I discovered by chance that the AVSpeechSynthesizer automatically completes some words instead of just outputting what it's supposed to. These are abbreviations for days of the week or months, but not all of them. I don't want either of them automatically completed, but only the specified text. The completion transcends languages. I have written a short example program for demonstration purposes. import SwiftUI import AVFoundation import Foundation let synthesizer: AVSpeechSynthesizer = AVSpeechSynthesizer() struct ContentView: View { var body: some View { VStack { Button { utter("mon") } label: { Text("mon") } .buttonStyle(.borderedProminent) Button { utter("tue") } label: { Text("tue") } .buttonStyle(.borderedProminent) Button { utter("thu") } label: { Text("thu") } .buttonStyle(.borderedProminent) Button { utter("feb") } label: { Text("feb") } .buttonStyle(.borderedProminent) Button { utter("feb", lang: "de-DE") } label: { Text("feb DE") } .buttonStyle(.borderedProminent) Button { utter("wed") } label: { Text("wed") } .buttonStyle(.borderedProminent) } .padding() } private func utter(_ text: String, lang: String = "en-US") { let utterance = AVSpeechUtterance(string: text) let voice = AVSpeechSynthesisVoice(language: lang) utterance.voice = voice synthesizer.speak(utterance) } } #Preview { ContentView() } Thank you Christian
5
0
1.9k
5d
iTunes Search API previews in an educational ear-training app
Hi, I’m building a free educational ear-training app for social dancers (Education category, no ads, no in-app purchases). In this dance tradition, recognising the orchestra by ear is a practical skill, not trivia. Each historical orchestra has its own rhythm, phrasing and character, and dancers adapt their movement to it: crisp and rhythmic for one, smooth and flowing for another, with dramatic pauses for a third. At social dance events, the music is played in sets by a single orchestra, so identifying it in the first seconds tells dancers how to move. This skill cannot be learned from text, notation or descriptions alone. It is acquired only by listening to the actual recordings and repeatedly practising recognising them, which is why authentic audio is essential. Teachers train this skill in class, and the app makes it practicable at home. Users learn through a catalogue of orchestras with style descriptions (what to listen for and how it affects the dance), A/B listening comparisons and short exercises with spaced repetition. After each answer the app explains which musical features identify the orchestra. As listening material, the app plays the official 30-second previews from the iTunes Search API: streamed only, never downloaded, saved or cached, each preview shows “provided courtesy of iTunes”, each preview has the official “Listen on Apple Music” badge linking to the exact recording, so users can listen to the full track and add it to their library, previews are never used as background music. The Search API terms say previews may be used “only to promote store content and not for entertainment purposes”. Is an educational exercise like this acceptable promotional use under these terms, or is MusicKit required for this kind of app? Apple Developer Support (case 103008374208) suggested I ask here. Thank you!
0
0
54
5d
iOS 27.2: iPhone 13 Pro / 14 Pro heat up sooner during 4K camera capture than on iOS 27.0
We make a camera app (AVCaptureSession at 4K, live preview, recording with AVAssetWriter). Since updating to iOS 27.2, a user with an iPhone 13 Pro reports that the phone gets hot while using our app. Our own iPhone 14 Pro also runs warmer on 27.2 than it did on 27.0. To check, we reran on the 14 Pro the same automated test we ran there on iOS 27.0 in September. Each run lasts 300 seconds with the phone on power and fully charged, Low Power Mode off, and starts at ProcessInfo.thermalState == .nominal. We log thermalState every 5 seconds. Capture is 3840x2160 at 60 fps in all three runs: Idle preview, no processing: iOS 27.0: stayed Nominal for all 300 s iOS 27.2 (24B115): Fair at 278 s Idle preview with a Metal overlay: iOS 27.0: stayed Nominal for all 300 s iOS 27.2: Fair at 123 s Recording, HEVC 10-bit: iOS 27.0: Fair at 38 s, Serious at 108 s iOS 27.2: Fair at 33 s, Serious at 83 s Frame delivery held up. The 5-minute recording lost no frames, even at Serious. Questions: Are there known changes in iOS 27.2 to power use or thermal management during camera capture (AVCaptureSession at 4K) on A15 / A16 devices? Have the thresholds behind ProcessInfo.thermalState or AVCaptureDevice.SystemPressureState changed in 27.2? What data would be most useful in a Feedback report for this: a sysdiagnose taken right after a run, or a specific Instruments template?
1
0
540
6d
Feature Request: Enable Multiple Simultaneous iPhone Cameras Through Continuity Camera
I use continuity camera. I use a clone iPhone 17 pro to have a multi-camera podcast setup. CamoCam gets A&V out of sync which creates WAY MORE work. Dear Apple Engineering and Product Development Team, I am requesting an important enhancement to Apple’s Continuity Camera technology. Currently, Continuity Camera limits users to a single iPhone camera connected to a Mac at a time. Apple should expand this functionality to allow two, three, four, or more iPhones to operate simultaneously as independent camera sources. Connect multiple iPhones simultaneously to a single Mac using USB or Wi-Fi. Recognize each iPhone & toggle between cameras. Thank you, Brandon Johnson
1
0
357
6d
AVAudioSession ioBufferDuration always default to 512 samples on MacOS27 no matter what is requested
Hello, I develop an audio processing demo app that has been working fine on iOS/iPad and on Mac ("developed for iPad") until I upgraded to MacOS27. The app is demonstrating low latency / high temporal resolution audio spectral analysis. I am using AVAudioSession, I request the audio IO buffer to be 32 samples. This still works fine on iOS/iPadOS, but it seems that when running on MacOS27 the buffer size always defaults to 512 samples no matter what I request (smaller or larger). This applies to the "Designed for iPad" version running on MacOS and any version running in the iPhone and iPad simulators on MacOS. The app seems to be working as intended on physical iPhones and iPads. I made a catalyst version and used AudioObjectSetPropertyData to force the IO bugger sizes to 32 samples on the system's active hardware device. This seems to succeed but still results in incorrect behaviour in my app; I am still diagnosing but I believe it's because this leaves AVAudioSession with incorrect data, and I am using AudioKit which relies on AVAudioSession (not confirmed). Regardless, is this change in behaviour intentional in MacOS27? Is there a way around it? The whole point of my app is to demonstrate efficient audio processing with very low latency - I need small input buffer size for that. Thank you for any help with this
2
0
428
6d
[PhotoKit] Significant Delay when Opening Photo/Video Gallery from Camera View
Experiencing a noticeable delay where opening the photo and video gallery from application's PTX camera interface takes approximately 3 to 4 seconds. This delay degrades the user experience and occurs consistently across both the latest iOS 27 RC and previous iOS 26 builds. There is a roughly 3-4 second delay between tapping the gallery button and the gallery interface actually rendering and becoming responsive. Steps Launch the application. Open the PTX Camera interface. Tap to select/open the Gallery. Observe the loading time.
0
0
46
1w
macOS 27.2 makes AUv3 plug-ins completely useless as soon as the user accesses a button with a native submenu.
https://youtu.be/HnNGgYZQBvYJust submitted a bug report FB25497228, and posting it here in hopes to get Apple engineers' attention because it's such a bad bug that macOS 27.2 introduced, and don't think it has a workaround unless Apple fixes it. This wasn't an issue in 27.0. Summary: Opening a native submenu in an out-of-process AUv3 plug-in and dismissing it without selecting anything will make the plug-in UI completely unresponsive to mouse input, and any animation will stop also. Only restart solves it. I can reproduce this with Mela in both Logic Pro and Ableton Live 12. I've attached a demo project to the bug report. It's Xcode Audio Unti extension template with a small modification, just added a button with a submenu. Mela can be found here if needed: https://apps.apple.com/us/app/mela-auv3-synth-fx-midi/id1668299428 Steps to reproduce with the attached project Load Mela as an AU instrument in Logic Pro or Ableton Live Open a factory patch. Open a module’s Actions menu (ellipsis buttons) Hover over Insert or Replace until the submenu appears, then dismiss it without selecting anything. Expected result Mela's UI continues to be interactive, e.g. parameters can be easily adjusted and modulation animations continue to work. Actual result No interaction can be performed, wether adjusting a prameter or dragging a module or pressing a button. Animations also stop. This bug renders my plug-in completely useless on macOS as it makes heavy use of submenus. Please fix it! Here's a link to the video demo of the issue: https://youtu.be/HnNGgYZQBvY
1
0
129
1w
Apple Immersive Video: Post-Production Workflow for Subtitles and Spatial Audio
I have two questions about the post-production workflow for Apple Immersive Video. First, regarding subtitles: I’ve noticed that when watching films in the Apple TV app on Apple Vision Pro, the subtitles seem to follow my head movements. How can we achieve the same effect in our own Apple Immersive Video projects? Is the head-tracked subtitle effect created during post-production, or is it handled by the playback app? Is there a specific workflow or subtitle format we should use? Second, regarding spatial audio: Once our sound mixer has completed a Dolby Atmos 7.1.4 mix, how should we import and configure the audio channels in DaVinci Resolve’s Fairlight for Apple Immersive Video delivery? Is there a specific channel mapping or export configuration we need to follow to ensure the spatial audio plays back correctly on Apple Vision Pro? Also, can we use an existing Dolby Atmos 7.1.4 mix directly, or does it need to be converted into Apple Spatial Audio Format (ASAF)?
0
0
50
1w
Camera app best practices
As a reminder, the recommended approach to monitor camera rotations, including on upcoming hardware, is to use the AVCaptureDevice.RotationCoordinator / AVCaptureDeviceRotationCoordinator API. In many common scenarios on iPhone Duo, proper use of the rotation coordinator is the only way to ensure that your camera previews and captures use the orientation expected by the user. AVCaptureVideoOrientation has been deprecated as of iOS 17.0 and iPadOS 17.0. When switching cameras in your app, make sure to create a rotation coordinator for that device. To ensure that your app has implemented the rotation coordinator API correctly, you should test different orientations and sizes of your app on an iPad with Stage Manager enabled. Additional information: Sample Code: Supporting device rotation in your camera app Tech Talk: Build a great camera experience for iPhone Duo WWDC23 session: Support external cameras in your iPadOS app
Replies
0
Boosts
0
Views
493
Activity
Oct ’26
3D scanning and 3D model with texture mapping
I am new here and would appreciate help in coding or an explanation what to use in swift for an app which will be able to capture LiDAR scanning and RGB data from taken pictures, generate a 3D mesh, and create .OBJ, .MTL, and .JPEG file set for further manipulation of 3D model. I am able to create from LiDAR scanning 3D mesh and .OBJ file but can not generate .MTL and .JPEG for a texture of 3D model.
Replies
2
Boosts
0
Views
975
Activity
14h
Hi-Res Lossless audio output on Apple TV 4K for third-party apps (tvOS 27)
Hello, I'm reaching out on behalf of Qobuz, a music streaming service that supports Hi-Res audio on all platforms. We have just released our Apple TV app, and we need to confirm the audio output limits that apply to third-party apps on tvOS. Here is our current understanding: Up to tvOS 26, audio output is limited by the system to 24-bit/48 kHz on all Apple TV models. Higher sample rates are resampled by tvOS. Starting with tvOS 27, Apple TV 4K (2021 and 2022 models) supports Hi-Res Lossless output up to 24-bit/192 kHz when connected over HDMI to compatible audio equipment (AV receiver or DAC). On our side, Qobuz streams and decodes audio up to 24-bit/192 kHz on Apple TV, and we don't restrict the resolution of our catalogue. Could you please confirm: Whether Hi-Res Lossless output up to 24-bit/192 kHz on tvOS 27 is available to all third-party apps, or only to Apple Music. If it is available to third-party apps, which APIs or configuration (e.g. AVAudioSession preferred sample rate, AVPlayer vs. AVSampleBufferAudioRenderer, entitlements) are required to get bit-perfect output at the source sample rate. Whether our understanding of the limits above is correct, including the supported Apple TV models. Thank you in advance for your help. Best regards, Jérémie Senior iOS Developer, Qobuz
Replies
0
Boosts
0
Views
116
Activity
21h
Media Extension format reader for MKV/WebM in several apps of one developer – appropriate use and conflicts?
I'm preparing several sandboxed macOS apps (macOS 26 and later) for the Mac App Store and would like to add Matroska/WebM support through a Media Extension format reader. Before implementing it, I'd like to clarify a few points. The apps work only with local video files the user opens or adds: a player for many videos at once (video wall), a practice player with loops and markers, an app for precise trimming and export, and a catalog of the user's video library with thumbnails and duplicate detection. None of them is network-facing. Plan: one format reader for Matroska and WebM (own implementation of RFC 9559, no third-party code), embedded as an ExtensionKit bundle. Video is decoded by the system decoders (H.264, HEVC, VP9 after VTRegisterSupplementalVideoDecoderIfAvailable, AV1 where available); no own video decoder. Each app calls MTRegisterProfessionalVideoWorkflowFormatReaders() and VTRegisterProfessionalVideoWorkflowVideoDecoders() at launch and shows a notice with a link to System Settings when the extension is disabled (AVErrorMediaExtensionDisabled). Questions: MTProfessionalVideoWorkflow.h and VTProfessionalVideoWorkflow.h say the registration functions are intended for applications supporting professional video workflows. Is it acceptable to call them from apps like these, which serve video editing, review and library management, but not a broadcast or camera workflow? Users may buy only one of the apps, so I'd embed the same format reader (same ClassImplementationID and CFBundleVersion, bundle identifier prefixed by each host app) in every app. Is that supported? When are AVErrorMediaExtensionConflict and kVTExtensionConflictErr returned, and how can they be avoided? Does the enable switch in System Settings apply per ClassImplementationID or per host app? Would a user who installs a second app have to enable the extension again? Is there a supported way to open System Settings directly at General > Login Items & Extensions > Media Extensions from an app? Are there App Review requirements specific to apps that embed Media Extensions, beyond guidelines 2.4.5 and 4.4? Thanks in advance.
Replies
3
Boosts
0
Views
404
Activity
22h
Camera preview rotated 90 degrees on initial presentation on iPadOS 27.2.1, corrected after returning from Control Center
Dear Apple Support Team, We are investigating a camera preview orientation issue on an iPad and would appreciate guidance on the relevant UIKit and AVFoundation behavior. Our app uses Flutter and the third-party Regula Document Reader SDK for passport MRZ scanning. We understand that third-party SDK internals are outside Apple’s support scope. Our question concerns the relationship between the active interface orientation, presentation lifecycle, and camera preview connection orientation. Environment Device: iPad (A16), hardware identifier iPad15,7 iPadOS: 27.2.1, as reported by the device and diagnostic export App distribution: TestFlight App version in the diagnostic log: 2.0.14, build 7 Flutter plugin: flutter_document_reader_api 9.8.1718 Runtime Regula SDK API version: 9.8.6944 Runtime Regula SDK Core version: 9.8.20492 Steps to reproduce Hold the affected iPad in landscape orientation and open the app. Open the passport scanner. The scanner interface appears in landscape, but the camera image appears rotated by 90 degrees. Open Control Center, then dismiss it and return to the app. The preview can then appear in the correct orientation. Close and reopen the scanner; the issue may recur. Physically rotating the device does not consistently resolve the issue. Expected: The preview should match the current interface orientation from initial presentation. Actual: The preview initially has an orientation mismatch and may recover only after leaving and returning to the app. Diagnostic observations We collected initial-entry and app-resume observations within the same scanner session: Before scanner presentation, the active UIWindowScene.interfaceOrientation is landscapeRight. The SDK’s presenting view controller belongs to the active application window. The scanner controller has landscape dimensions of approximately 1180 × 820. The third-party SDK’s supported interface orientation is configured for landscape right. However, the initial preview connection reports videoOrientation = portrait and videoRotationAngle = 90. Updating supported interface orientations and requesting layout updates did not resolve the initial mismatch in this test. A subsequent app-resume observation reports videoOrientation = landscapeRight and videoRotationAngle = 0. This change is recorded before our app’s delayed layout refresh. We recognize that interface orientation and capture rotation are different concepts, and that connection metadata alone does not establish the displayed pixel orientation. We are providing these observations alongside the visible symptom rather than treating a particular angle as universally correct. Scope and investigation status Our separate QR scanner and receipt camera work normally on the same device. The passport scanner also works normally on many other iPads. We have not established that this affects all devices running this iPadOS version. An app-side orientation enum comparison issue was corrected before collecting the build 7 log, but the preview mismatch remained. We have not isolated the cause to iPadOS, our presentation code, or the SDK’s capture initialization. We do not yet have a focused standalone Xcode reproduction project. We are also preparing an inquiry to the SDK vendor. Questions Are there known circumstances in which a camera preview initially uses portrait orientation despite being presented in a landscape UIWindowScene? What is the recommended lifecycle point for determining the initial interface orientation and configuring the preview connection, particularly while presentation or rotation transitions are in progress? Which supported APIs should be used to keep preview rotation synchronized with interface changes on this iPadOS version? Could the recovery after dismissing Control Center indicate an initialization or lifecycle ordering issue? What additional observations would help distinguish these possibilities? What should we include in a minimal native reproduction or system diagnostic collection to make this issue actionable? We can provide a symptom video and an application diagnostic export. These were collected in separate tests on the same affected device and are not time-synchronized. The application export is not an Apple sysdiagnose. Thank you for any guidance on how to investigate this further. With Best Regards, GTF_Japan_Service
Replies
0
Boosts
0
Views
21
Activity
22h
Supported diagnostics for a natural playback transition failure in a WKWebView hosting music.apple.com
We are evaluating an unreleased iPhone app that embeds the complete official music.apple.com page in WKWebView. The official website displays its own lyrics. Our app retains an independent website sign-in and local listening tools. A JavaScript bridge observes playback metadata and provides explicit transport commands through the page's existing MusicKit instance. It does not create a developer-owned MusicKit instance or extract lyrics, credentials, protected audio addresses, or DRM data. On an iPhone 14 Pro Max running iOS 27.2.1, a foreground track can play to its natural end, after which the queue position advances but the next track remains stopped at time zero. A filtered error observation reports MKError with reason NETWORK_ERROR. This identifies the SDK error category, not the underlying cause or request owner. The failure was observed before Safari inspection was attached as well as during inspection. Safari Web Inspector can connect to the app's main page. Our metadata-only observations include a fetch row with HTTP 200 and several subsequent fetch rows with no displayed HTTP status. We have not captured request addresses, headers, cookies, response bodies, HAR files, lyric text, or raw stacks. These rows cannot currently be linked to the SDK error. An earlier actual-zero-user-script control with the full native model and layout completed one foreground transition and continued playing the next track for 51 seconds. This is not a current matched comparison and does not identify a specific bridge operation. The complete bridge can also complete transitions in a separate Mac host. We have no deterministic minimal reproducer establishing an Apple or WebKit defect. The official-website branch leaves Media Session and audio-session ownership to the website and does not issue automatic next-track commands. No proposed global fetch wrapper has been installed, because adding Promise rejection handlers changes observable rejection behavior. We are seeking guidance before expanding instrumentation or requesting more real-device test time. Questions concerning this single transition failure: Is full music.apple.com playback in a third-party WKWebView, alongside observation and explicit transport through the page's existing MusicKit instance, a supported integration pattern? If not, which supported integration preserves a website account independent of the iPhone's Media & Purchases account? Which public diagnostics can distinguish cancellation from transport failure at this transition without exposing protected resource addresses, authorization values, response content, or raw stacks? Are there documented event-listener reentrancy, WKWebView lifecycle, or audio-session constraints that this host should follow when observing the existing player? Environment: iPhone 14 Pro Max; iOS 27.2.1; macOS 27.2.1; Xcode 27.2 (27B52). Experimental app version 0.65, build 67, not submitted. The existing public version is unchanged. Attachments: None. This draft contains no account identifiers, device identifiers, real-session logs, signing material, or source attachments.
Replies
1
Boosts
0
Views
103
Activity
1d
403 / 40300 "Invalid authentication" on every /me request, even with a new key and Media ID
My MusicKit setup worked for about a week, then every request that uses a Music User Token started failing with 403, code 40300, "Invalid authentication". That includes GET /v1/me/storefront. Catalogue requests with the same developer token still work. What I've tried, none of which helped: Signing in again through MusicKit JS (the sign-in itself succeeds) A new MusicKit key, twice A new Media ID with a new key tied to it Accepting the latest program agreements, then signing in again MusicKit JS in Safari gets the same refusal right after sign-in, so it isn't my server code. My Apple Music subscription is active, and I'm signing in with the account that holds it. Has anyone seen user tokens rejected like this and found the cause? I've seen a suggestion that an Apple Account password change can trigger it, but nothing about how to recover. Feedback filed as FB25575398
Replies
1
Boosts
0
Views
276
Activity
1d
Let Audio Units read the project's whole tempo and signature map (FB25609451)
I've filed FB25609451 and I'm posting it here so other Audio Unit developers can add their own feedback if they need the same. What I'd love in Logic Pro (and any AU host) is what REAPER already does for plug-ins: you insert the plug-in and it immediately knows the whole song, every bar's time signature and tempo, without playing anything, and it updates right away when you change a signature or tempo. In REAPER this works through its host interface (IReaperHostApplication): the plug-in calls TimeMap_GetMeasureInfo to read the start, time signature and tempo of any bar. For Audio Units today, HostCallback_GetBeatAndTempo / HostCallback_GetMusicalTimeLocation (AUv2) and musicalContextBlock / transportStateBlock (AUv3) give the current tempo and time signature, but nothing about the other bars. So a time-aware plug-in has to hear the song played through once, or the user pastes the Signature List into it and redoes it after every edit. Suggestion, read-only: A way for an Audio Unit to read the project's tempo and signature map (Signature track and Tempo track), for example a host callback for AUv2 and a block or property on AUAudioUnit for AUv3, returning every event with its position, time signature and tempo. A notification when the user edits them. Also useful: the current bar number in musicalContextBlock / HostCallback_GetMusicalTimeLocation, and the playback rate during Varispeed. It would help click and count-in tools, arpeggiators and sequencers, tempo-synced effects, and notation or visual displays. If you need this too, filing your own feedback that mentions FB25609451 helps. Leo Margarit, Margarit Audio (OddClick)
Replies
0
Boosts
0
Views
32
Activity
2d
Is Apple Music artwork allowed in a music discovery app without playback?
Hi Apple Developer Community, I'm developing an iOS app focused on music discovery and social interaction. Users can share songs with people nearby, and I'd like to use the Apple Music API to retrieve song metadata and album artwork. The artwork would appear on map markers, shared song cards, and user music profiles. The app is not primarily a music player, and users would be able to open songs in Apple Music. I'd like to clarify: Is this use of Apple Music metadata and album artwork permitted under the MusicKit / Apple Music API terms, even without in-app music playback? Would displaying artwork in these social discovery contexts require additional licensing or permission? If additional permission is needed, which official Apple team or licensing channel should I contact? I want to ensure the app complies with Apple's terms before release. Thank you for your guidance!
Replies
0
Boosts
0
Views
161
Activity
2d
MusicKitJS | Cannot play explicit songs | CONTENT_RESTRICTED
[Ticket on Feedback Assistant FB12353357] Hi there, We’re experiencing issues playing explicit songs using MusicKitJS for the Web (tested on both stable v1 and beta v3). Upon calling the SDK’s “play()” function, the following error gets logged in the console “CONTENT_RESTRICTED: Content restricted” and playback doesn’t begin. The Storefront we’ve tested in is “it”, but very likely all of them are impacted with the issue, here’s a few Adam IDs of affected tracks: 1681182396, 1683117248, 1669607876. A quick check with the REST APIs reveals indeed that the relevant thing all 3 of them have in common is "contentRating" being "explicit”. The bug isn’t however easy or predictable to replicate because it seems that it can be somewhat solved by fiddling with both the “Screen Time” restrictions settings within an iOS/iPadOS device (of course logged in with the same Apple account), as well as with the “Parental Controls” dashboard located in the Web version of the Apple Music’s settings page. We’re still not 100% sure what exactly “triggers” the fix, but both mentioned dashboards above are essential in attempting to solve it by trial and error. Specifically: in the “Parental Controls” dashboard what helps is actually turning ON the restrictions with the toggle, and then easing them up the most by specifically setting the less restricted available option in all 3 dropdown menus (pretty baffling); in the “Screen time” dashboard what helps is simply enabling/disabling the feature itself altogether, as well as the “Content & Privacy restrictions” toggle, and changing the level of allowed content between “Clean” and “Explicit”; I also want to highlight the fact that during the entire process, for the issue to be actually solved, users every time had to to restart their iPhone/iPad multiple times after changing a setting in “Screen time”, along with deauthorizing/authorizing (logging out and back in) their Apple Music account from the MusicKitJS SDK. The issue seems to always affect freshly created Apple accounts right from the start, we’re not aware of methods that can lead to the bug “coming back” and starting to happen again after being solved manually with the process above (meddling “randomly” with dashboards). It’s a pretty serious one because many of our users do not posses an Apple device and only use their Apple Music subscription on the Web and/or their Android device, meaning that the “Screen time” dashboard isn’t available for them. We’ve never been able to solve the problem on an Apple ID account solely by fiddling with the “Parental Controls” dashboard located in the Web version of the Apple Music’s settings page: tinkering with the “Screen time” settings was essential every single time, meaning owning an Apple device is essential to solve it. Last thing I’m adding is that the issue doesn’t seem to also affect listening to these explicit songs directly with the various first-party Apple Music clients (tested on the iOS native app, Android native app, and on the Apple Music WebApp). Steps to reproduce: on the Web, create a new Apple ID account and activate an Apple Music subscription (do not login with said account on an Apple device); go to the Apple Music WebApp settings page at music.apple.com/account/settings and make sure that the “Parental Controls” restrictions are turned OFF; open any explicit song in the Apple Music WebApp and confirm that playback is allowed; login and authorize the newly created account using any website/application integrated with the MusicKitJS SDK (v1 or v3, doesn’t matter); open the same explicit song as before (or any other) in said third-party client that uses the SDK and verify that playback doesn’t begin and an error “CONTENT_RESTRICTED: Content restricted” is logged in the console upon playing. Additional infos: Apple ID account region and language: Italy - Italian; Storefront affected: IT but possibly all of them; MusicKitJS versions affected: both v1 and v3; Browser where the issue was reproduced: Chrome v114. Attached you’ll find some informational screenshots. Thanks!
Replies
3
Boosts
0
Views
2k
Activity
2d
iOS ScreenCaptureKit: background frame processing and capture scope
I’m evaluating ScreenCaptureKit for an explicitly user-initiated, on-device text-recognition workflow on iPhone. Apple’s “Capturing screen content on iOS” sample currently describes iOS 27 full-display capture and capture continuing while the app is backgrounded. Before building a minimal prototype, I’d like to clarify: Can screen frames continue to be delivered and processed locally using Vision for text recognition while another app is foregrounded? What background configuration and processing limitations apply? Can capture on iPhone be restricted to a specific third-party app, or are the available scopes full-display capture and the capturing app’s own content? Is there a supported way to detect that the user has left the intended capture source and stop capture? Are there documented restrictions on capturing system apps, particularly Messages? The intended configuration has explicit system authorization, a visible capture indication, stop/cancel controls, no audio or camera capture, no network transmission, and no retained screen recording. Temporary recognition results would expire and be discarded; only explicitly user-selected output would be retained. This is a capability investigation, not a report of an observed failure. I haven’t run a device prototype yet.
Replies
0
Boosts
0
Views
138
Activity
2d
Mouse/Window Lag 4K Display
Hi, all! I recently redid my set up and bought a 44" 4K Samsung TV to mirror the display on my Macbook air. I connected everything using a Hyper Display HDMI hub. Everything is connecting ok, but I'm noticing that there is a slight lag in my mouse and display. The refresh rate is set to 60 and my display is set to 1920x1080. I've tried looking up everything and have had no luck. Any help would be appreciated!
Replies
0
Boosts
0
Views
27
Activity
2d
AUHAL input callback teardown: when is inputProcRefCon safe to release?
I am developing a macOS application that captures audio through an AUHAL input AudioUnit. The application registers an input callback using kAudioOutputUnitProperty_SetInputCallback. The callback receives an application-owned context through inputProcRefCon and obtains input audio using AudioUnitRender. The intended shutdown sequence is: Close application-level callback admission. Call AudioOutputUnitStop. Remove the callback using AudioUnitSetProperty with a zero-initialized AURenderCallbackStruct. Wait for callbacks already entered by the application to finish. Call AudioUnitUninitialize and AudioComponentInstanceDispose. Release the application-owned callback context. We use an atomic active-callback counter, covering all context accesses made by callbacks that have entered the counted region. However, this counter cannot account for a callback that Core Audio may have already dispatched but that has not yet executed its first instruction. My question: Is there a supported AUHAL teardown sequence that guarantees no previously scheduled, dispatched, or executing input callback can subsequently access inputProcRefCon? Specifically, does successful return from AudioOutputUnitStop, callback removal, AudioUnitUninitialize, or AudioComponentInstanceDispose provide such a guarantee? Is passing an AURenderCallbackStruct with both fields set to NULL a supported way to remove the input callback, and does removal have any documented completion semantics? If none of these operations provides the required guarantee independently, what is the recommended lifetime-management pattern for safely releasing the application-owned callback context? I have prepared a small standalone AUHAL test project that compiles the relevant Core Audio operations and passes deterministic offline lifecycle tests. Physical AUHAL activation and native callback teardown have not yet been executed, so I am not claiming a reproduced crash or verified native behavior. I am primarily seeking clarification of the supported Core Audio API contract, rather than a diagnosis of an observed crash. Thank you.
Replies
0
Boosts
0
Views
92
Activity
3d
AVSpeechSynthesizer pulls words out of thin air.
Hi, I'm working on a project that uses the AVSpeechSynthesizer and AVSpeechUtterance. I discovered by chance that the AVSpeechSynthesizer automatically completes some words instead of just outputting what it's supposed to. These are abbreviations for days of the week or months, but not all of them. I don't want either of them automatically completed, but only the specified text. The completion transcends languages. I have written a short example program for demonstration purposes. import SwiftUI import AVFoundation import Foundation let synthesizer: AVSpeechSynthesizer = AVSpeechSynthesizer() struct ContentView: View { var body: some View { VStack { Button { utter("mon") } label: { Text("mon") } .buttonStyle(.borderedProminent) Button { utter("tue") } label: { Text("tue") } .buttonStyle(.borderedProminent) Button { utter("thu") } label: { Text("thu") } .buttonStyle(.borderedProminent) Button { utter("feb") } label: { Text("feb") } .buttonStyle(.borderedProminent) Button { utter("feb", lang: "de-DE") } label: { Text("feb DE") } .buttonStyle(.borderedProminent) Button { utter("wed") } label: { Text("wed") } .buttonStyle(.borderedProminent) } .padding() } private func utter(_ text: String, lang: String = "en-US") { let utterance = AVSpeechUtterance(string: text) let voice = AVSpeechSynthesisVoice(language: lang) utterance.voice = voice synthesizer.speak(utterance) } } #Preview { ContentView() } Thank you Christian
Replies
5
Boosts
0
Views
1.9k
Activity
5d
iTunes Search API previews in an educational ear-training app
Hi, I’m building a free educational ear-training app for social dancers (Education category, no ads, no in-app purchases). In this dance tradition, recognising the orchestra by ear is a practical skill, not trivia. Each historical orchestra has its own rhythm, phrasing and character, and dancers adapt their movement to it: crisp and rhythmic for one, smooth and flowing for another, with dramatic pauses for a third. At social dance events, the music is played in sets by a single orchestra, so identifying it in the first seconds tells dancers how to move. This skill cannot be learned from text, notation or descriptions alone. It is acquired only by listening to the actual recordings and repeatedly practising recognising them, which is why authentic audio is essential. Teachers train this skill in class, and the app makes it practicable at home. Users learn through a catalogue of orchestras with style descriptions (what to listen for and how it affects the dance), A/B listening comparisons and short exercises with spaced repetition. After each answer the app explains which musical features identify the orchestra. As listening material, the app plays the official 30-second previews from the iTunes Search API: streamed only, never downloaded, saved or cached, each preview shows “provided courtesy of iTunes”, each preview has the official “Listen on Apple Music” badge linking to the exact recording, so users can listen to the full track and add it to their library, previews are never used as background music. The Search API terms say previews may be used “only to promote store content and not for entertainment purposes”. Is an educational exercise like this acceptable promotional use under these terms, or is MusicKit required for this kind of app? Apple Developer Support (case 103008374208) suggested I ask here. Thank you!
Replies
0
Boosts
0
Views
54
Activity
5d
iOS 27.2: iPhone 13 Pro / 14 Pro heat up sooner during 4K camera capture than on iOS 27.0
We make a camera app (AVCaptureSession at 4K, live preview, recording with AVAssetWriter). Since updating to iOS 27.2, a user with an iPhone 13 Pro reports that the phone gets hot while using our app. Our own iPhone 14 Pro also runs warmer on 27.2 than it did on 27.0. To check, we reran on the 14 Pro the same automated test we ran there on iOS 27.0 in September. Each run lasts 300 seconds with the phone on power and fully charged, Low Power Mode off, and starts at ProcessInfo.thermalState == .nominal. We log thermalState every 5 seconds. Capture is 3840x2160 at 60 fps in all three runs: Idle preview, no processing: iOS 27.0: stayed Nominal for all 300 s iOS 27.2 (24B115): Fair at 278 s Idle preview with a Metal overlay: iOS 27.0: stayed Nominal for all 300 s iOS 27.2: Fair at 123 s Recording, HEVC 10-bit: iOS 27.0: Fair at 38 s, Serious at 108 s iOS 27.2: Fair at 33 s, Serious at 83 s Frame delivery held up. The 5-minute recording lost no frames, even at Serious. Questions: Are there known changes in iOS 27.2 to power use or thermal management during camera capture (AVCaptureSession at 4K) on A15 / A16 devices? Have the thresholds behind ProcessInfo.thermalState or AVCaptureDevice.SystemPressureState changed in 27.2? What data would be most useful in a Feedback report for this: a sysdiagnose taken right after a run, or a specific Instruments template?
Replies
1
Boosts
0
Views
540
Activity
6d
Feature Request: Enable Multiple Simultaneous iPhone Cameras Through Continuity Camera
I use continuity camera. I use a clone iPhone 17 pro to have a multi-camera podcast setup. CamoCam gets A&V out of sync which creates WAY MORE work. Dear Apple Engineering and Product Development Team, I am requesting an important enhancement to Apple’s Continuity Camera technology. Currently, Continuity Camera limits users to a single iPhone camera connected to a Mac at a time. Apple should expand this functionality to allow two, three, four, or more iPhones to operate simultaneously as independent camera sources. Connect multiple iPhones simultaneously to a single Mac using USB or Wi-Fi. Recognize each iPhone & toggle between cameras. Thank you, Brandon Johnson
Replies
1
Boosts
0
Views
357
Activity
6d
AVAudioSession ioBufferDuration always default to 512 samples on MacOS27 no matter what is requested
Hello, I develop an audio processing demo app that has been working fine on iOS/iPad and on Mac ("developed for iPad") until I upgraded to MacOS27. The app is demonstrating low latency / high temporal resolution audio spectral analysis. I am using AVAudioSession, I request the audio IO buffer to be 32 samples. This still works fine on iOS/iPadOS, but it seems that when running on MacOS27 the buffer size always defaults to 512 samples no matter what I request (smaller or larger). This applies to the "Designed for iPad" version running on MacOS and any version running in the iPhone and iPad simulators on MacOS. The app seems to be working as intended on physical iPhones and iPads. I made a catalyst version and used AudioObjectSetPropertyData to force the IO bugger sizes to 32 samples on the system's active hardware device. This seems to succeed but still results in incorrect behaviour in my app; I am still diagnosing but I believe it's because this leaves AVAudioSession with incorrect data, and I am using AudioKit which relies on AVAudioSession (not confirmed). Regardless, is this change in behaviour intentional in MacOS27? Is there a way around it? The whole point of my app is to demonstrate efficient audio processing with very low latency - I need small input buffer size for that. Thank you for any help with this
Replies
2
Boosts
0
Views
428
Activity
6d
[PhotoKit] Significant Delay when Opening Photo/Video Gallery from Camera View
Experiencing a noticeable delay where opening the photo and video gallery from application's PTX camera interface takes approximately 3 to 4 seconds. This delay degrades the user experience and occurs consistently across both the latest iOS 27 RC and previous iOS 26 builds. There is a roughly 3-4 second delay between tapping the gallery button and the gallery interface actually rendering and becoming responsive. Steps Launch the application. Open the PTX Camera interface. Tap to select/open the Gallery. Observe the loading time.
Replies
0
Boosts
0
Views
46
Activity
1w
macOS 27.2 makes AUv3 plug-ins completely useless as soon as the user accesses a button with a native submenu.
https://youtu.be/HnNGgYZQBvYJust submitted a bug report FB25497228, and posting it here in hopes to get Apple engineers' attention because it's such a bad bug that macOS 27.2 introduced, and don't think it has a workaround unless Apple fixes it. This wasn't an issue in 27.0. Summary: Opening a native submenu in an out-of-process AUv3 plug-in and dismissing it without selecting anything will make the plug-in UI completely unresponsive to mouse input, and any animation will stop also. Only restart solves it. I can reproduce this with Mela in both Logic Pro and Ableton Live 12. I've attached a demo project to the bug report. It's Xcode Audio Unti extension template with a small modification, just added a button with a submenu. Mela can be found here if needed: https://apps.apple.com/us/app/mela-auv3-synth-fx-midi/id1668299428 Steps to reproduce with the attached project Load Mela as an AU instrument in Logic Pro or Ableton Live Open a factory patch. Open a module’s Actions menu (ellipsis buttons) Hover over Insert or Replace until the submenu appears, then dismiss it without selecting anything. Expected result Mela's UI continues to be interactive, e.g. parameters can be easily adjusted and modulation animations continue to work. Actual result No interaction can be performed, wether adjusting a prameter or dragging a module or pressing a button. Animations also stop. This bug renders my plug-in completely useless on macOS as it makes heavy use of submenus. Please fix it! Here's a link to the video demo of the issue: https://youtu.be/HnNGgYZQBvY
Replies
1
Boosts
0
Views
129
Activity
1w
Apple Immersive Video: Post-Production Workflow for Subtitles and Spatial Audio
I have two questions about the post-production workflow for Apple Immersive Video. First, regarding subtitles: I’ve noticed that when watching films in the Apple TV app on Apple Vision Pro, the subtitles seem to follow my head movements. How can we achieve the same effect in our own Apple Immersive Video projects? Is the head-tracked subtitle effect created during post-production, or is it handled by the playback app? Is there a specific workflow or subtitle format we should use? Second, regarding spatial audio: Once our sound mixer has completed a Dolby Atmos 7.1.4 mix, how should we import and configure the audio channels in DaVinci Resolve’s Fairlight for Apple Immersive Video delivery? Is there a specific channel mapping or export configuration we need to follow to ensure the spatial audio plays back correctly on Apple Vision Pro? Also, can we use an existing Dolby Atmos 7.1.4 mix directly, or does it need to be converted into Apple Spatial Audio Format (ASAF)?
Replies
0
Boosts
0
Views
50
Activity
1w