Green screen when allocating/deallocating a video view at the same time. #183
Comments
In version 1.20.0 I got the same problem even though it seem to be fixed when I read version description. It was playing properly in the first time, but when i open the other video (or the same video), the green screen will be shown. Please check the issue or point me what thing I was wrong. Thank you.
NCBVRVideoViewSingleton sharedInstance:
|
I am also still getting this issue on version 1.20.0 |
Does this happen even when you don't reuse the same GVRVideoView instance (don't use a singleton)? |
In my case, I have a ClassA instance that has a GVRVideoView. At some point, I get rid of my instance of ClassA and replace it with a new instance that has its own different GVRVideoView. The new GVR player gets stuck with a green screen. You can reproduce it with the code blow:
Also when creating two GVRVideoViews at the same time, the first one gets stuck with a green screen.
|
@sanjayc77 It's ok if I create new instance instead of using singleton. |
Anybody managed to sold that ? |
@tibewww It was still showing green screen if you use the same GVRVideoView instance for loading videos in many times. |
ok, so we don't have any solution ? |
issue still present on 1.30.0 despite the release note claims to have fixed it |
is there a way to load a new GVRVideoView eachtime you trigger the video by click button do you think ? |
This issue was, inadvertently, not fixed in 1.30. Sorry about the confusion. We will have this fix in the next release. |
@sanjayc77 When might that be available? |
any news about the next release date of the next version :( ? |
GVRVideoView is now deprecated. Switch to GVRKit. GVRKit provides fine grained control over AVPlayer playback and its rendering. See the updated VideoWidgetDemo sample. |
In my code I am playing a video with a GVRVideoView and at a certain time I want to stop and play a different video. The second video always shows a green screen, but the audio plays properly.
In this contrived example, the first video view doesn't need even need to be loaded with a video or added to any view to break the second video. If I wait until -dealloc is called on the first video view before creating the second, then everything works as expected.
I am getting this behavior on both 1.0.1 and 1.10.0. Versions 0.8.x and 0.9.x seem to work as expected.
The text was updated successfully, but these errors were encountered: