Replies: 2 comments 5 replies
|
It's a plain old hack but nobody else had ever thought about. Input latency isn't high all the time, but due to how streaming works latency can be doubled according to your render framerate(like how frame generation introduces latency). Warp drive mode cuts both encoding and decoding latency by forcing encoding in a much higher framerate so the overall latency can drop significantly. Warp2 tries to push the limits more aggressively, so it'll stress your host and client even more. Some lower end devices might actually get higher decoding latency in this mode. I don't work for Nvidia so it's nothing related to their latest technology. It should work on every card, not limiting to Nvidia. If it happens to have similarity with Reflex 2 then I'm honored to have this figured out on my own 😂 |
|
@ClassicOldSong Just want to piggyback on this thread. Does warp/warp2 need Apollo host? |
Uh oh!
There was an error while loading. Please reload this page.
Hi!
I am delighted to see that both Warp Drive and Warp 2 work wonderfully on the Nvidia Shield TV Pro client!
It has SEVERELY cut my input (decoding latency I presume) all the while being as smooth as the best previous option!
How does this work exactly and what is the difference between the two?
I would like to know more about how they work.
Are they somehow connected to frame warping tech that Nvidia showed off with their Reflex 2 tech?
All reactions