Torrent Creator needs a finishing touch...

[deadlikeoscar]

I haven't tried using the Torrent Creator up until today. When I did, the upload failed on the tracker due to the private flag not being set. I know that the Torrent Creator has a private flag already, but I believe that it needs to be set during torrent file creation, not after, for it to work properly on private trackers. I had to use uTorrent to create the torrent file and then all went as planned.

[markybob]

I haven't tried using the Torrent Creator up until today. When I did, the upload failed on the tracker due to the private flag not being set. I know that the Torrent Creator has a private flag already, but I believe that it needs to be set during torrent file creation, not after, for it to work properly on private trackers. I had to use uTorrent to create the torrent file and then all went as planned.

good point. i just finished programming this in. it's in svn if you wanna check it out and test it

[Lord_neo]

good implementation..

thanks guys!!

[deadlikeoscar]

What was that, 27 minutes!?! I can think of no other bittorrent team alive that can compete with that. Bravo! I will test it out as soon as I can.

[markybob]

What was that, 27 minutes!?! I can think of no other bittorrent team alive that can compete with that. Bravo! I will test it out as soon as I can.

that's what we like to hear... thanks, glad to help. this just goes to show that we really do listen to our users. i dont use private trackers or private torrents, so i dont run into these situations, which in turn often means that i dont realize there's a problem until someone speaks up.

[Lord_neo]

Another little feature??

A bar on the advanment of the torrent creation, in % may be fine

[deadlikeoscar]

Not sure why it took me a whole month to try the Torrent Creator out again but I have found that for some reason, it is still being rejected by the tracker as not having the private flag set in the torrent file when I try to upload the torrent to the tracker. There has to be something "non-standard" about the private flag that is being set by Deluge and it is being rejected on that basis alone. I will look around for some open source projects that use the private flag and see if maybe we can come up with what is wrong.

[Ux64]

Torrent Creator doesn't seem to support 4 MiB or even larger pieces. I have seen a lot of 4 MiB pieces being used with downloads from 8-16 gigabytes. I don't know if bittorrent currently supports larger ones?

And how about adding AUTO size option, which would choose piece size based on content size? So users wouldn't need to think about this. I love programs that choose right values without me being bothered by tons of different kind of technical questions.

- Thanks!

[markybob]

Torrent Creator doesn't seem to support 4 MiB or even larger pieces. I have seen a lot of 4 MiB pieces being used with downloads from 8-16 gigabytes. I don't know if bittorrent currently supports larger ones?

And how about adding AUTO size option, which would choose piece size based on content size? So users wouldn't need to think about this. I love programs that choose right values without me being bothered by tons of different kind of technical questions.

- Thanks!

no. the most allowed is 4MiB. this isnt a deluge thing, but a bittorrent thing. look in utorrent or azureus and you'll see the same limits.
and no; the piece size has a lot to do with your needs. do you want a large torrent file, but small pieces? or do you need a small torrent file?

[Ux64]

no. the most allowed is 4MiB. this isnt a deluge thing, but a bittorrent thing. look in utorrent or azureus and you'll see the same limits.

Yep. Ok, I guess when it's time for it, bittorrent protocol implements larger pieces.

and no; the piece size has a lot to do with your needs. do you want a large torrent file, but small pieces? or do you need a small torrent file?

Ok, I didn't even think about that part. I were thinking about peer 2 peer communication traffic quantity with large number of small peaces and needlessness of huge number of small pieces. User downloading 16 gigabyte file isn't using a modem (5kb/s) to download it. And distribution efficiency if there is only one seed, 1000 peers starting to download it at same time (then having a 1000 pieces would help). But yes, that's a good remark, this is very complex issue. So that's it. There is no easy way to implement auto feature which would meet all needs.

I remember tons of people nagging ed2k about having too large pieces (9.5 megabytes). It can restrict distribution efficiency with slow connections when large number of peer start downloading simultaneously.

- Thanks