This shows you the differences between two versions of the page.
making_torrents_with_bitcomet [2010/06/04 00:27] greywizard |
making_torrents_with_bitcomet [2015/08/15 04:21] |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Making torrents with BitComet ====== | ||
- | In order to share a single file or a file-set on the [[bittorrent|BitTorrent]] Network, the person who wants to share the content (and who will be the initial uploader/ | ||
- | |||
- | In order for the others to be able to access (download) the content you want to share they must possess the // | ||
- | |||
- | A question which often puzzles the minds of novice BitTorrent uploaders is the one about the trackers. At the creation time of the // | ||
- | |||
- | If you do not intend to upload the torrent on a private tracker index site then you should **use only** publicly **open trackers** which allow connections from anyone without requiring prior registration. Also in this case **you shouldn' | ||
- | |||
- | Once your // | ||
- | |||
- | Therefore, as a bottom line remember that once the .torrent file is created, in order to actually start sharing the contents it defines, you'll need to make sure that these conditions are met: | ||
- | |||
- | * you must make available the created .torrent file to the rest of the world (potential downloaders) since every person who will download the contents of the torrent will need the // | ||
- | * you must make sure that your BitComet client is running, that the // | ||
- | |||
- | The BitComet client has an embedded Torrent Maker dialog which will easily let you create the necessary // | ||
- | |||
- | After that all that's left for you to do, is to upload the // | ||
- | |||
- | Below you will find a detailed description of the Torrent Maker UI and it's options. | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | ===== Open torrent maker Dialog ===== | ||
- | |||
- | * Method 1: Drag-and-drop source file or folder to BitComet main Window or floating Window. | ||
- | * Method 2: Click " | ||
- | * Method 3: Click the " | ||
- | |||
- | * Torrent maker Dialog pops up:\\ {{: | ||
- | |||
- | ===== Choose source file or folder to make torrent ===== | ||
- | |||
- | **Source File** | ||
- | |||
- | Please first choose the type of source file, " | ||
- | |||
- | **Piece Size** | ||
- | |||
- | Unless you have a special need, keeping the default setting " | ||
- | |||
- | Note however, that for large files or file-sets (between a few GB and several tens of GB, or larger) the piece size in automatic mode may tend to become very large (2-4MB) in order to keep the .torrent file of a small size. This is not a very good thing, since a large piece size will often lead to slower piece propagation in the initial phase of the swarm, less efficient transactions inside the swarm and will often result in large amounts of [[torrent_related# | ||
- | |||
- | Therefore if you see that the default setting results in large piece size, you could experiment with manual settings of the piece size (trying to keep it no bigger than 1MB). As long as your .torrent file doesn' | ||
- | |||
- | In general, you should try to find a compromise between the piece size and the resulting size of the .torrent file, but as a thumb rule try not to get over 1MB piece size even for very big file-sets. If your .torrent file gets too big, then it's a sign that you should probably split your file-set and upload it in different, related torrents (e.g. MyContent - Part I.torrent, MyContent - Part II.torrent etc.) | ||
- | |||
- | **Tracker Server and DHT Network Node List** | ||
- | |||
- | Fill in the URL of the tracker server and DHT network node list in the blank filed. | ||
- | |||
- | But there are some points you need to pay attention when entering URLs, therefore, please read further on: | ||
- | |||
- | ---- | ||
- | |||
- | ==== BitComet Multi-server syntax specifications ==== | ||
- | |||
- | This section describes the syntax for the case when you want to add multiple tracker URLs which share the same servers. | ||
- | |||
- | **Server groups:** BitComet connects to all servers according to groups. And those URLs that share the same tracker servers are classified as one group, or in another words, the same server with different ports is regarded as one group. And BitComet only connects to one of the URLs in every group. Keep reading for instructions about how to write in this field: | ||
- | |||
- | 1. Torrent URLs: [ [Group A Server 1], [Group B Server 1], [Group C Server 1] ]. These URLs should be written like this in the blank field of Tracker Server and Node list: | ||
- | |||
- | * Line 1: Group A Server 1 | ||
- | * Line 2: Group B Server 1 | ||
- | * Line 3: Group C Server 1 | ||
- | |||
- | 2. Torrent URLs:[ [Group A Server 1, Group A Server 2, Group A Server 3]] These URLs should be written like this in the blank field of Tracker Server and Node list: | ||
- | |||
- | * Line 1: Group A Server 1 | ||
- | * Line 2: |Group A Server 2 (Please remember this " | ||
- | * Line 3: |Group A Server 3 | ||
- | |||
- | 3. Torrent URLs: [ [Group A Server 1, Group A Server 2], [Group B Server 1] ] These URLs should be written like this in the blank field of Tracker Server and Node list: | ||
- | |||
- | * Line 1: Group A Server 1 | ||
- | * Line 2: |Group A Server 2 | ||
- | * Line 3: Group B Server 1 | ||
- | |||
- | < | ||
- | |||
- | node:// | ||
- | For example: node:// | ||
- | |||
- | ==== Options ==== | ||
- | |||
- | Note: The default settings work well in most situations. If you want to know more | ||
- | about the options, please read further: | ||
- | |||
- | * //Private Torrent//: < | ||
- | * //Add DHT nodes to tracker list//: This enables using the DHT Network to retrieve peers for this torrent. [[using_dht_tracker|See Using DHT Tracker.]]. | ||
- | * //Align file to piece boundary//: This option, when enabled, will create a set of padding files in order to avoid pieces overlapping 2 different files, for multi-file torrents. [[align_file_to_piece_boundary|See Align File to Piece Boundary.]] | ||
- | * //Enable search for Long-Time Seed when downloading//: | ||
- | * //Calculate ED2K link for each file//: This option, when enabled, basically activates the eMule plugin and passes it the ED2K link for each file of the torrent, in order to attempt finding and downloading them concurrently, | ||
- | |||
- | **Output** (pathname for the generated .torrent file) | ||
- | |||
- | The default pathname is the same with the one of the source file. If you want to change the pathname, please click {{: | ||
- | |||
- | ===== Publisher Info ===== | ||
- | |||
- | **Publisher Info** (Optional) | ||
- | |||
- | {{: | ||
- | |||
- | * By ticking " | ||
- | |||
- | |||
- | |||
- | ===== Web Seeding ===== | ||
- | |||
- | **Web Seeding** (Optional) | ||
- | |||
- | Web seeding was implemented in 2006 as the ability of BitTorrent clients to download torrent pieces from an HTTP source in addition to the swarm. The advantage of this feature is that a site may distribute a torrent for a particular file or batch of files and make those files available for download from that same web server; this can simplify seeding and load balancing greatly once support for this feature is implemented in the various BitTorrent clients. In theory, this would make using BitTorrent almost as easy for a web publisher as simply creating a direct download while allowing some of the upload bandwidth demands to be placed upon the downloaders (which normally use only a very small portion of their upload bandwidth capacity). Read more [[http:// | ||
- | |||
- | If you know the HTTP source of a file that is the same as the source file (or the URL of the source file), you can enter the URL here. This is helpful for downloaders to acquire data, or in other words, download, from the HTTP server, in this way improving the downloading speeds and torrent health. | ||
- | |||
- | * When the torrent content is for a single file, a specific URL should be entered. For example:\\ {{: | ||
- | |||
- | |||
- | * If the published torrent is for a directory (muti-files), | ||
- | |||
- | < | ||
- | |||
- | |||
- | After you finished all the settings and modifications, | ||
- | |||
- | Note: Remember! When you have made a .torrent file, you must publish the torrent on a torrent site. | ||
- | And please make sure BitComet is started and seeding the task, so that others can download | ||
- | from you once they saved the .torrent file. | ||
- | Happy sharing! | ||
- | |||
- | ---- | ||
- | -[[bitcomet_options|Previous Page]] -[[http_ftp_batch_download|Next Page]]\\ | ||
- | -[[start|Main Index]] |