Media Player Classic - Home Cinema (MPC-HC) - v1.7.13

[andybaby]

You may need to configure MPC-HC to downmix to stereo, the Windows mixer which usually does the downmix if MPC-HC doesn't is a bit funky with unusual channel configurations.

Thanks, that does it.

[rahzel]

Anyone else having issues with MPC HC 1.7.2+ and Fullscreen Exclusive mode in MadVR? When I try to enter FSE mode on my Radeon 7750 HTPC, the bottom MPC bar/frame stays at the bottom and it doesn't enter FSE mode. I have to exit and fullscreen it again. With MPC 1.7.1 and below, I have no issues at all. This also only happens with videos that have a ~1.85/1.78 AR... movies that are ~2.35+ enter FSE mode fine, with no image of the bottom stuck on the screen.

[rahzel]

No one?

I have ruled out MadVR and LAV being the cause. I've tried the last 4 versions of madVR, and I've tried MPC 1.7.1 with the latest LAV filters forced as the preferred decoder and no issues. Only if I use 1.7.2 or 1.7.3 do I get this issue.

Using the latest AMD drivers, Win7 64-bit, x86 version of MPC.

[Stereodude]

I haven't seen that.

[clsid]

@rahzel
Are you using the classic Windows theme, or auto-hide taskbar option?

There are a few full-screen related bug reports on trac right now. Have a look here:
https://trac.mpc-hc.org/ticket/4004

[rahzel]

@rahzel
Are you using the classic Windows theme, or auto-hide taskbar option?

There are a few full-screen related bug reports on trac right now. Have a look here:
https://trac.mpc-hc.org/ticket/4004
Thanks, will give that a read.

I'm not using classic theme, I'm using a custom aero theme. I do have auto-hide taskbar enabled though (HTPC connected to my plasma). I wonder if that is causing the issue.

edit: maybe it's related to the auto-hide taskbar. Will give that a try, but I do wish to continue using the auto-hide taskbar setting, so hopefully this gets fixed. I made a comment in that ticket.

edit 2: I can confirm that disabling auto-hide taskbar fixes the problem.

[rock]

when mouse pointer hover on tooltip (e.g. control button, H/W), controls bar hide and appear quickly, somehow it feels strange for me

[Dark Eiri]

I'm quite surprised, coming back to HC after a long time using BE and seeing it has it's own internal RAR Source filter! I love it!

But it doesn't seem to support .mp4 files. I remember someone made a really simple fix for RARFileSource which is basically:


RFS.cpp has the following line added:

{ "mp4", &MEDIASUBTYPE_QTMovie },


So could you guys please implement that? (I'm assuming your code is similar to the RARFileSource.ax filter, I'm sorry if I got it wrong

EDIT: Oh... it seems to work with the x86 version... so it's only the x64 version that not working for .mp4 inside RAR :(

[vBm]

I'm quite surprised, coming back to HC after a long time using BE and seeing it has it's own internal RAR Source filter! I love it!

But it doesn't seem to support .mp4 files. I remember someone made a really simple fix for RARFileSource which is basically:


RFS.cpp has the following line added:

{ "mp4", &MEDIASUBTYPE_QTMovie },


So could you guys please implement that? (I'm assuming your code is similar to the RARFileSource.ax filter, I'm sorry if I got it wrong

EDIT: Oh... it seems to work with the x86 version... so it's only the x64 version that not working for .mp4 inside RAR :(

I'm using x64 and i can't confirm the problem.

And we already have that patch applied on top of vanilla RFS along with few other -> https://github.com/mpc-hc/rarfilesource/

[mzso]

Any way to stop mpc-hc from leaving full screen when it looses focus. I wanted to compare something with overlay mixer but I can't this way.

[kasper93]

If someone is interested here is latest LumaSharpen from SweetFX Shader Suite (http://forums.guru3d.com/showthread.php?p=4775046) ported for MPC-HC :) Just few changes needed to use it as standalone shader.

/*
_____________________

LumaSharpen 1.4.1
_____________________

by Christian Cann Schuldt Jensen ~ CeeJay.dk

It blurs the original pixel with the surrounding pixels and then subtracts this blur to sharpen the image.
It does this in luma to avoid color artifacts and allows limiting the maximum sharpning to avoid or lessen halo artifacts.

This is similar to using Unsharp Mask in Photoshop.

Compiles with 3.0
*/

/*-----------------------------------------------------------.
/ User settings /
'-----------------------------------------------------------*/

#define sharp_strength 0.65
#define sharp_clamp 0.035
#define pattern 8
#define offset_bias 1.0
#define show_sharpen 0

/*-----------------------------------------------------------.
/ Developer settings /
'-----------------------------------------------------------*/
#define CoefLuma float3(0.2126, 0.7152, 0.0722) // BT.709 & sRBG luma coefficient (Monitors and HD Television)
//#define CoefLuma float3(0.299, 0.587, 0.114) // BT.601 luma coefficient (SD Television)
//#define CoefLuma float3(1.0/3.0, 1.0/3.0, 1.0/3.0) // Equal weight coefficient

/*-----------------------------------------------------------.
/ Main code /
'-----------------------------------------------------------*/

float4 p0 : register(c0);
sampler s0 : register(s0);

#define px (1.0 / p0[0])
#define py (1.0 / p0[1])

float4 main(float2 tex : TEXCOORD0) : COLOR0
{
// -- Get the original pixel --
float3 ori = tex2D(s0, tex).rgb; // ori = original pixel
float4 inputcolor = tex2D(s0, tex);

// -- Combining the strength and luma multipliers --
float3 sharp_strength_luma = (CoefLuma * sharp_strength); //I'll be combining even more multipliers with it later on

/*-----------------------------------------------------------.
/ Sampling patterns /
'-----------------------------------------------------------*/
// [ NW, , NE ] Each texture lookup (except ori)
// [ ,ori, ] samples 4 pixels
// [ SW, , SE ]

// -- Pattern 1 -- A (fast) 7 tap gaussian using only 2+1 texture fetches.
#if pattern == 1

// -- Gaussian filter --
// [ 1/9, 2/9, ] [ 1 , 2 , ]
// [ 2/9, 8/9, 2/9] = [ 2 , 8 , 2 ]
// [ , 2/9, 1/9] [ , 2 , 1 ]

float3 blur_ori = tex2D(s0, tex + (float2(px, py) / 3.0) * offset_bias).rgb; // North West
blur_ori += tex2D(s0, tex + (float2(-px, -py) / 3.0) * offset_bias).rgb; // South East

//blur_ori += tex2D(s0, tex + float2(px,py) / 3.0 * offset_bias); // North East
//blur_ori += tex2D(s0, tex + float2(-px,-py) / 3.0 * offset_bias); // South West

blur_ori /= 2; //Divide by the number of texture fetches

sharp_strength_luma *= 1.5; // Adjust strength to aproximate the strength of pattern 2

#endif

// -- Pattern 2 -- A 9 tap gaussian using 4+1 texture fetches.
#if pattern == 2

// -- Gaussian filter --
// [ .25, .50, .25] [ 1 , 2 , 1 ]
// [ .50, 1, .50] = [ 2 , 4 , 2 ]
// [ .25, .50, .25] [ 1 , 2 , 1 ]


float3 blur_ori = tex2D(s0, tex + float2(px, -py) * 0.5 * offset_bias).rgb; // South East
blur_ori += tex2D(s0, tex + float2(-px, -py) * 0.5 * offset_bias).rgb; // South West
blur_ori += tex2D(s0, tex + float2(px, py) * 0.5 * offset_bias).rgb; // North East
blur_ori += tex2D(s0, tex + float2(-px, py) * 0.5 * offset_bias).rgb; // North West

blur_ori *= 0.25; // ( /= 4) Divide by the number of texture fetches

#endif

// -- Pattern 3 -- An experimental 17 tap gaussian using 4+1 texture fetches.
#if pattern == 3

// -- Gaussian filter --
// [ , 4 , 6 , , ]
// [ ,16 ,24 ,16 , 4 ]
// [ 6 ,24 , ,24 , 6 ]
// [ 4 ,16 ,24 ,16 , ]
// [ , , 6 , 4 , ]

float3 blur_ori = tex2D(s0, tex + float2(0.4*px, -1.2*py)* offset_bias).rgb; // South South East
blur_ori += tex2D(s0, tex + float2(-1.2*px, -0.4*py) * offset_bias).rgb; // West South West
blur_ori += tex2D(s0, tex + float2(1.2*px, 0.4*py) * offset_bias).rgb; // East North East
blur_ori += tex2D(s0, tex + float2(-0.4*px, 1.2*py) * offset_bias).rgb; // North North West

blur_ori *= 0.25; // ( /= 4) Divide by the number of texture fetches

sharp_strength_luma *= 0.51;
#endif

// -- Pattern 4 -- A 9 tap high pass (pyramid filter) using 4+1 texture fetches.
#if pattern == 4

// -- Gaussian filter --
// [ .50, .50, .50] [ 1 , 1 , 1 ]
// [ .50, , .50] = [ 1 , , 1 ]
// [ .50, .50, .50] [ 1 , 1 , 1 ]

float3 blur_ori = tex2D(s0, tex + float2(0.5 * px, -py * offset_bias)).rgb; // South South East
blur_ori += tex2D(s0, tex + float2(offset_bias * -px, 0.5 * -py)).rgb; // West South West
blur_ori += tex2D(s0, tex + float2(offset_bias * px, 0.5 * py)).rgb; // East North East
blur_ori += tex2D(s0, tex + float2(0.5 * -px, py * offset_bias)).rgb; // North North West

//blur_ori += (2 * ori); // Probably not needed. Only serves to lessen the effect.

blur_ori /= 4.0; //Divide by the number of texture fetches

sharp_strength_luma *= 0.666; // Adjust strength to aproximate the strength of pattern 2
#endif

// -- Pattern 8 -- A (slower) 9 tap gaussian using 9 texture fetches.
#if pattern == 8

// -- Gaussian filter --
// [ 1 , 2 , 1 ]
// [ 2 , 4 , 2 ]
// [ 1 , 2 , 1 ]

half3 blur_ori = tex2D(s0, tex + float2(-px, py) * offset_bias).rgb; // North West
blur_ori += tex2D(s0, tex + float2(px, -py) * offset_bias).rgb; // South East
blur_ori += tex2D(s0, tex + float2(-px, -py) * offset_bias).rgb; // South West
blur_ori += tex2D(s0, tex + float2(px, py) * offset_bias).rgb; // North East

half3 blur_ori2 = tex2D(s0, tex + float2(0, py) * offset_bias).rgb; // North
blur_ori2 += tex2D(s0, tex + float2(0, -py) * offset_bias).rgb; // South
blur_ori2 += tex2D(s0, tex + float2(-px, 0) * offset_bias).rgb; // West
blur_ori2 += tex2D(s0, tex + float2(px, 0) * offset_bias).rgb; // East
blur_ori2 *= 2.0;

blur_ori += blur_ori2;
blur_ori += (ori * 4); // Probably not needed. Only serves to lessen the effect.

// dot()s with gaussian strengths here?

blur_ori /= 16.0; //Divide by the number of texture fetches

//sharp_strength_luma *= 0.75; // Adjust strength to aproximate the strength of pattern 2
#endif

// -- Pattern 9 -- A (slower) 9 tap high pass using 9 texture fetches.
#if pattern == 9

// -- Gaussian filter --
// [ 1 , 1 , 1 ]
// [ 1 , 1 , 1 ]
// [ 1 , 1 , 1 ]

float3 blur_ori = tex2D(s0, tex + float2(-px, py) * offset_bias).rgb; // North West
blur_ori += tex2D(s0, tex + float2(px, -py) * offset_bias).rgb; // South East
blur_ori += tex2D(s0, tex + float2(-px, -py) * offset_bias).rgb; // South West
blur_ori += tex2D(s0, tex + float2(px, py) * offset_bias).rgb; // North East

blur_ori += ori.rgb; // Probably not needed. Only serves to lessen the effect.

blur_ori += tex2D(s0, tex + float2(0, py) * offset_bias).rgb; // North
blur_ori += tex2D(s0, tex + float2(0, -py) * offset_bias).rgb; // South
blur_ori += tex2D(s0, tex + float2(-px, 0) * offset_bias).rgb; // West
blur_ori += tex2D(s0, tex + float2(px, 0) * offset_bias).rgb; // East

blur_ori /= 9; //Divide by the number of texture fetches

//sharp_strength_luma *= (8.0/9.0); // Adjust strength to aproximate the strength of pattern 2
#endif


/*-----------------------------------------------------------.
/ Sharpen /
'-----------------------------------------------------------*/

// -- Calculate the sharpening --
float3 sharp = ori - blur_ori; //Subtracting the blurred image from the original image

#if 0 //New experimental limiter .. not yet finished
float sharp_luma = dot(sharp, sharp_strength_luma); //Calculate the luma
sharp_luma = (abs(sharp_luma)*8.0) * exp(1.0 - (abs(sharp_luma)*8.0)) * sign(sharp_luma) / 16.0; //I should probably move the strength modifier here

#elif 0 //SweetFX 1.4 code
// -- Adjust strength of the sharpening --
float sharp_luma = dot(sharp, sharp_strength_luma); //Calculate the luma and adjust the strength

// -- Clamping the maximum amount of sharpening to prevent halo artifacts --
sharp_luma = clamp(sharp_luma, -sharp_clamp, sharp_clamp); //TODO Try a curve function instead of a clamp

#else //SweetFX 1.5.1 code
// -- Adjust strength of the sharpening and clamp it--
float4 sharp_strength_luma_clamp = float4(sharp_strength_luma * (0.5 / sharp_clamp), 0.5); //Roll part of the clamp into the dot

//sharp_luma = saturate((0.5 / sharp_clamp) * sharp_luma + 0.5); //scale up and clamp
float sharp_luma = saturate(dot(float4(sharp, 1.0), sharp_strength_luma_clamp)); //Calculate the luma, adjust the strength, scale up and clamp
sharp_luma = (sharp_clamp * 2.0) * sharp_luma - sharp_clamp; //scale down
#endif

// -- Combining the values to get the final sharpened pixel --
//float4 done = ori + sharp_luma; // Add the sharpening to the original.
inputcolor.rgb = inputcolor.rgb + sharp_luma; // Add the sharpening to the input color.

/*-----------------------------------------------------------.
/ Returning the output /
'-----------------------------------------------------------*/
#if show_sharpen == 1
//inputcolor.rgb = abs(sharp * 4.0);
inputcolor.rgb = saturate(0.5 + (sharp_luma * 4)).rrr;
#endif

return saturate(inputcolor);
}


I was just curious how it work. I'm not a big fan of sharpening, but I use it for specific content that need it. And it's fine. I haven't done any comparison with sharpen shaders shipped with MPC-HC so don't even ask and check it yourself.

[turbojet]

kasper93: Is there any difference from http://forums.guru3d.com/showpost.php?p=4667177&postcount=96 besides the strength and pattern?

I've just recently switched to pattern 3 from pattern 8, and really liking the switch.

Ceejay.dk is a member here, I think he plans to open a thread for it in the software player forum soon.

[wanezhiling]

http://url.cn/NRORfj
DVD subtitle flickers.

[Rise]

Great Job guys! Using now with K-Lite Mega Codec and no big problems until now. Sometimes it starts unstable and i have to restart it.

Is there possible to make MPC-HC show album cover?
By the way, using win xp 32bits.

[LigH]

Who the :devil: still recommends using "codec packs"?! :confused: Especially since MPC-HC uses an own copy of LAV Filters. No more need for not clearly legal and riskless ballast in the system.

[Rise]

Who the :devil: still recommends using "codec packs"?! :confused: Especially since MPC-HC uses an own copy of LAV Filters. No more need for not clearly legal and riskless ballast in the system.

I was testing for now. If it does not show good results i will uninstall, simple =D.

[vood007]

K-Lite is okay, one of the better packages and its up-to-date, especially on XP.

[Virtual_ManPL]

I'm not seeing a new 64bit build on Official MPC-HC Nightly site (http://nightly.mpc-hc.org/).
Any ideas why?

EDIT:
64bit builds are back ;)

[Aleksoid1978]

Opened incorrect PGC on this DVD http://share.weiyun.com/60aa49d153cb3bc88654ff294e48cc8b - as result, incorrect play. :)
P.S. - or LAV Splitter fail to play, play only 00:02:00

[minaust]

Hi everybody!

I think I've discovered a bug, and I think I've troubleshot it down to the source. Here goes:

I re-ripped my only Blu-Ray disc to test a new ripping toolset, and I discovered that the duration of the finished MKV was severely misreported – 4:32:02 instead of the correct 1:47:21. It turned out that if I muxed the.264 stream into the mkv container with no audio, the duration was properly reported. Further testing showed I could mux in some audio files and get proper duration, and a misreported duration with others.

Testing the “faulty” mkv in other players all showed the proper duration. Checking the duration of the component files using various tools, such as virtualdub, mediainfo, winamp and others, all showed the proper duration. Media Player Classic 6.4.9.1 reported proper duration. MPC-HC 1.6.8.7417 showed proper duration. Mpc-hc 1.7.0.190 showed improper duration.

That made me think that LAV splitter may be at fault. So I went to my working MPC-HC folder (1.7.3 stable) and deleted the LAV folder. Then I went to the folder containing the standalone LAV filters (0.60.1) and installed them – and the duration was still misreported. I uninstalled the LAV splitter and set Haali as an external filter and set it as 'preferred', and problem solved, except this isn't a solution, it's just a fix.

Anybody else see anything like this?

Further observations:

Problem occurs in both 64 and 32-bit versions.
Playback appears to be normal, as long as you don't click on an invalid portion of the timeline.
Chapter points, if any, are all scrunched to the left side of the timeline.
Misreported duration is ALWAYS 4:32:02 – at least with this title.

Note: I have since ripped another Blu-Ray, and this one also has a misreported duration.
Duration of 1:54:43 is reported as 5:12:05.

Windows 7 Professional 64-bit

EDIT: Never mind - it's a known LAV Splitter issue - #433 as I recall.

[seiyafan]

This is a question regarding the built-in subtitles. Delay interval option doesn't seem to work, no matter what number I put the delay in the subtitle has always been the same. What did I do wrong?

I am on version 1.7.1

[vivan]

This settings changes step of subtitle delay (F1/F2 keys by default).
E.g. if you select 500 ms and then press F1 3 times you'll get the delay of -1500 ms.

[Masutin]

I have wishes if this is a place to make them.
1) Access of the list of recent files with one key stroke. Currently, you need to go to File, then Recent Files. Or at least provide Recent Files with an accelerator (underscored letter).
2) Show somehow when two or more audio tracks are available and if subtitles are embedded.

[seiyafan]

This settings changes step of subtitle delay (F1/F2 keys by default).
E.g. if you select 500 ms and then press F1 3 times you'll get the delay of -1500 ms.

Thanks!

[vomanci]

Using MPC-HC and madVR, is any gain using XYSubfilter over ISR when 99% of my subtitles are .srt ?

[nevcairiel]

Using MPC-HC and madVR, is any gain using XYSubfilter over ISR when 99% of my subtitles are .srt ?

Not really any huge advantages worth the extra trouble, IMHO.
Plain text subs or bitmap subs work just fine in MPC-HC ISR, it may only be ASS subtitles where XY has better performance.

[madshi]

XySubFilter still has advantages: madVR can queue the subtitles in its own queue. There's no issue with pausing and seeking. And XySubFilter is probably a bit faster, as well. Plus, if you get to that 1% of ASS subtitles for the odd anime, XySubFilter will give you properly color matched subtitles, scaled up correctly to the output resolution.

But yeah, the ISR generally works just fine, too, so if you're happy with it, no real need to change.

[vomanci]

Thank you for info.
A bug? In latest nightly unchecking "auto load subtitles" still loads them. Tried resetting and even reinstalling MPC. Same thing.

[kasper93]

There's no issue with pausing and seeking.

What issues are we talking about exactly?

And XySubFilter is probably a bit faster, as well.

After recent changes it should have much difference in performance for simple text subtitles at least, but I don't have any numbers.

Generally speaking ISR is just fine for everything except maybe some complex ASS where XY works better. At least it just fine for me :)

[madshi]

What issues are we talking about exactly?
The ISR used to have problems when madVR asked it to draw "unexpected" subtitle frames. E.g. with a paused image, madVR sometimes has to draw the paused frame multiple times (e.g. to draw and later remove the "Paused" OSD). Or when seeking, madVR suddenly asks the ISR to draw a subtitle frame with a totally different timecode than earlier subtitle frames. In these situations the ISR used to not draw anything for a few frames. I don't know, maybe this bug has been fixed in a more recent version? FWIW, madVR still forcefully hides the "Paused" OSD to avoid this specific issue with the ISR. Without this hack, basically the subtitles disappeared every time the user paused the video.

There's one more potential difference: In a future version madVR is going to get support for CIH projection setups, screen masking etc, and it will automatically move the OSD and also the subtitles into the unmasked (= visible) screen area. This kind of thing is already fully supported by the new subtitle interface (used by XySubFilter), but the ISR doesn't support that kind of stuff (at least not having this controlled by the video renderer), unless we extend the ISR interface.

[DeathAngelBR]

Hi.

I didn't know where exactly I should ask this.

I'm using CLI to encode a BDRip of constant frame rate (23.976), but after muxing mediainfo says it's variable frame rate.

Using official stable x264:

"avs4x264mod.exe" --seek-mode safe --x264-binary "x26410bit.exe" --preset veryslow --tune animation --crf 13.0 --deblock -1:-1
--keyint 240 --qcomp 0.8 --aq-strength 0.85 --merange 16 --psy-rd 0.60:0.00 --no-dct-decimate --no-fast-pskip --colorprim bt709
--transfer bt709 --colormatrix bt709 --fps 24000/1001 --force-cfr --input-res 1280x720 --frames 35031 --input-depth 16
--output "E:\SYMPHOGEAR\Symphogear G 04 video.264" "SymphogearG04.avs"

Using x264 tmod:

"avs4x264mod.exe" --seek-mode safe --x264-binary "x264tMod10bit.exe" --preset veryslow --tune animation --crf 13.0 --deblock -1:-1
--keyint 240 --qcomp 0.8 --fade-compensate 0.8 --aq-mode 3 --aq-strength 0.85 --merange 16 --psy-rd 0.60:0.00 --no-dct-decimate --no-fast-pskip
--colorprim bt709 --transfer bt709 --colormatrix bt709 --fps 24000/1001 --force-cfr --input-res 1280x720 --frames 35031 --input-depth 16
--output "E:\SYMPHOGEAR\Symphogear G 04 video tmod.264" "SymphogearG04.avs"

Even if I check the "fix bitstream information" and select 24000/1001p as frame rate in mkvmergegui, mediainfo still says it's VFR. Welp?

[LigH]

No reason for panic. MediaInfo reporting a variable frame rate doesn't mean much. The reason might just be that 24000/1001 is represented with timecode difference fluctuations of just one millisecond. Or it means simply that it is multiplexed in a container with a technique that supports VFR at all (e.g. via timestamps per frame or GOP), instead of assuming the same duration for all frames.

[DeathAngelBR]

No reason for panic. MediaInfo reporting a variable frame rate doesn't mean much. The reason might just be that 24000/1001 is represented with timecode difference fluctuations of just one millisecond. Or it means simply that it is multiplexed in a container with a technique that supports VFR at all (e.g. via timestamps per frame or GOP), instead of assuming the same duration for all frames.

... any workaround?

I created a timecodes file specifying 23.976fps through the entire range and it still says VFR.

[JanWillem32]

For as long as the video format allows time stamps at all, files are marked as VFR. There are video formats that don't allow time stamps, such as the Digital Cinema package files (these only specify frame rate in the header).
To solve this 'issue' either use a video fomat without time stamps, or add the option to scan and analyze all video time stamps in the MediaInfo source code.

[LigH]

Why do you believe that there is a problem at all?

... or add the option to scan and analyze all video time stamps in the MediaInfo source code.

So the reason lies in the fact that MediaInfo reads only a tiny bit of the file, just enough to detect its content. It does not scan the whole file, so it cannot know if all the timecodes are in regular distance for the whole playing time.

Still, I see no issue about a video "having a chance to have VFR".

[sneaker_ger]

MediaInfo doesn't mark all mkv files as VFR, though. Post a sample in the MediaInfo thread (http://forum.doom9.org/showthread.php?t=96516).

[DeathAngelBR]

MediaInfo doesn't mark all mkv files as VFR, though. Post a sample in the MediaInfo thread (http://forum.doom9.org/showthread.php?t=96516).

I just downloaded a standalone build of mediainfo, and it shows the frame rate correctly (CFR). I guess something is up with MPC-HC's built-in mediainfo.

[JohnLai]

Been away for quite a long time, anyone know what happen to mpc-hc audio renderer (wasapi) mode? It outputs static sound when the renderer is selected.

[SamKook]

The internal audio renderer has been broken for years(if it ever worked, never seen it myself).

mpc-be fixed it in their player though.

[kasper93]

Well it works. Just you need to have audio input that it "like". Generally it is not recommended to be used. I recommend you Reclock which is perfect if it comes to WASAPI.

[vomanci]

A bug? In latest nightly unchecking "auto load subtitles" still loads them. Tried resetting and even reinstalling MPC. Same thing.

Well, ISR still loads only external subtitles. Internal ones are not shown. you can check it by right click->subtitles. I have to disable them there not to show up.

[cyberbeing]

A bug? In latest nightly unchecking "auto load subtitles" still loads them. Tried resetting and even reinstalling MPC. Same thing.
Well, ISR still loads only external subtitles. Internal ones are not shown. you can check it by right click->subtitles. I have to disable them there not to show up.

If you go to Options->Subtitles->Misc and delete everything in the 'Autoload paths' box, that should prevent the ISR from loading with external subtitles.

[JohnLai]

The internal audio renderer has been broken for years(if it ever worked, never seen it myself).

mpc-be fixed it in their player though.


Well it works. Just you need to have audio input that it "like". Generally it is not recommended to be used. I recommend you Reclock which is perfect if it comes to WASAPI.

Very well, I shall test both options and see which one suits my needs best. Thanks!

[vomanci]

If you go to Options->Subtitles->Misc and delete everything in the 'Autoload paths' box, that should prevent the ISR from loading with external subtitles.

Still loads them. :confused:
I should specify i use madVR and XySubFilter.

[sneaker_ger]

The "Auto-load subtitles" box only affects MPC-HC's internal subtitle renderer ("ISR"), not XySubFilter.

[vomanci]

To be clear, i have "Auto-load subtitles" box unchecked but the ISR still loads external subtitles. The only way to disable them is by right click->subtitles->enable unchecked. Else i have the subtitles drawn twice, by ISR and XySubFilter. From what i knew, disabeling "Auto load..." should disable completely ISR, "subtitles" should be greyed out.

[cyberbeing]

I know what you mean vomanci, since sometimes the MPC-HC ISR setting will become bugged and refuse to disable the ISR on first or even multiple tries. I've yet to figure out a way to reliably reproduce it, but it is an issue which has been occurring off and on for well over a year.

If you fiddle with it a bit, you can usually fix it. Try the following:

Uninstall XySubFilter (and/or xy-VSFilter if applicable)
Re-enable the "Auto-Load Subtitles" checkbox and reset the "Autoload paths" setting for the ISR
Exit MPC-HC
Open Video with external subtitles and let the ISR load them
Disable the "Auto-Load Subtitles" the setting for the ISR
Exit MPC-HC
Open Video with external subtitles and now the "Subtitles" context menu should be greyed out and ISR fully disabled
If the "Subtitles" context menu is still NOT greyed out, repeat steps 1-7 on various videos with internal/external subtitles until successful
Go to Subtitle->Misc, enable "Ignore Embedded Subtitles" , and clear the "Autoload paths" box
Exit MPC-HC
Install XySubFilter again (and/or xy-VSFilter if applicable)
Open Video with external subtitles and everything should be normal, with the ISR remaining disabled for internal & external subtitles

[sneaker_ger]

So, any idea which registry key would be responsible for the hick-up? Surely there must be an easier way that also leads to a bugfix.

[vomanci]

Well, tried all steps . Nothing works. Plus i found out that if "Auto-load subtitles" is checked, XySubFilter isn't loaded no matter what the "Loading" state in it's settings is. I seem to remember a red text specifically saying to disable ISR or both will work at the same time.
One more thing: why must we exit the player in order for settings to work? Doesn't seem normal behavior to me.
I'll leave this bug for now. Maybe next nightly will work. Who knows. Still, i wonder how BE branch managed to make so many bug fixes and improvements compared to this one. Maybe you are lacking man power? Just curious.

[kasper93]

@vomanci: Can you give more information to help us reproduce the issue? When you unchecked "Auto-load subtitles" it's impossible that ISR is automatically loaded, but you can still trigger it when drag&drop subtitle file onto mpc-hc window and this is only way o trigger ISR I can think of. You don't need to exit player to make this setting works, just reload media file, because once ISR is loaded it will be used ;)