Your original.mov has got crazy values in the "ctts" atom. HEVC and H.264 has got a frame type called B that can reference previous and future frames, so they are stored out of order. This means the presentation timestamp (pts) and the decode timestamp (dts) are different, and the offset between the two is stored in the mov/mp4 ctts atom. Some players ignore this atom and uses the info stored in the video bitstream, so they might not display the issue. I would check the pts/dts of the sample buffers you are passing to AVAssetWriter.

The alert is shown only if there is a quarantine flag set on the app/executable. Homebrew doesn't add such flag.

Does it happens in Xcode 14.3?

Is that a space before "MetalHUDEnabled" or it's just Xcode indenting things in a weird way?

My understanding is that Apple takes 30% of every digital good sold inside your app. But check the App Store rules for confirmation.

Either crash or throw an exception probably. Did you ever test on 10.10?

I guess it depend where are you using those buffers. If you are encoding them with VideoToolbox or AVFoundation it will probably convert them to the appropriate colourspace set in the encoder, or maybe it will completely ignore it. Try and see.

Is there a quit menu item in the menu extra?

Xcode 14.3 has already been released yesterday.

The mp4 file format has got a creation data and modified date field that are set to the date of when it was created, so those will be different. You should check if the actual audio data is the same. Or you can use some app like l-smash to dump the structure of the mp4 file and compare the actual differences.

Because when not dragged/moved the app runs from a randomised location, maybe this breaks something inside your app. Some info on https://developer.apple.com/forums/thread/724969

I don't think so, that would make the entire feature pointless. It was made to shown users that something added a login or background item, so it being always shown is by design.

Try to wrap the content of the procQueue.async closure in an autoreleasepool. The queue has got it's own autoreleasepool that don't always drain after each closure is executed probably.

The documentation says: In macOS, in order for the system to provide a default Metal device object, you must link to the Core Graphics framework. You usually need to do this explicitly if you’re writing apps that don’t use graphics by default, such as command line tools.

VTDecompressionSession can decode a large number of formats, including HEVC. You can also list the available decoders to be sure what are the supported format on a particular device.