Using vImage pixel buffers to generate video effects

At a glance

Project structure

Source bundle/
├── vImagePixelBuffer-VideoEffects/
│   ├── vImagePixelBuffer_VideoEffectsApp.swift
│   ├── VideoEffectsEngine.swift
│   ├── ImageView.swift
│   ├── ContentView.swift
│   └── vImagePixelBuffer_VideoEffects.entitlements
├── Configuration/
│   └── SampleCode.xcconfig
└── vImagePixelBuffer-VideoEffects.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 6 source declaration(s).

Overall architecture

flowchart LR
    N1["vImagePixelBuffer_VideoEffectsApp"]
    N2["ContentView"]
    N3["VideoEffectsEngine"]
    N4["Accelerate APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

vImagePixelBuffer-VideoEffects/vImagePixelBuffer_VideoEffectsApp.swift:11 — architecture anchor

@main
struct vImagePixelBufferVideoEffectsApp: 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
    vImagePixelBufferVideoEffectsApp *-- VideoEffectsEngine : videoEffectsEngine
    VideoEffectsEngine o-- Pixelbuffersize : pixelBufferSize
    VideoEffectsEngine o-- CGImage : outputImage
    VideoEffectsEngine o-- vImageConverter : converter

Ownership evidence

vImagePixelBuffer-VideoEffects/vImagePixelBuffer_VideoEffectsApp.swift:14 — stored dependency or nearest verified ownership anchor

@main
struct vImagePixelBufferVideoEffectsApp: App {
    // ...
    @StateObject private var videoEffectsEngine = VideoEffectsEngine()
    // ...
}

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

vImagePixelBuffer-VideoEffects/vImagePixelBuffer_VideoEffectsApp.swift:12 — representative type boundary

struct vImagePixelBufferVideoEffectsApp: App {
    // ...
}

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

Access control

Reference code

vImagePixelBuffer-VideoEffects/vImagePixelBuffer_VideoEffectsApp.swift:14 — representative boundary

@main
struct vImagePixelBufferVideoEffectsApp: App {
    // ...
    @StateObject private var videoEffectsEngine = VideoEffectsEngine()
    // ...
}

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

Design patterns

Naming conventions

• Types: App: vImagePixelBufferVideoEffectsApp; Engine: VideoEffectsEngine; View: ContentView, CoreGraphicsImageView, ImageView.
• Protocols: no local protocol declaration in the scanned source.
• Methods: populateDestinationBuffer, renderDestinationBuffer, applyTemporalBlur, applyNoise, applyPosterization, applyColorThreshold, configureCaptureSession, captureOutput.
• Files: vImagePixelBuffer-VideoEffects/VideoEffectsEngine.swift, vImagePixelBuffer-VideoEffects/ImageView.swift, vImagePixelBuffer-VideoEffects/ContentView.swift.

Architecture takeaways

• vImagePixelBuffer_VideoEffectsApp is the main source-visible entry or composition anchor for this sample.
• Framework work reaches SwiftUI, AVFoundation, Accelerate, Cocoa 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

• Official Apple documentation