Zarxrax wrote:Yea, and avisynth+ is looking pretty sweet now. Vaporsynth is conceptually a nice thing, but I don't see it getting to the point avisynth is for a LONG time.
I wouldn't disagree with that, the problem with VapourSynth is that the script structure REQUIRES you to learn how it works, while AviSynth users can just simply copy paste one function and put it in their script.BasharOfTheAges wrote:You really think most people are actually trying to understand avisynth and not just copy-pasting lines from the guides or forum posts verbatim?
mirkosp wrote:I'm okay with lmw's proposal, but can anybody handle the html side of the guide?
Also, I think the first step in making a simple and straightforward guide should be to write down a good flowchart, so we'll be able to make the pages for the "choose your own adventure"-style easy guide.
Zarxrax wrote:It should just be a wiki or something.
Makes it a lot easier to keep updated too.
While true for most, it's not true for all. Additionally, many want to learn, but the current guides are too meaty in terms of content and that overwhelms the reader and makes it harder to find particular steps they may have missed. I've had good success with the guides I wrote for the PixelBlended website because they were basic and step by step, which made for a good reference to look back on.BasharOfTheAges wrote:The elephant in the room is, as always, that most people don't want to know HOW to do this stuff - they want someone to just do the work for them, because fuck learning I want to have fun. Set it up how you want, because, really, in the end, you're going to get burned out once you let the resentment build for a few years.
Users browsing this forum: No registered users and 1 guest