[codey2000]

@codey2000

Looking at their apps decompiled code, I see they convert the cenc data to level 0 if NONE of the below...

Code:

if (Util.SDK_INT > 22 || schemeData == null || schemeData.data == null || !C.WIDEVINE_UUID.equals(PsshAtomUtil.parseUuid(schemeData.data)) || PsshAtomUtil.parseVersion(schemeData.data) != 1)

Looking at your log, looks like your api level is 22 (which isn't greater than 22.)
So, Ill try convert the cenc data to level 0 and see if that helps.

Can you try this version please:
https://drive.google.com/file/d/18aQuQRQ...sp=sharing

It works!!! Thank you so much. Was this because I have a old firestick (version 2)?

[matthuisman]

Wow. Wasn't expecting that. I'll do more tests and get an update out. To confirm, you can playback right upto 4k?

[codey2000]

Wow. Wasn't expecting that. I'll do more tests and get an update out. To confirm, you can playback right upto 4k?

I can play HD content. Since it's a version 2 firestick it doesn't support 4k. I can try get a log so you can see what happens.

[codey2000]

Wow. Wasn't expecting that. I'll do more tests and get an update out. To confirm, you can playback right upto 4k?

I can play HD content. Since it's a version 2 firestick it doesn't support 4k. I can try get a log so you can see what happens.

I opened the Godzilla vs Kong movie in 4k and got audio, so I guess 4k playback works on devices that support 4k.

[matthuisman]

oh, if 1080 is working - then that also needs L1 widevine so looks like all good.

Just pushed 0.1.5 to the repo.
Can you please update to that and confirm everything still works fine

Thanks

[codey2000]

oh, if 1080 is working - then that also needs L1 widevine so looks like all good.

Just pushed 0.1.5 to the repo.
Can you please update to that and confirm everything still works fine

Thanks

I can confirm version 0.1.5 works fine after the update from the repo.

[matthuisman]

great. I plan on adding some new settings in the future to 
1) Enable / Disable Dolby Vision streams
2) Enable / Disable 4K streams
3) Enable / Disable H265 streams

UPDATE: Just pushed 0.1.6 that adds the above settings
note: dolby vision / 4k setting will only show if L1 device is enabled

[estuary_enthusiast]

Would you consider make HBO GO please?

[matthuisman]

There is already a HBO go addon. Search the forums

[matthuo]

Can I use the HBO Max addon based on Coreelec or Libreelec, and can it be played normally?

[matthuo]

My IP is 154.17.x.x, which is the IP of Los Angeles, USA. Why can't I connect to the slygui addon library?

[shoppedude]

My IP is 154.17.x.x, which is the IP of Los Angeles, USA. Why can't I connect to the slygui addon library?

It is possible that your ISP is blocking it at your router. I use Xfinity and if I turn on the Advanced Protection, several add-on sites (and other useful sites) get blocked.

[raina343]

@matthuisman subs now work, thank you very much for that
There is one problem however, which I hate to bring up since you went to the trouble for subs in the first place, and it appears to be in the pycaption subsystem, so I doubt you can do much about it

I took Southpark S23 E02 (band in china) as a sample.

the subs displayed onscreen for opening dialog are

[ Humming ]
Stan! Family meeting!
Nobody cares about that!
Come on!

now looking at the srt file converted by the addon

25
00:00:37,000 --> 00:00:42,000
[ Humming ]

26
00:00:42,000 --> 00:00:45,000
Stan! Family meeting!

27
00:00:42,000 --> 00:00:45,000
Get downstairs!

28
00:00:45,000 --> 00:00:45,000
I'm writing a song, Dad.

29
00:00:45,000 --> 00:00:46,000
Nobody cares about that!

30
00:00:46,000 --> 00:00:49,000
Come on!

so it appears lines 27 and 28 were skipped and looking at the timestamps it's easy to see why.  the timings are the same/overlapping

so I took a look at the source sub file on hbo (I mean they could just made life easier by using a more common sub format, sigh)

 <p region='pop1' style='basic' begin='00:00:37:01' end='00:00:42:06' tts:origin='35% 84.66%' tts:extent='27.5% 5.33%'>[ Humming ]</p>
   <p region='pop1' style='basic' begin='00:00:42:08' end='00:00:45:00' tts:origin='37.5% 79.33%' tts:extent='52.5% 5.33%'>Stan! Family meeting!</p>
   <p region='pop2' style='basic' begin='00:00:42:08' end='00:00:45:00' tts:origin='45% 84.66%' tts:extent='37.5% 5.33%'>Get downstairs!</p>
   <p region='pop1' style='basic' begin='00:00:45:02' end='00:00:45:17' tts:origin='10% 84.66%' tts:extent='60% 5.33%'>I'm writing a song, Dad.</p>
   <p region='pop1' style='basic' begin='00:00:45:19' end='00:00:46:19' tts:origin='30% 84.66%' tts:extent='60% 5.33%'>Nobody cares about that!</p>
   <p region='pop1' style='basic' begin='00:00:46:21' end='00:00:49:19' tts:origin='55% 79.33%' tts:extent='20% 5.33%'>Come on!</p>

and the timings are the same here.

so I went on a bit of a google trip, and came across

https://github.com/yanncoupin/stl2srt
this appears to be another python conversion utility. 
this utility appears to merge those rows with identical timestamps and also using the milliseconds timings that pycaption appears to drop out

so when I throw the XML subs file into that, I get

14
00:00:37,041 --> 00:00:42,250
[ Humming ]

15
00:00:42,333 --> 00:00:45,000
Stan! Family meeting!
Get downstairs!

16
00:00:45,083 --> 00:00:45,709
I'm writing a song, Dad.

17
00:00:45,792 --> 00:00:46,792
Nobody cares about that!

18
00:00:46,875 --> 00:00:49,792
Come on!
I've got big news!


which then appears works perfectly...

so I know you mentioned writing your own custom converter, but perhaps this will help avoid that need?

I know this is digging up an old issue, but whether it's on my end or not, I'm not sure, but this has started cropping up again as an issue.
both this and last week's episodes of 'The Nevers' have missing lines, in a vain similar to what was reported back  in this post.  Now this could be something on my end that I haven't or forgotten to do, since I did just recently switch my kodi install to a newer version of ubuntu, but from what I recally it was the way the XML was parsed previously, and wasn't dependent on any local dependency

[matthuisman]

oh, I think i did switch back to pycaption... I'll see if I can update that to not skip when timings are the same

@raina343
just pushed update to common module (0.29.3) to improve pycaption.
it now groups same timestamp subs together for webvtt output
and also now correctly implements the microsecond timings
you can force update by following: https://www.matthuisman.nz/2019/09/how-t...d-ons.html

please try update and let me know

[raina343]

oh, I think i did switch back to pycaption... I'll see if I can update that to not skip when timings are the same

@raina343
just pushed update to common module (0.29.3) to improve pycaption.
it now groups same timestamp subs together for webvtt output
and also now correctly implements the microsecond timings
you can force update by following: https://www.matthuisman.nz/2019/09/how-t...d-ons.html

please try update and let me know

seems to be working now.  Thanks!