It would be quite simple to replicate, just need someone who can determine what's causing it and my first thought was Wilbert. Yes, same issue with AVS+ too (1576) Also occurs on my Intel graphics system running 7 (the other is running 10 with a 750Ti) so it's not related to any Windows version or graphics card drivers. Again I've already looked at all the options, no difference. Either I get no image or a distorted one.įfdshow - no dev, no help. Renderer - No options to switch renderer in MPDN, but I've already tried all the options for output. Player - I've already asked as above, perhaps his conclusion could be wrong, IDK, that's what I'm trying to figure out. The logic is to start where you think someone can help :) ![]() So I guess that rules out my ever trying Vapoursynth :( Unfortunately that post was quickly followed by "R25 – Death to Windows XP!":. Support for Windows 98/Me/2000 dropped. Some kind of System Requirement entry could be a good idea on the Wiki, even if it has to be a bit vague. ![]() I've been targetting XP, is W2K officially supported by AVS ?, also, are there C/CPP variants for all functions ? Windows that could be faster (on paper) than Pentium I (with/without FPU). So I guess there could be some i386/i486's out there running ![]() Was hacked to install a more open (usable) version of Linux (LLL, The Little Linux Laptop). Ive got one of those Elonex ONE+ things (300MHz i386, bit faster than my original Pentium I 133MHz), but alas not the MIPS variant that Dont want to step over and above what is officially supported by the Avisynth dll, so I guess that may put it about PIII (I think ManolitoĪnd at least one of the devs/contributors to Vapoursynth use PIII), guess I'll just stick with straight CPP and avoid anything non-standard.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |