Max number of connections per torrent default is the maximum number of peers to which you can be connected on a torrent per default.
Sets the default number of seed and peer connections each torrent can have. A higher-than-optimal number here is the primary cause in reports of computer lagging when Azureus runs. Usually, 30 to 60 connections per torrent will suffice. Set it to or and your transfers may slow as protocol overhead increases noticeably.
Max connections globally is the total number of peers, for all torrents, to whom you will allow connections from this client. Prioritize most completed files where your client resources are limited Azureus will make more attempts to complete file downloads, and therefore usable, instead of maximising transfer rates. Allow multiple connections from the same IP leave this disabled unless you have a specific need for it or enjoy people leeching your bandwidth. Use lazy bitfield sends altered bitfield information when torrents switch from downloading to seeding.
At least Optonline detects the normal bitfield and sends spoofed packets to both peers causing the clients to terminate the connection. You should only use this option if you need to.
Prioritize first and last piece of file s tries to download the first and last pieces of individual files in the torrent. This allows previewing certain media files before they are completed. Those files are usually large, so this is of little use.
VLC Media Player is a better alternative. Ignore peers with these data ports ignores peers who have set these port numbers for their incoming connections. If your firewall complains that Azureus is trying to send email, then your firewall may be brain-dead and you should add 25 here.
Lower time here means more sensitiveness for smooth internet traffic. Files options [ edit ] This set of preferences allows you to fine tune the way Azureus handles the files it creates. Default directory defines a directory path you would like your torrents to automatically download into. This is one of the most useful settings here, as it enables you to relocate your data directory for new downloads.
Allocate and zero tells Azureus to pre-allocate the space to be used by the file and fill that space with zeroes before it starts downloading the actual data of the file. This means that there is no chance that later Azureus will stall because there is not enough space on the destination disk.
As the file is created at once, this option will also minimize fragmentation of the hard drive in comparison to incremental allocation.
If this option is checked, incremental file creation can not be used. Note: Default for this option is 'disabled', but enabling this option might be beneficial for most users, as the whole files to be downloaded would be created when torrent is added to Azureus. Enable incremental file creation will make Azureus increase the size of the file only as it is data is downloaded which means that you can trigger torrents that may take up a lot of space and that space will in reality remain available until actually needed to store file content.
If this option is checked, pre-allocation can not be used. Note: Selecting this option will result in Azureus only reserving as much disk space as is necessary for writing the last piece it has received.
For example, if it first received piece of a piece torrent, it would reserve space for pieces in the torrent. If then it next received piece , the reserved space would increase to half the complete size of the torrent as pieces would be alloacated. So, although only two pieces 0. Because you may have several torrents doing this at once, as well as other processes writing to the disk, this method will result in more fragmentation than using pre-allocation.
It may also cause unnecessary peaks to hard disk usage. Additionally, as pieces are downloaded in random order and priority based on piece rarity, this option is very seldomly useful. Append data to files as downloaded Note: new functionality in version 4. Truncate existing files will remove additional bytes at the end of a downloaded file e.
The option is most useful with MP3 files, to which some media players and inxeders like Windows Media Player, Roxio, etc. See also info about Existing data file length too large error message. Re-check pieces when download is done instruct Azureus to do a check at the end of download to be completely sure no piece of a file was missed.
If any piece doesn't pass the error correction, it is simply discarded and downloaded again. This option may cause occasional high CPU usage on slow systems. Enforce exclusive file write access locking across torrents This option was setup to deal up with issues involving multiple torrent. If you are getting errors that prevent download try removing this check. If you don't do this then Azureus will conduct a review of the download on startup to check the torrent content, which can take time.
You can specify the interval between saves which will then be the maximum time you would loose if you had to restart. You can also instruct Azureus to save the information about peers to speed up restarts. Update resume data every X minutes defines how frequently resume data is written to the. On crash-restart check entire file for completed pieces From error correction perspective this is good, but it may also cause quite heavy disk activity when starting the session.
Read also Vuze did not shutdown tidily. Save peer connections for quick reconnects caches information about the peers it's connected to and stores it in the. This cached information makes it possible to connect to peers and seeders even in the case of the tracker going offline. Max peers to save sets the maximum number of peer connections to cache per torrent , default is Auto-prioritize files with extension Individual file priorities can be viewed on the files tab of the advanced view.
Confirm when deleting data request a confirmation before deleting downloaded data. Deleted data does not go to the recycle bin. Typically the low-level information files of the operating system. Move deleted files to the Recycle Bin prevents the files being deleted completely for recovery purposes. Backup configuration files for recovery purposes tell Azureus to keep backup copies of the configuration files. At each Azureus session, the old configuration files are copied as.
Beta versions since 4. The deletion options have also been grouped better: Completion Moving [ edit ] Move completed files will move the files from the download directory to another location when they are completed. Directory is the directory you want torrents to be moved to when they finish downloading and start seeding. Unchecking this option will result in torrents staying in the download directory.
It can be hard to tell the difference between finished and incomplete torrents however, so it's recommended they be separated Move. Can be useful to keep track of. This is useful if you have certain torrents you want saved somewhere else, otherwise when they finished downloading they'd just get moved into the completed directory with the others. Torrents [ edit ] Save. Whenever Azureus opens a torrent, it will place a copy of the. Save directory.
Enter the directory you want to save your. Save backup. You may want to save a backup of your. Checking this option will make Azureus place a copy of the. By default add new torrents in a stopped state. If you want new torrents to be in "stopped" state rather than the normal "queued".
Import new. Import Directory. Sets the directory to be monitored. Sets how often to scan the directory for new. Begin stopped. Will load the torrent in a stopped state rather than queuing it. Decoding Character Sets [ edit ] These options control Vuze's reaction to strange character in file names of files included in a torrent. Removal Rules [ edit ] These options control how and when torrents are automatically removed from Vuze.
By default, Vuze will only remove updates for Vuze components when they are no longer needed. Some trackers can issue an error response such as "torrent is not authorized by this tracker". You may configure Vuze to automatically drop the torrent when such error messages are received. This type of error message from a tracker can be generated if the torrent was never authorized by the tracker, or when the tracker administrator wishes to prevent further distribution of bittorrent content for a particular torrent.
The latter case is common among trackers which distribute fansubbed anime, which eventually gets licensed - at which time distribution should cease. By enabling these features, you can help to prevent further distribution of bittorrent content that is no longer authorized for distribution.
Performance Options [ edit ] Friendly hash checking by default, Azureus uses friendly hash checking. You can disable this in the configuration. Friendly hash checking does not lock up your system while it does the hash checking. For faster systems, this should not be a problem but with slower machines, it can lead your system to be unusable until all the hash checking is done.
Enable disk cache enables disk cache, this could help reduce disk fragmentation. Note about active torrents : Like explained in the table above, all status information about the currently active torrents is stored in the file 'downloads.
Deleting them will remove all status information about your current torrents. So, be careful with those files. Note about plugins : Although deleting the settings file azureus.
You have to uninstall plugins through the uninstall wizard in Vuze menus or manually remove plugin files the subdirectory and the files either from the configuration directory or the Vuze program directory. You can create a file containing configuration presets i. Once the settings have been applied the file will be renamed to have a suffix of ". Note 1 : If you want to add all active torrents back into Vuze, you should copy across the active directory to your new configuration directory.
If you aren't able to add your torrents back in from the location that you saved your torrents to, then you can always copy the.
Note 2 : Bencoded files are specially encoded files used by torrent programs. There are special Bencode editors, which enable proper handling of the information.
Note 3 : A built-in command to reset configuration to default values was introduced in version 4. The command resides in the Mode options, where a Reset button will clean options stored in azureus. Jump to: navigation , search. Copy to Clipboard.
For example, to list all the torrents in Vuze, and get their name and the identifier used in other calls to identify the torrents, use. The best documentation for what is supported is the code itself. This documents the various methods and their arguments for example, what fields are supported on a torrent.
Most remote uis that support connecting to Transmission will also connect to Vuze Web Remote. The plugin inherits the options of a generic 'Web Plugin' those controlling port, protocol, pairing, access control.
It also adds a few options to supply a local link to the HTML web UI, control over whether or not 'uninteresting' downloads are made available typically this applies to downloads associated with Vuze component updates and whether or not to log interactions.
This view was added in Vuze version 5.
0コメント