Search options (Page 23 of 32)

Это либо результат плохого некачественного деинтерлейса, либо сам интерлейс. Советую попробовать включить деинтерлейс в видеодекодере и посмотреть поможет ли.

Lemme guess... If you set decoder to Intel QS or None or DXVA it works but with CUDA it doesn't?

Check Mediainfo. How much symbols does it have in its header? I know that mkvmerge used to double header's length somehow even though you see it as usual so if it has long encode settings written... crash.

Try to mux in mp4 with Yamb and then remux in mkv with mkvmerge.

I really suggest using these settings for Filling Black bars on FullHD monitor. Also I increase film's size (NUM_9 for Potplayer) somewhat so it wouldn't be that wide. Because trust me, you MUST do that with Lighting effect. You visually lie to your brain that you see a bigger picture, right? Your brain adopts itself to this thinking that all image gives you useful information. At the end you get what I got: watching Godzilla I didn't feel Godzilla. It should be HUGE but I didn't have that feeling.

Increase settings. Doubleclick SVP icon when playing FHD video.

Вы патчили экзешник плеера с 4GB patch?
У меня эта сборка. При установке плеера хоть пункт "заказать пиццу по завершению установки плеера" выставьте, но не выбираете SVP, а потом сами отдельно устанавливаете и настраиваете.

dj14hrl
They were working on it but they met severe problems. I couldn't say details about possible x64 release date even if I knew, same about it's current situation. All I can say however, don't expect RC in the closest future.

MAG79
and AVS 2.6 SVP Edition:

Where can we get it? Is there an opened link? 

Yes, main library core has been updated which can be used for its main purpose - frame interpolation script. But it was meant to be "easy to miss" because frame interpolation script is not the same as whole SVP Manager with real-time frame X>Y transition in player.
That is exactly why people see those bugs because it wasn't tested on SVP 3.1.6. It is tested by Beta-testers for now and it is not just those 2 core dlls that are different in the upcoming SVP build.

AVS 2.6 Should be in SysWow64, AVS+ in player's folder.

Nintendo Maniac 64, might be that different overclocking gives such variable result.

So you use Avisynth 2.5.8 SVP edition. Then try to put Avisynth 2.6 MT in the player's folder and try to play with thread number.

Except for every other man it is needed to go deep into knowledge about memory requirements for every type of script where i heard many times "why did you put so big value", "well, try to put bigger value now" etc.
It's much easier to use 2 scenarios instead: 1 - just do not write anything about memory if you use single thread and save your time; and 2 - Write SetMemoryMax(1024) if you use multiple threads.
Much safer for anyone who doesn't consider himself as Pro in AVS scriptbuilding and you let AVS to do its own memory allocating job in Single Tread scenarious.

You need to disable rightclick>video> video fiters of processing