Jump to content

RSS Feed Support for x264-CTU


Computer Guru

Recommended Posts

Can you please add support for x264-CTU as a format in the RSS parser?

Here's a sample listing:

<item><title>24.S06E24.720p.HDTV.x264-CTU</title>
<link>http://www.mininova.org/get/716117</link>
<pubDate>Tue, 22 May 2007 02:43:48 -0700</pubDate>
<description>24.S06E24.720p.HDTV.x264-CTU</description><enclosure url="http://www.mininova.org/get/716117" length="-1" type="application/x-bittorrent" /></item>

NOTE: This is just for illustration purposes. Don't actually download it.

x264-CTU are MKV files, 1.2 GB in size, higher quality than HR.HDTV with superior sound and video.

Link to comment
Share on other sites

I dunno....

Maybe I should be looking at the 720p.hdtv section?

In that case, why does CTU show up in the GUI? (I don't see XOR or LOL or whatever in that window, only CTU)

EDIT:

Unless the x264 bit is the format?

At any rate, there is something that needs to be changed in the RSS Parser :)

Link to comment
Share on other sites

CTU is the release group.. it could as well be released by any other release group..

HDTV is the format..

it's larger than HR.HDTV, because it's 720p (1280x720 progressive), while HR (half-resolution or whatever) is not HD (high definition), thus smaller in size..

perhaps several new options in the format combobox? (720p.HDTV, 1080i.HDTV, 1080p.HDTV)

Link to comment
Share on other sites

OK :D

Dear uTorrent Developers,

Would you please consider adding support for H264-encoded HDTV rips at 720p resolution in the RSS parser?

Also, would it be possible for you to stop the term `CTU` from showing in the title of said RSS entries, seeing as it does not pertain to the actual title of the episode being err.. viewed?

Thank You,

CG

:D

Link to comment
Share on other sites

if I may add my 2 cents ... formats are being added from time to time. Why not make this list / strings (which I never used...) simply user definable ? So that if someone wants to add to this predefined list his own, he can ?

I see two simple ways to do it:

1. add such a list to the existing properties->advanced->UI lists

2. better yet - support the "&" (logical and) symbol to the filter capabilities. Currently only the "|" (or) is supported and it is only natural to have both "or" and "and" available . This way - anyone ('advanced level") can add any additional and conditions/strings to the filter. I would add also the some way to control the order uT should parse the conditions.

In other words - support "simple regex" ... here is also some code that may do it... http://www.cse.yorku.ca/~oz/

What do you think, Richard ?

Link to comment
Share on other sites

As has been requested over and over again. Sure, regular expressions would be easy to implement if it's just a case of using an existing library that'd double the size of µTorrent just for *one* measly feature. Alas, that's not gonna happen.

Link to comment
Share on other sites

lol, i know :P

Anyway, No need to parse out the CTU or the x264.

In the past, uTorrent only worked with this (raw data) feed: http://tvrss.net/feeds/legacy/unique

Now you can use uTorrent with this (post-processed) feed instead: http://tvrss.net/feeds/unique - with it only the show's name shows up now

The resolution stuff still needs adding though.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...