2010-07-06, 02:58 | Link #1 |
encoding n00b
Join Date: Jul 2010
Location: Southern Brazil
|
Encoding documentation for total newbies
Hello,
I am a Brazilian fansubber, specialized in editing, and I am willing to learn to encode. That's enough introduction; now for the facts that outline the issue. I have been reading some Avisynth documentation (at its wiki), but it's not helping me a lot. It's generally quite overwhelming when present, or else absent/incomplete. The biggest issue is that there seem to be hundreds of filters for each thing I may want to do and there's no telling which way I should go. It's probably safe to say it's useless to me, although it will most certainly help more experienced people. I'm also not that much knowledgeable about technical stuff like banding, grain, artifacts, and other video problems (or audio problems for that matter); I know when something looks/sounds horrible, but I can't tell what the problem is from this technical POV. I tried to read stuff up in Wikipedia but soon gave up. As if that wasn't enough trouble, the x264 settings just confuse me. Too many settings, too little explanation of what they do and how they affect stuff. Doing some search I found this and this, I'll be trying those out soon. By now you see what the problem is. I have trouble with finding documentation that will give me the information I need without making me want to bang head against wall because I don't have a clue of what it's telling me. I also need the documentation I read not to be too outdated, otherwise I could just go read about encoding in DivX3. So, the request: can you please point me to good newbie guides on the many aspects of encoding that won't confuse me too hard? Also, a question: perhaps I would need someone to guide me? Not that there is anyone with the knowledge required and the time to properly do that... Thanks in advance. EDIT: Perhaps it would be interesting if the experienced people (/me looks @ TheFluff) shared a bit on their path to encoding knowledge. If nothing else, at least I'll know the learning curve is indeed as steep as it has been seeming to be and I'm not the first to have issues with it. Last edited by Hinoe; 2010-07-06 at 03:03. Reason: new idea |
2010-07-06, 05:45 | Link #3 |
Excessively jovial fellow
Join Date: Dec 2005
Location: ISDB-T
Age: 37
|
The problem isn't really that you're dumb or that the tutorials are bad, it's that the concepts involved simply aren't that easy to understand. Interlaced video may seem easy at a glance but the implications are wide-ranging and telecine has never been a trivial process. I can try to (and frequently have) explain things in more newbie-friendly ways, but I cannot make the underlying concepts easier to understand. The fact that "encoding" covers a very large range of distinct topics doesn't really help, either.
The "traditional" way of learning these things is the one you're using: banging your head against a wall for months at an end. I did it mostly the same way, by hanging around people who seemed to know what they were doing and listening to what they were saying despite not understanding much of it, printing out various documentation and reading it on the bus, experimenting with things on my own and failing again and again and again. I can't really offer any help with teaching methods; the way I learned is a pretty good way to lose interest in encoding. Most of the above applies to theoretical concepts; learning filtering is in large part a matter of experimentation, especially since filtering is subjective. I was never very good at it (mostly due to a lack of patience) and what I know is mostly outdated now anyway. I prefer not to filter very much, anyway. x264 options aren't that interesting either; sure it's nice to be able to tweak a few options and it's useful to understand how the encoder works, but it's not essential. Especially not since you should be using the presets/tunings, which were put there by people who most definitely know what they're doing. In the end, learning to encode is largely a matter of learning by doing; I'm not knowledgeable because I've spent a lot of time studying this, I'm knowledgeable because I've been doing stuff related to it, talking about it, explaining it and experimenting with it for years on end. I think the only recommendation I can give is to find someone that will put up with stupid questions, ask a lot, read a lot and do a lot of trial and error things, and you'll eventually pick things up. edit: also, it's important to understand what you're doing. Don't just copypaste filter chains or x264 settings just because, always try to understand why they look like they do.
__________________
Last edited by TheFluff; 2010-07-06 at 07:19. |
2010-07-06, 10:03 | Link #5 |
Fansubber/Scanlator
Join Date: Dec 2009
|
I think you could use this website for information about some filters and their options.
|
2010-07-06, 12:13 | Link #6 |
encoding n00b
Join Date: Jul 2010
Location: Southern Brazil
|
Hello,
I guess although it is sad that the learning curve is indeed as steep as it seems, it is also good to know that everyone else has been through this. I hope you guys can put up with my noob questions, then . I, for one, were always one of the first to go and tell people to RTFM; it's the first time that I'm actually not helped by The F***ing Manual (is swearing allowed here? The rules aren't very specific about it, unless I'm blind) as much as I'd like... This is actually interesting, it tickles my knowledge thirst; I'm going to keep at it. Other than that, thanks for the support, and thanks KoutetsuAnes for the link, I'll check it out. |
2010-07-06, 14:40 | Link #8 |
encoding n00b
Join Date: Jul 2010
Location: Southern Brazil
|
jfs,
What you have conveyed in so few words is my issue (and apparently the issue of many others) exactly. To me, such general overview, if one was ever made, should point out things like "what [banding/halo/artifacts/grain/blur/blah/...] is, how to detect it, what filters are available to fix it, and what you should be careful with when using them" (aka "hey, don't warpsharp to death"), or "what x264 settings you should REALLY avoid and why" (hello huge lookahead, I hear you cause blocking in anime + crf). It doesn't need to explain every single detail about the filters/settings, just give a general overview, and perhaps a few links to more details for the search-lazy. From that point on, it would probably be much easier to tackle stuff like filter documentation, because what you read suddenly isn't complete random garbage anymore. |
2010-07-06, 16:17 | Link #10 |
Fansubber/Scanlator
Join Date: Dec 2009
|
You could check this forum too it has good info.
You could also lurk in #encoders @ irc.rizon.net even though it's mostly empty or just lurk in irc channels until you get to know some encoders. |
2010-07-06, 19:58 | Link #11 | |
encoding n00b
Join Date: Jul 2010
Location: Southern Brazil
|
Quote:
Come on, I'm serious. There are so many changeable settings for a reason, right? ......right? Hmm... This is going to get somewhat off-topic, but... There's this encoder I know (considered one of the greatest anime encoders of Brazil afaik). He said that he noticed that if he used "for example, x264 --crf 18 -o video.mkv script.avs, the image quality is actually worse than x264 --crf 18 --no-mbtree -o video.mkv script.avs", due to blocking appearing in the non -no-mbtree video. He mentioned this issue was more noticeable when working with anime and crf, but didn't say what other ways of producing it there were. He's using x264 build 1659 ("yeah that's right I haven't updated it to 1666"), but says he noticed this since the introduction of lookahead. He also added that the issue has been lessened heavily since the first days of lookahead, and that it was way worse at the beginning. -- UPDATE -- He just gave me some screenshots. I should tell you I DON'T SEE ANY DIFFERENCE HERE, and then again the resolution is a joke (640x360 for HD source lol), but he claims he does. http://img341.imageshack.us/img341/4877/mbtree.png -> with lookahead http://img192.imageshack.us/img192/4519/nombtree.png -> --no-mbtree http://img266.imageshack.us/img266/193/lossless0001.png -> source (BD -> avs -> screen taken in vdub) used for the encodes Also, that was crf=20. -- UPDATE FOR SOME MORE SCREENS -- Now for some crf=18 720p: x264 options and output: http://pastebin.com/MxVMppCW with mbtree: http://img822.imageshack.us/img822/5807/commbtree.png without mbtree: http://img708.imageshack.us/img708/6870/semmbtree.png "This setting also generates a horrible amount of banding". -- I SHOULD SAY, FOR GREAT JUSTICE, THAT: -- I don't see any banding OR blocking... Either he's a visual genius, or I'm blind. Also, his friend said the with mbtree one has "quadriculado", layman's term for blocking. Dunno what to make of this now. (that my laptop screen sucks. Hello, HP.) Last edited by Hinoe; 2010-07-06 at 20:20. Reason: I have edited this post so many times I don't even need a reason anymore. :) |
|
2010-07-06, 20:20 | Link #12 | ||
x264 Developer
Join Date: Feb 2008
|
Quote:
Quote:
Almost anyone who describes themselves as an "encoder" is a clueless idiot who does nothing but poke at random buttons all day in the deluded belief that it helps them produce better results. Almost without fail, they know absolutely nothing about the internals of the options that they are setting. Don't be an "encoder". |
||
2010-07-06, 20:38 | Link #13 | |||
encoding n00b
Join Date: Jul 2010
Location: Southern Brazil
|
Quote:
Quote:
Quote:
Now, now, there's no need for all that rage. He made a claim, I'm not sure whether it's true or not, it's been put for analysis, that's all there is too it. |
|||
2010-07-06, 21:24 | Link #14 | |
x264 Developer
Join Date: Feb 2008
|
Quote:
Furthermore, you've already committed the cardinal sin of encoding by comparing two videos encoded at different bitrates and making a judgement about quality. |
|
2010-07-12, 15:54 | Link #15 |
Senior Member
Author
Join Date: Jul 2007
Location: Virginia Tech
|
You also tend to learn quite a lot through practice and trial/error. Start with something minimalist, like x264 settings somebody else tells you to use and maybe a few filters, try an encode, and see if you like it.
__________________
|
2010-07-17, 10:28 | Link #18 |
Translator, Producer
Join Date: Nov 2003
Location: Tokyo, Japan
Age: 44
|
Being a good encoder is like being a good scientist.
It's not what you know, but how good you are at knowing what you need to know and learning it. Relying on others is fine to start out, but if you can't learn on your own you'll never be more than a pale imitation of your mentor. (or mentar, for that matter).
__________________
|
2010-07-17, 22:31 | Link #19 | |
Klipsch
Join Date: Oct 2007
Location: Frontier
|
Of course.
Quote:
|
|
2010-07-22, 13:20 | Link #20 |
BECAUSE its moe moe!
Join Date: Aug 2008
Location: Massachusetts
Age: 39
|
I'm not an "encoder" or a "fansubber" but what I do know i learned from experimentation and reading the provided documentation. Personally I think its the best way to learn something instead of having to always go ask someone something when an issue comes up, There are instances where this is actually necessary but not with encoding.
|
|
|