Open gaycomputers opened 5 years ago
We are using webtorrent-cli
under the hood, can you check if using that directly works for you?
For note, it streams to my chromecasts just fine... all of them... all 6... even though I just want it on one specific one of them... ^.^;
If this project uses it's own fork of webtorrent (looks like it might?) then merging the https://github.com/webtorrent/webtorrent-cli/pull/58 PR would add the ability to select chromecasts then it looks like?
If this project uses it's own fork of webtorrent (looks like it might?)
That's right, but I don't want to maintain features I don't need, I've only forked it for adding support for IINA. When they'll merge that PR we can get back to this.
Heh, well right now the chromecast'ing is pretty useless otherwise as casting to everything gets my wife yelling at me... ^.^;
What is IINA speaking of, google is not being revealing and trying to use it just seems to exit without doing much of anything, no error or anything. I'm not finding an iina
program in the debian or ubuntu packaging repositories so it doesn't seem to be a program and I'm not finding any information about a protocol. Do you have information about it? Is it some custom protocol or something proprietary?
@OvermindDL1 It's a popular video player for macOS https://github.com/lhc70000/iina
Oooo, why is it showing up on linux then? Why add specific media players rather than an extension mechanism in the config file that allows for a <name>
-> /path/to/cmd -flags {video} --more-flags
where {video}
or whatever is replaced with the full file path to the video file (with other options for things like caption files or so forth). Then you'd be able to support any arbitrary program with relative ease on a user-by-user basis with perhaps some built-in options? If that's the point of the fork then that seems far better to PR upstream. :-)
As an aside, apparently that above PR 58 on the webtorrent repo is moving forward, it looks like it might make it in very soon!
why is it showing up on linux then? Why add specific media players rather than an extension mechanism
Because CLIFlix was basically an afternoon project.
Then you'd be able to support any arbitrary program If that's the point of the fork then that seems far better to PR upstream. :-)
Kind of, for instance IINA didn't have a CLI a few versions back, you certainly don't want to write an AppleScript in the terminal or a program that runs it, instead of just selecting "IINA" from a list or passing the "--iina" option, right?
If you'd like to submit a PR that adds support for adding support for custom media players let me know.
Because CLIFlix was basically an afternoon project.
Gotta love how such things become overnight sensations. ^.^
for instance IINA didn't have a CLI a few versions back
o.O That's... weird...
you certainly don't want to write an AppleScript in the terminal or a program that runs it
I thought Mac's used bash as their scripting interface? I've never even heard of AppleScript... ^.^;
Could just add a System Player
option that just xdg-open <file>
for just playing of the video (sans caption files or whatever), that would play with whatever is registered for the system then, would be a useful option as well (since cliflix is missing the player that I generally use, though I've been using it via ssh from my phone to play to the chromecasts, or trying anyway except for that bug...).
I thought Mac's used bash as their scripting interface? I've never even heard of AppleScript... ^.^;
Bash is the default shell. AppleScript is a weird language for talking to native mac apps.
Could just add a System Player option that just xdg-open
for just playing of the video
There's no complete video file until it's 100% downloaded. The other players open a url that webtorrent-cli provides (you can see that when webtorrent-cli starts up), doing what you ask would just open the browser. Besides I don't have time for this currently, feel free to make a separate issue about this is you want.
Returns following error.