3 ms·

24fps is movie framerates. It's the lowest fps which humans find tolerable. 16:1 compression ratio is based on DXT compression, which looks like ass, but is a

24fps is movie framerates. It's the lowest fps which humans find tolerable. 16:1 compression ratio is based on DXT compression, which looks like ass, but is able to be done in realtime if the server is beefy enough. 8:1 would be better. 32:1 would look so terrible that I'm not sure anyone would be willing to sit through it. Wifi is a requirement to make it go mainstream. Most people aren't willing to run physical cable through their living spaces, either due to lack of patience or equipment.

sliverstorm 13y ago
Powerline is almost there.
Dylan16807 13y ago
DXT is extremely lightweight compression designed to be decompressed in parallel during the rendering process. 10mbps is plenty if you're using a video codec, and the Pi has hardware H.264 support.
- nitrogen 13y ago
  H.264 imposes a few seconds of lag to get to that sort of compression ratio with acceptable quality. Good for movies, not so good for games.
  - Dylan16807 13y ago
    Are you sure about that? As I understand it you usually don't want to have more than 4-5 B-frames in a row. And if you use baseline profile you eliminate B-frames and can cut the latency to be less than a frame. See also: http://www.eetimes.com/document.asp?doc_id=1273759 http://www.eetimes.com/document.asp?doc_id=1273759 http://x264dev.multimedia.cx/archives/249 http://x264dev.multimedia.cx/archives/249
  - deleted 13y ago
    [deleted]
comex 13y ago
Why does it need to be a texture compression algorithm? Intel Quick Sync can encode H.264 with pretty low latency.
web007 13y ago
YouTube can stream from outside of my WiFi network at 720p or 1080p, streaming within it shouldn't be a problem. Pushing the codec pieces far enough down the stack that they're done by hardware will be the bottleneck. In any case, http://steamcommunity.com/groups/homestream http://steamcommunity.com/groups/homestream seems to answer this - they're going to build it.
jcampbell1 13y ago
I am confused by your calculations. What does texture compression have to do with video compression? A peak 5 mbps h264 video with no B frames would look very good and have no latency.

sliverstorm 13y ago

Powerline is almost there.

Dylan16807 13y ago

DXT is extremely lightweight compression designed to be decompressed in parallel during the rendering process. 10mbps is plenty if you're using a video codec, and the Pi has hardware H.264 support.

nitrogen 13y ago
H.264 imposes a few seconds of lag to get to that sort of compression ratio with acceptable quality. Good for movies, not so good for games.
- Dylan16807 13y ago
  Are you sure about that? As I understand it you usually don't want to have more than 4-5 B-frames in a row. And if you use baseline profile you eliminate B-frames and can cut the latency to be less than a frame. See also: http://www.eetimes.com/document.asp?doc_id=1273759 http://www.eetimes.com/document.asp?doc_id=1273759 http://x264dev.multimedia.cx/archives/249 http://x264dev.multimedia.cx/archives/249
- deleted 13y ago
  [deleted]

comex 13y ago

Why does it need to be a texture compression algorithm? Intel Quick Sync can encode H.264 with pretty low latency.

web007 13y ago

YouTube can stream from outside of my WiFi network at 720p or 1080p, streaming within it shouldn't be a problem. Pushing the codec pieces far enough down the stack that they're done by hardware will be the bottleneck. In any case, http://steamcommunity.com/groups/homestream http://steamcommunity.com/groups/homestream seems to answer this - they're going to build it.

jcampbell1 13y ago

I am confused by your calculations. What does texture compression have to do with video compression? A peak 5 mbps h264 video with no B frames would look very good and have no latency.