FastChannels - FAST Channels aggregator/manager

Playground
#2913

FastChannels v5.2.0... big thanks to @bnhf

Bridge / FastChannels Player (ah4c Multi-Tuner + Redesign)

  • Added multi-tuner support: the FastChannels Player bridge can now drive multiple ah4c tuners instead of just one (#41).
  • Redesigned the Bridge settings page. HDMI Capture and ah4c Capture now have separate, clearer sections instead of one combined card.
  • Added a new Tuner Authorization check that verifies each ah4c-configured tuner is reachable and authorized through ADB. It also reports the device’s operating system and auto-sleep status (#42).
  • Added a new Fire TV Device Controls window with:
    • Wake and sleep controls.
    • An Apply Headless Preset button that keeps the screen awake and disables sleep and screen-off timeouts for HDMI capture.
    • An option to restore the device’s previous settings.
  • FastChannels Player now detects when it is running an outdated build and offers a one-click update.
  • Added a post-install health check for Bridge setups (#45).
  • Fixed playback detection on Google TV and Android TV. Previously, it only recognized the Fire OS PlaybackState format.
  • Fixed FastChannels Player detection on multi-user Android devices.
  • Fixed an issue that incorrectly required an encoder URL for ah4c-only setups.
  • Fixed FastChannels Player restarting between ah4c tunes instead of remaining warm.
  • Fixed occasionally incorrect Android bridge feed totals.

DirecTV / Sling

  • Added an option to exclude FAST ad-supported channels from DirecTV and Sling lineups (#46).
  • Fixed DirecTV satellite-only lineup entries appearing even though they cannot be streamed (#48).

TV Everywhere

  • Improved error messages for Xfinity redirect loops and Discovery lookup failures during TV Everywhere authentication.
  • Fixed the FYI TV Everywhere login callback redirect.

Other Scrapers

  • Fixed Tubi failing silently when incorrect credentials were entered. Tubi now requires a valid login and clearly reports authentication failures.
  • Retired the DistroTV scraper following the shutdown of DistroTV.

Admin / Miscellaneous

  • Updated documentation to cover:
    • FAST-channel exclusion behavior.
    • A warning against using Vega OS Fire TV Sticks with FastChannels Player setups.
    • Android TV ADB troubleshooting steps.
  • Cleaned up the README and Docker Compose instructions related to the persistent ADB keys volume mount.
6 Likes
#2914

Anyone who was temporarily using my development build should switch to this at your earliest convenience. Very nice work @KineticMan!

2 Likes
#2915

thankee--

fyi I broke Samsung. pushing quick hotfix 5.2.1. whoops.

#2916

Just pulled http://ghcr.io/kineticman/fastchannels:latest and got v5.2.0, which is tagged latest here Releases · kineticman/FastChannels · GitHub

Did I jump the gun?

#2917

Looks like I need to release 5.2.1. Gimme 30.

2 Likes
#2919

Sounds good. Should I do the update now (to 5.2.0), or will that be 5.2.1 - a bit uncertain of the current status based on today's posts.

#2920

I am running 5.2.1 without issue. I haven't tried the bridge yet. But may this weekend.

1 Like
#2921

5.2.1 is latest and greatest. 5.2.0 had a bug that broke Samsung so I had to push a quick fix.

#2922

Update to latest, which will be 5.2.2 as of today, and be sure to disable both types of sleep on your streaming stick -- using the tools available under the Bridge tab, in the HDMI Capture section.

#2923

You may to push another update too as 5.2.1 failed to include an apk for FastChannels Player

1 Like
#2924

thanks -> fixed.. this APK thing is new to me!

1 Like
#2925

New release?

#2926

no, just added the APK to 5.2.1 ... i gotta remember to attach it everytime

#2927

Still didn't work. This may need a version bump indeed

#2928

sorry everyone. @Jean0987654321 told me i'm dumb.

v5.2.2 released — fixes missing Player APK

If you pulled v5.2.1 and the FastChannels Player install/update button said no APK was available, that's a known bug — the image published without it due to a build-order issue on our end, not anything wrong on your setup.

v5.2.2 is out now and includes the APK correctly, plus:

  • fc_player: no more launcher flash between channel changes (warm-stop fix)
  • Category audit cleanup (25 name overrides, a couple of leftover uncategorized channels fixed)

Just pull the new image and restart:
docker compose pull
docker compose up -d

No config or migration steps needed.

#2929

@KineticMan - just noticed a GUI bug on the Feeds page in v5.2.2:

image
image1089×440 58.9 KB

I can scroll down but not higher; I think it's "New Feed" that is cut off.

#2930

Has anyone had any difficulty in recording channels from the FastChannels Plex source?

For me, nearly every recording (possibly every recording) from my Plex FC source triggers an error in Channels DVR. For instance:

[ERR] Failed to start stream on channel 12005 via M3U-FastChannelsPlex: M3U: Could not fetch playlist from epg.provider.plex.tv: GET: https://epg.provider.plex.tv/library/parts/6a1610bebdf296985fd95603-66ad6025cb5d3b7fb5011c2d/variant.m3u8?x-plex-token=1DsegEgKhN1GT6KxWr9w&x-plex-advertising-identifier=&x-plex-client-identifier=93f848b8-11c8-4169-be2e-c6e0846ac614&x-plex-playback-id=p_a1a7735b-3207-4c08-9e2c-fe80eca49416&x-plex-playback-session-id=&x-plex-session-id=&x-plex-device=Linux&x-plex-device-name=Plex+Mediaverse&x-plex-advertising-donottrack=0&x-plex-drm=&x-plex-model=&x-plex-platform=Chrome&x-plex-platform-version=145.0.0.0&x-plex-product=Plex+Mediaverse&x-plex-device-screen-resolution=&x-plex-device-vendor=&x-plex-version=&x-plex-provider-streaming-start=1789162340&url=108b068615034ded100d6c8ec33e9202-9f4619c086d284e916089e3bdfe4be2ebb8f0646701ce32ab28e76e4b17049cd74b54ee9fcefef4f2f7dc20c4f071bb9177cb5b19e6835d7615efb619cf358c13d49ad4f5793bae280a14389d019554ed29811e95e952d9378587fce59d9b9b4ee6e69119316d7d6147bc4f03a40f8c768471897d9b506db87da37c6908b989c485e74b94691f2cde702e3eee2eedcb2eb32e1e4cd34d67fca119967baf936cd7013fb10b5ad3316a3e31c9ee1f681249ca59d233b0640128086622c3b60176566bf449fe20e93763a718e627aca281cffaa48956ee2a103117b1230c1e61a0989919bbd7ba0aab1f3299dc5b1a45acee820e3fe78d7c1ee34292a4a5a6991fe8474a3c9b201761489e05e6e280d79f894be7509a0da0dafc4d46d8ead86b6c83bedf050967f2131c49f4bdca85667c7b286569b37df57f19f4b439c0b05ac7569fd8166a5bd2344b92ab601746d51d2b1edc21a2a5e15711bf43dc0e1766dbd016ce33b08e6039839e938bf7ea77bd69469f11f7f2481bbd979b9e9bc05813523c26d6e326210e29ebd96799ae61c9486b89493f6a0d5ed908d5ace7e2b84870aef13f9375d5b4166eaa5123d82c444485c68c3e536cc9cc0af9706c5266c06a9332d87306a866bcb9764a9c445614b9a27cd2e7791a564a04bc4ef0699b7a909a5e704f6f7225afc60d9fd0b3f080b24c3e67af9e9b48efdd5cc180a3d61ed40deba65c415a17f1cec27e12a86b414ce7708457bf9ff6c1d6936dbccf0a776f0105f237f9615caf641a2ecdc18af333480a9c47da5010377027002d5f40869ba458552a2276bd67f97b261ec3911e8b5a6a057aee4605d5b3559f38d910e803c2eec427dc6a8761dc538414a4219879ff651e0e7d75bfe8018e163cb2ba664f9da9cf1af59e13c962acb7c4770e0f99fda52934b1572ea065333bdda0f80744e2b1a14549b0aafc354f8e24d8eaa9caaff542e3de00d5a092d277a835047b9765dfc34c423ae5a4a33777357e17f88f2cc1ed86c758e3e8a362f043dc7fd30d41dfae5d48f28b1fe6d00cfa8b68e3eff8df4423e383e38aca4aa694ed330ecfcfde426f516a5cf9e691e7a999ac01da3e2ddcdba22eff0171b49f1fa1c30c650f53d01a9108f48e9411b9fbc93fbfc8c18b56e24e27677c9df54e70941ca598aa67caff4bf047711ad65d358c9df0fbc736fb06762c94a7f6723ebd3026caaa12ab8b8d2746c373de372b710445741e6d5cab1fe964abfe23f032a584d26038d8d8cfcb78f4525f1e9acfd2dc9748621d926a31d61f680438024095488ba741507cbb6de0e04e623f9463f6f8305830fd30aa000be0c1f1709be66a3270556f0f8547e2f86fce70e6e58260943ee76a2c8e7d9e2106c7c159b2966940b7de1873ab3f59b6fc9e62751c087cc1870425884540e30d83f27ad34e9b1bb658d4c340fbdcb9065039485ea2ad4996bfd76f12929eb50dd23e387f870d2f953ab81ee54f72665b227482e8daa472dad0e2b97450d1349f702edd08f1c5c6bcb1b17b5376484318c6844af63f06e38b173a77eb78917fbc00e056a3e100b3d5e05488318890be2b4c3c61864c33016a9c00f2b4e157e3f734bb9981903ac56d9f5694df1291dd0baa1eaa629a702c4f8a00f82562a64da827079d2759ddc40cfe93def54e66bdeef5a06bdf66517de24ebd57cc936846c68697caa3299442ee9900d58b781608bf129389a1e1af65044cb4527f1d71181873bcc6d5b6388417c57d6ad4848fa4a2a44e0dac308c5717c8147376d461c4bf4784d24fef402b689831521ad834c460eae16c2d6c7be8cafeb72ce6f3bd1a4dbf83d13419ca6ed5c6f8c96bdc070af72c2154b077a618fd9d3a26c31097b1e48919d20afb82281aad0769779fa14f324dadd504cef258033ffdccf79f2336760cf06b7f3ba9bca8c4c732c57301639aa152636f851b08d5ce6331ded77ef54dcac38bf4a50446b619550d860a5786afa702eb80f2b0a1283432c4318354fe08d37a504234cba36257bd5f763bd53066d0b28d7a09edf29b179d35b627f7ddc06634ae27ec19d8113671330d6cc56786ac7993ef6428b8c52682de853b1168588d4b6f8b40511754c3f781773103f0a2a502d91560538e3740b72799dfb4601b80ff396ece8f8b9d0c6a6fe50b4a969ede6d039627ca14ca995ea6fdafb6209a66305357ef3d2b0e51f4a004efad742d610ad187d539867b7b921ba07eb49f2b494ebb23e7c23fdabef4faa7279ed2787c32a28c328e56836e4fdf108918ddd0eebf7fa0b76bc09d245433317cfd2fa2dac7e653f13e1afdd552b7f3bfddd8afb64f6e50fabaf9dade8886d84b93b89902022ce55a242074cc6ec95c006fd7d3fff653393a5ebdfe401f2a66c8ba9d4e6eab86ab5d6708e980392773819ba2efa87f70010e37944f31a62b58049d602dd9ecae9125ad1cf6b957461541416dcc48f6dce839a76013df3cb5fd774a87cdbe0a7106d65ccbb5c481c492f593471d1c804558e9cf097e5833b063e0dff461d3867e541897f3367b66e294819dd6646df68b23258ebfb599d45: 429 Too Many Requests

It has been quite some time since I have experienced an error like this one. If I recall correctly, @eric once told me that these very long line errors indicate a problem at the provider level, and not a CDVR issue. So, probably not a FastChannels issue either.

#2931

That 429 Too Many Requests comes directly from the plex server, although no idea why

#2932

Thanks for confirming that my memory isn't failing. :thinking: Things are still in there,:brain: just a bit foggy and slow...

1 Like
#2933

FastChannels gives you so many choices.
I have 1272 channels enabled from 15 different sources and only record from maybe 5 of those channels. Reminds me of my cable sub.

1 Like