OliveTin for Channels: An Interface for Misc Channels DVR Scripts & Tricks

[bnhf]

@chDVRuser

Now we just need you to create a site map (links to all your OliveTin for Channels Projects).
An OliveTin for Channels projects directory.
I always find myself searching for them since they aren't in one category here.

So you're thinking of a single post, with links to the threads that inspired each of the OliveTin-for-Channels Actions?

[bnhf]

New bnhf/olivetin:latest (aka bnhf/olivetin:2025.09.03) pushed this morning with Project One-Click support for the new Roku-Channels-Bridge. More details here:

Roku Tuner Bridge Official Release

Hey everyone, I'm excited to share a project I've been working on: Roku Tuner Bridge. This is a Dockerized application that lets you integrate your Roku devices as tuners within the Channels DVR software. It allows you to use streaming service channels from apps like YouTube TV, Philo, and others, just like traditional cable channels inside the Channels app. Key Features: Seamless Integration: Adds Roku-based channels directly into your Channels DVR guide. Dual M3U Support: Generates …

[chDVRuser]

@bnhf

So you're thinking of a single post, with links to the threads that inspired each of the OliveTin-for-Channels Actions?

I was thinking of a single (locked) post with links to all of your Olive-Tin for Channels projects.
Like these (I usually have to search, so not sure this is a complete list)

A docker-compose for every Channels-related extension – suitable for Portainer-Stacks!
Comskip Related: A Set of OliveTin-for-Channels Actions with Their Own Dashboard
OliveTin EZ-Start: A New Way to Deploy OliveTin-for-Channels Using Just Two Environment Variables to Get Started!
OliveTin EZ-Start: The Next Generation. Deploy OliveTin-for-Channels from the Command Line without the Need for Portainer to be Installed in Advance!
OliveTin for Channels: An Interface for Misc Channels DVR Scripts & Tricks
Project One-Click: All-in-One Installations of Docker Extensions and CDVR Custom Channels
Using OliveTin to Host YouTube Live Channel URLs Based on the Kister Method
Using OliveTin with TubeArchivist plus CDVR/TA Processing Script

[bnhf]

New bnhf/olivetin:latest (aka bnhf/olivetin:2025.09.06) pushed today with Project One-Click support for the nostalgic WeatherStar 4000+ via cc4c. More details here:

WeatherStar 4000

I've added the above to OliveTin-for-Channels' Project One-Click. Fill-in a few fields and click -- the container is downloaded, the Portainer Stack configured and the CDVR Custom Channels Source created! [screenshot-htpc6-2025-09-06-16-04-54] [screenshot-htpc6-2025-09-06-16-05-14]

[bnhf]

@chDVRuser

I would have remuxed it with ffmpeg instead of using fix timestamps.
When you run fix timestamps, it overwrites your original recording.
Before running fix timestamps, you should make a copy of the recording in case it makes it worse (based on experience).

What would you think about this process becoming an OliveTin Action?

Maybe start with the FileID, then make a backup, followed by remuxing with ffmpeg -- or something along those lines? The Action could make the backup by FileID regardless, and then offer the ffmpeg remux as an option?

[chDVRuser]

Not sure if it would be used enough to warrant an OliveTin Action.

I just use a simple script (Windows cmd file) that runs an ffmpeg remux against the recording (logging the ffmpeg output) and saves it as a .ts file (which is really what CDVR records to), optionally in the same directory as the recording. That way I can check the remux to see if it fixed it, and if so I move it over the original recording, replacing the recorded.mpg.

To do that, I drag and drop the recording on this Windows cmd file which exists on a local drive

ffmpeg_remux.cmd

@ECHO OFF
ECHO ...
IF %1.==. GOTO USAGE
REM Change current working directory to where this command script resides
%~d0
CD %~p0
REM Use your ffmpeg.exe to remux the recording to a new .ts file in the current directory
REM and redirect standard and error output to originalfilename_remux_log.txt
ECHO Remuxing %1
ffmpeg -ignore_unknown -i %1 -map 0 -acodec copy -vcodec copy -scodec copy "%~dp0%~n1.ts" > "%~n1_remux_log.txt" 2>&1
ECHO Remuxed %1
ECHO to file "%~dp0%~n1.ts"
ECHO Press Ctrl-C to keep remuxed file here, or to move it to the original directory
PAUSE
REM Move the remuxed file.ts so as not to overwrite the original.mpg
MOVE /Y "%~dp0%~n1.ts" "%~dp1"
GOTO FINISHED

:USAGE
REM Need the fully qualified filename.mpg to remux
ECHO Drop the file to be remuxed on this command file

:FINISHED
PAUSE
EXIT

[KineticMan]

did i miss a step?

[bnhf]

@KineticMan

did i miss a step?

No -- that's a me problem. I dropped the weatherstar4k files into the wrong build folder. I guess you're the first one to try it in production. I'll have a new version pushed shortly...

EDIT: It's built -- re-pull and redeploy and you should be good.

[KineticMan]

Thanks!

I still follow the directions to vnc into the server after one click?

[bnhf]

@KineticMan

I still follow the directions to vnc into the server after one click?

Yes.

[mexicanmamba]

Its been so long but how am I able to update Olivetin for Channels?

[bnhf]

New bnhf/olivetin:latest (aka bnhf/olivetin:2025.11.23) pushed today with Project One-Click support for ESPN4cc4c, ESPN4ch4c and ESPN4adbt. All three can be run simultaneously.

More details here:

ESPN+ with Custom Channels via ADBTuner

New bnhf/olivetin:latest (aka bnhf/olivetin:2025.11.23) pushed today with support for both spinning-up an ESPN4cc4c stack, and also adding however many ADBTuner ESPN virtual channels (aka lanes) desired. Both cc4c and ch4c are supported, and can be run side-by-side. The Action that creates x number of ESPN+ lanes in ADBTuner (which needs to match the number of lanes configured in the ESPN4cc4c stack), will also create an espn4adbt CDVR Custom Channels Source. Plus, the Action will delete any p…

[bnhf]

@mexicanmamba

Its been so long but how am I able to update Olivetin for Channels?

Stop the olivetin stack, go into the Portainer-Stacks Editor, and look for the Update the stack button. Use the Re-pull and redeploy slider after clicking the button.

[mackid1993]

Hey, just curious if anyone has a good guide to get this going on Unraid.

[bnhf]

@mackid1993

Hey, just curious if anyone has a good guide to get this going on Unraid.

I know there are at least a couple of people that have OliveTin-for-Channels running on Unraid, but nobody's written the process up.

Here are a couple of things to keep in mind:

• OliveTin-for-Channels requires Portainer -- so be sure you're comfortable with getting Portainer installed and running.

• A fully functioning OliveTin installation requires access to CVDR executables and recordings directories. If both are on the Unraid server, and you know their paths -- you should be good.

Other than that, if you understand at least basic concepts about Docker and Docker Compose it's not overly difficult.

[mackid1993]

Thanks, yeah, I was able to get it running with Portainer on Unraid!
I didn't realize that Portainer was required now that I know that it was pretty easy to get up and running!!

[kleywelsh]

I followed the above method for updating Olivetin and got this message:

Failed to pull images of the stack: compose pull operation failed: failed to create compose project: failed to load the compose file : decoding failed due to the following error(s): 'services[olivetin].environment' environment variable is declared with a trailing space

I am using Portainer (CE) 2.33.5 LTS. I stopped it only in Portainer. Should I have done something within Docker?

Any thoughts?

[bnhf]

@kleywelsh

Any thoughts?

Try the Docker Compose here:

A docker-compose for every Channels-related extension -- suitable for Portainer-Stacks!

I've just updated my docker-compose examples, in OliveTin-for-Channels, for the many excellent container projects that are suitable for use with Channels -- via the WebUI for Docker -- Portainer. I thought I'd post them here as well, for anyone not using OliveTin yet. The idea with the way these yamls are structured, is that you shouldn't need to do ANY editing of the yaml itself, all installation specific values should be set via the environment variables in that section of Port…

I believe the one in post #1 here is outdated. If the newer one works, confirm back here and I'll update it in this thread too...

[kleywelsh]

@bnhf

Stop the olivetin stack, go into the Portainer-Stacks Editor, and look for the Update the stack button. Use the Re-pull and redeploy slider after clicking the button.

This is the one that I tried. Should I try to other one? I stopped the olivetin stack on in Portainer not docker.

[bnhf]

@kleywelsh

This is the one that I tried. Should I try to other one? I stopped the olivetin stack on in Portainer not docker.

The post you referenced was regarding updating the olivetin container. The error you're seeing indicates the Docker Compose you're using is out of date.

Stop the stack in Portainer, and replace your current compose with the updated one I linked in my last post. You should also confirm the env vars you're using are up-to-date.