Search options (Page 41 of 55)

And presumably it works fine in a different media player, like the MPC-HC bundled with SVP?

At least for me, the answer was no - there was a point where increasing the CPU utilization actually increased the artifacts.

I'm seeing a similar under-utilization of the CPU.

I'm on a 2.4GHz Core 2 Duo and, when using my go-to overly-intensive unrealistic 720p stress-test video, my CPU utilization is only like 45%... I'm able to set SVP 4 to +30% which puts my CPU utilization at around 80% and everything still plays back perfectly smoothly.

Does the fact that I'm only using 720p make a difference? (most of my content is only 720p due to internet bandwidth constraints).  It should be noted that I can't even use all the default settings in SVP 3.1.7 due to my CPU not being fast enough and that my GPU doesn't support DXVA2 nor SVP's GPU acceleration.

Have you tried making a custom resolution with a refresh rate of 48hz and/or 72hz?  I imagine that would be better than speeding up 24fps content to 25fps...

Uhhh, you can do it with a few clicks even in this program, it's just a bit non-intuitive to actually get to the SVP converter in the first place.

The thing is, this program's main purpose is something completely different, so you pretty much need to completely ignore the first screen you see.  You have to go into Tools -> Media Encoder and then set the preset to 60fps.

Take a look at this video starting at 1:05:
https://youtu.be/xvWmP30GmUc?t=65s

...yeah, to me it still sounds like we're not talking about the same thing.

At least to me, what you described sounds like not the pixel response time but rather the panel refresh time (not an actual term AFAIK) - that being the amount of time for all pixels to change from one state to another.

What I was speaking of is the amount of time it takes for a single OLED pixel to transition from one state to another thereby not including the "waiting time" of waiting for any pixels located before said pixels to be updated.  AFAIK, this is typically what is referred to when speaking of to "pixel response time" (note that there is no standard definition for it).

Now yes, you would indeed still need a high refresh rate in order to not have a slow refresh time, but that wasn't my point.  I mean, even current OLED TVs can do 240hz and the like - they just can't accept an input video signal above something like 75hz.

DERP!  Double post...oh well. >_>

I would like to mention that I did not actually say 0.01ms but rather sub 0.1ms - that could even be 0.09ms.

But nevertheless, isn't that like saying CRTs cannot do high refresh rates because some low-end CRT monitor couldn't run above 75hz at an adequate resolution?  There's always going to be cheaper units with worse components - I mean, laptops with 15" 1366x768 LCD displays are still a thing!  My aunt had a Toshiba laptop with 1280x800 in 2004.

Is this not what "overdriving" is on LCD monitors?  AFAIK, there is no need to do such a thing on OLED displays...

Sorry, I was being half sarcastic - I thought my use of "Blasphemy!" would have made that apparent.  I mean, I am primarily a Windows user currently.

...but I would like to point out that none of those 3 pieces of software have native Linux versions.

I do at least appreciate the Linux version being free (currently).  I mean, closed source but free can at times be controversial in itself (read: Nvidia drivers) but closed source and costing money?  Blasphemy!

I am not complaining at all about paying for the continued development of something that was originally free.  Rewriting software takes time and energy, I understand that completely.

Question - if a new donor were to choose the $15 Mac perk, would they also get the Windows version of SVP?

...I don't see how that makes a difference.  If the manager is good, then any future versions may very well just be updates and iterations of it rather than completely separate rewrites.

Does MPC-HC crash when SVP is closed?