2019-01-12, 18:54
are there any plans to implement playready for windows?
2019-01-13, 11:44
Hi, sure, still waiting for a windows dev who is more into the window api things.
From my side I'll provide all information about the workflow, if someone signals time for development
From my side I'll provide all information about the workflow, if someone signals time for development
2019-01-18, 09:54
May I ask, what happended to your MediaCodec Async plans? You seem to have re-introduced MediaCodec via JNI in the respective branch?
2019-01-23, 17:33
I did some performance tests in my WIP branch, but it was no real improvement.
I'll wait until async is implemented in NDK and try again (Android API 28 IIRC)
I'll wait until async is implemented in NDK and try again (Android API 28 IIRC)
2019-01-23, 17:43
I might soon open a topic where I elaborate on performance while playing high bitrate 2160p60 content. Rendering a 4K frame every 16ms is critical. And I do experience problems. Amazon even suggests using Tunnel Mode Playback.
2019-01-23, 18:01
Tunneled playback is an option but does not really fit into kodi's VideoPlayer.
The only option is to write a new videoplayer (see rbpi / OMX) and bypass all the options which are posssible if you have control over the frames.
Beside this performance in tunneled mode (with my heavy 4K sample on AFTV4K (2017) was not too good. Because of that I didn't spend too much time on it.
The only option is to write a new videoplayer (see rbpi / OMX) and bypass all the options which are posssible if you have control over the frames.
Beside this performance in tunneled mode (with my heavy 4K sample on AFTV4K (2017) was not too good. Because of that I didn't spend too much time on it.
2019-01-25, 14:13
(2019-01-23, 18:01)peak3d Wrote: Tunneled playback is an option but does not really fit into kodi's VideoPlayer.
What tunneled playback mean?
2019-05-03, 09:26
(2019-01-13, 11:44)peak3d Wrote: Hi, sure, still waiting for a windows dev who is more into the window api things.
From my side I'll provide all information about the workflow, if someone signals time for development
I've just been notified your need of someone to wrangle WinApi. I'm unsure of how much time I currently have at my disposal, but Google being Google, the idea of dropping Widevine support is tickling. Let me know if you still need help with the implementation.
