MLB.TV for Channels

Playground Custom Channels
#490

so, here's an update: some bad news.

until the devs get back to me with a potential solution, this is pretty much dead in the water. no matter what i do, it is always playing the main audio feed and ignoring my alternate audio (which is the radio feed). i don't have a way to strip the default audio from the main video feed, so without channels respecting the alternate audio, we're out of luck here. this seems to be an issue that needs to be fixed with how channels handles alternate audio for custom channels before it will work.

1 Like
#491

Option 2 if it can be worked out would be the better way to handle this IMO.
Thanks for pursuing this!

#492

if worse comes to worse, I'll still put this out as a separate image so people can use it to create a separate container and run it in something like tivimate or Kodi (both of them are tested and working) if we can't get it working in channels...but I (like everyone else here I'm sure) hope we can figure this out. still need one of the devs to see this thread and hopefully have an answer (or a quick fix on their end).

1 Like
#493

Anyone know the proper way to define the storage (app/log) variables in unraid?

#494

I'm getting an error on the EPG.
Undefined variable $guideDayStart

It's here...
app/Http/Controllers/GuideController.php:492

Any thoughts?

#495

what does your env look like?

#496

Any word from the devs on this or further progress on audio feeds?

#497

nope, nothing yet. I'm stuck until we get confirmation on why the channels player won't load the alternate audio.

@tmm1 any update on this?

1 Like
#498

We don't have a way to wire up secondary audio to the player. There's no easy fix at the moment.

1 Like
#499

fair enough then. sorry guys, this isn't gonna work in channels...

i will try to get an image put together for those who have the ability to run this in a secondary player (like tivimate or kodi) and want to give it a shot. theoretically, you could just use that new image and run it both in channels (which will load the default audio) and then also run the same streams in tivimate or kodi, which should give you the radio feeds. that being said though, i'd run multiple containers if you can, just to avoid any potential issues while we're still working out the kinks.

it probably won't be until monday though, i'm in anaheim all weekend for the mets/angels series.

4 Likes
#500

I moved houses and i'm getting these kinds of boots on the container and can't seem to make anyway troubleshooting - the webpage loads but if something tries to load the m3u they get 500 errors

2022-06-12 21:03:08,197 INFO supervisord started with pid 1
2022-06-12 21:03:09,199 INFO spawned: 'nginx' with pid 8
2022-06-12 21:03:09,202 INFO spawned: 'php-fpm' with pid 9
[12-Jun-2022 21:03:09] NOTICE: fpm is running, pid 9
[12-Jun-2022 21:03:09] NOTICE: ready to handle connections
2022-06-12 21:03:10,298 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-06-12 21:03:10,298 INFO success: php-fpm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
192.168.1.239 - - [12/Jun/2022:21:03:27 -0400] "GET /m3u HTTP/1.1" 500 44040 "-" "Go-http-client/1.1" "-" 1.066 1.066 . -
192.168.1.239 - - [12/Jun/2022:21:03:52 -0400] "GET /m3u HTTP/1.1" 500 109640 "-" "Go-http-client/1.1" "-" 0.524 0.524 . -
2022-06-12 21:04:23,635 WARN received SIGTERM indicating exit request
2022-06-12 21:04:23,652 INFO waiting for nginx, php-fpm to die
[12-Jun-2022 21:04:23] NOTICE: Terminating ...
[12-Jun-2022 21:04:23] NOTICE: exiting, bye-bye!
2022-06-12 21:04:23,654 INFO stopped: php-fpm (exit status 0)
2022-06-12 21:04:23,675 INFO stopped: nginx (exit status 0)
2022-06-12 21:09:50,079 INFO supervisord started with pid 1
2022-06-12 21:09:51,081 INFO spawned: 'nginx' with pid 8
2022-06-12 21:09:51,083 INFO spawned: 'php-fpm' with pid 9
[12-Jun-2022 21:09:51] NOTICE: fpm is running, pid 9
[12-Jun-2022 21:09:51] NOTICE: ready to handle connections
2022-06-12 21:09:52,173 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-06-12 21:09:52,173 INFO success: php-fpm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
#501

try running the session and login clear commands. my somewhat random guess is that MLB is seeing you were already logged in at one IP and getting confused when you're trying to use the same player / device at a different IP.

docker exec -it channels-baseball php8 artisan session:clear
docker exec -it channels-baseball php8 artisan login:clear
#502

root@OffensiveBias:~# docker exec -it channels-baseball php8 artisan session:clear

GuzzleHttp\Exception\ClientException

Client error: POST https://ids.mlb.com/oauth2/aus1m088yK07noBfh356/v1/token resulted in a 403 Forbidden response:

<?xml version="1.0" encoding="utf-8"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/ (truncated...) at vendor/guzzlehttp/guzzle/src/Exception/RequestException.php:113 109▕ if ($summary !== null) { 110▕ $message .= ":\n{$summary}\n"; 111▕ } 112▕ ➜ 113▕ return new $className($message, $request, $response, $previous, $handlerContext); 114▕ } 115▕ 116▕ /** 117▕ * Obfuscates URI if there is a username and a password present +11 vendor frames 12 app/Services/MlbService.php:121 GuzzleHttp\Client::post() 13 app/Services/MlbService.php:77 App\Services\MlbService::refreshLogin() root@OffensiveBias:~#
#503

that means MLB is sending back a 403 when your server tries to log in. to me, that seems to indicate that they have blocked your IP for whatever reason (at least from getting the streams via API as this container does). does viewing on the web / mobile apps work?

#504

weird - might be a network thing - i have multiple vlans now going into my server

it works fine on app

#505

Error went away on its own. Maybe I was looking at the guide when there was no content. No clue.

#506

Hey, I went through this exact issue over the weekend. I confirmed the problem by trying to login to my MLB.tv account on the same device and it threw a non-specific error. I changed my password, still no luck. I then tried to login on another device and it worked. I'm doing something "unsupported" so I don't know how much detail I should go into but I changed some other things and it lit back up. If you want more info, we can talk offline.

1 Like
#508

just pushed a new version with some pretty significant changes. i'll try to outline them all here...

first: i changed the versioning scheme to make it a little easier to keep track of where we are (rather than trying to determine if something is a big enough change for a major version number increment)...moving forward, all versions released will be numbered by the year, month, and release number in that month (similar to how home assistant does their version numbers now). so, for example, this new version that was just pushed is 2022.6.1

second: TV feeds are now going to be on subchannel .1 for all teams. when you load this new version, you'll need to refresh your m3u to make sure everything lines up on the new subchannels instead of the original channel number without subchannel. the reason for this is related to the third major thing in this release...

third: radio feeds are available, although they won't work in channels (you'll have to use a different player to make them work). i would STRONGLY recommend you run multiple containers if you want the radio feeds, since having them show up in channels is pointless as it won't be able to load the alternate audio. in order to set this up, there are two new environment variables you can use:

MLB_SHOW_TV_FEEDS=true
MLB_SHOW_RADIO_FEEDS=true

  • if you don't set either one of these variables, the container will work exactly as it always has...it'll only show you the TV feeds (although as mentioned earlier, they'll now be on subchannel .1 for each team).

  • if you only set MLB_SHOW_RADIO_FEEDS to true, it will ONLY show the radio feeds on subchannel .2.

  • setting them both to true will show both feeds, with TV on subchannel .1 and radio on subchannel .2.

fourth (and final note) on the radio feeds specifically: there's a pretty significant delay on some of these sometimes (but not always). i don't have any way to account for that, so you'll likely want to use a player that allows you to control the audio offset. tivimate allows this for up to one full second in either direction, which for the most part has been good enough for me...although occasionally i've had to go a little bit longer and had to use a different player with a longer delay offset. kodi works well for this, although it does have issues decrypting the feeds on some android devices (i'm not at all sure why, it works perfectly on my phone but has issues on my chromecast with google tv).

i've done a lot of testing on this with the mets feeds over the past few weeks, but please put this through the paces if you'd like and let me know if you notice anything strange happening that needs fixed.

#509

almost on cue, it seems the radio feeds are broken. something must have gotten screwed up when i built this image.

i'll see if i can get it working ASAP.

edit: found the issue. it has to do with it trying to load the spanish audio feed instead...i'll make that an option in the next release, but for right now i am just going to get together a fix for english radio.

edit 2: pushed 2022.6.2, this one should work for english radio for all teams. i'm going to delete 2022.6.1 from the repo, since it has a pretty major flaw (it'll work for some teams but not all).

one caveat: when you first load this new version with the radio feeds, you're going to need to clear your sessions for this to work. there's a built in command that you can run from inside the container to accomplish this...

php8 artisan session:clear

edit 3: like clockwork, there's another issue i'm fixing now (relating to the radio overlay for the FOX regional games). it will work for the first team you load, but if you try to load the radio feed for the other team in one of those games it won't work.

#510

just pushed 2022.6.3 which should fix the issue described above.

and now, i'm logging off to enjoy my saturday evening. :slight_smile:

seriously though, feel free to put this through the paces and let me know if there's anything else broken.

edit: one final push for tonight, just fixed a potential issue with the radio feeds for the second game of a doubleheader. 2022.6.4 is now the latest image.

2 Likes