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

[Fofer]

@mjitkop

Thank you. It's always rewarding to know that something I did is actually helpful to others.

I've just tested out your script via OliveTin, and it worked well. Very exciting development, thanks for sharing it. Much appreciated!

[jsfullam]

So, now that our little Mina is fairly stable for the time being, I tested your Channel Collection Tool in Olivetin. That works pretty slick and easy. Thank you!

[cyoungers]

I use the fix thumbnails script in OliveTin and it seems to be working except a small percentage of my videos end up with a black thumbnail.

I assume the script is based on the work by @maddox so maybe I should post the question over there.

Use original YouTube thumbnails on your YouTube video imports

I wrote up a script to easily update an entire Video group full of YouTube videos in order to apply the original YouTube thumbnail to them. It written in Ruby, but could be easily ported to anything else. This is a script to process YouTube videos on Channels DVR Server to apply a nicer thumbnail. This assumes the YouTube ID and Original Date is in the EpisodeTitle of the video. IE, Name of Video_(2022-01-06)_[akZxhhcwkR4]. This should be the case if the filename is Name of Video_(2022-01-06)_…

Any ideas of what is going on here?

[istwok]

@themediaguy, would you mind sharing your script to start Victory Plus? I haven't had a chance to try automating it yet so have been starting it manually. With Victory Plus being on demand and serving multiple teams, I wasn't hopeful there would be a reliable way to start the Stars games.

[cyberskier]

I started getting an error tuning to TWiT quite long ago, and removed it from my collections. Unfortunately, at the time, I didn’t have time to check logs, etc. I’m now sitting down to try to troubleshoot, and the TWiT item in the OliveTin menu is green, but when I go in to kill the process by entering a “0” in the interval box, I get this error:

parse "1": invalid URI for request

OliveTin is pulling in the correct address for my Channels server.

I get that same error no matter what I put in the “Interval” box (4h, etc.), and I can’t get the TWiT box to not be green. There are no other log entires I can see in the OliveTin interface — I have the above message under “Standard Output” and nothing else . I checked for a log file on the server itself and find a TWiT.log, but all it contains is “60000=TWiT Tech Podcast Network”, and it is dated a few weeks ago.

I also have last_activity.log, which is the only log item I see with today’s date, but it only tells me the server version, that there were no changes found in any source, and when the next check is.

Any thoughts on how I can troubleshoot this? Thanks!

[Fofer]

@cyberskier

I started getting an error tuning to TWiT quite long ago,

Yes, FWIW, unfortunately TWiT ended their persistent livestream last year:

TWiT.tv livestream and XMLTV guide data

No more 24/7 livestream from TWiT Details here: Looking for Live Content? Due to costs associated with hardware and software used to provide the TWiT live stream 24/7 to multiple streaming providers, TWiT has made the difficult decision to end its always-on live stream. As of November 13, 2023, we will no longer stream re-runs while not doing live production. We will strive to stream on YouTube as often as possible during live production of some of our shows. If you wish to watch …

They still livestream on a schedule though.

[cyberskier]

Ah, thanks. Any idea how to stop the process in OliveTin? I presume that is why it is persistently green.

[Fofer]

Sorry, I don’t, but I’m sure @bnhf will be able to explain soon

FWIW, even if the YouTube/Twitch livestream is no longer 24/7, the XMLTV converted from their .ics calendar should still load fine. These are separate files.

[bnhf]

@cyberskier

I presume that is why it is persistently green.

0 should kill any active process -- then refresh the page.

[bnhf]

@cyoungers

I assume the script is based on the work by @maddox so maybe I should post the question over there.

Yes. OliveTin is just running the @maddox script.

[cyberskier]

@bnhf

0 should kill any active process -- then refresh the page.

That, in the “Interval” box, gives me the same “parse "1": invalid URI for request” when I run it (click “Start” after putting in the 0) , and the box on the main page remains green after a refresh.

[bnhf]

@cyberskier

That, in the “Interval” box, gives me the same “parse "1": invalid URI for request” when I run it (click “Start” after putting in the 0) , and the box on the main page remains green after a refresh.

OK, I'll check it out when I get home. A couple of driving days ahead before that happens. I'll get back to you.

[bnhf]

@cyberskier

That, in the “Interval” box, gives me the same “parse "1": invalid URI for request” when I run it (click “Start” after putting in the 0) , and the box on the main page remains green after a refresh.

I believe I duplicated what you're seeing:

That's telling you you have an invalid URL for the healthchecks.io "ping". Instead of entering 1 for the healthchecks.io value, you should either leave the default in there which is (this is a dummy value and is equivalent to "none"):

https://hc-ping.com/your_custom_uuid

or your actual healthchecks.io URL (if you set one up). Either way, there has to be a valid URL format in that field, or the "kill" is never processed. You're basically failing at the field validation level, so the script never runs.

[cyberskier]

Thanks. That enabled me to stop the TWiT process. I don't recall ever changing the healthchecks_io field, but putting "https://hc-ping.com/your_custom_uuid" in there let me run it without error, and then a page refresh confirmed it worked. Thanks!

[jaidenc]

Olivetin worked great on my old synology nas but for some reason I can't get it to work on my new model. Unfortunately I deleted the stack in portainer that I had been using after it wouldn't initially work, but I think I set it up how it was before and it still isn't working.

Everything works up until I run the check/try to do anything and I get this.

EDIT:
I had to check to affirm my own sanity and yes, the nas can ping itself from itself.

[bnhf]

@jaidenc

Everything works up until I run the check/try to do anything and I get this.

Try using the Docker internal gateway as your IP address, and see if that makes a difference. So, instead of 192.168.1.2, use 172.17.0.1. This assumes CDVR is running on the same Synology NAS as OliveTin.

[jaidenc]

That was it! Thank you!

[NeilSingerman]

I tried to do a new stack in Portainer extension in Docker the stack option is no longer there any help would be appreciated to fix it I am running on Macos.

Thanks

[bnhf]

@NeilSingerman

I tried to do a new stack in Portainer extension in Docker

The Portainer extension, installed through Docker Desktop, is not the full version. Uninstall that, then from Terminal:

docker run -d -p 8000:8000 -p 9000:9000 -p 9443:9443 --name portainer \
    --restart=always \
    -v /var/run/docker.sock:/var/run/docker.sock \
    -v portainer_data:/data \
    cr.portainer.io/portainer/portainer-ce:latest

[NeilSingerman]

@bnhf

docker run -d -p 8000:8000 -p 9000:9000 -p 9443:9443 --name portainer \
    --restart=always \
    -v /var/run/docker.sock:/var/run/docker.sock \
    -v portainer_data:/data \
    cr.portainer.io/portainer/portainer-ce:latest

Thanks