Sample CodemacOSReviewed 2026-07-21View on Apple Developer

Applying vImage operations to video sample buffers

At a glance

Item	Summary
Purpose	Use the vImage convert-any-to-any functionality to perform real-time image processing of video frames streamed from your device’s camera.
App architecture	A Swift sample with the source-visible chain `VideoCaptureApp` → `ContentView` → `Accelerate APIs`.
Main patterns	Delegate or data-source callbacks, SwiftUI environment injection
Project style	3 scanned source file(s) across Swift, organized around ranked entry, type, and file boundaries.

Project structure

Source bundle/
├── VideoCapture/
│   ├── VideoCaptureApp.swift
│   ├── ContentView.swift
│   ├── VideoCapture.swift
│   └── VideoCapture.entitlements
├── Configuration/
│   └── SampleCode.xcconfig
└── VideoCaptureSample.xcodeproj/
    ├── .xcodesamplecode.plist
    └── project.pbxproj

Structure observations

Architecturally prominent files are ranked from entry points and role-named declarations; resource-only paths are omitted.
Primary languages: Swift.
The verified tree contains 4 project/configuration file(s) and 4 source declaration(s).

Overall architecture

flowchart LR
    N1["VideoCaptureApp"]
    N2["ContentView"]
    N3["Accelerate APIs"]
    N1 --> N2
    N2 --> N3

Reference code

VideoCapture/VideoCaptureApp.swift:9 — architecture anchor

@main
struct VideoCaptureApp: App {
    // ...
}

Interpretation

The arrows summarize the source-visible entry, role-named types or folders, and framework direction; when nodes come from structural folders, the sequence is a high-level interpretation rather than proof that every adjacent node calls the next. Ownership is claimed only where the next section cites a stored property or assignment. The diagram is intentionally limited to the dominant path into Accelerate.

Ownership and state

classDiagram
    VideoCaptureApp *-- VideoCapture : videoCapture
    AppDelegate o-- VideoCapture : videoCapture
    ContentView o-- VideoCapture : videoCapture
    VideoCapture o-- FourCharCode : pixelFormat

Ownership evidence

VideoCapture/VideoCaptureApp.swift:12 — stored dependency or nearest verified ownership anchor

@main
struct VideoCaptureApp: App {
    // ...
    @StateObject private var videoCapture = VideoCapture()
    // ...
}

Owner	Object or state	Relationship	Mutation authority
`VideoCaptureApp`	`VideoCapture` (`videoCapture`)	owns wrapper-managed state	Owning lexical scope
`AppDelegate`	`VideoCapture` (`videoCapture`)	stores or receives	App/module collaborators
`ContentView`	`VideoCapture` (`videoCapture`)	receives environment-provided state	The environment provider is authoritative
`VideoCapture`	`FourCharCode` (`pixelFormat`)	stores or receives	App/module collaborators

Composition arrows indicate a source-visible construction expression or locally owned value state; aggregation means the owner stores or receives a dependency without proving exclusive lifetime ownership.

Class and protocol design

VideoCapture/VideoCaptureApp.swift:10 — representative type boundary

struct VideoCaptureApp: App {
    // ...
}

Type	Responsibility	Depends on or conforms to
`VideoCaptureApp`	Application entry and top-level composition	`App`
`AppDelegate`	Receives callback-driven events	`NSObject`, `NSApplicationDelegate`
`ContentView`	User-interface presentation and input forwarding	`View`
`VideoCapture`	Owns feature behavior and collaborator lifecycle	`NSObject`, `ObservableObject`

No local protocol conformance is claimed as protocol-oriented design; external framework conformances are listed only as dependencies.

Access control

Symbol	Access	Verified effect	Likely rationale
`videoCapture` (`VideoCapture/VideoCaptureApp.swift:12`)	`private`	Use is restricted to the lexical declaration and same-file extensions allowed by Swift.	Inference: keep state mutation or dependency lifetime inside the owning implementation.
`ContentView` (`VideoCapture/ContentView.swift:8`)	`implicit internal`	No explicit modifier means the Swift declaration is internal to the module.	Inference: app-target collaboration needs no exported library surface.

Reference code

VideoCapture/VideoCaptureApp.swift:12 — representative boundary

@main
struct VideoCaptureApp: App {
    // ...
    @StateObject private var videoCapture = VideoCapture()
    // ...
}

Swift declarations without a modifier are internal; explicit private, fileprivate, private(set), public, or open entries above are interpreted by language semantics. Objective-C/C samples instead rely on header and implementation boundaries, which are not equivalent to Swift lexical privacy.

Logic ownership and placement

Logic	Owning type or file	Placement rationale
Application entry and top-level composition	`VideoCaptureApp`	The source’s `App` suffix makes this role explicit.
Receives callback-driven events	`AppDelegate`	The source’s `Delegate` suffix makes this role explicit.
User-interface presentation and input forwarding	`ContentView`	The source’s `View` suffix makes this role explicit.

Design patterns

Pattern	Source evidence	Purpose or tradeoff
Delegate or data-source callbacks	`VideoCapture/VideoCaptureApp.swift:26`	Callback protocols invert event delivery back into the sample’s owner.
SwiftUI environment injection	`VideoCapture/ContentView.swift:12`	The environment supplies state or a capability without threading it through every initializer.

Naming conventions

Types: App: VideoCaptureApp; Delegate: AppDelegate; View: ContentView.
Protocols: no local protocol declaration in the scanned source.
Methods: applicationShouldTerminateAfterLastWindowClosed, applicationWillTerminate, createConverter, convertVideoFormatToRGB, stopRunning, configureCaptureSession, captureOutput, fourCharCodeToString.
Files: VideoCapture/VideoCaptureApp.swift, VideoCapture/ContentView.swift, VideoCapture/VideoCapture.swift.

Architecture takeaways

VideoCaptureApp is the main source-visible entry or composition anchor for this sample.
Framework work reaches SwiftUI, AVFoundation, Accelerate through a deliberately small high-level chain; the detailed API graph remains inside the cited implementation files.
Stored-property evidence identifies lifecycle collaboration; it does not by itself prove exclusive object ownership.
Access-control conclusions separate verified language visibility from the likely design rationale.
The source does not justify labeling the design protocol-oriented.

Source map

Source file	Relevant symbols
`VideoCapture/VideoCaptureApp.swift`	`VideoCaptureApp`, `AppDelegate`
`VideoCapture/ContentView.swift`	`ContentView`
`VideoCapture/VideoCapture.swift`	`VideoCapture`

Official Apple documentation