RenderHeads / UnityPlugin-AVProVideo

AVPro Video is a multi-platform Unity plugin for advanced video playback
https://www.renderheads.com/products/avpro-video/
235 stars 28 forks source link

Android player freezes at first frame using URLs #79

Closed kfaber33 closed 5 years ago

kfaber33 commented 5 years ago

I’m working on a unity+vuforia app for Android/iOS using your amazing AVPro full component to reproduce videos from the web using URLs. It was working very fine until I updated the version 1.9.12 with 1.9.16, getting the android version no more able to play any video. The problem is that after running MPlayer.OpenVideoFromFile(MediaPlayer.FileLocation.AbsolutePathOrURL, "

AndrewRH commented 5 years ago

A couple of things to try:

1) Try switching the video API (in MediaPlayer > Platform Specific > Android) - does that help? 2) Try removing Vuforia, we've heard in the past that Vuforia can cause problems - does that help?

Otherwise, if you email us your PDF invoice, or invoice number, then we can send you the old 1.9.12 version to downgrade to while we investigate.

pedrovf commented 5 years ago

I got the same problem here, but without Vuforia. I'm using VR (oculus GO, with Exoplayer), and if a play a video, it freezes on the first frame!! It was working with the Trial Version(1.9.14), but yesterday I bought the full version for Android (v 1.9.16) and it stopped working!!! And 1 more thing, it only works if I restart the Oculus, but just for 1 time! If I close the app and then open it again, it just stops working! Can you guys please send me the 1.9.14 version? I need to finish this quick!!!

kfaber33 commented 5 years ago

Yesterday I tried changing some setting, at the end it seems that switching Exoplayer to Mediaplayer (AVPRO Android specific setting) do the trick! Let me know if this works also for you!

pedrovf commented 5 years ago

Ohh I already did that! It worked but I would prefer if it works with Exoplayer, cuz before (v 1.9.14) it was working with Exo. Conclusion: Exoplayer is the problem! Changing to MediaPlayer seems to be the workaround for now

kfaber33 commented 5 years ago

I would prefer to use Exoplayer too :)

kfaber33 commented 5 years ago

BTW the issue with exoplayer seems to persist even without Vuforia

pedrovf commented 5 years ago

Yep, and my left eye (Oculus GO) is flickering with Mediaplayer :/

AndrewRH commented 5 years ago

pedrovf, so with 1.9.16 Oculus Go left eye is flickering? It was working in 1.9.14? Hmm..is this with our example stereo scene? Do you have the UpdateStereoMaterial in your scene? Are you using single or multi-pass VR? I'll reply to your email now. Thanks :)

pedrovf commented 5 years ago

Well, I kinda fixed it by setting the eyeTextureResolutionScale to 1.5f, but I don't know why! It was flickering when I was using 1.25f, but with Exoplayer it wasn't flickering. I tested with single and multi-pass (same result), but I'm using the unity Skybox/Panoramic material because if I use the sphere, the bottom and top sides of the video will be distorted. I didn't need the UpdateStereoMaterial to be able to make it work...It was working perfectly with the 1.9.14

pedrovf commented 5 years ago

So, I downloaded the 1.9.14 version you guys sent me, and it worked flawlessly!! Using exoplayer, and without flickering! Thanks for the amazing support @AndrewRH !! I'll answer your email with more details about the problem! :D

kfaber33 commented 5 years ago

Dear Andrew, please can you share AVPro 1.9.14 also with me? I would like to test if I can have exoplayer working in my project too :)

AndrewRH commented 5 years ago

kfaber33, please email unitysupport@renderheads.com and invoice your PDF purchase invoice and we'll organise 1.9.14 for you.

Thanks,

Ste-RH commented 5 years ago

We have just released Version 1.9.17, which includes some fixes in the ExoPlayer API path. Please do grab it and let us know if the problems you were encountering with 1.9.16 have been addressed.

AndrewRH commented 5 years ago

We'll close this issue in a couple of days, as we've proposed a solution (new plugin version) but haven't heard anything back.

Thanks,

AndrewRH commented 5 years ago

Closing this issue - presumed fixed