DaddyLive, PlutoTV, XUMO, M3U/XMLTV, SamsungTV, Plex, TVGuide interfaces (appliance)

G Kazaroth

Yep, in fact, if you have 0.9.12.11 and look at the top of the log, there should be something in all caps that say something like STOP NAMING THINGS LIKE THAT... lol

john tocher

log file size zero

G Kazaroth

Looks like the Plex channel data at https://i.mjh.nz/Plex/ is hosed up. If you already have the channels imported, don't delete them until the site gets this fixed.

G Kazaroth

Are you talking about the log file that you have disabled, or the system log file that you log to that should never be zero.

john tocher

I am looking for information about naming convention of m3u instances. I guess I am supposed to look for this in a log file instead of the release notes?

G Kazaroth

Outstanding. We already have the issue written and if you are saying you can help write the release notes, that would be awesome. Thank you.

john tocher

lol. to do that I would have to understand what is going on. I don't. Appreciate cabernet. I will just do m3u via other means for now. Thanks.

R W

G Kazaroth is it possible to use the epg files from the newer update on an older update?

G Kazaroth

According to the change log, the EPG database changed in version 0.9.11.x and has not changed since, so the linked files should be cross compatible. They would not be compatible with 0.9.10.x. Versions 0.9.12 had changes to the way the database was provided to the client. The client setting "Use Channel # for Channel ID" significantly improved the correlation issues with Plex, Emby and JellyFin and the what Plex displayed as the channel number in the guide.

R W

G Kazaroth wrote:

> According to the change log, the EPG database changed in version 0.9.11.x and has not changed since, so the linked files should be cross compatible. They would not be compatible with 0.9.10.x. Versions 0.9.12 had changes to the way the database was provided to the client. The client setting "Use Channel # for Channel ID" significantly improved the correlation issues with Plex, Emby and JellyFin and the what Plex displayed as the channel number in the guide.

I changed that setting on Cabernet but I am still getting the Unknown Airing error. But when I add the tuner to Plex and it scans the channels it matches the channels right.

ALso, I'm not seeing in the logs the amount of days of it pulled from the EPG.

R W

This is the log from Plex when I add the tuner and download the EPG data:

Apr 17, 2023 23:56:50.155 [0x7f83b57cbb38] DEBUG - [Req#11d1ee] DVR:Device: Device was alive, refreshed device://tv.plex.grabbers.hdhomerun/1050F2CF.
Apr 17, 2023 23:56:50.155 [0x7f83b57cbb38] DEBUG - [Req#11d1ee] DVR:Device: Testing grabber HDHomerun device device://tv.plex.grabbers.hdhomerun/1058EA0F at http://192.168.69.111:6077 Apr 17, 2023 23:56:50.155 [0x7f83b57cbb38] DEBUG - [Req#11d1ee] DVR:Device: Device device://tv.plex.grabbers.hdhomerun/1058EA0F was already known, refreshing database info
Apr 17, 2023 23:56:50.155 [0x7f83b57cbb38] DEBUG - [Req#11d1ee/HCl#99f1] HTTP requesting GET http://192.168.69.111:6077/discover.json Apr 17, 2023 23:56:50.157 [0x7f83c791eb38] DEBUG - [HttpClient/HCl#99f1] HTTP/1.0 (0.0s) 200 response from GET http://192.168.69.111:6077/discover.json Apr 17, 2023 23:56:50.158 [0x7f83b57cbb38] DEBUG - [Req#11d1ee/HCl#99f2] HTTP requesting GET http://192.168.69.111:6077/lineup_status.json Apr 17, 2023 23:56:50.160 [0x7f83c791eb38] DEBUG - [HttpClient/HCl#99f2] HTTP/1.0 (0.0s) 200 response from GET http://192.168.69.111:6077/lineup_status.json Apr 17, 2023 23:56:51.880 [0x7f83c999ab38] VERBOSE - We didn't receive any data from 192.168.69.4:55530 in time, dropping connection.
Apr 17, 2023 23:56:51.882 [0x7f83c9b9db38] VERBOSE - Didn't receive a request from 192.168.69.4:55530: End of file

G Kazaroth

Well, that has very little info. It has nothing to do with the download of the EPG data and only has to do with Plex detection of the tuner. It really makes no sense to have this data on this forum, so if you really want to resolve this, you need to write an issue in Cabernet and submit a DEBUG log from startup through the successful execution of the EPG scheduled event.

G Kazaroth

0.9.12.14
0.9.12 expected updates are complete. Plan to start work on 0.9.13 next week. Daddylive really tested Cabernet with Connection Refuse and HTTP 500 error codes, but it has made Cabernet more stable. These changes are all in the internalproxy area. Enjoy!

Vic K

works with cabernet-0.9.12.14 ubuntu 22.04

Not sure if this will work on windows or not.

This will get your 486 channels and it will not break channel update or software upgrade features or any other features. EPG should be 4 or less as the added channels epg cause a bug and epg fails.

Software updates will more then likely break the added channels and you might have to do these steps again and possibly need a new version of my udpated files.

1. stop cabernet (must be stopped)
2. copy list.index to ~/plugins_ext/provider_video_daddylive/resources/list.index
3. overwrite channel_list.json to ~/plugins_ext/provider_video_daddylive/resources/channel_list.json
4. overwrite channels.py ~/plugins_ext/provider_video_daddylive/lib/channels.py
5. adjust your config.ini to have epg of 4 or less (if you never configured epg in ui then its default to 2 so no need to do this step)
5. start cabernet

6. If you dont see additiona channels after the steps above it could be due to last refresh of channels being too recent. you can either wait till channel scan happens again or try to initiate it via gui Schedule_task optoin. If you not patient and want it instantly then go to /data/db/channels.db and delete it and restart cabernet.

if you update to new version this might not work but you can try by doing steps above. For example my last mod stopped working after cabernet moved plugins from plugins folder to plugins_ext folder

anders suarz

you guys run cabernet on jellyfin? just curious if epg runs well there.

i can play channels.

G Kazaroth

If you are having issues, take a look at https://github.com/cabernetwork/cabernet/issues/78

Martin Runneals

anders suarz wrote:
> you guys run cabernet on jellyfin? just curious if epg runs well there.
>

> i can play channels.

The guide is working well for DaddyLive. I need to make adjustments to the Pluto EPG refresh intervals..
I did notice for Pluto channels it will go to black for a commercial break and stay black unless I restart the channel. need to figure that out. otherwise it works great with Jellyfin .

Hardcore Jax

hi! Can this program be used with any streaming tv service ?
I can watch live tv from https://www.allente.se/ with my web browser after i login with mymail@mail.com and mypassword
If i press play on a channel and copy the path it looks like this: https://tv.allente.se/channels/5470/tv/asset/live/4091441/svt1-hd So will this app handle the login like chrome if i put the channel links in a m3u or do i need a plugin to do that ?

G Kazaroth

It can provide streaming for any non-DRM based ATSC 1.0 stream (which is almost everything). The M3U plugin does not support authentication unless it is part of the URL (as in https://username:pwd@url/...). The plugin design does support any type of authentication, so you would need to create your own plugin for the type of authentication used. There is currently no support for creating plugins.

G Kazaroth

Cabernet 0.9.13.00-RC1

This is a Release Candidate containing the mux capability to connect multiple clients to a single provider stream. It has no effect on VOD-based channels. Clients tend to believe that streams should be continuous and will cause a restart of the stream, if no data flows for 10 seconds. This reset causes a déjà vu event that backs up the last few seconds and replays them. This version tries to keep that from happening and helps to maintain the current good connection, by not doing the restart requested, but instead, continuing to provide the stream from the provider to the client streams that are available. This has increased the stability of daddylive plugin and removed the déjà vu event.

I have upgraded my server and it worked without issue. Further testing is needed to verify nothing new has been broken. The biggest issue found and resolved was defunct processes when stopping the streams.

The main page has been updated and now shows the number of clients connected to the provider stream. For VOD streams, two tuners are used for two streams from the same channel while one tuner is used when the same non-VOD channel is streamed (The number of clients will show 2).

« Previous Page Next Page »