NLite windows build

[sub]

So you fixed that on the server? NMT and Kodi work fine by and I think I just url encoded the string (except '\\/:%.?=;') to handle accented characters etc, hopefully this won't impact those clients.

The server was a better place to fix this, since the URL is more accurate now, but let me know if it does cause those a problem and I'll provide an updated server that conditionally does this escaping.

[mvallevand]

No problems with Kodi, I don't really use the NMT anymore.

Here is a comparison of NLite vs VLC, Kodi (web client) and NextPVR clientmode with the same file so not bad but hopefully this can be tweaked . NLite and VLC also use most of the WDF CPU. NLites's network use is bursty, it is the only one playing via http.

Martin

[sub]

No problems with Kodi, I don't really use the NMT anymore.

Thinking about it, the NMT doesn't use this same activity stuff, so it should fine too (nothing should have changed from what it currently receives). I haven't used an NMT in years.

Here is a comparison of NLite vs VLC, Kodi (web client) and NextPVR clientmode with the same file so not bad but hopefully this can be tweaked . NLite and VLC also use most of the WDF CPU. NLites's network use is bursty, it is the only one playing via http.

I'm sure we'll be able to improve things a bit over time, but unknown how much. I don't know that much about libvlc or libsdl at this stage, but there may be options for further use hardware acceleration.

[mvallevand]

I am always worried about the /stream API and the NMT. I know you had to add the tweak &mode=http for fred250 which I also used in x-newa because of the difference in the read length and looking there still seems like there is a discrepancy between the requested content-length and what is sent.

Martin

[sub]

I am always worried about the /stream API and the NMT. I know you had to add the tweak &mode=http for fred250 which I also used in x-newa because of the difference in the read length and looking there still seems like there is a discrepancy between the requested content-length and what is sent.

This escaping change will only change for the filenames sent via the webclient interface, then NMT filenames will still have the spaces etc...so that change shouldn't have had any flow on effects to the NMT.

Yeah, I remember the difference, and wish it wasn't that way.

[mvallevand]

Keystroke handling needs some work,

- num pad ignored
- page up/down not working
- Home key not working
- Backspace not acting as back.

- ctrl F/R not working in EPG
- Skip/Next keys not working in EPG

Martin

[sub]

Give these a go. It should address all those, and get the freetext entry in the Search screen work (which always used a slightly different input mechanism to allow for keyboards with national characters - umlauts etc)

[mvallevand]

Give these a go. It should address all those, and get the freetext entry in the Search screen work (which always used a slightly different input mechanism to allow for keyboards with national characters - umlauts etc)

These still aren't working

- Backspace not acting as back.
- ctrl F/R not working in EPG Just sent as F and R Kodi sends 131142 and 131154
- Skip/Next keys not working in EPG no key sent

Also forgot to mention my favourite for navigating on slow clients, no function keys work. 112 to 120 work in Kodi for fn1-9

Not sure why a new NextPVR is included are new and different key= combinations then the NMT and Web Client?

Martin

[sub]

- Backspace not acting as back.
- ctrl F/R not working in EPG Just sent as F and R Kodi sends 131142 and 131154
- Skip/Next keys not working in EPG no key sent

I just double checked, and these three are definitely working for me. I've rebuild it an reattached, in case I got something wrong last time.

I'll check the F keys.

The SDL key codes aren't a good match to the Windows key codes, so I'm having to translate a lot of them.

[mvallevand]

No still nothing the BS is key=8 but I had to map that to 27 for Kodi.

Martin