Comment by Maursault
3 years ago
Let's see you try that over ssh. The subject is command line graphics and video. What you have liked to is nothing of the sort, those are not terminal graphics but rather conventional GPU graphics and merely opening a graphic window within the command prompt on a local machine to play the video. Why bother to do that when you're sitting locally at the machine with access to the GUI and all the GUI media applications?
ffmpeg is a dependency of mplayer, but ffmpeg on it's own can't transcode or reinterpret video as ASCII. The reason for the exercise is only to show that video and graphics can be displayed on the command line within the limitations of the command line, namely, text only.
> Let's see you try that over ssh
I do that everyday lol
> What you have liked to is nothing of the sort and merely opening of a window within the command prompt on a local machine
I don't think you understand: sixels work IN BAND, meaning ssh will transmit the full video flux "after" it's converted into sixels (it's a little more complicated than that, but I'm trying to say don't expect a SYN/ACK outside of ssh own), which will then be rendered on the remote terminal into pictures upon reception.
It's just like doing 'cat' on a remote file: the content will be transmitted regardless, just at different speeds depending on your available bandwith
> Why bother to do that when you're sitting locally at the machine with access to all the GUI applications?
I prefer the terminal, it's more efficient.
>>Let's see you try that over ssh
>I do that everyday lol
Unconvincing. lol
If you tried to transmit video using the sixel protocol over ssh, you will experience bandwidth issues and immediately fail.
>>What you have liked to is nothing of the sort and merely opening of a window within the command prompt on a local machine
>I don't think you understand: sixels work IN BAND, meaning ssh will transmit the full video flux after it's converted into sixels, which will then be rendered on the remote terminal into pictures upon reception. It's just like doing 'cat' on a remote file
This will not work.
"Sixel is broken because the emulation behavior depends on the font size, thus theoretically can't be supported by terminals that don't have the concept of pixel size (e.g. a detached tmux). Sixel is broken because it cannot be supported by tmux with side-by-side panes. Sixel's palette-based approach is also a terrible legacy, practically unable to transfer photos."[1]
[1] https://gitlab.freedesktop.org/terminal-wg/specifications/-/...
> If you tried to transmit video using the sixel protocol over ssh, you will experience bandwidth issues and immediately fail.
Even abstracting away your incomplete understanding of how sixels work, have you considered the possibility I may have access to way more bandwidth than you? (and I most likely do)
> This will not work.
Yes it does.
I have written lots of sixel code (I've yet to see any of yours), tried to explain you the failure in your reasoning, yet you still don't believe me, then you deny the reality of my lived sixel experience with... a biased quote?
Whatever. Have it your way. I'm out.
2 replies →
False. I could open sixels images over SSH with an XTerm.