Zinwell NextGen TV Box + Encoder + ah4c = Success (But What About HDR?)

OK, so you're saying your original bmitune.sh (the script I was trying to clean-up to add to the next build of ah4c) doesn't actually work? And of course, if that's true, my cleaned-up version won't work either.

Does the script you posted most recently work correctly? If so, I have another tuneChannel function we can use that will duplicate that -- but do it in a fashion where additional channels can be added to the M3U without needing to modify the bmitune.sh script.

1 Like

I fixed the {{.IPADDRESS}} in the m3u thanks to your help however the port was wrong it should be 7654 not 7664 for the m3u. I would like to see how we could simplify the tunechannel() stuff since like I said you need to input the keycodes manually for 2 digits or more (you can also do this for 1 digit channels).

{{ .IPADDRESS }} needs to have a space as shown between each inside curly brace. Your version above doesn't have that.

Here's an example of a tuneChannel() function, that takes channel numbers with multiple digits, and sends each digit as an individual keyevent:

 tuneChannel() {
  for (( digit=0; digit<${#channelID}; digit++ )); do
    keypress=${channelID:$digit:1}
    $adbTarget shell input keyevent KEYCODE_$keypress
  done
}

The port number can be whatever you want it to be. It's 7654 INSIDE the container, but that can be 7664 or whatever on your host computer. The port you want to use OUTSIDE the container is defined by HOST_PORT in your Portainer-Stack variables. The value you use there should be reflected in your IPADDRESS value which contains both the hostname (or IP address), and the port you chose to use.

I have 3 ah4c containers running on ports 7654, 7664 and 7674.

Just got this working. Thanks for all of your hard work. I had to modify bmitune.sh and zinwell.m3u. my files are below. Again, thanks for all of your hard work.

#!/bin/bash
# bmitune.sh for zinwell/livetv
# 2025.01.26

#Debug on if uncommented
set -x

#Global
channelID="$1"
streamerIP="$2"
adbTarget="adb -s $streamerIP"

#Trap end of script run
finish() {
  echo "bmitune.sh is exiting for $streamerIP with exit code $?"
}

trap finish EXIT

#Tuning is based on channel number values from zinwell.m3u

tuneChannel() {
  for (( i=0; i<${#channelID}; i++ )); do
    keypress="${channelID:$i:1}"
    $adbTarget shell input keyevent KEYCODE_$keypress
    sleep 2
  done

  $adbTarget shell input keyevent KEYCODE_DPAD_CENTER


}

main() {
  tuneChannel
}

main

#EXTM3U

#EXTINF:-1 channel-id="102.1" channel-number="" tvc-guide-stationid="" tvg-group="" tvg-logo="",CBS 2 NEXTGENTV
http://{{ .IPADDRESS }}/play/tuner/02-1

#EXTINF:-1 channel-id="104.1" channel-number="" tvc-guide-stationid="" tvg-group="" tvg-logo="",NBC 4 NEXTGENTV
http://{{ .IPADDRESS }}/play/tuner/04-1

#EXTINF:-1 channel-id="147.1" channel-number="" tvc-guide-stationid="" tvg-group="" tvg-logo="",WNJU 47 NEXTGENTV
http://{{ .IPADDRESS }}/play/tuner/47-1
1 Like

Hmmm. Now I need to see if this could work with the (piece of junk) GTMedia X1. I picked one up for a song, as a failsafe. I would love to have this working in channels.

How has your encoder handled HDR? Too many of the stations near me have gone faux HDR.

1 Like

No problem. Congrats to you for pulling this post out of obscurity! I went back and forth with the OP for a couple of days back in January to put this together, but he never closed the loop on it. I had no idea if it was working or abandoned. Turns out what we had was just a couple of minor tweaks away.

Thanks for posting the updated script, and I'll add this to a fresh ah4c build shortly. For anyone that wants to give this a try, Project One-Click is the easiest way, if you have OliveTin-for-Channels installed (be sure you're using the latest OliveTin Docker Compose, and have the most recent version of the container).

Otherwise, there's a Docker Compose available in the usual place:

New bnhf/ah4c:latest (aka bnhf/ah4c:2025.09.23) pushed this morning with updates to scripts/zinwell/livetv and zinwell.m3u.

Just tried your bmitune.sh it works great. also tweaked my m3u a little the dashes were not needed

see below:

#EXTM3U

#EXTINF:-1 channel-id="102.1" channel-number="" tvc-guide-stationid="" tvg-group="" tvg-logo="",CBS 2 NEXTGENTV
http://{{ .IPADDRESS }}/play/tuner/021

#EXTINF:-1 channel-id="104.1" channel-number="" tvc-guide-stationid="" tvg-group="" tvg-logo="",NBC 4 NEXTGENTV
http://{{ .IPADDRESS }}/play/tuner/041

#EXTINF:-1 channel-id="147.1" channel-number="" tvc-guide-stationid="" tvg-group="" tvg-logo="",WNJU 47 NEXTGENTV
http://{{ .IPADDRESS }}/play/tuner/471

Picture quality is not as good as my hdhomeruns or adbtuner so I would appreciate it if there is somethning we can do about that.

Screenshot below from vlc

Also the bitrate is much lower in channels than what I have set on my linkpi

1 Like

ah4c is just a proxy, so the stream Channels is getting is what your encoder is putting out. Check the settings on your encoder, but maybe this is the HDR issue previously discussed in the ADBTuner thread?

1 Like

I switched my linkpi to cbr and upped the contrast. looks much better on cbs. nbc still looks dark screenshot below

That looks like HDR, at least on NBC, and probably both channels. ah4c does have the capability to pipe a stream through its included ffmpeg, but the resource requirements for the ah4c container will go from basically nothing to an unknown something (if you follow what I mean). The idea would be to tone map HDR to SDR.

It may also be possible to use Intel Quick Sync, but that's untested, and of course you'd need an Intel GPU. I don't get the slightest whiff of a TV signal here in the mountains, so it'd be up to you to get things setup and to do the testing. This all assumes that your Docker host computer isn't the usual low-end, outdated gear so many use. :slight_smile:

I should also mention adb does not work on wifi, it requires ethernet.

1 Like

I actually have an nvidia gpu. how would I do this? thanks

I believe this has mostly been used by people capturing from internal cards, but I remember somebody awhile back using it with an encoder -- however, I can't find that thread atm.

Right now, you're using env vars like:

TUNERx_IP=
ENCODERx_URL=

For each virtual tuner. This would change to:

TUNERx_IP=
ENCODERx_URL=
CMDx_DEVICE=
CMDx=

If this works the way I think it should (it's not something I've needed myself), you'd leave ENCODERx_URL blank, and put that value in CMDx_DEVICE. Then, your ffmpeg command would go in CMDx.

You can look at the sullrich/ah4c repo for some specific examples using encoder/capture cards.

Keeping the current structure of the ah4c Docker Compose, you'd add the following (one for each tuner, with their actual numbers like: 1, 2, 3, 4) in the environment: section of the compose, and the above values would go in the Environment variables section of the Portainer-Stacks Editor:

- CMD1=${CMD1}
- CMD1_DEVICE=${CMD1_DEVICE}

I'd start with some really simple ffmpeg command, that would allow you to confirm it's working and get a feel for the performance hit.

EDIT: It's possible you leave the ENCODERx_URL value as is, leave CMDx_DEVICE blank, and just put your ffmpeg command in CMDx. Try it that way first. This post, and a few after it, are the ones I was thinking of:

getting the following error:

[ERR] Failed to run command exec: ""ffmpeg": executable file not found in $PATH

I added the following to my stack:

  - CMD1_DEVICE=
  - CMD1="ffmpeg -i http://192.168.1.70:8090/stream0 -c:v h264_nvenc -vf yadif=0:-1:1,hqdn3d,flags=lanczos -c:a copy -f mpegts -"

Probably something to do with the shell running ffmpeg not inheriting the $PATH, because ffmpeg is there and it's on the path.

Try: /usr/bin/ffmpeg

EDIT: Or, try losing the double quotes...

noe I get the following:

[ERR] Failed to run command fork/exec "/usr/bin/ffmpeg: no such file or directory

Did you try :point_up:

now I get:

[EXECUTE] Stderr: '+ channelID=471

Worked for me, using an ffmpeg command to send a blank screen for 5 seconds. Here's the Docker Compose, and the env vars I used:

 services:
  ah4c: # This docker-compose typically requires no editing. Use the Environment variables section of Portainer to set your values.
    # 2025.09.13
    # GitHub home for this project: https://github.com/bnhf/ah4c.
    # Docker container home for this project with setup instructions: https://hub.docker.com/r/bnhf/ah4c.
    image: bnhf/ah4c:${TAG:-latest}
    container_name: ${CONTAINER_NAME:-ah4c}
    hostname: ${HOSTNAME:-ah4c}
    dns_search: ${DOMAIN:-localdomain} # Specify the name of your LAN's domain, usually local or localdomain
    ports:
      - ${ADBS_PORT:-5037}:5037 # Port used by adb-server
      - ${HOST_PORT:-7654}:7654 # Port used by this ah4c proxy
      - ${SCRC_PORT:-7655}:8000 # Port used by ws-scrcpy
    environment:
      - IPADDRESS=${IPADDRESS} # Hostname or IP address of this ah4c extension to be used in M3U file (also add port number if not in M3U)
      - NUMBER_TUNERS=${NUMBER_TUNERS} # Number of tuners you'd like defined 1, 2, 3 or 4 supported
      - TUNER1_IP=${TUNER1_IP} # Streaming device #1 with adb port in the form hostname:port or ip:port
      - TUNER2_IP=${TUNER2_IP} # Streaming device #2 with adb port in the form hostname:port or ip:port
      - TUNER3_IP=${TUNER3_IP} # Streaming device #3 with adb port in the form hostname:port or ip:port
      - TUNER4_IP=${TUNER4_IP} # Streaming device #4 with adb port in the form hostname:port or ip:port
      - TUNER5_IP=${TUNER5_IP} # Streaming device #5 with adb port in the form hostname:port or ip:port
      - TUNER6_IP=${TUNER6_IP} # Streaming device #6 with adb port in the form hostname:port or ip:port
      - TUNER7_IP=${TUNER7_IP} # Streaming device #7 with adb port in the form hostname:port or ip:port
      - TUNER8_IP=${TUNER8_IP} # Streaming device #8 with adb port in the form hostname:port or ip:port
      - TUNER9_IP=${TUNER9_IP} # Streaming device #9 with adb port in the form hostname:port or ip:port
      - ENCODER1_URL=${ENCODER1_URL} # Full URL for tuner #1 in the form http://hostname/stream or http://ip/stream
      - ENCODER2_URL=${ENCODER2_URL} # Full URL for tuner #2 in the form http://hostname/stream or http://ip/stream
      - ENCODER3_URL=${ENCODER3_URL} # Full URL for tuner #3 in the form http://hostname/stream or http://ip/stream
      - ENCODER4_URL=${ENCODER4_URL} # Full URL for tuner #4 in the form http://hostname/stream or http://ip/stream
      - ENCODER5_URL=${ENCODER5_URL} # Full URL for tuner #5 in the form http://hostname/stream or http://ip/stream
      - ENCODER6_URL=${ENCODER6_URL} # Full URL for tuner #6 in the form http://hostname/stream or http://ip/stream
      - ENCODER7_URL=${ENCODER7_URL} # Full URL for tuner #7 in the form http://hostname/stream or http://ip/stream
      - ENCODER8_URL=${ENCODER8_URL} # Full URL for tuner #8 in the form http://hostname/stream or http://ip/stream
      - ENCODER9_URL=${ENCODER9_URL} # Full URL for tuner #9 in the form http://hostname/stream or http://ip/stream
      - CMD1=${CMD1} # Typically used for ffmpeg processing of a device's stream
      - CMD2=${CMD2} # Typically used for ffmpeg processing of a device's stream
      - STREAMER_APP=${STREAMER_APP} # Streaming device name and streaming app you're using in the form scripts/streamer/app (use lowercase with slashes between as shown)
      - CHANNELSIP=${CHANNELSIP} # Hostname or IP address of the Channels DVR server itself
      - ALERT_SMTP_SERVER=${ALERT_SMTP_SERVER} # The domainname:port of the SMTP server you'll be using like smtp.gmail.com:587. This is for sending ah4c alerts if tuning fails.
      - ALERT_AUTH_SERVER=${ALERT_AUTH_SERVER} # The auth server for the e-mail you'll be using like smtp.gmail.com
      - ALERT_EMAIL_FROM=${ALERT_EMAIL_FROM} # The e-mail address you'd like your ah4c failure alert e-mails to show as being from.
      - ALERT_EMAIL_PASS=${ALERT_EMAIL_PASS} # Gmail and Yahoo both support the creation of app-specific e-mail passwords, and this is the way to go! It's NOT recommended to use your everyday e-mail password.
      - ALERT_EMAIL_TO=${ALERT_EMAIL_TO} # The e-mail address you'd like your alert e-mails sent to.
      #- ALERT_WEBHOOK_URL=""
      - LIVETV_ATTEMPTS=${LIVETV_ATTEMPTS} # For FireTV Live Guide tuning only, set maximum number of attempts at finding the desired channel
      - CREATE_M3US=${CREATE_M3US:-false} # Set to true to create device-specific M3Us for use with Amazon Prime Premium channels -- requires a FireTV device
      - UPDATE_SCRIPTS=${UPDATE_SCRIPTS:-true} # Set to true if you'd like the sample scripts and STREAMER_APP scripts updated whether they exist of not
      - UPDATE_M3US=${UPDATE_M3US:-true} # Set to true if you'd like the sample m3us updated whether they exist of not
      - TZ=${TZ} # Your local timezone in Linux "tz" format
      - SPEED_MODE=${SPEED_MODE:-false} # Set to false if you'd like the target streaming app to be closed after each tuning cycle (limited script support).
      - KEEP_WATCHING=${KEEP_WATCHING:-235m} # In supported scripts, set the delay before resending a tuning deeplink to prevent "Are you still watching?" type messages. Examples: Use 4h for 4 hours or 240m for 240 minutes.
      - AUTOCROP_CHANNELS=${AUTOCROP_CHANNELS} # Space separated list of channels (by number) with black borders on 4 sides to autocrop while maintaining aspect ratio. Requires LinkPi Encoder! 
      - LINKPI_HOSTNAME=${LINKPI_HOSTNAME} # Hostname or IP address of your LinkPi encoder. For use with AUTOCROP_CHANNELS.
      - LINKPI_USERNAME=${LINKPI_USERNAME} # LinkPi username. For use with AUTOCROP_CHANNELS.
      - LINKPI_PASSWORD=${LINKPI_PASSWORD} # LinkPi password. For use with AUTOCROP_CHANNELS.
      - USER_SCRIPT=${USER_SCRIPT} # A custom user script to be run at container start. If placed in /HOST_DIR/olivetin, only the script name is required, like ./userscript.sh
    volumes:
      - ${HOST_DIR:-/data}/ah4c/scripts:/opt/scripts # pre/stop/bmitune.sh scripts will be stored in this bound host directory under streamer/app
      - ${HOST_DIR:-/data}/ah4c/m3u:/opt/m3u # m3u files will be stored here and hosted at http://<hostname or ip>:7654/m3u for use in Channels DVR - Custom Channels settings
      - ${HOST_DIR:-/data}/ah4c/adb:/root/.android # Persistent data directory for adb keys
    restart: unless-stopped

As always, I don't recommend editing the compose directly, but rather put the env vars (which are unique to you, in the section designed for that in the Portainer-Stacks Editor). Here are mine:

TAG=latest
CONTAINER_NAME=ah4c
HOSTNAME=ah4c
DOMAIN=localdomain tailxxxxx.ts.net
ADBS_PORT=5037
HOST_PORT=7654
SCRC_PORT=7655
IPADDRESS=htpc6:7654
NUMBER_TUNERS=2
TUNER1_IP=firestick-rack1:5555
ENCODER1_URL=http://encoder_48007/0.ts
CMD1=ffmpeg -i ${ENCODER1_URL} -ss 5 -c:v copy -c:a copy -f mpegts -
TUNER2_IP=firestick-rack2:5555
ENCODER2_URL=http://encoder_48007/4.ts
CMD2=ffmpeg -i ${ENCODER2_URL} -ss 5 -c:v copy -c:a copy -f mpegts -
STREAMER_APP=scripts/firetv/channels
CHANNELSIP=media-server8
ALERT_SMTP_SERVER=smtp.gmail.com:587
ALERT_AUTH_SERVER=smtp.gmail.com
ALERT_EMAIL_FROM=[Redacted]
ALERT_EMAIL_PASS=[Redacted]
ALERT_EMAIL_TO=[Redacted]
LIVETV_ATTEMPTS=
CREATE_M3US=false
UPDATE_SCRIPTS=false
UPDATE_M3US=false
TZ=US/Mountain
SPEED_MODE=false
KEEP_WATCHING=235m
AUTOCROP_CHANNELS=
LINKPI_HOSTNAME=[Redacted]
LINKPI_USERNAME=[Redacted]
LINKPI_PASSWORD=[Redacted]
USER_SCRIPT=
HOST_DIR=/data
CDVR_M3U_NAME=channels.m3u

This way you can easily swap out an old compose for new, or share it with someone else.

EDIT: Once you get this running, you'll probably want to reduce the output to the Portainer logs, or they'll be flooded.

I'd suggest trying:

-loglevel quiet

between the ffmpeg and the -i

1 Like