651

(17 replies, posted in Using SVP)

messedupduck wrote:

yeah, ive pretty much tried everything. I'm starting to wonder if it is a hardware issue because i have been getting 'display driver error and recovered' messages.

Well you've got integrated graphics - just unplug your discrete GPU, plug your monitor directly into your motherboard, install the Intel GPU drivers, and see if the issues go away.

Link to Intel GPU drivers for the 3770:
https://downloadcenter.intel.com/produc … Processors


Normally if you wanted to use the Intel GPU with SVP you wouldn't need to uninstall your Nvidia drivers nor even physically remove the discrete GPU, but if you're possibly having hardware issues then that's a different story...

652

(17 replies, posted in Using SVP)

messedupduck wrote:

How old? I installed what i had before updating nvidia if thats what you mean.

That is what I meant.

Once you did that, did you try uninstalling SVP and then re-installing?

Couldn't you cheat and just make a variable framerate video with both 24fps and 30fps without telecine?

Of course, I have absolutely no idea on how to achieve such a thing...

654

(17 replies, posted in Using SVP)

Did you try installing old drivers after having ran DDU?

655

(17 replies, posted in Using SVP)

messedupduck wrote:

I did.

Intel, AMD, and Nvidia? (not just one of them)

656

(17 replies, posted in Using SVP)

Did you try uninstalling the drivers for Nvidia, Intel, and AMD via DDU?

I had an issue where SVP wouldn't see my Intel GPU until I ran DDU and uninstalled Nvidia, AMD, and Intel GPU drivers and then re-installed the newest Intel and AMD GPU drivers (for reference I have Intel integrated graphics and had upgraded from an Nvidia discrete GPU to an AMD discrete GPU).


BTW, what is your CPU?

657

(512 replies, posted in Using SVP)

The bug was fixed by default since Windows 8, so it does not exist in newer versions of Windows.

For users with Win7 or Vista and have the hotfix installed, the results should be exactly the same as Win8 and newer.

On Win7 and Vista without the hotfix installed, using 96KHz is usually the safest bet (depending on the audio drivers, it sometimes does not even let you successfully install the hotfix).



Oh, and on the subject of resampling, do note that Creative and Asus sound cards will resample even when using WASAPI exclusive (it is noted however that Asus soundcards do not resample ASIO, no idea about Creative), so it's important that both the Windows "Sound" control panel and your soundcard drivers are set to the same sampling rate.

More info:
https://yabb.jriver.com/interact/index.php?topic=78291

658

(512 replies, posted in Using SVP)

If you're including audio then you may want to mention something about the resampling bug that exists on Vista and Windows 7:

https://www2.iis.fraunhofer.de/AAC/ie9.html

Note that setting 96000Hz also seems to be somewhat of a work around (supposedly the issue still exists, but using 96KHz definitely minimizes any quality loss due to said bug).

659

(22 replies, posted in Using SVP)

Chainik wrote:

anyway there'll be a huge update to the core libs soon enough, maybe your issue is already fixed

And just for reference, Chainik has previously stated that this huge update is coming in "days" rather than "months".

hannescx wrote:

Avs forum is bit....

Even the HTPC section?

I just want to say, this is totally a discussion for AVSforum.

Also, I just want to mention that this year's OLED TVs aren't actually available just yet (the E6 model should be out any day now).

hannescx wrote:

Samsung seems to be good choice

But LG's the only one making TV-sized OLED panels...

663

(4 replies, posted in Using SVP)

Perhaps try with a fresh copy of MPC-HC portable?


1. "Install" (it's really just a fancy-looking extractor) MPC-HC portable:
http://portableapps.com/apps/music_vide … c-portable

2. Run MPC-HC portable and then follow the instructions here to set it up for SVP:
http://svp-team.com/wiki/SVP:MPC-HC

3. Close MPC-HC portable and then launch it again.

4. Finally in MPC-HC portable, open the video you're trying to play through SVP and see if it works.


NOTE: "livestreamer"will not work correctly with MPC-HC Portable.  If you are not a user of "livestreamer" or do not even know what "livestreamer" is, then ignore this warning.

Chainik wrote:

this's already planned for some future update...

Hopefully some of those features include settings in the GUI for the values that ThomasLiddiard found regarding differences in interpolation between SVP3 and SVP4 (Link1 and Link2)


Nevertheless, are we talking about days or months for these updates?  I'm not looking for a release date or anything, I just want to know if I should bother with changing my configuration so as to provide a less-optimal stop-gap solution until such a feature is implemented.

665

(2 replies, posted in Using SVP)

You wouldn't happen to be running a 60fps video, would you?

If so, refer to this thread:
http://www.svp-team.com/forum/viewtopic.php?pid=56025

Currently if you crop a 1280x720 video to, say, 1280x704, SVP will crop off 8 pixels on the top and 8 pixels on the bottom.

What I want to do instead is crop 16 pixels off of the top and none from the bottom.


Is it possible to do such a thing in SVP4 Pro? (without actually re-encoding the video that is)

667

(6 replies, posted in Using SVP)

You could always try a fresh copy of MPC-HC Portable.


1. "Install" (it's really just a fancy-looking extractor) MPC-HC portable:
http://portableapps.com/apps/music_vide … c-portable

2. Run MPC-HC portable and then follow the instructions here to set it up for SVP:
http://svp-team.com/wiki/SVP:MPC-HC

3. Close MPC-HC portable and then launch it again.

4. Finally in MPC-HC portable, open the video you're trying to play through SVP and see if it works.


NOTE: "livestreamer"will not work correctly with MPC-HC Portable.  If you are not a user of "livestreamer" or do not even know what "livestreamer" is, then ignore this warning.

Just an FYI, SVP only accepts YV12 as the input, which is an 8bit 4:2:0 color space.

In LAVfilters, you might want to try unchecking every color space except YV12 and making sure that dithering is set to "Random".

Also in LAVfilters, you may also want to try fiddling with the color range (labeled "RGB output levels").

669

(64 replies, posted in Using SVP)

Maybe it's be a good idea to make your own thread in the dev forum section dedicated to these results?  That is, just to give said results more visibility.

Also, so as to not make it sound redundant, you probably don't want to name such a thread something similar to this thread but rather maybe something along the lines of "Differences and mistakes in underlying interpolation between SVP3 and SVP4?"

670

(6 replies, posted in Using SVP)

OK then, does this issue still occur if you close SVP completely? (right-click on the SVP icon next to the clock, then select "Exit".

671

(10 replies, posted in Using SVP)

ITN wrote:

Is this still possible with SVP 4?

ReClock is completely separate from SVP, so the fix posted by MAG79 should still work...

672

(64 replies, posted in Using SVP)

dlr5668 wrote:

Someone posted early 317 beta claimed it works much better than final. Did you test it ?

I wasn't a beta tester at the time, so I've no idea where such a thing would even be.

673

(6 replies, posted in Using SVP)

cyberYT wrote:

which it is where the settings are saved fdshow

Errr, no offense, but I really have no idea what you're trying to say here...

674

(64 replies, posted in Using SVP)

mashingan wrote:

Of course, for 720p video and Hexagon search, the rise should within "common" CPU's capabilities. Especially if one has very good CPU, the different of CPU usage can be neglected.

My HTPC only uses a 2.4GHz Core 2 Duo with no GPU acceleration nor HW decoding...

On the other hand, my primary desktop system is a 4.6GHz Pentium G3258.

mashingan wrote:

SVP3 is available

3.1.7 gives me crazy juddery flickering 80-90% of the time (unless I disable GPU acceleration) and 3.1.6 and earlier is noticeably slower than SVP4.

675

(64 replies, posted in Using SVP)

mashingan wrote:

But just be aware, the larger the value (the pixel that to be analysed), the more burden to CPU. Even changing -8 to -10 could give significant rise in CPU usage (especially if combined with Exhaustive Search).

To be honest, the difference in CPU utilization between "Average" and "large" always seemed within margin of error to me...

mashingan wrote:

SVP4 seems to use analyse.main.search.coarse.type = 2, it's Hexagon Search while SVP3 is using the value 4, Exhaustive Search. The Hexagon Search is way lighter than Exhaustive Search. I personally use 4 for 720p and 3 for 1080p (Uneven Multi Hexagon search, UMH).

This to me seems like the kind of thing that should have a visible setting in the GUI when you're not using the "Automatic options selection" no?