Problems with newest framework version
Hi.
I am using your framework and constantly checking your useful updates, but this last update is not working as expected. The SimpleVideoFilter example application after recording the 10 second long video floods the console with the following error: CVOpenGLESTextureCacheCreateTextureFromImage failed (error: -6661) and after updating my iOS project when simply recording a video, with no filters applied, the sound is cut-off about half-way. So if I record a 12 seconds long video, the first 6 seconds has audio and after that no audio, only video.
What do you think can be the problem?
I ran the new version of the SimpleVideoFileFilter. It works very well. The only issue I had was that no audio is played while the video is streamed to the texture.
Is there a way to toggle audio for the video texture?
Do you plan to release a class for video texture that does not "piggy back" off of the movie writer.? The reason I mention this is because the movie recording is a special feature.. and distinct from the video texture.
Great update!
Currently, the movie filtering options are based around filtering and re-recording movies, not playback. I don't have the appropriate timing code in there for playback, and I haven't done any work with playing audio while running the movie.
All audio that is processed by the framework is done so for recording, because that has been what people cared the most about. If you'd like to work on this, I'd welcome any contributions in that area for synchronizing the timing of video and audio playback.
The texture cache error has now been fixed in the latest framework code. The sound issue might have been fixed, too, but I need to investigate that.
The audio issue is one that others have identified, and I'm taking a look at that.
The CVOpenGLESTextureCacheCreateTextureFromImage messages are due to something screwing up the texture caches after a movie has finished recording, so I'm working on that right now. It doesn't seem to affect the actual display of video, though.