Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. Dismiss Notice

Video Video is not being rendered when using URL on some Android devices

Discussion in 'Audio & Video' started by jaguardigital, Sep 19, 2019.

  1. jaguardigital

    jaguardigital

    Joined:
    Sep 29, 2015
    Posts:
    5
    Hi

    We're getting this error when trying to load an URL on the native Video Player in Unity 2019.2.

    E/NdkMediaExtractor: sf error code: -1010
    W/Unity: AndroidVideoMedia: Error opening extractor: -10000
    (Filename: ./PlatformDependent/AndroidPlayer/Modules/Video/Private/AndroidVideoMedia.cpp Line: 475)

    The bug appears when installing the 360 videos App we're developing, specifically on Xiaomi cellphones with Android 9. On an Iphone 6 and other multiple Android phones we have tested the App, it works ok.

    The error has been already reported here: https://answers.unity.com/answers/1666303/view.html
    and here: https://issuetracker.unity3d.com/is...ndered-when-using-url-on-some-android-devices

    Does anybody know if there is any chance to avoid this issue using a Video Player asset like UMP Pro or MPMP? We are short of time and can't wait for a bug solution
     
    Last edited: Sep 19, 2019
  2. Brad-Newman

    Brad-Newman

    Joined:
    Feb 7, 2013
    Posts:
    184
    I'm not using URLs, just loading videos from an uncompressed local Asset Bundle:

    Warn MediaExtractor: FAILED to autodetect media content.
    Error MediaExtractor: Trace connect 0x0 0xbf955600
    Error NdkMediaExtractor: sf error code: -1010
    Warn Unity: AndroidVideoMedia: Error opening extractor: -10000
    Warn Unity: (Filename: ./PlatformDependent/AndroidPlayer/Modules/Video/Private/AndroidVideoMedia.cpp Line: 457)
     
    Last edited: Jan 10, 2020
  3. Brad-Newman

    Brad-Newman

    Joined:
    Feb 7, 2013
    Posts:
    184
  4. Umresh

    Umresh

    Joined:
    Oct 14, 2013
    Posts:
    56
    I'm getting the same error in unity 2019.3. Did you find the fix?