DisplayHUB / Knowledge wiki

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
android:encoder [2026/11/17 08:06] – created - external edit 127.0.0.1android:encoder [2026/11/17 19:41] (current) – external edit 127.0.0.1
Line 1: Line 1:
 ====== Android encoder setup ====== ====== Android encoder setup ======
 +**Coming soon. Currently in beta.** [[https://displayhub.us/beta/?app=encoder|Request consideration into the beta program]]. Public APK downloads are paused.
 ===== Capture one HDMI source ===== ===== Capture one HDMI source =====
 Use a dedicated ARM64 Android 8+ device with USB host/OTG and hardware H.264. A hub's HDMI output is not an HDMI capture input. Use a dedicated ARM64 Android 8+ device with USB host/OTG and hardware H.264. A hub's HDMI output is not an HDMI capture input.
Line 5: Line 6:
   - Connect authorized HDMI source -> UVC capture dongle -> hub data port -> Android device.   - Connect authorized HDMI source -> UVC capture dongle -> hub data port -> Android device.
   - Connect the charger to the hub's charging input.   - Connect the charger to the hub's charging input.
-  - Install the signed [[https://displayhub.us/android-encoder/|Encoder APK]].+  - Once invited, install the Encoder app using the private beta instructions.
   - Open DisplayHUB Encoder and grant the required camera, selected audio, notification, and USB permissions.   - Open DisplayHUB Encoder and grant the required camera, selected audio, notification, and USB permissions.
   - Choose Always open DisplayHUB for the capture device when offered.   - Choose Always open DisplayHUB for the capture device when offered.
Line 11: Line 12:
   - Complete setup, then manage at ''http://ENCODER_IP:8080/''.   - Complete setup, then manage at ''http://ENCODER_IP:8080/''.
  
-The controller is discovered on the LAN. Verify its saved address includes '':8081''. Start at 720p30 and 4,000 kbps. Capture starts when the configured app opens; there is no normal browser Start/Stop workflow.+Your one controller per location is discovered on the LAN. Verify its saved address includes '':8081''. Start this input at 1080p30 (Full HD) and approximately 6,000 kbps when supported; lower quality if necessary. Capture starts when the configured app opens; there is no normal browser Start/Stop workflow.
  
 ===== Check before unattended use ===== ===== Check before unattended use =====
Line 17: Line 18:
  
 ===== Supported capabilities ===== ===== Supported capabilities =====
-USB HDMI capture, hardware H.264, AAC/HLS, Opus/WebRTC, and [[:encoder:overlays|layered overlays]] are supported. Capture modes depend on USB and hardware codec capabilities. File/network primary input, SRT, and board-specific maintenance are not Android encoder features. Protected HDMI may not be capturable; no content-protection bypass is provided.+USB HDMI capture, hardware H.264, AAC/HLS, Opus/WebRTC, and [[:encoder:overlays|layered overlays with visual examples]] are supported. Capture modes depend on USB and hardware codec capabilities. File/network primary input, SRT, and board-specific maintenance are not Android encoder features. Protected HDMI may not be capturable; no content-protection bypass is provided. 
 + 
 +{{:screenshots:overlay-example.png?800|Example overlays rendered by the real editor over TV color bars, not applied to the live encoder}}
  
 Normal production updates retain settings and require Android installation approval. [[:encoder:updates|Update details]]. Normal production updates retain settings and require Android installation approval. [[:encoder:updates|Update details]].

Read-only public knowledge base, maintained through the site's deployment files. Powered by DokuWiki. Device and firmware behavior must be qualified on your actual equipment.