Media Player Classic - BE Win32/x64

[combucha]

Hi

1) How to force MPC-BE to play video on start with window size matched to 100% video size? Every video I open is played in small window (dafault player size). I think tried all combinations from player menu, resetting mpc and nothing.

2) Some yt videos can't be rendered at all, for ex: https://www.youtube.com/watch?v=_A5OdIdLYJI
Why?

[hdboy]

I did not understand what the problem is.

I have a sound bar with optical input. It can only handle Dolby and dts. So I use the internal mpc audio decoder, ac3 encoding option, and wasapi renderer to convert dts-hd and truehd audio into spdif bit stream for the sound bar. This works fine except with some truehd audio streams, where I get massive frame drops if I select sync video to audio or garbled sound if I select sync audio to video.

As far as I can tell, what the problematic audios have in common is a greater than 48khz sample rate. Is this a known limit? MPCBE's cpu usage is only 12%, so it's not overloading my cpu. It's not a huge deal since there's usually an alternative lo res audio stream, but I like to figure it out.

[Aleksoid1978]

Can you upload short sample file with TrueHD problematic stream, I check at my home A/V receiver.

[arrgh]

Hi
on the Shark007 Homepage one can see the following message for the "Shark Codecs" :

"Current releases introduce 3D MVC decoding within MKV Containers"
"When the 3D decoder is active, LAV Video will report, Active Decoder: msdk mvc"

...will this open the option to playback MVC coded MKVs in MPC-BE ?

thanks

[Shark007]

Hi
on the Shark007 Homepage one can see the following message for the "Shark Codecs" :

"Current releases introduce 3D MVC decoding within MKV Containers"
"When the 3D decoder is active, LAV Video will report, Active Decoder: msdk mvc"

...will this open the option to playback MVC coded MKVs in MPC-BE ?

thanks
On my Tools page, I release pre-configured versions of MPC-BE for use when installing my codec package. If you were to use a current version of my codec package and a player downloaded from my Tools page that includes madVR, it would work with 3D MVC MKV files without any further configuration.

[hdboy]

Can you upload short sample file with TrueHD problematic stream, I check at my home A/V receiver.

Sorry, I've been sick with flu

I uploaded a clip (81M)

http://www.filedropper.com/truehd96

In MPC audio decoder, please disable TrueHD bitstreaming and enable AC3 encoding because that is what needs to be tested.

[v0lt]

...will this open the option to playback MVC coded MKVs in MPC-BE ?
Provide samples to see.

[Aleksoid1978]

Sorry, I've been sick with flu

I uploaded a clip (81M)

http://www.filedropper.com/truehd96

In MPC audio decoder, please disable TrueHD bitstreaming and enable AC3 encoding because that is what needs to be tested.

Thanks - fixed.

[RY]

Found what the cause was can you fix this?

msacm.vorbis makes mpc-be x64 crash on launch
it's used by FL Studio 64-Bit to play Vorbis Ogg files
if I disable the codec using sysinternals autoruns mpc-be works fine hope you can fix this.

[ryrynz]

Time to release 1.4.6? Also could you update SVN repository link on OP please? It's no longer up to date.

[Aleksoid1978]

Found what the cause was can you fix this?

msacm.vorbis makes mpc-be x64 crash on launch
it's used by FL Studio 64-Bit to play Vorbis Ogg files
if I disable the codec using sysinternals autoruns mpc-be works fine hope you can fix this.

Crash in external codec - how we can fix it??

But - I think we can disable this codec for using in mpc-be to prevent using & crash.

[RY]

Yes can you stop mpc from reading msacm.vorbis - vorbis.acm
it works on mpc-be 32-bit I think it's clashing with the 64-bit msacm.vorbis

[v0lt]

Also could you update SVN repository link on OP please? It's no longer up to date.
https://svn.code.sf.net/p/mpcbe/code/trunk - for SVN client
https://sourceforge.net/p/mpcbe/code/HEAD/tree/trunk/ - for browser

[Klaus1189]

What can I adjust here?
Can I get 10 bit per color (Deep Color) here without D3D-Fullscreen mode?

I'm on Windows 10 Pro 64-bit

[hdboy]

Thanks - fixed.

thank you, could you release a build? I tried to install VS to build it myself but the install keeps failing half way through.

[RY]

These are the source directories could you block them please thanks.

msacm.vorbis Ogg Vorbis CODEC for MSACM

c:\windows\system32\vorbis.acm
c:\windows\syswow64\vorbis.acm

[v0lt]

Why not just use the built-in Vorbis decoder?

ACM decoders can not be blocked separately. You can block the ACM Wrapper in external filters.

[RY]

I am using internal codecs but FL Studio installs these because it needs them to playback ogg files, I tried blocking the ACM Wrapper but still results into a crash.. Any other solutions? it works if I disable the one that's in the system32 folder but its needed for playback in FL Studio.

[v0lt]

@RY
c:\windows\system32\vorbis.acm -x64
c:\windows\syswow64\vorbis.acm - x86
I think one of the files can be uninstalled without affecting the FL Studio. Then you can use the appropriate player version (x86 or x64).

Player code we will not change.

[RY]

Ok thanks I will just turn it on instead of renaming it when I need to use it.

Question 1: under Frame synchronization does V-sync have to be on or does windows 10 do it automatic with the nvidia gpu drivers?

2: is Bicubic the highest quality Resizer?

[Klaus1189]

What can I adjust here?
Can I get 10 bit per color (Deep Color) here without D3D-Fullscreen mode?

I'm on Windows 10 Pro 64-bit

Nobody knows that?

[FDisk80]

Nobody knows that?

You got your answer a while ago.
http://forum.doom9.org/showthread.php?p=1755257#post1755257
And it was No.

[Klaus1189]

But what can I adjust here then?

[FDisk80]

But what can I adjust here then?

Nothing, you can't get it to work without FSE mode.

[Klaus1189]

Aah ok, this setting is only for D3D fullscreen mode. I didn't know that. :thanks:

[Klaus1189]

A drop down list is too small - one letter is cut off:
https://drive.google.com/file/d/0B4y5u0gBKYqbREtNaEZHOV83YVk/view?usp=sharing

[Klaus1189]

updated german translation
https://drive.google.com/file/d/0B4y5u0gBKYqbWHNQYU9FRktGaVk/view?usp=sharing

[Reino]

Hello Aleksoid1978,

MPC-BE doesn't successfully parse this hls-manifest-playlist (https://kalturahd-vh.akamaihd.net/i/content/r71v1/entry/data/412/112/1_yjrbfoc0_0_,e1d20ia2,r7mao8mk,ybgd4av0,439hamb1,3lu536fi,8ojsff0g,_2.mp4.csmil/master.m3u8). Actually it only loads the highest quality stream (the 1080p stream in this case) and the "Navigate" -> "Jump To" menu remains empty. Bug?

[Aleksoid1978]

It's not a bug - hls playlist not parsing.

[Reino]

But why not? Every other manifest-playlist I opened with MPC-BE in the past got parsed, including this one:

http://reino.degeelebosch.nl/files/Manifest-playlist.png

Why is the initial manifest-playlist I was talking about not being parsed just like the rest?

[Aleksoid1978]

CoRoNe

I was wrong - hls m3u playlist parsing, but only from http. You link - https. It's a limitation.

[Reino]

I didn't realize MPC-BE couldn't parse https.
Is it really a limitation, or can you add support for https?

[Aleksoid1978]

At now time - it's limitation. Maybe add support parsing https link in features, who know :)

[scollaco]

Aleksoid1978...first fo all thansk for the amazing mpc-be player. I use it exclusively and have never gone back to another player.

I'm a noob and don't understand exactly how things work...but I had a question. Since madVR/LAV can now play 3D MVC and blurays, I noticed the subtitles render in 3d but not at the proper depth. Is it the subtitle renderer inside the player that is responsible for allowing us to adjust the depth of the subs. Currently I don't see any way to do this. Seems like only top/bottom and side-by side subs work.

thanks

[madshi]

@devs,

I've had to introduce ISubRenderCallback4 as a new interface for the ISR (of course all the old versions are also still supported). For 3D subtitles I need to be able to tell the ISR at which 3D depth to render the subtitles.

It sounds complicated, but it's really simple. You only need to look at the new "int xOffsetInPixels" parameter. And all you need to do is to add this integer (it can be positive or negative) to the subtitle X position. So if "xOffsetInPxels" e.g. has a value of -3, you would draw the subtitle at position e.g. "x,y:97,100" instead of "x,y:100,100".

Here's the new interface definition:

[uuid("C89CF1D4-29C5-4A96-8AAC-528EC6F7AF1E")]
interface ISubRenderCallback4 : public ISubRenderCallback3
{
STDMETHOD(RenderEx3)(REFERENCE_TIME frameStart, REFERENCE_TIME frameStop, REFERENCE_TIME avgTimePerFrame, RECT croppedVideoRect, RECT originalVideoRect, RECT viewportRect, const double videoStretchFactor = 1.0, int xOffsetInPixels = 0, DWORD flags = 0) = 0;
};
If you have any questions, just let me know.

@scollaco, good timing... :D

[scollaco]

@devs,

I've had to introduce ISubRenderCallback4 as a new interface for the ISR (of course all the old versions are also still supported). For 3D subtitles I need to be able to tell the ISR at which 3D depth to render the subtitles.

It sounds complicated, but it's really simple. You only need to look at the new "int xOffsetInPixels" parameter. And all you need to do is to add this integer (it can be positive or negative) to the subtitle X position. So if "xOffsetInPxels" e.g. has a value of -3, you would draw the subtitle at position e.g. "x,y:97,100" instead of "x,y:100,100".

Here's the new interface definition:

[uuid("C89CF1D4-29C5-4A96-8AAC-528EC6F7AF1E")]
interface ISubRenderCallback4 : public ISubRenderCallback3
{
STDMETHOD(RenderEx3)(REFERENCE_TIME frameStart, REFERENCE_TIME frameStop, REFERENCE_TIME avgTimePerFrame, RECT croppedVideoRect, RECT originalVideoRect, RECT viewportRect, const double videoStretchFactor = 1.0, int xOffsetInPixels = 0, DWORD flags = 0) = 0;
};
If you have any questions, just let me know.

@scollaco, good timing... :D


Thanks Madshi...you are the best!

[Aleksoid1978]

@devs,

I've had to introduce ISubRenderCallback4 as a new interface for the ISR (of course all the old versions are also still supported). For 3D subtitles I need to be able to tell the ISR at which 3D depth to render the subtitles.

It sounds complicated, but it's really simple. You only need to look at the new "int xOffsetInPixels" parameter. And all you need to do is to add this integer (it can be positive or negative) to the subtitle X position. So if "xOffsetInPxels" e.g. has a value of -3, you would draw the subtitle at position e.g. "x,y:97,100" instead of "x,y:100,100".

Here's the new interface definition:

[uuid("C89CF1D4-29C5-4A96-8AAC-528EC6F7AF1E")]
interface ISubRenderCallback4 : public ISubRenderCallback3
{
STDMETHOD(RenderEx3)(REFERENCE_TIME frameStart, REFERENCE_TIME frameStop, REFERENCE_TIME avgTimePerFrame, RECT croppedVideoRect, RECT originalVideoRect, RECT viewportRect, const double videoStretchFactor = 1.0, int xOffsetInPixels = 0, DWORD flags = 0) = 0;
};
If you have any questions, just let me know.

@scollaco, good timing... :D

I just now add support ISubRenderCallback4 interface and something strange - no matter use 3D or not, what video is playback - xOffsetInPixels always = 4 and flags = 1.

[madshi]

I just now add support ISubRenderCallback4 interface and something strange - no matter use 3D or not, what video is playback - xOffsetInPixels always = 4 and flags = 1.
Have you updated to the latest LAV nightly? Forgot to mention that it is needed to get proper 3D subtitle depth information from LAV to madVR. Without that I'm defaulting to a 3D subtitle depth of 4 (which is a bit nearer to our eyes than the screen). With the latest LAV depth might start as 4, but once the movie plays and actual subtitles are visible, the depth should sometimes be different.

Always getting offset=4 and flags=1 sounds like a bug, though. With 2D movies it should be an offset of 0. And with 3D movies it should alternate between +4/1 and -4/2 for left/right eyes. Sorry about that, will fix that in the next build.

[Aleksoid1978]

Have you updated to the latest LAV nightly? Forgot to mention that it is needed to get proper 3D subtitle depth information from LAV to madVR. Without that I'm defaulting to a 3D subtitle depth of 4 (which is a bit nearer to our eyes than the screen). With the latest LAV depth might start as 4, but once the movie plays and actual subtitles are visible, the depth should sometimes be different.

Always getting offset=4 and flags=1 sounds like a bug, though. With 2D movies it should be an offset of 0. And with 3D movies it should alternate between +4/1 and -4/2 for left/right eyes. Sorry about that, will fix that in the next build.

Question about getting 3D subtitle depth information from LAV - you take it's from LAVSource ?? If yes - how you do it, what interface or some different way ??
Why i want to know - i implement support MVC demuxing in matroska/mpeg-ts.

[nevcairiel]

Question about getting 3D subtitle depth information from LAV - you take it's from LAVSource ?? If yes - how you do it, what interface or some different way ??
Why i want to know - i implement support MVC demuxing in matroska/mpeg-ts.

The depth information comes from the video decoder.

[madshi]

I just now add support ISubRenderCallback4 interface and something strange - no matter use 3D or not, what video is playback - xOffsetInPixels always = 4 and flags = 1.
Ok, v0.90.12 is released. It now always sends "xOffsetInPixels=0" for 2D movies. However, for 3D movies I can't confirm that "flags" is always set to 1. It should properly alternate between 1 and 2, and the xOffsetInPixels value should alternate between + and -. I tested that with a test build of MPC-HC sent to me by kasper93 and it seems to work just fine.

Question about getting 3D subtitle depth information from LAV - you take it's from LAVSource ?? If yes - how you do it, what interface or some different way ??
Why i want to know - i implement support MVC demuxing in matroska/mpeg-ts.
This information is in h264/MVC SEI information blocks. So it's not the splitter but the decoder who provides this information. The decoder attaches this information directly to the IMediaSamples. See "MediaSideData3DOffset" here:

https://raw.githubusercontent.com/Nevcairiel/LAVFilters/master/common/includes/IMediaSideData.h

Edit: nevcairiel was faster.

[Aleksoid1978]

madshi thanks.

[madshi]

There's one additional thing the splitter will have to do: The SEI depth information blocks contain an array of depths, one depth for each subtitle track, one for GUI etc. Currently madVR simply uses the "min" of all these values for subtitle rendering. For a "perfect" solution madVR needs to know which array index belongs to the currently selected subtitle track. This information is stored in the Blu-Ray playlist files. nevcairiel is planning to export this information from LAV Splitter in a future version. Maybe you can then do the same for the internal MPC-BE splitter? That said, if you don't do that, it's not a deal breaker. The current "min" solution madVR uses seems to work reasonably well (but it's not perfect).

[Aleksoid1978]

For a "perfect" solution madVR needs to know which array index belongs to the currently selected subtitle track. This information is stored in the Blu-Ray playlist files. nevcairiel is planning to export this information from LAV Splitter in a future version. Maybe you can then do the same for the internal MPC-BE splitter?

In what format you need this information ??

[madshi]

In what format you need this information ??
In IPropertyBag. I think the latest LAV should already have this included. If you look for IPropertyBag, madVR reads most/all of them and makes use of it. Specifically, madVR reads (or will read) the following:

"ROTATION": allows madVR to auto-rotate a video which needs rotation
"STEREOSCOPIC3D": allows madVR to know early whether a movie is 3D or not (optimized initialization)
"STEREOSCOPIC3DMODE": allows madVR to know whether left or right eye comes first (important!)
"stereo_subtitle_offset_id": index of 3D subtitle depth track
"stereo_interactive_offset_ids": comma separated list of indexes for IG 3D depth tracks (used for madVR 3D OSD depth)

The last two are brand new and not in madVR v0.90.12 yet. They will be added next weekend. They practically let me know which array indexes in the SEI 3D depth information have which meaning and which I should use for subtitles and OSD.

[Aleksoid1978]

In IPropertyBag. I think the latest LAV should already have this included. If you look for IPropertyBag, madVR reads most/all of them and makes use of it. Specifically, madVR reads (or will read) the following:

"ROTATION": allows madVR to auto-rotate a video which needs rotation
"STEREOSCOPIC3D": allows madVR to know early whether a movie is 3D or not (optimized initialization)
"STEREOSCOPIC3DMODE": allows madVR to know whether left or right eye comes first (important!)
"stereo_subtitle_offset_id": index of 3D subtitle depth track
"stereo_interactive_offset_ids": comma separated list of indexes for IG 3D depth tracks (used for madVR 3D OSD depth)

The last two are brand new and not in madVR v0.90.12 yet. They will be added next weekend. They practically let me know which array indexes in the SEI 3D depth information have which meaning and which I should use for subtitles and OSD.

Ok - i understand. Question about "stereo_subtitle_offset_id" - it's value can't be different for different subtitles track ??

[madshi]

Yes, it will often be different for different subtitle tracks! I'm not sure yet what madVR will do: Maybe I'll ask "stereo_subtitle_offset_id" every time I start rendering subtitles for a frame. Or maybe I can find a way to be notified when the subtitle track changes, so I don't have to ask "stereo_subtitle_offset_id" all the time.

[nevcairiel]

Yes, it will often be different for different subtitle tracks! I'm not sure yet what madVR will do: Maybe I'll ask "stereo_subtitle_offset_id" every time I start rendering subtitles for a frame. Or maybe I can find a way to be notified when the subtitle track changes, so I don't have to ask "stereo_subtitle_offset_id" all the time.

There should generally be something happening when the subtitle track changes. With LAV the graph will stop to do the change and then resume.

[madshi]

Yeah, I was planning to look into a log to see what happens in that situation and maybe find a good place to update the "stereo_subtitle_offset_id" information. On the other, I suppose the splitter will have this information handy, anyway, and asking it once per frame (so 24 or 60 times a second) doesn't sound like it would likely cause any performance issues, so maybe I'll choose the easy way out and ask it once for every frame (at the moment when I render it).

[Aleksoid1978]

With LAV the graph will stop to do the change and then resume.

With MPC-BE's MPEG Splitter is the same.