Web Interface

From NMTWiki

Easy and suitable for everyone.

Applicable only for the following:

PCH NMT models:	A100/110/B110
Others NMT's:	HDX/eGreat

Many of the NMT functions can be accessed via a web browser. Due to the constantly evolving firmware and user apps the links below may change and become outdated. If you notice any not working then please update them.

In the following list, IP-Address is the IP address of your NMT, for example 192.168.2.2.

NOTE: Accessing these pages is NOT part of an official remote administration feature, except for application administration pages (e.g. Torrent and Usenet clients). The rest of the links here are listed for educational purposes. If you click on some link or button on a page you will probably get redirected to 127.0.0.1 (e.g. localhost on your own PC), and the linked page will not load properly. In this case you can try replacing the 127.0.0.1 IP in the URL with the IP of your NMT.

Applications

BTPD Bit Torrent client: http://IP-Address/torrent/bt.cgi
Transmission: http://IP-Address:8077; username: nmt; password: 1234
Transmission 1.51 (if installed separately): http://IP-Address:9091
NZBGet (Usenet client): http://IP-Address:8066
MyiHome: http://IP-Address:8088/app/player/intro/action/intro.php
Casgle iDVR: http://IP-Address:8055

Configuration

Home: http://IP-Address:8883/start.cgi
Preferences: http://IP-Address:8883/preferences.htm
Audio/Video: http://IP-Address:8883/display.html
Network Share: http://IP-Address:8883/network_share.html
Network: http://IP-Address:8883/network.html
NMT Applications: http://IP-Address:8883/media_server.html
DVD/Audio CD: http://IP-Address:8883/dvd.html
Maintenance: http://IP-Address:8883/maintenance.html

NMT Application Start/Stop-Links

(in order of apperenace in Setup-Menu)

Usable screen area and image sizes

User philofred make a report on details for visible screen area resolution. See thread here: http://www.networkedmediatank.com/showthread.php?tid=25615

This included a set of tests about screen/area resolution and bitmap rendering quality of NMT browser. These kind of tests should help HTML content developers for NMT (MSP plugins, web services and multimedia jukebox interfaces).

Test files and considerations

The zip file including the tests is available here: Htmltest1.zip. Unzip the files to the PCH and browse them with doc file type (the blue button on 100-series remote control).

Each test is just a simple HTML page using PNG and JPG bitmaps. The first set (test_1X.htm) is related to screen/area resolution. The second set (test_2X.htm and test_3X.htm) is related to rendering quality of high resolution bitmaps.

In this case description the setup is a Popcorn Hour A-110 outputting via HDMI cable to a Sony Full HD TV (HD Ready 1080p) handling 1920x1080p resolution. The Popcorn Hour is setup to output the video mode 1920x1080p @ 50Hz. So NMT browser is used in HD mode.

Mentioned pixel coordinates are specified in pixel columns and rows. By example 1280x720 screen goes from column 0 to 1279 (width) and goes from raw 0 to 719 (height). Top-left pixel is (0, 0) and bottom-right is (1279, 719). In the tests I noticed both PNG and JPG bitmaps give exactly the same behavior and are supported equally.

Testing screen/area resolutions

Test 10: NMT browser screen resolution
Specs: It displays a tiled blue grid bitmap with 100x100 resolution as HTML background and a void HTML body.

Results:

Display seems OK. Between 12 and 13 times horizontally. A little more than 7 times vertically so 1280x720.
Sometimes a frame around the screen is not displayed and is outside the TV screen (the "overscan" area). This is due to the TV and can optionally be turned off (in your TV settings).

Conclusions:

As mentioned in MSP Design document, the NMT browser has a fixed screen resolution 1280x720 even if the PCH video output is set to 1920x1080.
A TV overscan is present in this case, as mentioned in MSP Design document as well.
PNG format is correctly supported as background bitmap (MSP Design doc advices to save background bitmap as JPG).

Test 11: NMT browser body resolution (usable area)
Specs: It displays a tiled blue grid bitmap with 100x100 resolution as HTML background and a big red table in HTML body.

Results:

Width: the table does not fit exactly the whole screen widely (width="100%"). Height: the table is too high to fit the screen height, this is wanted, so scrolling down stops it at the "bottom end" to know the bottom raw without any more scrolling.
Looking carefully the screen and the tiled blue grid bitmap: the table starts at (92, 36) and ends at (1187, 683). So the body width is 1096 (=1187-92+1) and the body height is 648 (=683-36+1).

Conclusions:

At first sight, the HTML body resolution (the usable area) is different from the one specified by the MSP Design document i.e. 1100x656.

Test 12: NMT browser body resolution (usable area)
Specs: It displays a tiled blue grid bitmap with 100x100 resolution as HTML background and the body is composed of the same blue grid bitmaps that fills the HTML body area with a tiled bitmap 100x100, a bitmap 96x100 on the right and a bitmap 100x48 at the bottom. No table used here.

Results:

Display seems OK. 6 rows of 10 bitmaps 100x100 + 1 bitmap 96x100 and last raw of 10 bitmap 100x48. Bottom-right corner empty.

Conclusions:

The HTML usable area (body) is at least 1096x648, but check the overscan on your TV!

Test 13: the exact width of the body
Specs: The same as Test 12 but the bitmap on right side is 100x97 (one red pixel wider).

Results:

The bitmaps on the right side are not displayed correctly: a line feed is done before displaying it because it is too wide.

Conclusions:

The HTML usable area has 1096 pixel width and no more (without scrolling).

Test 14: the exact height of the body
Specs: The same as Test 12 but the bitmap at the bottom is 49x100 (one red pixel higher).

Results:

The bitmaps at the bottom are displayed correctly but you can scroll one pixel down (down and up keys shift the body).

Conclusions:

The HTML usable area has 648 pixel height and no more (without scrolling).

Test 15: table resolution declaration
Specs: It displays a tiled blue grid bitmap with 100x100 resolution as HTML background and a red table as HTML body. Table content is small but defined with height="100%".

Results:

The table is small and does not go to the screen bottom.

Conclusions:

The height specified in table is not taken into account (even specified in pixels).

Conclusions about screen/area resolutions:
Test 12, Test 13 and Test 14 demonstrate the usable area for HTML content is 1096x648. I do not know about the specified 1100x656. Maybe somebody could explain me.

Test 11 and 15 prove putting the HTML body content in a HTML table with width="100%" can avoid the user to scroll to the right but height="100%" has no effect so if HTML content is higher than 648 pixels, the user can scroll down. This is good to know if you want avoid scrolling content. Or maybe I do not specify it correctly in HTML and somebody can help me.

Tests about rendering quality of high resolution bitmaps

Tests 2X: bitmap resolution in the body
Specs: It displays a tiled blue grid bitmap with 100x100 resolution as HTML background and a high resolution bitmap (red grid) as HTML body. Note: there is no zoom feature is those tests.
Test 20: bitmap is 1000x648 pixels
Test 21: bitmap is 1024x648 pixels
Test 22: bitmap is 1096x648 pixels
Test 23: bitmap is 1280x720 pixels
Test 24: bitmap is 1920x1080 pixels

Results:

Bitmap rendering is OK until 1024x648 and then there is an unexplained degradation above the size 1024. 1096x648 should be correct (fulfill the area resolution) but the quality is bad.

Conclusions:

Bitmap size above 1024 pixels won't be correctly displayed (both width and height, but height is more or less useless as max is 648).

Tests 3X: bitmap resolution in the background
Specs: It displays a high resolution background bitmap and a small blue table as HTML body (to be able to see the background).
Test 30: background bitmap is 1000x1000 pixels
Test 31: background bitmap is 1024x1024 pixels
Test 32: background bitmap is 1100x1100 pixels
Test 33: background bitmap is 1280x720 pixels
Test 34: background bitmap is 1920x1080 pixels

Results:

The same as with tests 2X: bitmap rendering is OK until 1024x648 and then there is an unexplained degradation above the size 1024. 1280x720 should be correct (fulfill the background resolution) but the quality is bad.

Conclusions:

The same as with tests 2X.

Conclusions about rendering quality of high resolution bitmaps
Both in background or the HTML body, bitmaps above 1024 pixels (width or height) have their quality impacted leading to bad rendering. Maybe Syabas has an explanation about this issue or is this a bug?. There is nothing to do with the size in bytes, I tried with heavy bitmaps (>3MB) and it behaves the same: correct rendering below 1024 pixels, bad above.
These issue is not new and it just confirmed what is said in this thread: showthread.php?tid=9437

As an example, look carefully the background bitmap of the MSP Community site of the GrimRadioList (Music group) in a PC browser and then on your TV screen:

http://plugin.mspsite.com/action/showservice.jsp?homePath=http://www.mspportal.com/community&serviceid=grimradiolist&res=1280x720

http://plugin.mspsite.com/action/showservice.jsp?homePath=http://www.mspportal.com/community&serviceid=grimradiolist&res=1280x720

The quality is totally different because the size is 1280x720 (above 1024), note the blockyness in the left part.

General conclusion:

HTML body area is 1096x648.
Bitmaps should be below 1024 pixels (width and height) to get a correct rendering, both in the background and in the body.
No limit about the size in bytes.
Background bitmap can also be PNG.

Note: you may get different results depending upon your TV's overscan settings.

Web Interface

From NMTWiki

Contents

Applications

Configuration

NMT Application Start/Stop-Links

UPnP AV Server

MyiHome Server (PHP)

FTP Server

Samba Server

NFS Server

Torrent

Usenet Client

Casgle i-DVR

Usable screen area and image sizes

Test files and considerations

Testing screen/area resolutions

Tests about rendering quality of high resolution bitmaps

Views

Personal tools

Navigation

Search

Toolbox