Guest User

Untitled

a guest
Feb 22nd, 2012
706
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 23.29 KB | None | 0 0
  1. ............ NFO .............
  2. --
  3. - -
  4. - The SD x264 TV Releasing Standards 2012 -
  5. LTTTT-
  6. -++TT++
  7. - L[ INTRO ]- -
  8. - -
  9. - x264 has become the most advanced video codec over the past few years. -
  10. - Compared to XviD, it is able to provide higher quality and compression at -
  11. - greater SD resolutions. It also allows better control and transparency over -
  12. - encoding settings. With CRF in the mix, we can also ensure that a diverse -
  13. - array of material will get the most appropriate bitrate for them and not -
  14. - arbitrary and fixed sizes. This standard aims to bring quality control back -
  15. - to SD releases. There are many standalone players/streamers such as TviX, -
  16. -Hour, WDTV HD Media Player, Boxee, Xtreamer, PS3, XBOX 360, iPad, & -
  17. - HDTVs that can playback H264 and AAC encapsulated in MP4. -
  18. - -
  19. - The SD x264 TV section was formed to separate releases from the ruleless -
  20. - world of TV-XviD. This document will cover the rules and guidelines for -
  21. - only SD resolution x264 television rips. -
  22. - -
  23. LTTTT-
  24. -++TT++
  25. - L[ RELEASE RULES ]- -
  26. - -
  27. - Compliance with this document is optional as of its pre date, and -
  28. - mandatory as of 2012-02-22 16:00 UTC. -
  29. - -
  30. - Video: -
  31. - - Sources requiring resize are to be cropped and resized using sharp -
  32. - resizers such as Lanczos/Lanczos4, Spline36, or Blackman. Bicubic is -
  33. - banned. -
  34. - - HD video taken from the decoded HD output of a set-top box (e.g. -
  35. - component, DVI, HDMI) may be used as a source; source must be tagged -
  36. - in dirname as AHDTV. Decoded output of PDTV or DSR sources is banned. -
  37. - Releases taken from a natively recorded transport stream shall be tagged-
  38. - as HDTV, PDTV, or DSR. Dupes are as follows: HDTV > AHDTV > PDTV > DSR. -
  39. - AHDTV captures must be done at the native format of the channel, e.g. -
  40. - 720p or 1080i. -
  41. - - Sources that sideconvert 1080i to 720p (such as BellTV) are allowed but -
  42. - must be tagged as PDTV or DSR. -
  43. - - If there is a question as to the validity of a source, the release -
  44. - may be nuked source.sample.requested_<reason.for.nuke> (e.g. -
  45. - source.sample.requested_suspicion.of.analog.source) within 24 hours of -
  46. - pre. The group has 24 hours from the nuke to pre a RARed SOURCE.SAMPLE -
  47. - that is at least 10 seconds in length in order to document that the -
  48. - source is valid. Failure to provide source proof or providing bad -
  49. - source proof shall result in the release remaining nuked, and it may -
  50. - then be propered. -
  51. - - Improper IVTC methods that result in jerky playback, such as Force -
  52. - Film, are banned -
  53. - - Interlaced video sources must be deinterlaced with a smart deinterlacer -
  54. - such as Yadif. FieldDeinterlace is banned. -
  55. - - Group watermarks of any kind on the video are banned -
  56. - - Intros, outros, betweenos, or any other form of defacement of the -
  57. - episode are banned -
  58. - - "Native" refers to the standard in which the video was produced (e.g. -
  59. - NTSC or PAL). NTSC produced video is native to NTSC, PAL produced video -
  60. - is native to PAL. PAL produced video that is broadcast in NTSC is -
  61. - converted. NTSC produced video that is broadcast in PAL is converted. -
  62. - - Converted video that has significant artifacting (e.g. blended frames) -
  63. - and cannot be reversed to native must use CONVERT tag -
  64. - - Converted video that does not have significant artifacts does not need -
  65. - convert tags and may not be nuked for the conversion -
  66. - - Native releases are allowed after those tagged CONVERT. Use NATIVE tag. -
  67. - -
  68. - Audio: -
  69. - - Allowed audio formats are VBR AAC LC (Low Complexity). -
  70. - - Average bitrate on AAC audio must be 96 - 160 kbps. -
  71. - - AAC audio must be normalized and downconverted to stereo. -
  72. - - Nero and Apple encoders are recommended. FFmpeg is banned. -
  73. - - Dupes based on audio format are forbidden and must be tagged INTERNAL -
  74. - - Multiple language audio tracks are allowed and must be listed in NFO -
  75. - - Dupes are not allowed based on multiple audio tracks -
  76. - - Severe audio drops resulting in one full missing word or otherwise the -
  77. - inability to understand material dialogue is considered to be a -
  78. - technical flaw and may be propered -
  79. - - Audio that is 120ms or more out of sync or drifts more than 120ms -
  80. - between any two points (e.g. needing -80 at one and +40 at another) is -
  81. - considered to be technically flawed and may be propered -
  82. - -
  83. - Framerate: -
  84. - - IVTC or deinterlacing must be applied as needed -
  85. - - 50/60fps video may be released at 50/60fps or 25/30fps. Releasing true -
  86. - 25/30fps video at 50/60 is considered a technical flaw. -
  87. - - In rare cases, 25/50Hz sources should be IVTC'd to 24 or 30 fps. -
  88. - - In rare cases, 30/60Hz sources should be IVTC'd to 25fps. -
  89. - Failure to apply IVTC when needed is a technical flaw. -
  90. - -
  91. - Codec/Container: -
  92. - - Video codec must be x264 (8-bit depth). -
  93. - - Container must be MP4. -
  94. - - You will have 30 days from latest x264 rev date to update in order to -
  95. - maintain all bug fixes and improvements in the x264 codec -
  96. - - Stripping or falsifying encode information in the file header is banned -
  97. - - Custom muxing tools are permitted; however, output must be compatible -
  98. - with standard demuxers. -
  99. - - Custom Matrices are allowed -
  100. - - Encoded colorspace must be 4:2:0. -
  101. - - Deblocking must be used; values are at the discretion of the group. -
  102. - (default is enabled, 0:0 settings) -
  103. - - No setting can go below what is specified by --preset slow. -
  104. - - Keyframe interval (--keyint) must be at least 200 and at most 300. It -
  105. - is recommended to be 10*framerate (film=240, PAL=250, NTSC=300). -
  106. - - Minkeyint must be 30 or less -
  107. - - Colormatrix must be set to source specification. If not specified by -
  108. - source, bt709 must be used for sources with resolution greater than or -
  109. - equal to 1280x720 (e.g. HDTV and some PDTV) and sources with lower -
  110. - resolutions must use bt601 (e.g. DSR and some PDTV). -
  111. - - Constant Rate Factor (--crf) must be as follows: -
  112. - -TT -
  113. - - Compressibility - CRF - General Examples - -
  114. - ++++ -
  115. - - High - 19-20 - Scripted, Talk Shows, Poker, Animation - -
  116. - - Medium - 21-22 - Documentary, Reality, Variety - -
  117. - - Low - 23-24 - Sports, Awards, Live Events, Competitive- - -
  118. - - - - Reality - -
  119. - L++- -
  120. - - x264 parameters shall not vary within a release -
  121. - - Zones (--zones) are forbidden. -
  122. - - Any deviation in CRF from given examples must be specifically justified -
  123. - in the NFO. Use discretion when deviating CRF by matching the -
  124. - compressibility of the show to a corresponding CRF value. CRF values -
  125. - below 19 and above 24 are never permitted. -
  126. - - As a general suggestion, average video bitrate in excess of 1500kb/s -
  127. - is a sign that a higher CRF value should be chosen, when possible -
  128. - - Allowed parameters for --tune (optional) are film/grain/animation -
  129. - - Level 3.1 must be respected. -
  130. - - Suggested command line: -
  131. - x264.exe --crf ## --preset slow --level 3.1 --colormatrix bt709 -o -
  132. - out.h264 in.avs -
  133. - -
  134. - Resolution: -
  135. - - WS HDTV and WS PDTV sources with greater than 720px horizontal res must -
  136. - be cropped as needed and resized to 720px width and mod2 height to -
  137. - maintain proper AR. -
  138. - - WS PDTV sources with horizontal source res of 720-704px must be cropped -
  139. - as needed and only height must be resized to the proper anamorphic AR -
  140. - using mod2. Upscaling/downscaling is forbidden. -
  141. - - All other sources, including FS HDTV, must be cropped as needed and -
  142. - resized to 640px width and mod2 height to maintain proper AR. -
  143. - - When cropping, remove everything that is not actual picture, including -
  144. - black or other colored borders, duplicate lines, and full-time tickers. -
  145. - Removing or retaining fading edges is at capper's discretion and shall -
  146. - not be considered undercropped or overcropped. -
  147. - - In the case of varying crops, crop to the most common frame size (e.g. -
  148. - pitch/primary view in sports). -
  149. - - Actual picture area may be over- or under-cropped by 1px maximum per -
  150. - side. More than 1px on any side is considered a technical flaw. -
  151. - - Encoded Video resolution must be within 2% of the original aspect ratio -
  152. - To calculate AR error (%): (Original AR - Release AR)/Original AR * 100 -
  153. - OAR = (SourceWidth-CropLeft-CropRight)/(SourceHeight-CropTop-CropBottom)-
  154. - Release AR = EncodedWidth / EncodedHeight -
  155. - -
  156. - Subs: -
  157. - - Optional, but encouraged -
  158. - - Text based format is preferred (e.g. SubRip, SubStation Alpha, etc). -
  159. - - Subtitles must be in "Subs" directory. -
  160. - - Burned subtitles will only be allowed when the source exhibits such -
  161. - subtitles in the picture itself -
  162. - - Subtitles cannot be used as a basis for a dupe -
  163. - - Group marks in subtitles are banned -
  164. - -
  165. - Packaging: -
  166. - - Releases must be packed in RAR file format. -
  167. - - Rars may be in 15, 20, or multiples of 50 MB. 15 and 20 MB sizes must -
  168. - contain 1-101 files. Multiples of 50 MB must contain 10-101 files. -
  169. - 1MB = 1,000,000 bytes. -
  170. - - Multi-episode releases with no clear delineation such as credits must -
  171. - not be split -
  172. - - RAR compression must not be used -
  173. - - Recovery and MD5 record are optional -
  174. - - Encryption or password protection is forbidden -
  175. - - Must have SFV and NFO -
  176. - - RAR, SFV, and sample files must have unique, lowercase filenames with -
  177. - the group tag. -
  178. - - Missing SFV or RAR(s) on all sites is considered a technical flaw. -
  179. - Corrupt RARs (errors on extraction) are considered technical flaws. -
  180. - SFVFix and RARFix are not permitted. Uploading a missing SFV or RAR to -
  181. - all presites after pre is not permitted. Release REPACK. -
  182. - -
  183. - Credits/Previously On: -
  184. - - Previously on footage is optional, but suggested to be included -
  185. - - Full end credits must be included if they contain show content or -
  186. - outtakes/bloopers. End credits are optional and suggested if they are -
  187. - clean, and purely optional in other cases. -
  188. - -
  189. - Samples: -
  190. - - REQUIRED! -
  191. - - 50-70 seconds in length and in a separate folder marked as Sample -
  192. - - Must be taken from the episode, not encoded separately -
  193. - - Stream samples are recommended for any questionable issue with the -
  194. - source, e.g. no IVTC possible -
  195. - -
  196. - Propers: -
  197. - - Propers are only permitted in the case of a technical flaw in the -
  198. - original release (e.g. Bad IVTC, Interlacing, missing footage, bad crop,-
  199. - commercials, bad x264 settings used, bad source, etc.) -
  200. - - Scrolling or other alert messages added by a station (e.g. weather, -
  201. - Amber alerts) must be at least 30 seconds in length in order to -
  202. - nuke/proper -
  203. - - Drops with missing footage but no missing dialog must be at least 2 -
  204. - seconds long in any one instance to be considered a technical flaw -
  205. - - Proper reason must be clearly stated in nfo, including timecodes and -
  206. - extent of the flaw when appropriate -
  207. - - Sample of propered release is encouraged -
  208. - - Qualitative propers are not allowed -
  209. - - Flaws (such as drops) present in any optional content are not a flaw -
  210. - and shall not be nuked or propered. -
  211. - - Propers based upon the rules set forth here are allowed only on -
  212. - releases that come after this document goes into effect -
  213. - -
  214. - Internals: -
  215. - - Internals are allowed to be pred for any reason, including releases -
  216. - with technical flaws or those done with alternate codecs, containers, -
  217. - or settings for experimental purposes -
  218. - - Any severe technical flaws or deviations must be mentioned in the NFO -
  219. - - With the exception of the following rule, internal releases may only be -
  220. - nuked for severe technical flaws or deviations that are not mentioned -
  221. - in the NFO -
  222. - - Using DIRFIX.iNTERNAL to avoid a dupe nuke is banned, and such -
  223. - dirfixes shall be nuked fix.for.nuke -
  224. - -
  225. - Directory Naming: -
  226. - - Show.Name.SXXEXX.Episode.Title.HDTV.x264-GROUP -
  227. - - Show.Name.YYYY.MM.DD.Guest.Name.HDTV.x264-GROUP for daily or other -
  228. - dated shows -
  229. - - Episode title and guest name are optional -
  230. - - Show.Name.PartXX.HDTV.x264-GROUP for miniseries -
  231. - - ALL others are FORBIDDEN. (e.g 0x00 000 EXX.EP.TITLE PART.VI) -
  232. - Sport: -
  233. - - League.YYYY.MM.DD.Event.EXTRA.TAGS.HDTV.x264-GROUP -
  234. - - Competition.YYYY-MM.Event.EXTRA.TAGS.HDTV.x264-GROUP -
  235. - Using just the year is only permitted if the event is once per year -
  236. - (e.g. a WWE PPV). In the case of leagues which have seasons that span -
  237. - multiple years, it is permissible to tag the release with just the years-
  238. - of the season. Inclusion of MM and DD is mandatory for all constantly -
  239. - running shows (e.g. WWE). -
  240. - If there is no league, the sport needs to be used instead -
  241. - The following are some examples of correct directory names: -
  242. - - EPL.2010.01.01.Manchester.United.vs.Arsenal.HDTV.x264-GROUP -
  243. - - TNA.Impact.2010.03.02.HDTV.x264-GROUP -
  244. - - WWE.WrestleMania.2010.PPV.HDTV.x264-GROUP -
  245. - - Tennis.US.Open.2011.Final.Player1.vs.Player2.HDTV.x264-GROUP -
  246. - - Different shows that have the same title in different countries (e.g. -
  247. - The Marriage Ref) must have the ISO 3166-1 alpha 2 country code in the -
  248. - directory name, except for UK shows (e.g. The.Marriage.Ref.UK not -
  249. - The.Marriage.Ref.GB). ISO country code is not needed for the original -
  250. - show (e.g. The.Marriage.Ref.US is forbidden). -
  251. - - Different shows with the same name in the same country produced in -
  252. - different years must have the year of the first season in the directory -
  253. - name, e.g. Human.Target.2010 and Doctor.Who.2005. Year is not needed -
  254. - for the first show with a particular name. -
  255. - - Channel name (e.g. National.Geographic, History.Channel) shall not be -
  256. - tagged on any normal series starting after this ruleset's effective -
  257. - date. Miniseries and single-episode docus may optionally be tagged with -
  258. - the channel name. -
  259. - - The use of audio format tags such as AAC, and AAC.x.x is FORBIDDEN -
  260. - - READ.NFO tag is allowed; however, discretion is recommended -
  261. - - PROPER.READ.NFO is NOT allowed. The NFO is REQUIRED to have a reason; -
  262. - therefore, the tag is redundant. -
  263. - - All repacks must include detailed reason as to why it's being repacked -
  264. - in the nfo -
  265. - - Other permitted tags are: PROPER, REPACK, RERIP, REAL, UNCUT, DUBBED, -
  266. - SUBBED, iNTERNAL, OAR, PPV, CONVERT, NATiVE -
  267. - - Acceptable characters in naming a directory include (NO spaces or -
  268. - double dots - single dots ONLY): -
  269. - -
  270. - ABCDEFGHIJKLMNOPQRSTUVWXYZ -
  271. - abcdefghijklmnopqrstuvwxyz -
  272. - 0123456789._- -
  273. - -
  274. - Nukes: -
  275. - Releases must be nuked for any of the following reasons: -
  276. - - Any valid proper listed in the propers section -
  277. - - Missing nfo, or missing Sample -
  278. - - Invalid directory naming format -
  279. - - Mislabeled directory that could prevent finding the release in a -
  280. - dupecheck, including incorrect season/episode/date or incorrect title -
  281. - - Dupe -
  282. - - Releases may not be propered for bad tagging or missing nfo/sample -
  283. - -
  284. - Fixes: -
  285. - - The following fixes are allowed: NFOFix, SampleFix, DirFix, SyncFix, -
  286. - ProofFix -
  287. - - DirFix requires NFO and NFO must state which release is being fixed -
  288. - - The original release shall be unnuked when a valid fix is released -
  289. - - A proper may not be released for an issue that was fixed, unless the -
  290. - fix does not completely correct the issue -
  291. - -
  292. LTTTT-
  293. -++++
  294. - The SD x264 TV Releasing Standards 2012 (2012-02-22) -
  295. - -
  296. LTTTT-
  297. -++TT++
  298. - L[ GROUPS ]- -
  299. - -
  300. - TVx2642012 rules created by the following groups: -
  301. - -
  302. - ASAP BAJSKORV C4TV D2V DiVERGE FTP KYR -
  303. - LMAO LOL MOMENTUM SYS TLA YesTV -
  304. - -
  305. LTT-
  306. LT\ Thanks to the x264 developers for their assistance in /T-
  307. LT\ determining assistance in determining the best /T-
  308. L\ mix of encode settings.
Advertisement
Add Comment
Please, Sign In to add comment