We are writting our own distribution platform, which for the most part, works well with HLS on iOS/macOS/Safari. However, in trying to generate DASH-compatible playlist files, we noticed that the fMP4s mediafilesegmenter generates have a non-0 `tfdt` box (the track decode time) for the first segment. Typically, we've seen this value be exactly 10 seconds (seen in video), but sometimes it can also be 9.945 seconds as well (seen in audio), so we were wondering what the reason for this was. Would it be a bad idea to "correct" this value to 0 for the first segment, and adjust downstream segments accordingly? Is the first segment's `tfdt` actually dependent on the source?Thank you for any insight you may be able to provide,Dimitri
dimitri
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
From
Los Angeles
Post
Replies
Boosts
Views
Activity
macOS 15 includes a neat section in System Preferences Settings to change the dynamic text size, as outlined see: https://support.apple.com/guide/mac-help/make-text-and-icons-bigger-mchld786f2cd/mac
However, it's not immediately clear a) how to get one's app in this list, and b) if the usual methods from iOS to react to text size even work on macOS. Does anyone have any experience here? Or should I implement my own controls in my app's settings and call it a day?
For context, my app is a macOS-native SwiftUI app.