mashingan
I certainly understand that the 'best' settings does not simply mean 'higher numbers must be better'. Also, anime content requires much different settings and performance than 'filmed' series or movies, which is why I said something quite similar to what you pointed out in a earlier post I made to another thread.
Sure, a 6700k is probably "enough" for most people's anime interpolation preferences, but that is only because it rarely contains any mathematically coherent motion to actually interpolate.
For all other use cases, no CPU & GPU combination currently exists that can deliver anything close to 'good enough' performance. Then again, some people like their interpolated frames to still contain aliased motion (aka. the whole 'film look' vs. 'soap opera effect' debacle) and SVP4 makes achieving that with very few other artifacts quite easy with very modest computational requirements.
Nintendo Maniac 64 wrote:...I do not understand why some are saying the 6700K is a better choice.
This is actually a pretty complicated issue, but the simple answer is a combination of:
1) SVP not being very well threaded (or more accurately, the MVTools library running on avisynth has a badly hacked form of threading support (optimal number of threads for maximum SVP performance on a 4-core 4790k = 24) that does not scale very far (hard 32bit memory limits my 8-core 5960x to threads = 26)) and has a pretty high threading overhead) which leads to a fairly bad case of Amdahl's law
2) Skylake has a ~10% IPC advantage over haswell (properly vectorised AVX2 code sees a much larger increase (almost 50% over Haswell's AVX2 code execution) but no one writes code like that these days), and the 6700k overclocks (on average) another 5-10% further. Together with the faster caches and memory (assuming decent DDR4 memory since you have to buy new RAM anyway), I would put the 6700k's net per-core advantage at around 20%, which is very close to the real-world benefit of 50% more cores.
(Having an 8-core 5960x, I can testify that doubling the cores from the 'standard' i7 4700-series makes absolutely no difference in 99% of applications and games; if I had the choice between a 32-core @ 4Ghz CPU and one with the same architecture, but only 4 cores at 6Ghz I would jump on the latter in an instant).
However, if you already have a 5820k, getting a 6700k will not improve your performance in SVP, they should perform very similarly if both have been given a solid overclock. It probably will improve your performance in most other applications a bit, but don't expect a constant 20% improvement in all single-threaded apps either. That is the real reason for recommending the 6700k over the 5820k, not because the 6700k will be much faster in SVP.
Also, using the IGP in any way would be a very bad idea. Combining an otherwise equal CPU and GPU onto one die just serves to dramatically reduce the performance of both. If intel could replace all that wasted die space with some more cache and expanded speculative execution resources, then we would probably have an instant 50~60% jump in IPC, but they'd never do that... more useless cores markets way better.
Chainik wrote:Blackfyre
I still cannot max out all the settings
good for you 
A simple statement that keeps floating around that does not really explain the problem that well. 'maxing' the settings in SVP's GUI by simply pushing all the blue bars as far right as they will go does nothing but make most people's PCs drop frames (and display severely artifacted ones in many other cases).
As I (and indeed all the developers aswell) have said before, this is why there are so many reports of SVP4 looking so much better while requiring less CPU resources to do so (apart from most people simply preferring the 'sharp' look of temporal aliasing). If people don't educate themselves about the algorithm being implemented by actually reading the source code, seeing where those variables go and understanding how that mathematically alters the accuracy of the extracted motion vectors in different situations, then how are they supposed to set the 'best' values for their own system?
Jeff R 1 wrote:Blackfyre _ However for the last 6 or so months I have been running @ 4.7Ghz constant & cooled (Note: I still cannot max out all the settings).
I wonder just how much it would take to max out the settings _ are you using and GPU at all ?
Well, I can give you an idea if you'd like. My system specs is in my profile (a 5960x @ 4.7GHz, SLI Titan X'es @ 1.3GHz and 128GB RAM) and my current setup is to encode my video and watch it later since I get about 0.8~1fps. Getting such a high speed requires splitting my video file into halves and encoding each with 4 cores and one of the Titan x'es in a separate virtualdub instance (this explicit parallelism almost doubles the processing framerate).
I believe these SVP settings that I am using for high quality Blu-Ray playback is about as far as the current SVP libraries can be pushed with regards to maximum SSIM (what I optimise for; aka. the subjective part) for good, noise and artifact free sources in a 32-bit process.
So, to answer your question, to 'max out' SSIM with the current SVP libraries in real-time (assuming 24->60fps) would require a system capable of around two orders of magnitude more processing power than what I have, without resorting to more cores or more GPUs (since the split file hack can't be used in real-time), which is equivalent to around four times! the performance increase we got (while clockspeeds were still being increased between 1985 and 2005).
Theoretically, this can be done within the next decade, but would require a complete re-write of the MVTools library with explicit multi-threading and advanced AVX-512 inline ASM optimisations for all data processing functions to efficiently offload the data to a CUDA (OpenCL could also work I guess) implementation of the actual MV-searching and determining functions which (if you have taken a look at the MVTools library) is a task that would probably cost a few million dollars in software development (although with these Russian coders you never know... they have this astonishing way of just getting stuff done with much less resources than most people thought would be required).
