expanded resolution options for android tpc
GregG
Just some guy...
There are many android tablets that handle 1920x1080+ native and it would be very valuable to have at least a 1920x800 resolution option so we could do a direct "save as different panel type" from a 2000XL panel design and have all the new supported features transfer over.
Comments
-
You can make custom resolution definitions for TPDesign4.
The file is "ppf.xml" in your Common Files/AMX Shared folder.
Back up the ppf file, then pick a profile to alter, change the resolution info, restart TPD4 and try that entry.
Here's one entry for a 5200.
<panelEntry>
<type>MVP-5200i</type>
<description>5.2 inch color wireless touch panel with intercom</description>
<deviceID>329</deviceID>
<screenSize>52</screenSize>
<numVideoWindows>0</numVideoWindows>
<numWirelessVideo>0</numWirelessVideo>
<isAudioDisabled>0</isAudioDisabled>
<hasLightSensor>0</hasLightSensor>
<hasMotionSensor>0</hasMotionSensor>
<hasBatteryLevel>1</hasBatteryLevel>
<hasCradleSensor>1</hasCradleSensor>
<hasAMX38IREmit>1</hasAMX38IREmit>
<hasAMX455IREmit>1</hasAMX455IREmit>
<hasVoIP>1</hasVoIP>
<userIRCount>8</userIRCount>
<usbType>RNDIS</usbType>
<fdType>2</fdType>
<textType>advType1</textType>
<panelImage>images\MVP-5200i.jpg</panelImage>
<resolution>
<resolutionEntry>
<width>800</width>
<height>480</height>
<setupPages>MVP-800x480.TP4</setupPages>
<externalButtons>MVP-5200i_ExternalButtons.xml</externalButtons>
<refreshRate>
<rate>60 Hertz</rate>
</refreshRate>
</resolutionEntry>
</resolution>
<systemCodeGroup>G4 Common Codes v2</systemCodeGroup>
<systemCodeGroup>MVP Common</systemCodeGroup>
<systemCodeGroup>Modero Common Codes</systemCodeGroup>
<systemCodeGroup>MVP 8400 Common</systemCodeGroup>
<systemCodeGroup>mips Firmware with Sound Common</systemCodeGroup>
<systemCodeGroup>Wireless G</systemCodeGroup>
<systemCodeGroup>Modero Secondary Interface Codes</systemCodeGroup>
<systemCodeGroup>USB Network Interface Codes</systemCodeGroup>
<systemCodeGroup>Modero Sensors Codes</systemCodeGroup>
<systemChannels>
<codeEntry>
<code>289</code>
<adv>1</adv>
<text>Battery Setup: Disable Panel Dim When On Battery Power</text>
<description>When active will turn off the panels automatic dimming of the brightness to 80%</description>
</codeEntry>
<codeEntry>
<code>260</code>
<adv>1</adv>
<text>Secondary Network Interface: Setup Secondary Network Interface</text>
</codeEntry>
<codeEntry>
<code>261</code>
<adv>1</adv>
<text>Primary Network Interface: Setup Primary Network Interface</text>
</codeEntry>
</systemChannels>
<systemAddresses/>
<deviceIDs>
<deviceID>329</deviceID>
<deviceID>274</deviceID>
<deviceID>327</deviceID>
<deviceID>332</deviceID>
<deviceID>333</deviceID>
<deviceID>334</deviceID>
<deviceID>343</deviceID>
<deviceID>378</deviceID>
<deviceID>379</deviceID>
</deviceIDs>
</panelEntry> -
We do not encourage or recommend editing the PPF.XML file without understanding you may break things in TPDesign4 as a result. Also, any changes you make are likely to be overwritten when updating TPDesign4, G4SupportFiles, or TPTransfer as each application edits/replaces sections within the PPF.XML as well as other resources.
Importantly, TPControl is TP4 file agnostic. That means, you can transfer ANY TP4 file created under any template/resolution to TPControl. So, you can simply send the 2000XL TP4 file to TPControl and if required use the 'Screen Resize' options in TPControl Settings to adjust to suit.
Also, 1920x1080 is available under the 'Windows (TPC)' TPDesign4 file templates, if you would like to use it.
Hope this helps. -
I agree, small errors will break the definition. Save a clean copy and make a backup of your edited copy if it works. A new install of nearly anything related to TPTRANSFER or TPD4 may overwrite your custom file.
The main reason to take your chances and do this is to support an Android of odd size - there are so many different resolutions in the Android family of devices. There is a marked loss of speed when SCALING or STRETCHING is turned on, especially with the Android TPC app that is slower than the iOS to begin with. Making a native size project is a way to preserve whatever speed you can. (Don't use visual effects like fade either, they eat speed like candy on the Android.)
Worth the risks, but yes, be sure you know what you are doing, test, back up old and new files, and leave yourself a way to recover. -
I have actually already converted a 2000XL file into a Win8 1920x1080 version and was using that to test on my PC. I never tried loading it into the android version. (I'll have to return my hacker license now).
FYI for anyone interested:
I assigned the 1920x1080 tpc win8 file to an android device and it loaded and looks fine.
I assigned a standard 2000XL (1920x800) file and it also loads just fine (with black bars on top and bottom).
The Win8 TPC app installs on the intel desktop version of windows, so now we have an "xpanel" of our own. -
Cool, thanks for the update Greg. No need to turn your hackers license in just yet
Leave a Comment
Categories
- All Categories
- 2.5K AMX General Discussion
- 922 AMX Technical Discussion
- 514 AMX Hardware
- 502 AMX Control Products
- 3 AMX Video Distribution Products
- 9 AMX Networked AV (SVSI) Products
- AMX Workspace & Collaboration Products
- 3.4K AMX Software
- 151 AMX Resource Management Suite Software
- 386 AMX Design Tools
- 2.4K NetLinx Studio
- 135 Duet/Cafe Duet
- 248 NetLinx Modules & Duet Modules
- 57 AMX RPM Forum
- 228 MODPEDIA - The Public Repository of Modules for Everyone
- 943 AMX Specialty Forums
- 2.6K AMXForums Archive
- 2.6K AMXForums Archive Threads
- 1.5K AMX Hardware
- 432 AMX Applications and Solutions
- 249 Residential Forum
- 182 Tips and Tricks
- 146 AMX Website/Forums