- Installer command line parameters
- Command line interface
- Portable mode
- Linux support
- Windows XP support
Installer command line parameters
NSIS is used for installer creation so all its command line parameters are available (like silent install or specifying output directory). For list of possible parameters read NSIS documentation: section Installer Usage.
Additionally are available next parameters:
- /NODESKTOPICON - do not create Desktop icon
- /PORTABLE - install portable version
Command line interface
|Switch to Simple Mode, paste URL from Clipboard and start downloading
|Switch to Convert Mode, paste URL from Clipboard and start converting
|Switch to Advanced Mode, paste URL from Clipboard and start analysis
|Use URL and mode from magnet link and start processing
|Ignore translation libraries
|Override directory where to place downloaded files
|Override format to convert to (Convert Mode only). Expected extension without a dot e.g.
|The only acceptable value is
exit. When specified, program exits after downloading
|Override preset to use. Expects name of preset configured via menu
|Override source quality to use. Acceptable values:
smallest_video, 144p, 240p, 360p, 480p, 720p, 1080p, 1440p, 2160p, 3072p, best_video, 32k, 64k, 128k, 192k, 256k, best_audio
Magnet link format: s3dyd://action=URL, where action is one of 'download', 'convert', 'analyze'. Example:
3dyd.exe --magnet s3dyd://download=https://www.youtube.com/watch?v=gtktg9hbC_g
If program installed not portable, it registers in the system custom protocol s3dyd. In this case magnet links can be run without specifying program path. Example (will work only if program installed nonportable): s3dyd://analyze=youtube.com/watch?v=gtktg9hbC_g.
Program can be used in portable and non-portable mode. The difference is where the program stores its settings and intermediate data (like search results, feeds content etc). In non-portable mode the settings are stored in registry, data is stored in application data folders of current user. In portable mode all this is stored in the program directory.
32-bit and 64-bit versions can be placed in the same directory, intermediate data and program settings in this case will remain be separate.
Program is being made keeping Wine in mind, so everything should work ok under it.
Better to set Windows version for the program to
Windows XP otherwise some UI parts may be displayed incorrectly.
If you see the error containing
SSL connect error (35), go to menu
Tools Options Advanced and in
net.libcurl select the one containing
Actually that is most likely because libgnutls package, that is needed by Wine to provide schannel functionality, is not installed. This library is an optional dependency for Wine (or at least that is so on some distributions) so it could be not installed automatically. Installation of that package should resolve the problem. Package name differs across Linux distributions and Wine versions so no exact name here.
Windows XP support
Minimum supported Windows version for 32-bit program version is Windows XP SP2. Non-SSE-capable CPUs are also supported. In case of 64-bit program version, minimum supported Windows version is Vista.
Note, as of February 2017 it looks like Youtube switched to more secured HTTPS version that is not supported by Windows XP native SSL backend. If you are getting an error containing
SSL connect error (35), go to
Tools Options Network libcurl and select the one containing
So if something does not work, you could notify about it since this is not always noticeable from development point of view.
Help Miscellaneous Integration