This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
making_torrents_with_bitcomet [2010/06/04 00:25] greywizard |
making_torrents_with_bitcomet [2010/06/04 00:34] greywizard |
||
---|---|---|---|
Line 13: | Line 13: | ||
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: | 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 available the created |
* you must make sure that your BitComet client is running, that the // | * you must make sure that your BitComet client is running, that the // | ||
Line 44: | Line 44: | ||
Unless you have a special need, keeping the default setting " | 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# | + | 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' | + | 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.) | + | 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** | **Tracker Server and DHT Network Node List** | ||
Line 92: | Line 92: | ||
about the options, please read further: | about the options, please read further: | ||
- | * //Private Torrent//: < | + | * //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.]]. | * //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.]] | * //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.]] | ||
Line 98: | Line 98: | ||
* //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, | * //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) | + | **Output** (pathname for the generated |
The default pathname is the same with the one of the source file. If you want to change the pathname, please click {{: | The default pathname is the same with the one of the source file. If you want to change the pathname, please click {{: | ||
Line 130: | Line 130: | ||
After you finished all the settings and modifications, | 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. | + | 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 | And please make sure BitComet is started and seeding the task, so that others can download | ||
- | from you once they saved the .torrent file. | + | from you once they saved the //.torrent// file. |
Happy sharing! | Happy sharing! | ||