-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Away streams only #32
Comments
You might want to check out mlbv, it has this feature and was recently updated for 2019 compatibility. See the readme, section 5: https://github.com/VirtualParticle/mlbv
|
I can't reproduce this. Are you using the latest git master? |
I think this is a feature request. As in, they want the ability to select their favorite team's game, but get the opponent's broadcast, even if they don't know who the opponent is. |
Ah! In that case, this should already be supported by updating config.yaml with the following settings:
There's no reliable way to do override the feed type from the command-line right now, but I'll fix that shortly. |
* Provider options set when the identifier is parsed were overriding command-line options. This prevented things like streamglob play://phi:feed_type=away from working. * This commit adds options from the provider only if they're not specified on the command-line. This should enable command-line home/away stream selection without having to specify the name of the home/away team.
As of @9706f5c, setting preferred stream should work either in the config file (by specifying remote/local for each team) or via the command-line (by adding
|
I use the latest version. Both commands: Also Installing everything from the beginning doesn't change that behaviour. |
Whoops, maybe it was a bug report. Sorry! :) |
Just wondering if this is being addressed. Like eithrial above, on certain games, I can only get the visiting-team's stream. Otherwise, great work everyone !! |
For example streamglob download://mlb/2019-06-17.tor pick away stream instead of the home one.
The text was updated successfully, but these errors were encountered: