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.
The SLR scraper currently sets filenames for every resolution possible, and every fisheye projection possible when the video is fisheye. It adds both
MONO
andTB
for 360. All of this can be determined via their API...I'm not sure if it adds up to much, or how the DB compression works, but compare 5,847 bytes of "filenames" when every single name possible is used for a fisheye projection video with 580 bytes when only the actually possible ones are used. There are 40,000 some odd scenes on SLR if you scrape everything from every studio...
Gigantic wall of text
vs.
Before:
After:
It can now also determine the correct projection
For 360 video as well as other fisheye projections
The entire scraper might need a looksie (by someone more knowledgeable!!!) to see where the API can be used instead; we're already grabbing that JSON anyways, but then using colly for almost everything.