[libbluray-devel] JRE for Android part 3

[Vitor Dall'Acqua]

You are right.
That's why I asked for the source with Petri's changes.

But they probably would want me to create the build process.
And this is out of my league.

I will try to convince somebody to take this showing as this works as
expected. As you mentioned as a proof of concept.

But for the moment, the JRE library can be installed as an addon, not
support by Kodi.
The only thing is that environment variables need to be set for it to work
and libbluray needs 3 or 4 lines of code to work too.

I once worked with my Kodi build, called Kodi HDR Edition.
Since windows had no public api to turn hdr on and off and pass the
metadata I had to use nvidia and amd private apis. This could not be part
of Kodi.

So i maintained it for more than a year and an unofficial build.
The same is happening with Dolby Vision on android right now, until ffmpeg
team decides to add support for mkv dolby vision we are doing it our way
but it won't get merged into Kodi.

And the same will happen to bluray menu playback.
It will be a standalone build with standalone addon for people to use until
it gets merged with Kodi as a binary addon.

 (I'll just use the same build that supports dolby vision)

Not much different to the way vpeter does for CoreElec. You have to use his
image of the OS for bluray menu support.



On Sat, Jan 30, 2021, 2:45 PM Shaya Potter <spotter at gmail.com> wrote:

> On Sat, Jan 30, 2021 at 7:27 PM Vitor Dall'Acqua <veggav at gmail.com> wrote:
>
>> This problem is true for every disc, regular or uhd.
>> Since the shield is doing all the hard work with software rendering the
>> entire menu becomes slow.
>> But this isn't perceptible with the shield on 1080p because it has the
>> power to render it and display the menu.
>>
>> Both cases you present might be the reason for that.
>>
>> But I would say that the missing ts packets have a higher chance of being
>> the one.
>>
>> The good news is that I tried several regular blurays and everything
>> plays just fine.
>>
>> This is probably the last step we have to work with, after that is just
>> preparing for release.
>>
>> Also, Petri, do you think you could share the changes you made on JRE to
>> allow it to run without JAVA_HOME?
>>
>> And did you create a make file to compile it? Or did it by hand?
>>
>> And finally, the changes needed on libbluray are just a few lines of code
>> on bdj.c.
>> Do you think a #ifdef android would be a good idea?
>>
>> I believe that even VLC could play full disks on Android too.
>>
>
> if I had to guess, I think kodi would want more.  They wouldn't want to
> drop a prebuilt jvm into their tree, they would want their build process to
> use jvm sources, perhaps apply a set of patches to it, and build the jvm as
> part of the normal android build.  Of course, I could be wrong.  I think
> the work that's been done in these threads is proof of concept to
> demonstrate that it can work and its something kodi should support by
> default as part of their "store" builds..  I'd think that it would be
> constructive for you to loop in kodi's android developers to this
> discussion.  i.e. they might know intricacies of android that the rest of
> us are missing.  thoughts?
> _______________________________________________
> libbluray-devel mailing list
> libbluray-devel at videolan.org
> https://mailman.videolan.org/listinfo/libbluray-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.videolan.org/pipermail/libbluray-devel/attachments/20210130/8de9ed37/attachment-0001.html>