Earlier quoted context omitted.
I think it would actually be "harder" to encrypt since it wouldn't be as compressible as normal video (if you lower the resolution to match). Note you can tunnel arbitrary ports in ssh for data if that's what you're thinking of.
Text is extremely compress-able. Admittedly, this is not common text, and is many "snapshots" of the whole screen, but I believe LZ-based compression would still be extremely effective on this data. The OP above said it can only be one of ten characters, and one of 256 colors, and a 100x40 grid, so it would likely require similar data rates to get this level of quality from a video stream, I would think, since the 10…
Show HN: A Simple terminal-based video chat – renders in ASCII and has audio
31–40 of 48 posts
Re: Show HN: A Simple terminal-based video chat – renders in ASCII and has audio
#32This is awesome! Wonder how it compares with mine (github.com/billyeh/termchat). Would love to share notes with the maker, since audio was something I did not even consider while I was making it. The image processing part is fun, though!
I helped create it at a recent hackathon. the ascii is rendered by calculating the intensity of any given pixel, mapping that intensity to a character based on how much that character fills up space ('@' would be bright and '.' would be dark) and then approximating the color of the pixel to fit within the 256 available I've noticed your implementation uses websockets, which are built on top of TCP. we used UDP and en…
http://aa-project.sourceforge.net/aalib/
http://caca.zoy.org/wiki/libcaca
and possibly other clones too. Might help improve the visuals.
Re: Show HN: A Simple terminal-based video chat – renders in ASCII and has audio
#33Re: Show HN: A Simple terminal-based video chat – renders in ASCII and has audio
#34Re: Show HN: A Simple terminal-based video chat – renders in ASCII and has audio
#35This is awesome! Wonder how it compares with mine (github.com/billyeh/termchat). Would love to share notes with the maker, since audio was something I did not even consider while I was making it. The image processing part is fun, though!
Re: Show HN: A Simple terminal-based video chat – renders in ASCII and has audio
#36Earlier quoted context omitted.
I helped create it at a recent hackathon. the ascii is rendered by calculating the intensity of any given pixel, mapping that intensity to a character based on how much that character fills up space ('@' would be bright and '.' would be dark) and then approximating the color of the pixel to fit within the 256 available I've noticed your implementation uses websockets, which are built on top of TCP. we used UDP and en…
You can go a bit further to get significantly higher color depths using ASCII block characters 176, 177, 178. By using the foreground and background ANSI colors and blending them by using these three characters (25%, 50%, 75%) you can achieve some quite realistic images. If you're more interested in resolution, using half block characters like 220 and 223 can allow you to double your vertical resolution at the cost o…
Do you have any good examples of calculating the right foreground/background colors to use?
Re: Show HN: A Simple terminal-based video chat – renders in ASCII and has audio
#37Earlier quoted context omitted.
https://csl.name/jp2a/
Thanks. It would be better to have some navigation functions like what you can do on Windows with the default image preview program, so that users can browse through a series of images without having to convert them one by one.
Re: Show HN: A Simple terminal-based video chat – renders in ASCII and has audio
#38Re: Show HN: A Simple terminal-based video chat – renders in ASCII and has audio
#39"VIDIOC_STREAMON: Invalid argument libv4l2: error turning on stream: Invalid argument
Can't seem to get it to work trying anything on github etc and want to get enough around to file a real issue.
Re: Show HN: A Simple terminal-based video chat – renders in ASCII and has audio
#40:( Anyone get the error "VIDIOC_STREAMON: Invalid argument libv4l2: error turning on stream: Invalid argument Can't seem to get it to work trying anything on github etc and want to get enough around to file a real issue.