INTERACT FORUM

More => Old Versions => JRiver Media Center 20 for Windows => Topic started by: rlebrette on August 02, 2014, 05:26:27 am

Title: [REQ] AviSynth integration in a RedOctober profile
Post by: rlebrette on August 02, 2014, 05:26:27 am

What about integrating the AviSynth preprocessor in a RedOctober HD++ profile?
A lot of us are using it to improve the rendering of HD and SD content.
But we have to use the custom mode which is a little more complicated to use for new comers.
Having it integrated as MadVR and LAV will make the setup easier.

Title: Re: [REQ] AviSynth integration in a RedOctober profile
Post by: 6233638 on August 02, 2014, 07:35:35 am

AviSynth has always caused lip-sync problems for me.
Shader support might be a better solution for post-processing.

Title: Re: [REQ] AviSynth integration in a RedOctober profile
Post by: Boltron on August 02, 2014, 07:39:41 pm

+1 for Shader support.

Title: Re: [REQ] AviSynth integration in a RedOctober profile
Post by: OO7livier on August 07, 2014, 06:06:36 am

+1
OO7livier

Title: Re: [REQ] AviSynth integration in a RedOctober profile
Post by: Olivier C. on September 30, 2014, 10:50:47 am

+1

Avisynth is way more powerful than shaders and work fine with MPC-HC.
Upscale algorithms like Spline144, etc are unavailable in shaders.

Title: Re: [REQ] AviSynth integration in a RedOctober profile
Post by: 6233638 on September 30, 2014, 11:33:44 am

Quote from: Olivier C. on September 30, 2014, 10:50:47 am

Avisynth is way more powerful than shaders and work fine with MPC-HC.
Upscale algorithms like Spline144, etc are unavailable in shaders.

madVR has Spline 36 and Spline 64 implementations. Increasing the number of taps generally increases sharpness at the cost of ringing.
There are better algorithms out there such as madVR's Jinc anti-ringing scaling and NNEDI3 image doubling.

Title: Re: [REQ] AviSynth integration in a RedOctober profile
Post by: Olivier C. on October 07, 2014, 01:07:47 pm

Quote from: 6233638 on September 30, 2014, 11:33:44 am

madVR has Spline 36 and Spline 64 implementations. Increasing the number of taps generally increases sharpness at the cost of ringing.
There are better algorithms out there such as madVR's Jinc anti-ringing scaling and NNEDI3 image doubling.

I use an avisynth script to scale over the desktop resolution (1920x1080 -> 2880x1620), then it applies sharpen and UnsharpHQ filters in this higher resolution and then madVR downscales that to 1920x1080 (Catmull Rom LL+AR).
--> it's by far the best quality i can get.

I use a dering technique in avisynth too.

I also developed an avisynth script "Before and After" in order to watch immediately the result with and without my script (because ffdshow can not do that for avisynth)

Spline144 alone is not the best scaler (ringing) but in the context i use it, it's the best one, for me at least, to my eyes and my display.

I use also NNEDI3 in avisynth for SD content. My CPU is much powerful than my GPU so i use also avisynth for SD / NNEDI3.


It's the reason why i use MPC-HC instead of JRiver.

Also the fact that JRiver states that the wheel mouse is for seeking video also irritates me and they don't want to change anything. Many users have requested this but they don't want to hear anyone.

I don't know why they have hardcoded a such thing and why they can not open that (for example with a new option).

So, for me :  

For playing video files, i use an external player like MPC-HC (Avisynth, madVR, etc).
I will not upgrade anymore until they will hear all their users (you can read numerous requests for changing wheel mouse in full screen while playing video).

Here is the link of my post : http://yabb.jriver.com/interact/index.php?topic=90662.msg627386#msg627386
And i am still waiting for their answer ....  :-\