Rimsky
Это как такое?
а ты попробуй  big_smile

7,977

(466 replies, posted in Эксплуатация SVP)

А чем всякие куда-выверты лучше веками проверенного dxva (в Win7, конечно)?

7,978

(6 replies, posted in Using SVP)

redlid
Try to reinstall / update ffdshow to the version bundled with SVP 3.0.6.

Sun
"FHD + GPU + cross off" где? wink

7,980

(395 replies, posted in Эксплуатация SVP)

t2Vovik
зря он кол-во потоков зарезал

Sun
Скрипт работает но реального уплавнения не происходит. При отключенном CF все ок.

Это что-то новенькое  hmm
SVPmark с кроссом и без можно прогнать?

zsax
Да как бы и не должен. Вообще внутри Avisynth вся обработка идет строго в 8 бит на канал, больше не будет.

Если просто использовать Avisynth скрипт в ffdshow

какой конкретно скрипт?
внутренние функции может быть иногда переварят 10 бит
mvtools - нет

Can't wait for a "success story"  big_smile

http://www.ntcore.com/4gb_patch.php

But I think 15 threads should be enough even for 5:1 frame interpolation. 19 threads and more will produce more FPS in encoding but for real-time 15 is fine.

Just tried to patch potplayermini.exe myself - works well with 19 threads and half-pixel now  tongue

akak1997
What would it take to get SVP on 64bit?

In the next 1<=N<=5 years - no way  big_smile

See the message above.

The problem is:

- with larger interpolation coefficient (in your case 120:24 = 5:1) you need more threads to fully load CPU
- more CPU cores => more threads
- more threads => more memory

Try MPC-HC, it should be more tolerant to memory consumption.
Or you may patch potplayer's exefile with this tool - http://www.ntcore.com/4gb_patch.php

akak1997
I can see Potplayer using ~1gb of ram b4 it crashes.

Hmm. For me 15 threads are working with both "pixel" and "half-pixel".
Anyway, if interpolation to 120 Hz will work well with 15 threads - you're lucky smile

akak1997
Number of threads: 19

OK, I've just checked, for PotPlayer it's a memory issue.
With 19 threads and half-pixel SVP eats over 2GB which is too much for PotPlayer => it crashes.
MPC-HC's .exe is patched to support up to 3GB, but lets make it work at least with PotPlayer smile

So, decrease num of threads to 15 OR set motion accuracy "to pixel".

akak1997

Something is seriously wrong with your setup  hmm

1. May be you've "Motion estimation accuracy" set to "To quarter-pixel"?
2. Does PotPlayer works with SVP turned off?
3. Post here "Show -> Additional information" after player crash
4. Do you've any codec packs installed?

a few beers for the new year
Thanks! smile

0. Your hardware should handle 120 Hz perfectly. What kind of "trouble" you've got?
0.1. Have you got any problems playing 24->60 FullHD ? If not try to increase "number of threads" for 120 Hz mode to something like 20-24.

1. There's very good guide for encoding with SVP (MVTools)
2. SVP can generate script for video encoder - see "Make -> AVS-script for video" in main menu.

Maken1
http://www.svp-team.com/forum/misc.php?item=898&amp;download=1

7,993

(17 replies, posted in Using SVP)

Eternalzack
I placed avisynth.dll(2.6)in the root directory of megui, but megui still using 2.5.8

You have to place it not in the root directory but near x264.exe. So I think it's tools\x264 subdir.

7,994

(17 replies, posted in Using SVP)

Yeah, I've just checked 2.6 alfa3, and confirm that simple script with only LanczosResize() is 1.5 times faster with 2.6.

So the simpliest solution for you is to unpack (not install) 2.6 and place it's avisynth.dll in MeGUI folder.

And SVP will not work with this 2.6 version cause it lacks MT functions.

7,995

(17 replies, posted in Using SVP)

Eternalzack
install SVP (Run svp once)

Right. And when you run SVP for the first time it overwrites system's avisynth.dll with it's own version.

7,996

(17 replies, posted in Using SVP)

Resizing is the only time consuming function here and it's a built-in Avisynth function.
May be it was improved in 2.6, something like sse2-3-4  hmm

7,997

(17 replies, posted in Using SVP)

Could you post here your script?
And the Avisynth 2.6.0 version, where did you get it?

7,998

(17 replies, posted in Using SVP)

I don't know. May be it's just a difference between 2.5.8 and 2.6.0 with your script.

So your possible choices are:
- use SVP with your fast Avisynth. It should work, but will need more memory.
- use SVP with it's own Avisynth: you can place SVP's one in the video player's folder (near .exe file), then SVP will use this version instead of one located in SysWOW64.
And don't forget to remove/rename "avisynth.dll" from SVP\Distr\MT folder or else SVP will overwrite SysWOW64\avisynth.dll on each run.

7,999

(17 replies, posted in Using SVP)

Cool, but download speed from that site is about ~5 K/s.
Still downloading  big_smile

Anyway, SVP's Avisynth is just regular 2.5.8. The difference is only when there's an additional "svp_scheduler=true" instruction in the script (which is added by SVP).

8,000

(26 replies, posted in Using SVP)

simacom
Does the different RAM speeds play a role in SVP?  Also which is better for SVP 1GB or 2GB version

it doesn't matter