Anyone Got video Player working in Android?

Hi Matt!

Sorry you're having trouble with playback on Android, an important rework was done for b10, but is missing one important bug fix having to do with clips not starting when the timestamp of the first frame is not 0. Many clips have their first frame start at frame 1 which trips some logic in our Android decoding implementation. This is fixed in the next version (beta 11).

It would be helpful if you can test with videos that start at 0 (here's an example):
http://download.blender.org/peach/bigbuckbunny_movies/BigBuckBunny_640x360.m4v

Thanks for helping,

Dominique
A/V developer at Unity

 

OK, thanks for trying out. Can you also try both with GLES2 and GLES3 Graphics APIs?

There si a GL extension that has to be present for the decode-to-texture to work, and GLES2 and 3 each have their on flavour of the extension. If you have time, please submit a bug with the project as well as the logcat from your device so we can make sure we cover this scenario in our tests.

Thanks for your patience!

Dominique
A/V developer at Unity

 

Hi Matt,

Thanks for taking the time to dig through this. For the audio to work, did you use the "Audio Source" Audio Output Mode? The "Direct" Audio Output Mode doesn't yet work outside of OSX / iOS, so you have to assign an Audio Source to the Video Player (in the UI or through scripting) for the audio to be heard on Android. I've recently added a warning in the console when we detect the direct mode being used in a context where it isn't yet supported.

When you have the bug id you submitted, please post it to this thread so everyone can follow its progress.

Dominique

 

Excellent, thanks Matt for trying this out!

So this leaves us with:

• We have to see what we can do about GLES3 being selected by default when Auto Graphics API is on and preventing the GLES2 API from being used (the bug you logged).
• We need to document that direct output doesn't work (yet) on Android. In fact, it only works for OSX / iOS for now, and I've added a warning about this that is sent to the log, but of course on your device it will be rather subtle: it goes to the device's log. This feature will be implemented in a future release.

Anything else?

Dominique
A/V developer at Unity

 

OK, thanks for the clarification. We'll have to see in what order the APIs are tried and how the VideoPlayer can influence the choice of the graphics API at startup time.

Dominique
A/V developer at Unity.

 

Hi again,

Follow-up: for anyone following this situation, the workaround really is to force the Graphics API to GLES2 because on devices that don't have full support for GLES3 (including the GL_OES_EGL_image_external_essl3 extension), the VideoPlayer will not work. We'll have to devise a solution for having the VideoPlayer work on GLES3 implementations that don't have this extension (at least one solution comes to mind, but has performance implications) but meanwhile, please force the Graphics API to GLES2 when faced with this problem.

Dominique
A/V developer at Unity.

 

Hi MaskedMouse,

Thanks a lot for taking the time to report this, I'll see what we can do to reproduce locally with a similar device. I am working on a number of improvements to this situation that will be tested in the upcoming days. If you can, please report details about your device (exact model, OS version) so we can make sure to correctly cover this.

Note that with the version you are using, the only "valid" configuration for testing is keeping auto graphics API off and only leaving GLES 2 in the list. The version I am working on right now should let you use both GLES2, GLES3 or Auto. Of course there is a lot of variability in the video playback world on Android, so we cannot be sure for every device, but we're doing everything we can to improve this.

Dominique
A/V developer at Unity.

 

GLES3 on Nexus 5 has been tested locally and now works. We're making every effort for these improvements to make it in time for the 5.6 release. Vulkan is an entirely different discussion however and is not supported by the Android VideoPlayer for now.

Thanks for your time,

Dominique
A/V developer at Unity.

 

Hi Corin!

Yes, I'm really interested, thanks for the offer!

Would you mind submitting the project as a bug report so we have all the info (Unity version, project, logcat) at the same place? It helps with internal communication and prioritization as well and makes it easier to enlist the help of QA and support teams.

I understand that performance problems start to creep up as you raise complexity, but it would make profiling and general investigation easier if you kept the simplicity level as low as possible - while keeping the performance problems visible of course.

It could be that the solution resides in using a more lightweight video, but it will be a good exercise to go through your project to see if there are any low-hanging fruits.

Note that the closest device I have to test this is a Nexus 6 running 6.0.1. Think this is an adequate substitution?

Dominique

 

Thanks for submitting this! 360p is definitely reasonable so we should be able to do something.

Also please add the bug id on this thread so I can go have a look asap.

About the OMX.google.aac.decoder, this is a audio-related message (AAC being the audio codec for audio streams that normally accompanies H.264 video streams), so this is likely not related to the GL error.

Dominique