iOS AVPlayer cant play 240 fps video

前端 未结 1 458
没有蜡笔的小新
没有蜡笔的小新 2020-12-11 14:06

I recorded a 240 fps video after changing the AVCaptureDeviceFormat. If I save that video in the photo library, the slowmo effect is there. But, If I play that file from doc

相关标签:
1条回答
  • 2020-12-11 14:31

    It's a bit annoying, but I believe you'll need to re-create the video in an AVComposition if you don't want to lose quality. I'd love to know if there is another way, but this is what I've come up with. You can technically export the video via AVAssetExportSession, but using a PassThrough quality will result in the same video file, which won't be slow motion- you'll need to transcode it, which loses quality (AFAIK. See Issue playing slow-mo AVAsset in AVPlayer for that solution).


    The first thing you'll need to do is grab the source media's original time mapping objects. You can do that like so:

    let options = PHVideoRequestOptions()
    options.version = PHVideoRequestOptionsVersion.current
    options.deliveryMode = .highQualityFormat
    
    PHImageManager().requestAVAsset(forVideo: phAsset, options: options, resultHandler: { (avAsset, mix, info) in
    
        guard let avAsset = avAsset else { return }
    
        let originalTimeMaps = avAsset.tracks(withMediaType: AVMediaTypeVideo)
            .first?
            .segments
            .flatMap { $0.timeMapping } ?? []
    
    }
    

    Once you have timeMappings of the original media (the one sitting in your documents directory), you can pass in the URL of that media and the original CMTimeMapping objects that you would like to recreate. Then create a new AVComposition that is ready to play in an AVPlayer. You'll need a class similar to this:

    class CompositionMapper {
    
    let url: URL
    let timeMappings: [CMTimeMapping]
    
    init(for url: URL, with timeMappings: [CMTimeMapping]) {
        self.url = url
        self.timeMappings = timeMappings
    }
    
    init(with asset: AVAsset, and timeMappings: [CMTimeMapping]) {
        guard let asset = asset as? AVURLAsset else {
            print("cannot get a base URL from this asset.")
            fatalError()
        }
    
        self.timeMappings = timeMappings
        self.url = asset.url
    }
    
    func compose() -> AVComposition {
        let composition = AVMutableComposition(urlAssetInitializationOptions: [AVURLAssetPreferPreciseDurationAndTimingKey: true])
    
        let emptyTrack = composition.addMutableTrack(withMediaType: AVMediaTypeVideo, preferredTrackID: kCMPersistentTrackID_Invalid)
        let audioTrack = composition.addMutableTrack(withMediaType: AVMediaTypeAudio, preferredTrackID: kCMPersistentTrackID_Invalid)
    
        let asset = AVAsset(url: url)
        guard let videoAssetTrack = asset.tracks(withMediaType: AVMediaTypeVideo).first else { return composition }
    
        var segments: [AVCompositionTrackSegment] = []
        for map in timeMappings {
    
            let segment = AVCompositionTrackSegment(url: url, trackID: kCMPersistentTrackID_Invalid, sourceTimeRange: map.source, targetTimeRange: map.target)
            segments.append(segment)
        }
    
        emptyTrack.preferredTransform = videoAssetTrack.preferredTransform
        emptyTrack.segments = segments
    
        if let _ = asset.tracks(withMediaType: AVMediaTypeVideo).first {
            audioTrack.segments = segments
        }
    
        return composition.copy() as! AVComposition
    }
    

    You can then use the compose() function of your CompositionMapper class to give you an AVComposition that is ready to play in an AVPlayer, which should respect the CMTimeMapping objects that you've passed in.

    let compositionMapper = CompositionMapper(for: someAVAssetURL, with: originalTimeMaps)
    let mappedComposition = compositionMapper.compose()
    
    let playerItem = AVPlayerItem(asset: mappedComposition)
    let player = AVPlayer(playerItem: playerItem)
    playerItem.audioTimePitchAlgorithm = AVAudioTimePitchAlgorithmVarispeed
    

    Let me know if you need help converting this to Objective-C, but it should be relatively straight forward.

    0 讨论(0)
提交回复
热议问题