Showing black on initial recorded video frame about cameraengine HOT 8 CLOSED

I figured out the issue. The appendBuffer is writing audio ahead of the video. As a workaround, I don't do startWriting until video is given....

func appendBuffer(sampleBuffer: CMSampleBuffer!, isVideo: Bool) {
    if CMSampleBufferDataIsReady(sampleBuffer) {
        //MARK:ROSS - start writing only when video is ready...
        if self.assetWriter.status == AVAssetWriterStatus.Unknown && isVideo {
            print("Writer: startWriting")
            let startTime = CMSampleBufferGetPresentationTimeStamp(sampleBuffer)
            self.assetWriter.startWriting()
            self.assetWriter.startSessionAtSourceTime(startTime)
        }
        if isVideo {
            if self.videoInputWriter.readyForMoreMediaData {
                print("Writing video...")
                self.videoInputWriter.appendSampleBuffer(sampleBuffer)
            }
        }
        else {
            if self.audioInputWriter.readyForMoreMediaData {
                print("Writing audio...")
                self.audioInputWriter.appendSampleBuffer(sampleBuffer)
            }
        }
    }
}

from cameraengine.

No problem. Being able to pause and resume recording would be great feature. Great work by the way.

from cameraengine.

@MFaarkrog I did, it already implemented. Please update your pod.
Do you still have the issue ?

from cameraengine.

I will check that. Thank you so much for your return ! It really helps.

from cameraengine.

@remirobert Great work on this library 👍 Any chance you know when you'll update the above?

from cameraengine.

@remirobert
Hey this issue still persists. I checked your code and missing was && isVideo in this line by @roceller

 if self.assetWriter.status == AVAssetWriterStatus.Unknown && isVideo

which fixes the problem for me atleast. Whereas before, each video I took had a black or white frame at the start.

from cameraengine.

@remirobert Sorry for the delayed response. Yeah, I still have the issue in the project I'm working on.
I haven't tried otymartin's fix yet, though.

from cameraengine.

It's fixed, check the next commit with swift 3 update

from cameraengine.