feat: SG-44605: Optimize the loading and scrubbing of S3/Streaming media in RV - #1380
Open
deltag0 wants to merge 22 commits into
Open
feat: SG-44605: Optimize the loading and scrubbing of S3/Streaming media in RV#1380deltag0 wants to merge 22 commits into
deltag0 wants to merge 22 commits into
Conversation
Signed-off-by: deltag0 <ioan.1931@gmail.com>
Signed-off-by: deltag0 <ioan.1931@gmail.com>
Signed-off-by: deltag0 <ioan.1931@gmail.com>
Signed-off-by: deltag0 <ioan.1931@gmail.com>
Signed-off-by: deltag0 <ioan.1931@gmail.com>
Signed-off-by: deltag0 <ioan.1931@gmail.com>
Signed-off-by: deltag0 <ioan.1931@gmail.com>
deltag0
requested review from
bernie-laberge,
cedrik-fuoco-adsk and
eloisebrosseau
as code owners
August 17, 2026 18:00
Signed-off-by: deltag0 <ioan.1931@gmail.com>
Signed-off-by: deltag0 <ioan.1931@gmail.com>
Signed-off-by: deltag0 <ioan.1931@gmail.com>
Signed-off-by: deltag0 <ioan.1931@gmail.com>
Signed-off-by: deltag0 <ioan.1931@gmail.com>
Signed-off-by: deltag0 <ioan.1931@gmail.com>
Signed-off-by: deltag0 <ioan.1931@gmail.com>
Signed-off-by: deltag0 <ioan.1931@gmail.com>
deltag0
marked this pull request as draft
August 17, 2026 20:12
Signed-off-by: deltag0 <ioan.1931@gmail.com>
Signed-off-by: deltag0 <ioan.1931@gmail.com>
deltag0
marked this pull request as ready for review
August 19, 2026 15:36
Signed-off-by: deltag0 <ioan.1931@gmail.com>
Signed-off-by: deltag0 <ioan.1931@gmail.com>
Signed-off-by: deltag0 <ioan.1931@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
feat: Optimize the loading and scrubbing of S3/Streaming media in RV
Summarize your change.
shared:protocolDescribe the reason for the change.
Previously, when media hosted on shotgrid was opened in OpenRV, to view a new file, there had to be a request made over the network, which was adding 1-2 seconds of latency every time a user jumped to a new file. This made scrubbing virtually impossible because of the delay. To improve this problem, the idea was to cache the media's raw bytes locally, so that RV can decode the bytes locally instead of having to establish a new HTTP connection for a new file. This would work, but would require us to manually jump to the new file for the caching to start. So, background threads to download every file were spawned.
I believe the number of threds for this process should be proportional to the amount of media the user loaded, as a lot of the time the threads should be inactive, waiting on the network.
Soon after, it was found that even if all media was cached before a user streams it on RV, scrubbing would still be painful because there were FFMPEG reader clones which had to establish their own connection, so they still added latency. To fix this, the connections were established at load time, with background threads, when the media is opened (after pre-loading).
Describe what you have tested and on which operating system.
Add a list of changes, and note any that might need special attention during the review.
If possible, provide screenshots.