Done, to the extent i could - it gets big quick...
1 Like
I did a lot of troubleshooting on that. I first created all the folders it asked for (in /app/tmp and /app/config), then, ensured I had ownership. I even installed the docker container using the -user flag to make sure that my username (which is an admin) owned the docker container and the folder. But, eventually, I just took out all referenced to the paths and let it do its thing. Great work bytheway. Any chance you'll be taking a look at Bally Sports channels?
1 Like
Can I see how you're running the docker run command?
I don't think I'll do Bally Sports anytime soon... I don't have access to them at all and the login flow for that looks interesting to say the least
Just had a chance to test out the new update and wow. I had been using the old version to record games that I worked on but there were always problems. The new container recorded my game tonight perfectly, much better quality than before and didn't miss a second of it. Thank you so so much!
First M1 Mac record ( on ESPN+ , not 3) didn't go well. Slew of these:
2022/10/07 19:46:14.540051 [DVR] Recording for job 1665183890-11 from M3U-ESPNPlus ch7002 into "TV/Union vs. UConn/Union vs. UConn 2022-10-07-1904.mpg" for 2h48m45.493926s
2022/10/07 19:49:18.853550 [SNR] Buffer statistics for "TV/Union vs. UConn/Union vs. UConn 2022-10-07-1904.mpg": buf=2%,0%-100% drop=2%
2022/10/07 19:49:18.935075 [MTS] Statistics for "TV/Union vs. UConn/Union vs. UConn 2022-10-07-1904.mpg": skipped=0 unhandled_packets=0 discontinuity_detected=0 transport_errors=0 invalid_pts=0 invalid_dts=0 saw_pcr=true saw_pmt=true highest_pts=2665.602956
2022/10/07 19:49:19.039915 [TNR] Closed connection to M3U-ESPNPlus for ch7002 EPlusTV 7002
2022/10/07 19:49:19.044152 [DVR] Error running job 1665183890-11 Union vs. UConn: Transcoder Reset: Playlist skipped to a higher sequence (47106 -> 47110): http://localhost:8000/channels/7002.m3u8
1 Like
I see that error too.
In my case with hlstube feeding an M3U channel.
The channel can work fine for days and then get multiple of these errors in a single recording.
Apologies for the newbie question. I am new to docker. I was able to run the container, get my ESPN+ activated and it generated the channel list and programming. Where does the m3u file or xml file get generated and saved? I am unable to find it. Most likely user error.
I tried http://192.168.x.x:8000/xmltv.xml
I am hoping to use this with Tivimate.
3 Likes
If 8000 is the port you used then xmltv.xml is correct for the guide and then the m3u is http://192.192.x.x:8000/channels.m3u.
I am getting 'site cannot be reached. refused to connect' error.
I have container running on Docker Desktop app on my M1 iMac.
Its local ip address is 192.168.1.89. So I have tried:
192.168.1.89:8000/channels.m3u
192.168.1.89:8000/xmltv.tv
Again, I am brand new to this stuff so it could be simple user error.
1 Like
ssigning Seattle Kraken vs. Anaheim Ducks to Channel #1
Assigning Seattle Kraken vs. Anaheim Ducks to Channel #2
Assigning UC San Diego vs. CSU Fullerton to Channel #4
Assigning Cal Poly vs. CSU Northridge to Channel #6
Assigning Bangladesh vs. Pakistan (6th T20) to Channel #7
Assigning Vancouver Canucks vs. Edmonton Oilers to Channel #8
Assigning UC Irvine vs. UC Riverside to Channel #9
Assigning Marshall Postgame Presser to Channel #10
Assigning Women's Asia Cup 2022 to Channel #3
=== Done building the schedule ===
killall: ffmpeg: no process killed
=== Getting events ===
Looking for live events...
Looking for upcoming events...
Cleaning up old events
=== Done getting events ===
=== Building the schedule ===
=== Done building the schedule ===
=== Starting Server ===
Server started on port 8000
=== Getting events ===
Looking for live events...
Adding event: UC Santa Barbara vs. CSU Fullerton
Looking for upcoming events...
Cleaning up old events
=== Done getting events ===
=== Building the schedule ===
=== Done building the schedule ===
=== Starting Server ===
Server started on port 8000
2 Likes
Can I see your docker run command?
I am not sure where to find this. Sorry.
Docker is so foreign to me.
Just the command to start the container
1 Like
Putting out some feelers for people who are interested in ESPN3 support. I don't have a supported ISP, so I can't develop it locally. I'll need some kind of temporary VPN setup to a volunteer
Got it all setup. The hardest part was trying to figure out the location of the Docker folder to put in the terminal command on my Mac/Server. So far it has been working great and I've been recording all the new season games of NHL on ESPN+. Everything seems to be 60fps 720p and stereo.
I have the beta running well and authenticated. But, the container loses the authentication pretty much every day (I haven't actually done the troubleshooting to see how often). After it loses the authentication, I have to delete the docker container and reinstall it to get a new token/password. Do you have any idea why my docker container would continually lose authentication? Am I missing a setting?
No, I'm probably not handling refreshing the auth tokens. I'll look into this. You shouldn't have to delete your docker containers. Deleting the tokens.json file should do it.
Do you mind DM'ing my your docker logs so I can see what tokens are failing?
As soon as I lose authorization again, I'll send some logs. When I reinstalled, it reset the log.
Does anyone have a guide on how to do this now for espn 3/ sec+? Can devs work on it to add ? Would be an awesome feature