From my experience in shipping multiple complex AVFoundation apps, you can
safely (assuming you know what you are actually doing) • :
Build AVAssets /
Build AVMutableCompositions
Build AVVideoCompositors /
Build AVVideoCompositionLayerInstructions
Build AVPlayerItems
Build
On 20.12.2016 at 17:58 Kyle Sluder wrote:
> On Tue, Dec 20, 2016, at 08:59 AM, Andreas Falkenhahn wrote:
>> So everybody knows that all things relating to UIKit have to be done
>> on the main thread.
>> But what about AVFoundation functions which bear some resemblance
I’ll also argue that if you’re needing to do this kind of thing from a
background thread, your code isn’t factored properly.
Managing the UI of the app is far too complex a task to try to coordinate among
multiple threads. The current best practices for concurrent programming suggest
that you
On Tue, Dec 20, 2016, at 08:59 AM, Andreas Falkenhahn wrote:
> So everybody knows that all things relating to UIKit have to be done
> on the main thread.
>
> But what about AVFoundation functions which bear some resemblance to
> UIKit APIs? Do these have to be called on the main th
So everybody knows that all things relating to UIKit have to be done
on the main thread.
But what about AVFoundation functions which bear some resemblance to
UIKit APIs? Do these have to be called on the main thread too or can
they also be called from a worker thread?
For example, when adding
