[#60210]
Written by: Mizery_Made [05/10/2007, 18:32]
just recently started messing with rss on this site, loving it. alot easier then
checking back here ever hour or two to see if somethings been upped. though,
here in the last couple of days, a few of the shows i bother to watch have
suffered from needing repacks/propers. is there a way to set things up so
azureus will catch the initial release, then if a proper is released then it
goes ahead and adds that aswell?
i've tampered around with the settings for a while, didn't really try too much
but i tried a few things and i couldn't devise a method of accomplishing this.
anyone with further experience then i have any ideas on the matter?
thanks
[#60346]
Written by: rippk [06/10/2007, 12:22]
i recently just setup rss feed and loving it as well. i have good success with
utorrent catching repacks and propers. i followed the tutorial and have eztv,
bt-chat and the other eztv clone setup. so that if one goes down, i can switch
feeds. works great
one cool thing that would be great is to set it up somehow so that it stops
downloading the original when the proper comes out. save some bandwidth! i'm
guessing this is more of a client issue than an rss/eztv issue .. but it would rock.
the funny thing about this whole downloading thing is thus. i generally
download from bittorent faster than i can record and reencode stuff on my pvr!!!
and the quality is much better, no commercials either. i only record on my pvr
if i'm actually watching it 'live' so i can pause and skip commercials if i want.
[#60366]
Written by: Mizery_Made [06/10/2007, 15:54]
i went looking and came across a second rss plugin for azureus, this one called
"scanerss." got to tampering with it, and it has a couple different options for
history. one of them is based on a hash of the torrent filename, so it would
prevent you from downloading the same torrent again, yet still catch any propers
or repacks that follow.
in toying with it, i tested it with "las vegas" which had a proper released this
week, with this hash history method, it caught both the original aswell as the
proper, so i think i'm going to give this one a shot come monday's releases, see
how it performs. *shrugs*
[#60370]
Written by: Mizery_Made [06/10/2007, 16:38]
rippk, since you have no problem catching the proper/repack releases,
maybe something you could do is set up a second set of rules specifically for
the proper/repack releases, then have the option to give "highest priority" to
it. wouldn't exactly be a full fix to your whole "stop old version, start
proper/repack" but it would be a step. that would then put the new release in
front of the older release meaning it'd finish before, might give you a chance
to be around to stop/delete the old release manually. *shrugs*
just an idea. though, i guess that would namely only have an effect if you only
have a few torrents going at a time, the rest being automatically queued.
*shrugs again*
[#60382]
Written by: Mizery_Made [06/10/2007, 18:31]
really? i might have to rethink using utorrent once version 1.8 is released then.
[#60389]
Written by: rippk [06/10/2007, 19:23]
thanks for doing some digging aydin and others. i'll certainly got vote )for
good measure) and eagerly await 1.8. of course, i could just upgrade my
connection or computer. but i'm just too cheap and poor! lol
while there ... might as well bug them to get rss working through webadmin also.
| 1 of 1 |
