Systems and methods for adjusting buffer size
Methods and systems are provided for adjusting a size of a buffer based on a probability that a rewind request will be received during a currently playing segment of media. When the system determines that receiving a rewind request is likely, the system will increase the size of a buffer such that the rewind request can be accommodated using data from the buffer. When the system determines that receiving a rewind request is unlikely, the system will decrease the size of the buffer to free resources for other system components.
1. A method comprising:
buffering a first segment of a media asset in a buffer having a first buffer size;
detecting an event associated with a second segment of the media asset;
in response to detecting the event, determining an attribute of content corresponding to the second segment of the media asset;
determining a likelihood of receiving a rewind request during the second segment of the media asset based on the attribute of the content associated with the second segment and a preference stored in a user profile; and
in response to determining that the likelihood exceeds a predetermined value:
calculating an amount of storage required to buffer the second segment;
determining whether the calculated amount of storage exceeds a maximum buffer size;
in response to determining that the calculated amount of storage exceeds the maximum buffer size, increasing the size of the buffer to the maximum buffer size;
in response to determining that the calculated amount of storage does not exceed the maximum buffer size, increasing the size of the buffer to the calculated amount of storage; and
buffering the second segment of the media asset in the buffer having the increased buffer size.
2. The method of claim 1 , wherein determining the likelihood of receiving a rewind request during the second segment of the media asset comprises:
determining the likelihood of receiving the rewind request exceeds the predetermined value when the event matches the preference stored in the user profile; and
determining the likelihood of receiving the rewind request does not exceed the predetermined value when the event does not match the preference stored in the user profile.
3. The method of claim 1 , wherein the preference stored in the user profile is a preferred genre of the user, and wherein determining the likelihood of receiving the rewind request during the second segment of the media asset comprises:
determining a genre associated with the event; and
determining the likelihood exceeds the predetermined value when the genre associated with the event matches the preferred genre of the user.
4. The method of claim 1 , further comprising reducing the size of the buffer to the first buffer size, in response to detecting an end of the second segment.
5. The method of claim 1 , further comprising outputting the buffered second segment in a reverse order in response to detecting a rewind request.
6. The method of claim 1 , further comprising:
storing a viewing history corresponding to the user in the user profile; and
determining the preference based on the viewing history.
7. The method of claim 1 , wherein determining the event associated with the second segment of the media asset comprises:
receiving metadata associated with the second segment of the media asset; and
detecting, based on the metadata, the event.
8. The method of claim 1 , wherein determining the event associated with the second segment of the media asset comprises:
analyzing video data associated with the second segment of the media asset; and
detecting based on the analyzing, an event associated with the second segment.
9. A system comprising control circuitry configured to:
buffer a first segment of a media asset in a buffer having a first buffer size;
detect an event associated with a second segment of the media asset;
in response to detecting the event, determining an attribute of content corresponding to the second segment of the media asset;
determine a likelihood of receiving a rewind request during the second segment of the media asset based on the attribute of the content associated with the second segment and a preference stored in a user profile; and
in response to determining that the likelihood exceeds a predetermined value:
calculate an amount of storage required to buffer the second segment;
determine whether the calculated amount of storage exceeds a maximum buffer size;
in response to determining that the calculated amount of storage exceeds the maximum buffer size, increase the size of the buffer to the maximum buffer size;
in response to determining that the calculated amount of storage does not exceed the maximum buffer size, increase the size of the buffer to the calculated amount of storage; and
buffer the second segment of the media asset in the buffer having the increased buffer size.
10. The system of claim 9 , wherein the control circuitry is further configured, determining the likelihood of receiving a rewind request during the second segment of the media asset, to:
determine the likelihood of receiving the rewind request exceeds the predetermined value when the event matches the preference stored in the user profile; and
determine the likelihood of receiving the rewind request does not exceed the predetermined value when the event does not match the preference stored in the user profile.
11. The system of claim 9 , wherein the preference stored in the user profile is a preferred genre of the user, and wherein the control circuitry is further configured, when determining the likelihood of receiving the rewind request during the second segment of the media asset, to:
determine a genre associated with the event; and
determine the likelihood exceeds the predetermined value when the genre associated with the event matches the preferred genre of the user.
12. The system of claim 9 , wherein the control circuitry is further configured to reduce the size of the buffer to the first buffer size, in response to detecting an end of the second segment.
13. The system of claim 9 , wherein the control circuitry is further configured to output the buffered second segment in a reverse order in response to detecting a rewind request.
14. The system of claim 9 , wherein the control circuitry is further configured to:
store a viewing history corresponding to the user in the user profile; and
determine the preference based on the viewing history.
15. The system of claim 9 , wherein the control circuitry is further configured to determine the event associated with the second segment of the media asset comprises:
receive metadata associated with the second segment of the media asset; and
detect, based on the metadata, the event.
16. The system of claim 9 , wherein the control circuitry is further configured to determine the event associated with the second segment of the media asset comprises:
analyze video data associated with the second segment of the media asset; and
detect based on the analyzing, an event associated with the second segment.