7 ms·

While not the person to whom the question was directed, I'd offer that the move from QuickTime to AVFoundation (taken directly from iOS) & friends (CoreMedia, C

by kefka_p 10y ago

While not the person to whom the question was directed, I'd offer that the move from QuickTime to AVFoundation (taken directly from iOS) & friends (CoreMedia, CMIO) was one such example. Core Media I/O was released a few years ago to replace vdig and/or sequence grabber IIRC. Despite being released a few years back, the only documentation available for CMIO is a sample project. AVFoundation was limited in terms of codec support relative to QuickTime offering only support for built-in codes. Just as an example. Of course QuickTime had no 64-bit future so Apple had to do something but it was and still is a bit of a mess years down the road.

jawngee 10y ago
Are you kidding? AVFoundation is in nearly every way superior to QuickTime, minus the fact that you couldn't make ref movies with it until El Capitan. QuickTime's API sucks in comparison. Source: I write a video editor for macOS.
- kefka_p 10y ago
  Not kidding at all. There was a lot of noise during the transition on various mailing lists, as I recall. Even as an end-user the issue presented quite a few problems. While AVFoundation is generally a better API it remains less capable than the QuickTime umbrella was. Again refer to the functionality provided by vDig and Sequencer APIs. A simple case: try to slap together a video mixing app sometime that takes input from the camera or other source, processes some effects on it, and dumps the output back as pseudo device that can be used by other apps. Unless things have changed drastically the last time I looked into the matter, such a thing isn't possible within the constraints of AVFoundation itself. You have to resort to the essentially undocumented CoreMedia IO API. Apple does provide similar functionality for other types of devices at a higher level i.e. scanners, digital cameras via some other API I can't recall off the top of my head at the moment. =]

by kefka_p 10y ago

jawngee 10y ago

Are you kidding? AVFoundation is in nearly every way superior to QuickTime, minus the fact that you couldn't make ref movies with it until El Capitan. QuickTime's API sucks in comparison. Source: I write a video editor for macOS.

kefka_p 10y ago
Not kidding at all. There was a lot of noise during the transition on various mailing lists, as I recall. Even as an end-user the issue presented quite a few problems. While AVFoundation is generally a better API it remains less capable than the QuickTime umbrella was. Again refer to the functionality provided by vDig and Sequencer APIs. A simple case: try to slap together a video mixing app sometime that takes input from the camera or other source, processes some effects on it, and dumps the output back as pseudo device that can be used by other apps. Unless things have changed drastically the last time I looked into the matter, such a thing isn't possible within the constraints of AVFoundation itself. You have to resort to the essentially undocumented CoreMedia IO API. Apple does provide similar functionality for other types of devices at a higher level i.e. scanners, digital cameras via some other API I can't recall off the top of my head at the moment. =]