| Both sides previous revision
Previous revision
Next revision
|
Previous revision
|
making_torrents_with_bitcomet [2010/06/04 00:27]
greywizard |
making_torrents_with_bitcomet [2015/08/15 04:21] (current)
|
| ====== Making torrents with BitComet ====== | ====== 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/[[peers_seeds_torrent_tracker_dht_peer_exchange_pex_magnet_links#seeds|seeder]]) has to create first a small file called a "//.torrent//" file (e.g. //MySharedContent.torrent//). This file contains [[wp>metadata]] about the shared files and the eventual [[peers_seeds_torrent_tracker_dht_peer_exchange_pex_magnet_links#tracker|trackers]] for the torrent (such as [[wp>Hash_code|hash]] value, file size and name, [[peers_seeds_torrent_tracker_dht_peer_exchange_pex_magnet_links#tracker|piece]] size and hash, tracker IP etc.). | 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/[[peers_seeds_torrent_tracker_dht_peer_exchange_pex_magnet_links#seeds|seeder]]) has to create first a small file called a "//.torrent//" file (e.g. //MySharedContent.torrent//). This file contains [[wp>metadata]] about the shared files and the eventual [[peers_seeds_torrent_tracker_dht_peer_exchange_pex_magnet_links#tracker|trackers]] for the torrent (such as [[wp>Hash_code|hash]] value, file size and name, [[peers_seeds_torrent_tracker_dht_peer_exchange_pex_magnet_links#Pieces|piece]] size and hash, tracker IP etc.). |
| |
| In order for the others to be able to access (download) the content you want to share they must possess the //.torrent// file you have just created for that content first. Therefore you'll have to make sure that you propagate it through some means. The most used and easy way is to upload the //.torrent// file on a [[peers_seeds_torrent_tracker_dht_peer_exchange_pex_magnet_links#torrent|torrent]] index web site, from where other users who are searching for the respective content will be able to download it and after that, their clients will automatically initiate BitTorrent downloads from you, by using the metadata information contained inside the //.torrent// file to locate the eventual tracker and eventually you as a seeder as well as the other peers in the swarm. | In order for the others to be able to access (download) the content you want to share they must possess the //.torrent// file you have just created for that content first. Therefore you'll have to make sure that you propagate it through some means. The most used and easy way is to upload the //.torrent// file on a [[peers_seeds_torrent_tracker_dht_peer_exchange_pex_magnet_links#torrent|torrent]] index web site, from where other users who are searching for the respective content will be able to download it and after that, their clients will automatically initiate BitTorrent downloads from you, by using the metadata information contained inside the //.torrent// file to locate the eventual tracker and eventually you as a seeder as well as the other peers in the swarm. |
| 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 //.torrent// file first in order to initiate the download. This is easiest done by uploading the //.torrent// file on a torrent index site (use the on-site specific instructions for the detailed steps on doing that); | * 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 //.torrent// file first in order to initiate the download. This is easiest done by uploading the //.torrent// file on a torrent index site (use the on-site specific instructions for the detailed steps on doing that); |
| * you must make sure that your BitComet client is running, that the //.torrent// file is added as a task in your [[bitcomet_task_list|Task List]] and that the respective task is running (seeding) as well (this will be indicated by an upward red arrow-like icon in front of your task). | * you must make sure that your BitComet client is running, that the //.torrent// file is added as a task in your [[bitcomet_task_list|Task List]] and that the respective task is running (seeding) as well (this will be indicated by an upward red arrow-like icon in front of your task). |
| |
| |
| After that all that's left for you to do, is to upload the //.torrent// file on one or more index sites and wait for other peers to find the stuff you shared on that site, download the //.torrent// file and start downloading from you. Therefore, don't forget to leave your client and the task running continuously for a while (at least until you can see another one or two additional seeds created inside the swarm). | After that all that's left for you to do, is to upload the //.torrent// file on one or more index sites and wait for other peers to find the stuff you shared on that site, download the //.torrent// file and start downloading from you. Therefore, don't forget to leave your client and the task running continuously for a while (at least until you can see another one or two additional seeds created inside the swarm). |
| | |
| | <html><span style=color:darkred;font-weight:bold>Attention!</span><br></html><file>If you upload your torrent on private trackers' index sites you'll be required to re-download the .torrent file you |
| | uploaded and add it in your Task List before being able to seed (at least most of them will ask you this). |
| | That is because they modify the .torrent file and embed pass-keys in it in order to permit access to the tracker only |
| | for their members. |
| | |
| | Therefore, make sure that you remove from your Task List the task which was added when you clicked on the "Make Torrent" |
| | button. |
| | After that re-download the .torrent file which you uploaded to the index site, then in the Task Properties dialog |
| | that pops up, point it to the location where the files of the torrent reside and after the automatic hash-check that |
| | will follow, it will be added as a seeding task in your Task List.</file> |
| | **Therefore, make sure that you read very attentively the uploading rules for every index site you will use.** |
| |
| Below you will find a detailed description of the Torrent Maker UI and it's options. | Below you will find a detailed description of the Torrent Maker UI and it's options. |
| Unless you have a special need, keeping the default setting "Auto" is recommended. | Unless you have a special need, keeping the default setting "Auto" is recommended. |
| |
| 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#what_is_rubbish_data_and_why_am_i_downloading_so_much_of_it|garbage data]] for peers who have unreliable connections (the hash-check is performed only after the whole piece is received by a BitTorrent client). | 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#what_is_rubbish_data_and_why_am_i_downloading_so_much_of_it|garbage data]] for peers who have unreliable connections (the hash-check is performed only after the whole piece is received by a BitTorrent client). |
| |
| 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't get very big (it stays under, let's say, 1MB) that should be OK for very large file-sets. HTTP index sites can handle the download of .torrent files of this size, relatively easy, and a smaller piece size results in a far more efficient transactions inside the swarm, faster initial propagation of the pieces and less rubbish data for other peers. | 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't get very big (it stays under, let's say, 1MB) that should be OK for very large file-sets. HTTP index sites can handle the download of //.torrent// files of this size, relatively easy, and a smaller piece size results in far more efficient transactions inside the swarm, faster initial propagation of the pieces and less rubbish data for other peers. |
| |
| 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** |
| about the options, please read further: | about the options, please read further: |
| |
| * //Private Torrent//: <html><span style=color:Fuchsia>Attention!</span></html> Use this <html><span id="private">option</span></html> **only** if the tracker rules require it (i.e. you intend to upload this torrent on a private tracker). This option when checked, will enable the private flag in the torrent file which will automatically disable PEX, DHT, LT-Seeding, [[torrent_exchange|Torrent Exchange]] ([[torrent_share_and_torrent_archive|Torrent Share]] in older versions) and downloading from the eDonkey and Kad Networks through the [[using_emule_plugin|eMule plugin]], for that specific torrent, in any BitComet client downloading it (as well as in all other clients which comply to the private flag specifications). Basically the only peers a client will be able to obtain when downloading the contents of this torrent, will be those provided by the tracker specified in the .torrent file. (Read more on [[inside_bitcomet#private_trackers|private trackers]]) | * //Private Torrent//: <html><span style=color:Fuchsia>Attention!</span></html> Use this <html><span id="private">option</span></html> **only** if the tracker rules require it (i.e. you intend to upload this torrent on a private tracker). This option when checked, will enable the private flag in the torrent file which will automatically disable PEX, DHT, LT-Seeding, [[torrent_exchange|Torrent Exchange]] ([[torrent_share_and_torrent_archive|Torrent Share]] in older versions) and downloading from the eDonkey and Kad Networks through the [[using_emule_plugin|eMule plugin]], for that specific torrent, in any BitComet client downloading it (as well as in all other clients which comply to the private flag specifications). Basically the only peers a client will be able to obtain when downloading the contents of this torrent, will be those provided by the tracker specified in the //.torrent// file. (Read more on [[inside_bitcomet#private_trackers|private trackers]]) |
| * //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.]] |
| * //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, from the eDonkey and Kad Networks, as well. [[using_emule_plugin|See Using eMule plugin.]] (This needs the eDonkey plugin to be enabled on the [[bitcomet_options|Options page]]). | * //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, from the eDonkey and Kad Networks, as well. [[using_emule_plugin|See Using eMule plugin.]] (This needs the eDonkey plugin to be enabled on the [[bitcomet_options|Options page]]). |
| |
| **Output** (pathname for the generated .torrent file) | **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 {{:tm_05.png|}} to navigate to the destination or enter a path manually. | The default pathname is the same with the one of the source file. If you want to change the pathname, please click {{:tm_05.png|}} to navigate to the destination or enter a path manually. |
| After you finished all the settings and modifications, please do not forget to hit the "Make torrent" button, to finish. | After you finished all the settings and modifications, please do not forget to hit the "Make torrent" button, to finish. |
| |
| 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! |
| |
