General > Current & Future L-E Projects
Yawara, yet again \o/
gumbaloom:
124 regular anime episodes
1 animated movie
1 live action movie
1 end of series OVA
-gumbaloom
gumbaloom:
Well Yawara 41 is out folks, hope you have enjoyed the recent spate of fast releases.
Yawara is now a joint project with Froth-Bite and I'm pleased to say that Yawara 42 is edited and will be typeset soon and work is already far advanced on the 2nd OP and ED which we will need from Ep 46 onwards.
For those who need catch up I put up batch torrents today of 21 - 25, 26 - 30 and 31 - 35. I'll prolly do a 36 - 41 batch torrent once Ep 46 is released.
Just an interesting statistic for you, with Ep 41 and those 3 batch torrents I went through circa 30GB of torrent bandwidth on my new server today :o . Its a good job I like Yawara isnt it ? XD . But please do try and help your fellow leecher out if you can by seeding those batch torrents as I can't keep my box on there all the time I dont have an unlimited supply of bandwidth to consume ;) .
Regards
-gumbaloom
Anax:
I'm working at getting my BT client set up to seed everything nicely again. Unfortunately, the 21-25 batch torrent doesn't work for me! :( Anyway, I'll be seeding everything else as I can. :)
chaokwan:
The torrent file for the Yawara batch ep21-25 doesn't seem to be working for me. I get an error msg. I use Azureus. Is the torrent file ok?
Anax:
I've figured out what the problem is--this particular file was created with Azureus, and it looks like Azureus did something weird in that one specific instance. The "dht_backup_enable" item in the "azureus_properties" part of the torrent should be an integer, but is instead a string (containing the value "1").
A *second* problem is that Azureus reads the file enough to cache its own internal copy of the .torrent file, which will keep the error coming back, even if you fix the file.
Look in your Azureus cache (...wherever Azureus keeps stuff on your system.../active/) for a file called 3938659FE003D69303ADFCB4E7774BB9A5193B0F.dat (and possibly that same name .dat.bak) You'll need to delete this file before continuing. You should probably shut down Azureus, then delete this file, then start back up again.
Once you've done that, you can load a repaired .torrent file into Azureus (my version is attached here as .torrent.txt, to get past the attachment filters--sorry), and all should be well. Because the change is outside of the info section of the .torrent, it doesn't change the tracker signature, and all continues to work as expected. I might ask that someone from L-E upload my repaired version (or repair the file themselves) to .torrent sources (I got mine from scarywater), since this problem is going to hit any user of a recent Azureus version--and the workaround (as you see above) isn't trivial.
Thanks.
(Edit: Oh, and I found the torrent going with 11 peers and no seeds--everbody was almost almost almost done, too. Happily seeding away, now.)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version