Systems and methods for player input motion compensation by anticipating motion vectors and/or caching repetitive motion vectors
Systems and methods for reducing latency through motion estimation and compensation techniques are disclosed. The systems and methods include a client device that uses transmitted lookup tables from a remote server to match user input to motion vectors, and tag and sum those motion vectors. When a remote server transmits encoded video frames to the client, the client decodes those video frames and applies the summed motion vectors to the decoded frames to estimate motion in those frames. In certain embodiments, the systems and methods generate motion vectors at a server based on predetermined criteria and transmit the generated motion vectors and one or more invalidators to a client, which caches those motion vectors and invalidators. The server instructs the client to receive input from a user, and use that input to match to cached motion vectors or invalidators. Based on that comparison, the client then applies the matched motion vectors or invalidators to effect motion compensation in a graphic interface. In other embodiments, the systems and methods cache repetitive motion vectors at a server, which transmits a previously generated motion vector library to a client. The client stores the motion vector library, and monitors for user input data. The server instructs the client to calculate a motion estimate from the input data and instructs the client to update the stored motion vector library based on the input data, so that the client applies the stored motion vector library to initiate motion in a graphic interface prior to receiving actual motion vector data from the server. In this manner, latency in video data streams is reduced.
1. A computer-implemented method for caching motion vectors comprising:
generating one or more motion vectors at a server, wherein the motion vectors are generated based on predetermined criteria;
transmitting the generated motion vectors and one or more invalidators to a client, wherein the generated motion vectors and invalidators are cached at the client;
transmitting an instruction to the client to receive input from a user, wherein the client is configured to match the input to cached motion vectors or invalidators; and
transmitting an instruction to the client to apply the matched motion vectors or invalidators to effect motion compensation in a graphic interface.
2. The method of claim 1 , wherein the motion vectors are cached in a look-up table.
3. The method of claim 1 , wherein the one or more invalidators are associated with one or more cached motion vectors.
4. The method of claim 3 , wherein the one or more invalidators are configured to disable the one or more cached motion vectors.
5. The method of claim 1 , further comprising the step of instructing the client to delete one or more cached motion vectors if input is matched to a cached invalidator associated with the one or more motion vectors.
6. The method of claim 1 , wherein the motion vectors are unique and predictable.
7. The method of claim 1 , wherein the motion vectors are generated ahead of time or during runtime.
8. The method of claim 1 , wherein the motion vectors are stored at the server and sent to the client to be cached on-demand.
9. The method of claim 1 , wherein the motion vectors are game-generated.
10. The method of claim 9 , wherein the game-generated motion vectors are generated as per-pixel motion vectors and transformed into per-macroblock motion vectors.
11. A system for caching motion vectors, wherein over a network, a server:
generates one or more motion vectors, wherein the motion vectors are generated based on predetermined criteria;
transmits the generated motion vectors and one or more invalidators to a client, wherein the generated motion vectors and invalidators are cached at the client;
transmits an instruction to the client to receive input from a user, wherein the client is configured to match the input to cached motion vectors or invalidators; and
transmits an instruction to the client to apply the matched motion vectors or invalidators to effect motion compensation in a graphic interface.
12. The system of claim 11 , wherein the motion vectors are cached in a look-up table.
13. The system of claim 11 , wherein the one or more invalidators are associated with one or more cached motion vectors.
14. The system of claim 13 , wherein the one or more invalidators are configured to disable the one or more cached motion vectors.
15. The system of claim 11 , further comprising the step of instructing the client to delete one or more cached motion vectors if input is matched to a cached invalidator associated with the one or more motion vectors.
16. The system of claim 11 , wherein the motion vectors are unique and predictable.
17. The system of claim 11 , wherein the motion vectors are generated ahead of time or during runtime.
18. The system of claim 11 , wherein the motion vectors are stored at the server and sent to the client to be cached on-demand.
19. The system of claim 11 , wherein the motion vectors are game-generated.
20. The system of claim 19 , wherein the game-generated motion vectors are generated as per-pixel motion vectors and transformed into per-macroblock motion vectors.
21. The system of claim 11 , wherein the invalidators are one of or a combination of player inputs and time windows.