![]() ![]() What's new is that x264 avs input use avs2pipemod, before it was using direct avs input, I changed it in order to support 10 bit. If I recall correctly then the default in staxrip is avs2pipemod for x264 and x265 using AviSynth and for VapourSynth it's vspipe. I think it's always good when an application is feature rich, of course when an application has many features some care has to be taken to structure everything and add some search features so users can find the features easily. ![]() Maybe one of the piping tools has a rare bug, people can then try another piping tool then. Some people might want to use another x265 build that don't has avs input support or maybe Wolfberry stops making builds. I like Wolfberry's builds because they support avs input, for that it's good that the piping tool can be disabled. Maybe if somebody is used to do things in a certain way or want to try out a different way, maybe just for fun. What is the purpose of offering the user a choice between several piping tools instead of just hardcoding one that works? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |