mirror of
https://github.com/TheFrenchGhosty/TheFrenchGhostys-Ultimate-YouTube-DL-Scripts-Collection
synced 2024-11-10 06:24:14 +00:00
Minor grammar/syntax changes
- modify wsl/cygwin heading levels to be consistent with thefrenchghosty's existing files in docs folder - Clarify long-path'ed files as not being corrupt or problematic - tell the user they can organize files as they wish, but caveat emptor - exercise restraint by not adding section telling user to consider using linux
This commit is contained in:
parent
a39d9490c2
commit
c404623ace
3 changed files with 13 additions and 11 deletions
|
@ -1,6 +1,6 @@
|
|||
## About Paths
|
||||
|
||||
### What is a path
|
||||
### What is a path?
|
||||
|
||||
The path of a file or folder specifies its location on the filesystem. The path length refers to the total number of character in the path.
|
||||
- C:\Users\username\Pictures\Places\France\Paris.jpeg (a file path, 51 characters)
|
||||
|
@ -16,13 +16,13 @@ Windows has a 260-character path length limit for compatibility reasons. This me
|
|||
|
||||
It's possible for programs to use alternate methods to bypass the 260-character limit. This is because Windows' underlying NTFS filesystem supports "long paths" with lengths of up to 32,767 characters, [even since the days of Windows XP](https://stackoverflow.com/questions/265769/maximum-filename-length-in-ntfs-windows-xp-and-windows-vista). Incidentally, this is even higher than Linux's 4096-character limit.
|
||||
|
||||
However files and folders created by programs that support long paths will be impossible to manipulate in programs that don't support them, or in Windows itself. They are valid files, but will not be able to be easily opened, copied, moved, renamed, or deleted, without the use of special tools.
|
||||
However files and folders created by programs that support long paths will be impossible to manipulate in programs that don't support them, or in Windows itself. They will not be able to be easily opened, copied, moved, renamed, or deleted, without the use of special tools. The files themselves are perfectly valid and not corrupt, and having long paths is not a problem per se, just an inconvenience.
|
||||
|
||||
---
|
||||
|
||||
### Path lengths and the scripts
|
||||
|
||||
These scripts were designed to both neatly organize videos as well as preserve as much information about them as possible, since this information is often valuable to archivists. The names of both the videos and the folders they are stored in may include (but are not limited to):
|
||||
These scripts were designed to both neatly organize videos as well as preserve as much information about them as possible, since this information is often valuable to archivists. The names of both the videos and the folders they are stored in may include (in various combinations):
|
||||
- channel name,
|
||||
- playlist name,
|
||||
- upload date,
|
||||
|
@ -41,7 +41,7 @@ Other programs may work. (WIP)
|
|||
|
||||
"Metro" apps appear to support long paths. "Movies & TV" (built in to Windows 10), or VLC (from the Microsoft Store).
|
||||
|
||||
Video players running *inside* WSL do work. To get the videos to display, you need to set up an Xserver (e.g. Xming), or use MobaXterm which has one built in, and possibly install PulseAudio (untested). This is a somewhat complex process and is not recommended for beginners.
|
||||
Video players running *inside* WSL do work. To get the videos to display, you need to set up an Xserver (e.g. Xming), or use MobaXterm which has one built in, and possibly install PulseAudio (untested). This is a somewhat involved process and is not recommended for beginners.
|
||||
|
||||
---
|
||||
|
||||
|
@ -61,6 +61,8 @@ Enable a "Group Policy" setting introduced in recent versions of Windows 10 to [
|
|||
|
||||
Choose a shorter path by not saving files too deeply into the folder tree. This is not really an option for these scripts, if you already store them in the root of the drive.
|
||||
|
||||
Organize videos and their containing folders with your own organization system (i.e., shorten their names). This is an issue of personal preference. If you break the scripts because it can't files where it expects them to be, that is your problem to deal with.
|
||||
|
||||
---
|
||||
|
||||
### Further resources
|
||||
|
|
|
@ -1,11 +1,11 @@
|
|||
### Installation using Cygwin, Git Bash or similar:
|
||||
## Installation using Cygwin, Git Bash or similar
|
||||
|
||||
#### Known Issues
|
||||
### Known Issues
|
||||
* If you are receiving a permission denied error when attempting to execute python, [this thread](https://stackoverflow.com/questions/56974927/permission-denied-trying-to-run-python-on-windows-10) may be helpful.
|
||||
* Downloaded videos will likely exceed Windows' 260-character path length limit and not be playable out of the box. You should read more about [paths](docs/About-Paths.md) to familiarize yourself with the issue, as well as some potential workarounds.
|
||||
|
||||
|
||||
#### Required Software
|
||||
### Required Software
|
||||
In order to run these scripts, the following software packages must be installed:
|
||||
|
||||
* [Cygwin](https://www.cygwin.com/), [Git Bash](http://git-scm.com), or some other application that enables Bash functionality in Windows.
|
||||
|
@ -14,7 +14,7 @@ In order to run these scripts, the following software packages must be installed
|
|||
* [ffmpeg](https://www.ffmpeg.org/) - Make sure this is in your PATH.
|
||||
* [atomicparsley](https://github.com/wez/atomicparsley) (optional) - Make sure this is in your PATH.
|
||||
|
||||
#### Configuration
|
||||
### Configuration
|
||||
First, make sure that all dependencies are installed and your PATH is configured properly by opening your Bash terminal of choice and executing the following:
|
||||
|
||||
* `python --version`
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
### Installation using WSL:
|
||||
## Installation using WSL
|
||||
WSL allows the running of a modified Linux environment (Ubuntu, Debian, OpenSUSE, and more) inside Windows 10. Unlike a virtual machine, it can directly interact with Windows files on the hard drive.
|
||||
|
||||
Main benefits are that it's created by Microsoft, so it's more likely to be better supported. Benefits for the purposes of these scripts are the ability to keep dependencies (ffmpeg, atomicparsley, yt-dlp) up-to-date with package managers like apt or pip.
|
||||
|
@ -6,12 +6,12 @@ Main benefits are that it's created by Microsoft, so it's more likely to be bett
|
|||
However the setup process does necessitate a relatively large one-time download and storing of WSL's files (approximately 2GB) - users taking issue with this may consider the other options such as Cygwin or Git Bash. [Compare the above here.](https://askubuntu.com/questions/1042285/reduce-size-of-a-wsl-installation-ubuntu-18-on-windows-10)
|
||||
|
||||
|
||||
#### Known Issues
|
||||
### Known Issues
|
||||
* The latest version of WSL (WSL2) stores the Linux filesystem hierarchy ( /* ) inside a virtual hard disk file. To avoid this file ballooning in size ([and having to manually shrink it in the future](https://stephenreescarter.net/how-to-shrink-a-wsl2-virtual-disk/)), it's recommended to store the scripts and videos outside of the Linux filesystem, inside a Windows drive (e.g. "/mnt/c/" for "C:\\", or "/mnt/d/" for a drive mounted at "D:\\" )
|
||||
* Downloaded videos will likely exceed Windows' 260-character path length limit and not be playable out of the box. You should read more about [paths](docs/About-Paths.md) to familiarize yourself with the issue, as well as some potential workarounds.
|
||||
|
||||
|
||||
#### Required Software
|
||||
### Required Software
|
||||
Follow the "Manual Install" instructions in the [Windows Subsystem for Linux Installation Guide for Windows 10](https://docs.microsoft.com/en-us/windows/wsl/install-win10).
|
||||
|
||||
Once WSL is installed, download the latest [release](https://github.com/TheFrenchGhosty/TheFrenchGhostys-YouTube-DL-Archivist-Scripts/releases) and follow the "Installation (Linux)" section of this README.
|
||||
|
|
Loading…
Reference in a new issue