Is there any way to get it to ignore the stable channel number data and renumber all of the channels in a feed afresh?
1 Like
Not sure I understand your question
1 Like
I'm not sure how to say it more clearly...
I would like to be able to renumber the channels in a feed, starting with a specified channel number, with no attempt to keep the channel numbers stable.
I had a feed that started at 20000. I tried to change the starting channel number to 30000. Most of the channels retained the numbers in the 20000 range.
If you want to create a fail-safe scenario for important channels, you can enable more than one, add them to different feeds/sources, and adjust the priority of each source in CDVR.
1 Like
Ahh. I have a “sticky” feature in there that when you changed the feed number start, it probably only affected any new channel added to it.
Couple options you have:
- delete feed and remake it
- on CDVR, set the custom source to ignore channel number and have CDVR assign the channum
My own personal scrape of vidaa gives nearly 800 channels...
Are you filtering the non US/CA regions?
looks like I can add more regions. will add to config next version.
1 Like
I think the api returns over 1400+ but they need lot of filtering and tweaking, to correctly put them in the right countrys and languages etc, Also a lot of dupes plus drmed dash ones..
you can compare with https://www.apsattv.com/vidaa.m3u
Yeah. That was what I referred to as "stable channel numbers". It would be nice to have a Renumber button to override the "sticky" feature one time.
Thanks for mentioning this, this was first I’ve heard of Dockwatch, I installed this morning and can already see how much of an upgrade this is over watchtower for managing container updates, and it offers a whole lot more. Much appreciated!
1 Like
Same with SamsungTV Plus unfortunately, the recommended 360 minute scraping interval isn't cutting it for me, those channels haven't been consistently populated in the guide. More usually they've been empty. I'm experimenting down to 60 or 120 minutes instead. Anyone else?
What do I learn from the "ch#" column of the channel list?
I ask because the channel list has become rather crowded and I don't understand what purpose this mostly-empty column serves. Maybe it serves some purpose if you don't specify starting channel numbers for your feeds.
The best one thus far for EPG horizon has been one of the newest ones (TCL). Here's a little chart:
| Scraper | Code Horizon | Actual DB Horizon | DB Programs | Scrape Interval | Status | Notes |
|---|---|---|---|---|---|---|
| TCL TV+ | 7 days | 7.0d | 83,163 | 12h | enabled | Matches exactly |
| Stirr | API-dictated | 37.3d | 31,850 | 6h | enabled | Far-future events (sports/specials) inflate MAX end_time; typical depth unknown |
| Free Live Sports | API-dictated | 7.4d | 11,610 | 6h | enabled | API returns ~1 week |
| Distro TV | 24 hours | 5.6d | 6,301 | 12h | enabled | API gives more than now,24h implies; old rows accumulate without purge before re-scrape |
| Plex | ~3 days | 2.5d | 16,863 | 3h | enabled | Slightly under expected; consistent |
| Xumo Play | ~2 days forward | 1.5d | 17,188 | 12h | enabled | Close to expected |
| Tubi | API-dictated | 1.4d | 7,468 | 6h | enabled | API returns ~34h |
| Pluto TV | ~36 hours | 1.3d | 11,773 | 6h | enabled | Scraped 4h ago -> ~35h from scrape time (consistent) |
| Local Now | ~few hours (5 progs) | 22.6h | 2,842 | 1h | enabled | 5 programs x hourly scraping stacks to ~22h accumulated coverage |
| Vizio WatchFree+ | 24 hours | 11.6h | 5,219 | 6h | enabled | API returns less than requested; ~15.6h from scrape time |
| Samsung TV Plus | Mirror-dictated | 10.6h | 4,898 | 6h | enabled | XMLTV mirror file covers only current day/night portion |
| LG Channels | API-dictated (short) | 10.6h | 1,789 | 3h | enabled | Scraped 2.3h ago -> ~13h from scrape; consistent with fairly short description |
| Roku | Now/next only | 10.6h | 4,123 | 1h | enabled | Better than expected; linearSchedule carries ~11.5h from scrape time |
3 Likes
It's just the Chan-Num for the channel in the default feed... I added it for those that refused to use Feeds.
I don't love it either, but some asked for it.
1 Like
I'm not certain that there is anything to be "learned" from the ch# column. Initially, it seems that to identify the current channel number assigned in the default feed.
More importantly, for those of us who prefer to assign specific channel numbers to specific channels, you can enter a number of your choosing and it will persist in your own custom feeds.
Manually selected "sticky" channels numbers are identified with the "padlock" symbol as in the far right of this example.
Since Channels DVR won't actually refresh sources XMLTV at different intervals (even though set different, verified by checking DVR log), I set all my Channels DVR sources using XMLTV to refresh every hour. And do the same in FastChannels.
1 Like
@Fofer I searched this thread for FilmRise and didn't see any other posts other than this small section so just asking if you were able to get the guide data to sync up? If so, what did you end up doing? I'm in the Eastern Time Zone.
No, I came to the conclusion that a mere time-shift of the guide wouldn't fix the issue, because I tried a few experiments over the course of a few days, and the sequence of the concerts being broadcast wasn't matching up with any sequence in the guide, many days before or after. I think @chDVRuser has it right on this particular FAST channel:
Then I remembered I still have Qello Concerts, and my own collection of concert files set up as Virtual Channels, so I moved on, with enough music concert content to enjoy.
Further help from @chDVRuser was this great suggestion though. I haven't tried it myself yet, but it looks great, involves Prismcast or similar:
Sorry, but here is another suggestion. I can't stop myself...
It would be nice if the channel preview modal were to include an indication of how much scraped guide data is available for the channel. Either hours or number of programs would suffice.
This information is already presented in the duplicate helper modal, but in this case, I was trying to choose between two channels that were duplicates but not detected as such. The channel names were sufficiently different that I'm not surprised FastChannels did not recognize them as duplicates.
Gotcha, thanks for the update. I did see @chDVRuser post too and it looked a little too much to research/do at this time. If I do try to work on it in the future I'll post here my progress. Thanks again for the update!