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. We have updated the language to the Editor Terms based on feedback from our employees and community. Learn more.
    Dismiss Notice
New Forum User Notice Update to the Unity Editor Software Terms

Video E/OMXNodeInstance ERROR: UnsupportedIndex on 2018.3.0 f2

Discussion in 'Audio & Video' started by Alex_in_wonderland, Sep 20, 2019.

  1. Alex_in_wonderland

    Alex_in_wonderland

    Joined:
    Aug 2, 2017
    Posts:
    9
    Hi,

    We are trying unity videoplayer on 2018.3.0f2 and got the following error complaining about OMX. I tried to disable "multithread rendering". But still got the same issue. Is this a bug of unity or improper video codec types or device related issues? Anyone had similar issue?

    The device is tivco android box from 3divi

    video format is:

    upload_2019-9-20_13-39-52.png


    upload_2019-9-20_13-39-27.png

    also we got the following error messages while videoplayer is playing.
    upload_2019-9-20_13-40-55.png
     

    Attached Files:

    Last edited: Sep 20, 2019
    Alex_in_wonderland, Sep 20, 2019
    #1

  2. Domas_L

    Domas_L

    Unity Technologies

    Joined:
    Nov 27, 2018
    Posts:
    111
    Hello! Can the movie be played on the device outside of Unity’s context, for example, using the embedded media player? Also, could you check if the issue still reproduces on newer versions of Unity (preferably 2019.2 stream)? Starting with 2019.1, Vulkan is supported and it uses a different approach for decoding the movie (it goes into system memory prior to texture) so we may have move luck with this alternative.

    If that still doesn't help, could you please submit a bug report with a minimal reproduction project for this issue and reply in here with the issue ID?
     
    Domas_L, Sep 20, 2019
    #2

  3. Alex_in_wonderland

    Alex_in_wonderland

    Joined:
    Aug 2, 2017
    Posts:
    9
    Hi Domas,

    There are no such error messages out side Unity's context. We tried 2019.2.6f1 without a good luck. Already submit a bug report.
     
    Alex_in_wonderland, Sep 23, 2019
    #3