This repository has been archived by the owner on Nov 18, 2022. It is now read-only.
Sort inner files for optimal download order #364
Comments
hugbug
added a commit
that referenced
this issue
Apr 22, 2017
hugbug
added a commit
that referenced
this issue
Apr 22, 2017
- reordering inner files after adding nzb to queue; - reordering inner files after adding direct renaming; - new command “GroupSortFiles” in api-method “editqueue”.
hugbug
added a commit
that referenced
this issue
Apr 22, 2017
subcommand “SF” of remote command “-E“
To fix: |
hugbug
added a commit
that referenced
this issue
Apr 30, 2017
hugbug
added a commit
that referenced
this issue
Apr 30, 2017
hugbug
added a commit
that referenced
this issue
May 1, 2017
hugbug
added a commit
that referenced
this issue
May 23, 2017
hugbug
added a commit
that referenced
this issue
Oct 9, 2017
hugbug
added a commit
that referenced
this issue
Oct 9, 2017
- reordering inner files after adding nzb to queue; - reordering inner files after adding direct renaming; - new command “GroupSortFiles” in api-method “editqueue”.
hugbug
added a commit
that referenced
this issue
Oct 9, 2017
hugbug
added a commit
that referenced
this issue
Oct 9, 2017
hugbug
added a commit
that referenced
this issue
Oct 9, 2017
hugbug
added a commit
that referenced
this issue
Oct 9, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When nzb-file is added to queue the files listed within nzb can be in a random order. To ensure download of archive parts in correct order the files must reordered (alphabetically).
This feature is a prerequisite for unpack during downloading which is the ultimate goal.
Even without advanced unpack the sorting of inner files have another usage: when archive files come in sorted order it is possible to start watching of video file directly from archive (when using video players supporting playback from archives).
When direct renaming is active (#362) the sorting must be done again after the correct file names become known.
The text was updated successfully, but these errors were encountered: