CPU: i5 2500 or i7 2600 depending on how much you're willing to spend; or wait a few months for Bulldozer
RAM: 4-8GB
GPU: if you want one, get something like a nVidia GTS450 or similar

(19/04/2011 08:22 AM)ProperBritish Wrote:  but from experience, you don't really need to encode that much unless you're getting .ts files from a source in Japan yourself.

Any self respecting fansub group should encode direct off transport streams.  You can get those from Japanese P2P networks like share, Perfect Dark, if you don't have an in house capper (which like almost no groups have).

And from what I've seen, a lot of groups that don't have .*ts sources still re-encode whatever raws they use, either because they think they can improve the efficiency or quality of the raw's encoding, or they don't want to be seen as groups that remux raws (which is tied with bad implications).

(19/04/2011 08:22 AM)ProperBritish Wrote:  Then use mkvmux to make the mkv

MKVMerge (from MKVToolNix package)

(19/04/2011 08:22 AM)ProperBritish Wrote:  [SS] Infinite Stratos - 02 (1280x720 h264) [90008EDD].mkv
by group SS (StrikeSubs i think)

Static Subs.  Way way way more famous than Strike Subs (StrikeS).

(19/04/2011 08:22 AM)ProperBritish Wrote:  The CRC/hash thingies are usually only used to make it easier for people to search for your files.

Lolwut?

No, the hash is there so people can check the integrity of their file.

(19/04/2011 08:22 AM)ProperBritish Wrote:  You can of course use photoshop to make fancy hardcoded subs, but I've never done that :/

You fansub?

(20/04/2011 02:35 AM)Assassinator Wrote:  

(19/04/2011 08:22 AM)ProperBritish Wrote:  The CRC/hash thingies are usually only used to make it easier for people to search for your files.

Lolwut?

No, the hash is there so people can check the integrity of their file.

Might not be the purpose, but it actually can be quite effective to search via the hash.

(20/04/2011 03:35 AM)ZiNgA BuRgA Wrote:  

(20/04/2011 02:35 AM)Assassinator Wrote:  

(19/04/2011 08:22 AM)ProperBritish Wrote:  The CRC/hash thingies are usually only used to make it easier for people to search for your files.

Lolwut?

No, the hash is there so people can check the integrity of their file.

Might not be the purpose, but it actually can be quite effective to search via the hash.

If the actual purpose was to make it easy to search, then they would something more sensical than a random string of hex numbers.

So something like SSIS01HD (SS Infinite Stratos 01 HDTV Release) instead of 90008EDD.

The searching thing can only be a side effect at best.

But "SSIS01HD" gives no additional information to the main filename.  Not to mention, say, if Strike Sub decided to do it...
Random strings are used as identifiers in a number of places, eg MKV segment IDs.  It can be said that the CRC allows you to both verify the file as well as provide an easy identifier to search for, as opposed to supplying an SFV file.

(20/04/2011 03:57 AM)ZiNgA BuRgA Wrote:  But "SSIS01HD" gives no additional information to the main filename.

"SSIS01HD" gives the advantage that it's predictable.  That is, knowing it, you can predict episode 12 to be "SSIS12HD".  On the other hand, to know the hash of the twelfth episode, you will need to either know the full filename, or have the actual file.  If you have to search the full file name first, then that sort of defeats the purpose of "easier to search" because you have to do 2 searches, 1 for the file name, then again with the hash.

(20/04/2011 03:57 AM)ZiNgA BuRgA Wrote:  Random strings are used as identifiers in a number of places, eg MKV segment IDs.  It can be said that the CRC allows you to both verify the file as well as provide an easy identifier to search for

That's different because it's both computer generated and computer read (so assigning something random would be easier than assigning something sensible).  And also because it needs absolute uniqueness (if 2 segments have the same segment ID, bad stuff would probably happen).

(20/04/2011 03:57 AM)ZiNgA BuRgA Wrote:  as opposed to supplying an SFV file.

Because the way fansubs are released (progressively), it would mean a separate sfv file for every episode, which causes all sort of annoyances.

(This post was last modified: 20/04/2011 04:37 AM by Assassinator.)

(20/04/2011 04:32 AM)Assassinator Wrote:  "SSIS01HD" gives the advantage that it's predictable.  That is, knowing it, you can predict episode 12 to be "SSIS12HD".  On the other hand, to know the hash of the twelfth episode, you will need to either know the full filename, or have the actual file.  If you have to search the full file name first, then that sort of defeats the purpose of "easier to search" because you have to do 2 searches, 1 for the file name, then again with the hash.

I often use it for searching for direct links.  Easy to get a hash off a torrent site, then paste the hash into a DDL search.
File names are just as predictable, so this "identifier" you're giving is really just unnecessarily duplicating info.

(20/04/2011 04:32 AM)Assassinator Wrote:  That's different because it's both computer generated and computer read (so assigning something random would be easier than assigning something sensible).  And also because it needs absolute uniqueness (if 2 segments have the same segment ID, bad stuff would probably happen).

Computers can generate identifiers from filenames quite easily.  They can even append a hash or uniquifier to ensure uniqueness.

(20/04/2011 04:32 AM)Assassinator Wrote:  Because the way fansubs are released (progressively), it would mean a separate sfv file for every episode, which causes all sort of annoyances.

Because it seems that containers like MKV don't embed their own hash...
Only anime seems to be done that way anyway.  Other TV shows never seem to have hashes appended.  Most transfer protocols (torrent, TCP etc) have error detection anyway, so verifying integrity actually isn't terribly important.