[RELEASE] Stream Link/File Manager for Channels [Streaming Library Manager Extension]

Update on the YouTube channels issue: So, I suspected YouTube flagged my IP because I used Tivimate with multiple streams. However, a few months ago, my ISP had put my router in a commercial VLAN with a static IP, because someone in my household had issues with their work VPN. This morning I found their work VPN was "broken", and they had been using their hot spot for days and never told me. My ISP has just merged with another company, so I suspect something got "rebooted" or "reassigned to default". I put in a ticket, and ISP fixed the routing issue. Magically, YouTube streams work normally again without a VPN or signing into the YouTube account!! My external IP is exactly the same today as it always has been, so that was not part of the mix. Thought this might be helpful for others.

These features and fixes should be working as of this version:

1 Like

@babsonnexus
Log issue/change? Was the log config changed?
I just updated to the v2026.03.29.1338...
Here's the only thing in my podman/linux log:
image

Meanwhile, the Controls/Logs show:

[youtube] Gd9d4q6WvUY: Downloading iframe API JS
[youtube] Gd9d4q6WvUY: Downloading player 8e54e4ea-main
[youtube] Gd9d4q6WvUY: Downloading web safari player API JSON
[youtube] [jsc:node] Solving JS challenges using node
[debug] [youtube] [jsc:node] Using challenge solver lib script v0.8.0 (source: python package, variant: minified)
[debug] [youtube] [jsc:node] Using challenge solver core script v0.8.0 (source: python package, variant: minified)
[debug] [youtube] [jsc:node] Running node: node --permission -
[WARNING] [youtube] Unable to fetch GVS PO Token for web_safari client: Missing required Visitor Data. You may need to pass Visitor Data with --extractor-args "youtube:visitor_data=XXX"
[youtube] Gd9d4q6WvUY: Downloading m3u8 information
2026-03-29 08:14:15.621756:  INFO: Extraction successful for https://www.youtube.com/watch?v=Gd9d4q6WvUY.
2026-03-29 08:14:15.621851:  INFO: Found 6 formats.
2026-03-29 08:14:15.621951:  INFO: Best format URL found using m3u8: https://manifest.googlevideo.com/api/manifest/hls_playlist/expire/1774829654/ei/9mvJacKsHLyRsfIPnPPT6A0/ip/72.253.16.202/id/Gd9d4q6WvUY.4/itag/301/source/yt_live_broadcast/requiressl/yes/ratebypass/yes/live/1/sgoap/gir%3Dyes%3Bitag%3D140/sgovp/gir%3Dyes%3Bitag%3D299/rqh/1/hls_chunk_host/rr2---sn-i5f5ppuxa-ioal.googlevideo.com/xpc/EgVo2aDSNQ%3D%3D/playlist_duration/30/manifest_duration/30/bui/AUUZDGK6RmKF449EXMgtFlYIy2xvaERZog6rw5ZblDWTq_kW1p3_7XrnFNOAu0kjkl05h7m4rZPCUMpq/spc/jlWavb3-8aVNGS_9kppPe7WJN1hAbiGdtib2vJ1YQcE5HNlFWzQ0Vfzf8tYPNj-Vt6h31Q/vprv/1/ns/CxdWqK1Etizya-Eh2PiWC80T/reg/0/playlist_type/DVR/initcwndbps/3708750/met/1774808055,/mh/jt/mm/44/mn/sn-i5f5ppuxa-ioal/ms/lva/mv/m/mvi/2/pl/19/rms/lva,lva/dover/11/pacing/0/keepalive/yes/fexp/51565116,51565681/n/rw3n0Fib5XD5Vw/mt/1774807722/sparams/expire,ei,ip,id,itag,source,requiressl,ratebypass,live,sgoap,sgovp,rqh,xpc,playlist_duration,manifest_duration,bui,spc,vprv,ns,reg,playlist_type/sig/AHEqNM4wRQIhAICf4xy4ooDjQOqVqw-t8X6W_ZhQcHQRrmBjHxe80DTSAiBFZxg7k0aQyUs39HsO_dFEDAUEkdT6IF2QR9jIofpUnQ%3D%3D/lsparams/hls_chunk_host,initcwndbps,met,mh,mm,mn,ms,mv,mvi,pl,rms/lsig/APaTxxMwRAIgGP1LSD9ZLo6x-sIaKbfMgd_JrChPwTdeY57OD9oHIQgCIHSFJKaAwz1QihSWj4gmwN9lbO4ZO9QlAoUnFgLnqJws/playlist/index.m3u8
[info | 2026-03-29 08:14:15,624] - 10.89.3.6 - - [29/Mar/2026 08:14:15] "GET /playlists/streams/stream?url=https://www.youtube.com/watch?v=Gd9d4q6WvUY HTTP/1.1" 200 -

OK, update... so the last entry in the podman/linux log was 08:11...
Then at 08:24, a slew of entries showed up in the container log...

See above:

No support is or will be offered for any logging outside SLM's internal methodology.

1 Like

Are we the only two that understand what we're saying and showing?
I gave up and just view the log from within SLM now.

Thanks. Looking good!

1 Like

@chDVRuser no worries, I'll do the same going forward... use only the slm logs...

1 Like

Technically this is how I'm looking at it. I could be wrong.
Docker captures stdout and stderr streams from running containers and logs them.
It appears that the container stdout is being buffered somehow since that output is being delayed.

Just one example.
This log entry timestamped 13:00:13 local time (20:00:13 UTC) was logged by docker at 21:22:59 UTC.

UTC time container log      Local (UTC-7) time
2026-03-29T21:22:59.634787Z 2026-03-29 13:00:13.017508:  INFO: Best format URL found using m3u8: https://manifest.googlevideo.com/api/manifest/hls_playlist/...

So something kept that stdout buffered for over an hour.

Like I said, because of this the SLM container log will not be current, so I'm using the SLM log for this container.

Thanks

I installed this in Windows. How do I uninstall it?

  1. In Task Manager, make sure slm.exe is not running. If it is, close it.
  2. In Task Scheduler, delete the Streaming Library Manager task.
  3. In Environment Variables, delete the SLM_PORT
  4. Delete the directory where you did the install.

NOTE: If you are migrating to another environment or installation type, you MUST save your program_files directory first to maintain everything you have done. Place the entire contents of that in the new location's installation and you'll be GTG!