New TAP to manage the PVR using HTML/CSS/JavaScript.

DeltaMikeCharlie · #21

I did some testing this morning and narrowed down the performance issue to my use of strcat() to build the JSON output string.

I did a quick test of strcat() vs keeping track of the length of the string in an external variable and using strncpy() with an offset and got a 400 fold improvement in performance.

I'm going to explore this further as well as looking into caching.

Isarwolf · #22

I wanted to test TMA1 but had no succes.
Perhaps CRP2401 is somewhat different to the SRP-Series.

I got this log:

Code: Alles auswählen

TMA1 Started: 09:27:56.

Initialising listening socket.
Setting listening socket 93 to non-blocking mode.
About to 'bind' listening socket 93.
About to 'listen' listening socket 93.
Listening socket 93 initialisation complete.
Got connection from 192.168.178.20.
Got connection from 192.168.178.20.
Got 354 bytes of data.
GET / HTTP/1.1
User-Agent: Opera/9.80 (X11; Linux i686) Presto/2.12.388 Version/12.16
Host: 192.168.178.33:8000
Accept: text/html, application/xml;q=0.9, application/xhtml+xml, image/png, image/webp, image/jpeg, image/gif, image/x-xbitmap, */*;q=0.1
Accept-Language: de-DE,de;q=0.9,en;q=0.8
Accept-Encoding: gzip, deflate
Connection: Keep-Alive


Method: 'GET'
Path: '/'
Processing Command '/' (1).
Trying to send home page.
Sending 
HTTP/1.1 200 OK
Content-Type: text/html
Content-Length: 116

<html><head>
<title>404 Not Found</title>
</head><body>
<p>The requested URL was not found.</p>
</body></html>

Sent 404 - 181.
Got 403 bytes of data.
GET /favicon.ico HTTP/1.1
User-Agent: Opera/9.80 (X11; Linux i686) Presto/2.12.388 Version/12.16
Host: 192.168.178.33:8000
Accept: text/html, application/xml;q=0.9, application/xhtml+xml, image/png, image/webp, image/jpeg, image/gif, image/x-xbitmap, */*;q=0.1
Accept-Language: de-DE,de;q=0.9,en;q=0.8
Accept-Encoding: gzip, deflate
Referer: http://192.168.178.33:8000/
Connection: Keep-Alive


Method: 'GET'
Path: '/favicon.ico'
Processing Command '/favicon.ico' (12).
Trying to send home page.
Sending 
HTTP/1.1 200 OK
Content-Type: text/html
Content-Length: 116

<html><head>
<title>404 Not Found</title>
</head><body>
<p>The requested URL was not found.</p>
</body></html>

Sent 404 - 181.

DeltaMikeCharlie · #23

Method: 'GET'
Path: '/'
Processing Command '/' (1).
Trying to send home page.
Sending
HTTP/1.1 200 OK
Content-Type: text/html
Content-Length: 116

<html><head>
<title>404 Not Found</title>
</head><body>
<p>The requested URL was not found.</p>
</body></html>

Did you copy index.html into /ProgramFiles/Settings/TMA1/public_html on your PVR?

Isarwolf · #24

DeltaMikeCharlie hat geschrieben:Did you copy index.html into /ProgramFiles/Settings/TMA1/public_html on your PVR?

Yes I have copied as requested the file to this folder.

Isarwolf · #25

It was my fault.
I have named the folder "public html" without underline.

I have changed it and now I got a result.

DeltaMikeCharlie · #26

It's good to hear that you got it working. Can you please share your findings?

How many channels do you have?
How fast do they load?
Can you change channels OK?
Can you list the timers?

Isarwolf · #27

I have 118 channels
It needs less then three seconds
Yes, I can change channels
Yes I can list the timers

On my tablet I can change the channels by touchscreen.

I think the time should be in 24h notation

Sirius · #28

TMA1 A-004 (11.08.2013)

"742 records found".

First loading needed 60 seconds.

Then I closed browser window, and opened again:
I did this several times and it needs always 42 seconds.

When it was loaded the change between "Channels" to "Timers" and back to "Channels" needs about 0.5 second.

DeltaMikeCharlie · #29

Thanks for the feedback everyone.

I am currently working on a way to speed up loading the channels. I hope to implement it on the weekend.

I think the time should be in 24h notation

I don't recall intentionally using 12h format anywhere, but that does not matter just yet. Eventually, the date/time format will be controlled by the user and can be in whatever format they like. The JavaScript code could use the default date/time format of the browser, for example.

As you can also see, the proof-of-concept is only in English. I plan to support multiple languages. The question here would be which language setting to use? 1) The language of the PVR or 2) The language of the browser. At the moment, I am favouring using the language of the PVR for consistency, but I am happy to hear other opinions. Are there many multi-lingual households that would want to personalise the interface language per person?

DeltaMikeCharlie · #30

I have uploaded a new test version to my ftp site that should be a lot faster loading channels.

I have added an entry to the log for how long a command takes to complete. There are 2 versions of the TAP included in this release, both have the extra logging, but one has the faster code and the other has the original code.

I would be interested to see the difference on a PVR with hundreds of channels. My PVR with 30 channels reduced from 10 ticks to 1 tick to list the channels. Be careful, if you do try both TAP versions, I have found it best to reboot the PVR rather than unloading/loading the TAPs.

Please note: I have deliberately not fixed the channel character issue so that I can compare the channel loading times only.

FireBird · #31

The fast version just displays "No records found" for both channels and timers.

Code: Alles auswählen

Got connection from 192.168.0.1.
Got connection from 192.168.0.1.
Got 282 bytes of data.
GET / HTTP/1.1
Accept: text/html, application/xhtml+xml, */*
Accept-Language: de-AT
User-Agent: Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.1; Trident/6.0)
Accept-Encoding: gzip, deflate
Host: 192.168.0.214:8000
DNT: 1
Connection: Keep-Alive
Cache-Control: no-cache


Method: 'GET'
Path: '/'
Processing Command '/' (1).
Trying to send home page.
Closing home file.
Home file closed.
NetHTTPRespond Sending header: 67.
NetHTTPRespond Sent: 67.
NetHTTPRespond Sending payload: 10750.
NetHTTPRespond Sent: 10750.
Response sent.
Command completed in 1 ticks.

Isarwolf · #32

Thanks for the 24h notation.

:

TMAfast works very quickly with 118 channels.

In the list of timers there is the sorting not correct. I compare with the timer list of SmartEPG.

The scan timer is wrong and two "repetition timer"
A blocked timer will not be shown.

DeltaMikeCharlie · #33

FireBird hat geschrieben:The fast version just displays "No records found" for both channels and timers.

It's like the home page is being delivered but the JavaScript is not activating.

Can you try: http://192.168.0.214:8000/api?function= ... action=get! and see if that returns anything to your browser?

FireBird · #34

DeltaMikeCharlie hat geschrieben:Can you try: http://192.168.0.214:8000/api?function= ... action=get! and see if that returns anything to your browser?

I get a long list of text with the channel details. The problem seems to be connected with the Internet Explorer (V10). If I try the same with FireFox, I get the ?no records found? for a very short period, and then it refreshes the display with the correct channel list. As there was a newer index.html in the zip, I?ve also updated that one.

The difference between slow and fast version is 10086 vs. 51 ticks.

DeltaMikeCharlie · #35

The difference between slow and fast version is 10086 vs. 51 ticks.

Wow! That is a huge difference.

I did not test the latest version with IE, only FireFox. From memory, IE 10 has a "compatibility" mode. Did you try that?

DeltaMikeCharlie · #36

Out of interest, how do people with 400/500/1000+ services manage them? Do you just use the standard Favourites list that the PVR provides, or is there another mechanism for managing satellite/cable services?

FireBird · #37

Now I wanted to try the compatibility mode and IE even worked in standard mode. The Toppy has been rebooted before every test.

I’d suggest that you forget about it until more people report that problem or until there is some way to reproduce the behaviour.

I mainly use only about 60 channels, which create the first block in the channel list. The remaining 1100 are just there for curiosity (e.g. if someone reports a SmartEPG problem with one of these) and build an alphabetically sorted second block. I do not use favourites.

Sirius · #38

TMA1 A-005b (17.08.2013)

The new fast version is really fast !!

"742 records found" with old version it needed 42 seconds to show the Channel list,
and now with the new version only 1 second

The log of the fast version is attached.
With the slow version I got no records found.

Bug (?):
When I selected channel number 3 the SRP-2100 switches to TV channel 3.
When I switched more than two times back to the same channel, the browser marked this selected channel in red, but the SRP-2100 didn't change the channel.
Now I can only switch to other channels which I had never switched before.

Info:
First I had both TAPs in ProgramFiles.
When I started one of them with SmartFiler, the other tma TAP was also green marked (as running)

Info 2:
I use only about 50 channels, which are sorted in first place of channel list.

FireBird · #39

~~[quote="Sirius"]~~When I started one of them with SmartFiler, the other tma TAP was also green marked (as running)[/quote]
The public SmartFiler just checks the TAPID and I assume the both version use the same ID and therefore will both be shown in green when one of them is running.

Sirius · #40

Ah Ok.
Only a display problem, and only one tap is really running.

TTD Forum

New TAP to manage the PVR using HTML/CSS/JavaScript.

AW: New TAP to manage the PVR using HTML/CSS/JavaScript.

AW: New TAP to manage the PVR using HTML/CSS/JavaScript.

AW: New TAP to manage the PVR using HTML/CSS/JavaScript.

AW: New TAP to manage the PVR using HTML/CSS/JavaScript.

AW: New TAP to manage the PVR using HTML/CSS/JavaScript.

AW: New TAP to manage the PVR using HTML/CSS/JavaScript.

AW: New TAP to manage the PVR using HTML/CSS/JavaScript.

AW: New TAP to manage the PVR using HTML/CSS/JavaScript.

AW: New TAP to manage the PVR using HTML/CSS/JavaScript.

AW: New TAP to manage the PVR using HTML/CSS/JavaScript.

AW: New TAP to manage the PVR using HTML/CSS/JavaScript.

AW: New TAP to manage the PVR using HTML/CSS/JavaScript.

AW: New TAP to manage the PVR using HTML/CSS/JavaScript.

AW: New TAP to manage the PVR using HTML/CSS/JavaScript.

AW: New TAP to manage the PVR using HTML/CSS/JavaScript.

AW: New TAP to manage the PVR using HTML/CSS/JavaScript.

AW: New TAP to manage the PVR using HTML/CSS/JavaScript.

AW: New TAP to manage the PVR using HTML/CSS/JavaScript.

AW: New TAP to manage the PVR using HTML/CSS/JavaScript.

AW: New TAP to manage the PVR using HTML/CSS/JavaScript.