如何提升UIView转CVPixelBuffer的转换性能？

你的当前流程（UIView → UIImage → CVPixelBuffer）存在额外的中间数据拷贝和上下文切换开销，直接跳过UIImage环节、复用资源能大幅提升性能，以下是具体优化方案：

1. 核心优化：直接将UIView渲染到CVPixelBuffer #

去掉UIImage转换步骤，直接把UIView的layer渲染到CVPixelBuffer对应的CGContext中，减少一次完整的图像数据拷贝操作：

func viewToPixelBuffer(view: UIView) -> CVPixelBuffer? {
    let size = view.bounds.size
    let pixelFormat = kCVPixelFormatType_32BGRA // 和AVAssetWriterInput的格式保持一致
    
    // 创建兼容CGContext的CVPixelBuffer
    var pixelBuffer: CVPixelBuffer?
    let bufferAttributes: [CFString: Any] = [
        kCVPixelBufferWidthKey: Int(size.width),
        kCVPixelBufferHeightKey: Int(size.height),
        kCVPixelBufferPixelFormatTypeKey: pixelFormat,
        kCVPixelBufferCGImageCompatibilityKey: kCFBooleanTrue,
        kCVPixelBufferCGBitmapContextCompatibilityKey: kCFBooleanTrue
    ]
    
    let status = CVPixelBufferCreate(kCFAllocatorDefault,
                                     Int(size.width),
                                     Int(size.height),
                                     pixelFormat,
                                     bufferAttributes as CFDictionary,
                                     &pixelBuffer)
    
    guard status == kCVReturnSuccess, let buffer = pixelBuffer else {
        return nil
    }
    
    CVPixelBufferLockBaseAddress(buffer, .init(rawValue: 0))
    defer { CVPixelBufferUnlockBaseAddress(buffer, .init(rawValue: 0)) }
    
    // 创建指向CVPixelBuffer内存的CGContext
    guard let context = CGContext(data: CVPixelBufferGetBaseAddress(buffer),
                                  width: Int(size.width),
                                  height: Int(size.height),
                                  bitsPerComponent: 8,
                                  bytesPerRow: CVPixelBufferGetBytesPerRow(buffer),
                                  space: CGColorSpaceCreateDeviceRGB(),
                                  bitmapInfo: CGImageAlphaInfo.premultipliedFirst.rawValue | CGBitmapInfo.byteOrder32Little.rawValue) else {
        return nil
    }
    
    // 转换坐标系：UIKit的原点在左上角，CGContext原点在左下角
    context.translateBy(x: 0, y: size.height)
    context.scaleBy(x: 1.0, y: -1.0)
    
    // 直接渲染view的layer到上下文
    view.layer.render(in: context)
    
    return buffer
}

2. 进阶优化：复用CVPixelBuffer池 #

视频录制是连续帧操作，每次创建新的CVPixelBuffer会带来内存分配/释放的额外开销，用CVPixelBufferPool复用缓冲能进一步提升性能：

class PixelBufferPool {
    private let pool: CVPixelBufferPool
    
    init(targetSize: CGSize, pixelFormat: OSType = kCVPixelFormatType_32BGRA) {
        let poolAttributes: [CFString: Any] = [
            kCVPixelBufferWidthKey: Int(targetSize.width),
            kCVPixelBufferHeightKey: Int(targetSize.height),
            kCVPixelBufferPixelFormatTypeKey: pixelFormat,
            kCVPixelBufferCGImageCompatibilityKey: kCFBooleanTrue,
            kCVPixelBufferCGBitmapContextCompatibilityKey: kCFBooleanTrue
        ]
        var pool: CVPixelBufferPool?
        CVPixelBufferPoolCreate(kCFAllocatorDefault, nil, poolAttributes as CFDictionary, &pool)
        self.pool = pool!
    }
    
    func acquirePixelBuffer() -> CVPixelBuffer? {
        var pixelBuffer: CVPixelBuffer?
        let status = CVPixelBufferPoolCreatePixelBuffer(kCFAllocatorDefault, pool, &pixelBuffer)
        return status == kCVReturnSuccess ? pixelBuffer : nil
    }
}

// 使用示例（和AVAssetWriter的输出尺寸保持一致）
let videoSize = CGSize(width: 1920, height: 1080)
let bufferPool = PixelBufferPool(targetSize: videoSize)

// 每帧录制时获取缓冲并渲染
if let buffer = bufferPool.acquirePixelBuffer() {
    CVPixelBufferLockBaseAddress(buffer, .init(rawValue: 0))
    defer { CVPixelBufferUnlockBaseAddress(buffer, .init(rawValue: 0)) }
    
    guard let context = CGContext(data: CVPixelBufferGetBaseAddress(buffer),
                                  width: Int(videoSize.width),
                                  height: Int(videoSize.height),
                                  bitsPerComponent: 8,
                                  bytesPerRow: CVPixelBufferGetBytesPerRow(buffer),
                                  space: CGColorSpaceCreateDeviceRGB(),
                                  bitmapInfo: CGImageAlphaInfo.premultipliedFirst.rawValue | CGBitmapInfo.byteOrder32Little.rawValue) else {
        return
    }
    
    // 若view尺寸和视频尺寸不一致，可在这里添加缩放渲染逻辑
    context.translateBy(x: 0, y: videoSize.height)
    context.scaleBy(x: 1.0, y: -1.0)
    yourView.layer.render(in: context)
    
    // 将buffer传给AVAssetWriterInput写入视频
}

3. 其他辅助优化点 #

• 统一分辨率：让UIView的尺寸和视频输出尺寸保持一致，避免渲染后再缩放带来的额外开销。
• 避免强制解包：原代码中的img!.cgImage存在崩溃风险，改用可选绑定处理失败场景，同时避免不必要的崩溃中断录制流程。
• Metal加速（可选）：如果设备支持Metal，可以用Metal将UIView渲染到纹理，再转换为CVPixelBuffer，性能比CGContext的CPU渲染更高，适合高性能录制场景。

内容的提问来源于stack exchange，提问作者user10309700