Media Player Classic - BE Win32/x64

[Aleksoid1978]

Originally Posted by SamKook

I did

I see - LAV Audio Decoder set "incorrect" channel mask. It must 0x06f instead 0x3f for 5.1 output.

P.S. Update. Now work fine with LAV Audio - http://aleksoid.voserver.net/MPC-BE/...EXCLUSIVE_2.7z

[Aleksoid1978]

Originally Posted by ontherocks

With the settings as mentioned in this post, I am able to obtain bit-exact playback with wav files. But the issue remains the same with hi resolution lossless wma files.
Example wma files could be obtained from here
ftp://www.unipheyemusic.com/audio/TestPageSamples
here
http://www.gimell.com/recording-free...wnloads-1.aspx
and here
http://www.gimell.com/recording-free...wnloads-2.aspx

1 - in MPC Audio Decoder check all output format - 16/24/32/float
2 - what's wrong with .wmv playback ??

[SamKook]

Originally Posted by Aleksoid1978

I see - LAV Audio Decoder set "incorrect" channel mask. It must 0x06f instead 0x3f for 5.1 output.

P.S. Update. Now work fine with LAV Audio - http://aleksoid.voserver.net/MPC-BE/...EXCLUSIVE_2.7z

It was also behaving the same with MPC internal decoders(except for the 0x60f vs 0x3f).

I tested v2 and nothing's changed:


If the input is limited to 16bit, it will play at 48KHz with both LAV and MPC, but anything higher and it drops to 44.1KHz. The output is always 16bit.

[Aleksoid1978]

Originally Posted by SamKook

If the input is limited to 16bit, it will play at 48KHz with both LAV and MPC, but anything higher and it drops to 44.1KHz. The output is always 16bit.

Make screen of this Audio Setting in you system:

[SamKook]

The default format for shared mode in the advanced tab was the culprit, changing it will change the output bit and KHz. I was only changing it in the audio driver software.

But that seems like pretty odd behavior.
Shouldn't the renderer use the highest settings supported by the hardware instead of using the default set in windows? And shouldn't exclusive mode ignore windows settings(especially when they specify it's for shared mode and is a default value, not a fixed one) and use the hardware directly or am I missing something here.

[Aleksoid1978]

Here 3 test build. Must work with 24bit/32bit output
http://aleksoid.voserver.net/MPC-BE/...EXCLUSIVE_3.7z

P.S. Before test - check "Allow bit-exact output" in MPC Audio Renderer settings.

[SamKook]

v3 will use the closest supported settings from the input when "Allow bit-exact output" is checked which is very nice.

So I now get 24bit and 48KHz for 32bit 48KHz sources regardless of what setting is set for the default shared mode.


A quick unrelated question: Is there a way to only launch the player in fullscreen when you open the player, like mpchc does instead of going to fullscreen every time a new file is opened?
When I decide to exit fullscreen after loading something directly or if I launch the player without loading a video or audio file, I'd really like it to not switch to fullscreen automatically if I load a new video or audio file. mpchc behaves like that and I love it since if I'm not already in fullscreen after the player is launched the first time, I most likely want to stay in windowed mode.

[Aleksoid1978]

Originally Posted by SamKook

A quick unrelated question: Is there a way to only launch the player in fullscreen when you open the player, like mpchc does instead of going to fullscreen every time a new file is opened?
When I decide to exit fullscreen after loading something directly or if I launch the player without loading a video or audio file, I'd really like it to not switch to fullscreen automatically if I load a new video or audio file. mpchc behaves like that and I love it since if I'm not already in fullscreen after the player is launched the first time, I most likely want to stay in windowed mode.

Try this - check "Remember window size" and "Remember window position".

[SamKook]

Originally Posted by Aleksoid1978

Try this - check "Remember window size" and "Remember window position".

I'll try it after I finish watching my current youtube video since I can't resume it if I restart the player, but if they do the same thing as mpchc, then I don't want those two enabled even if they actually prevent the player from going to fullscreen mode when a file is opened after the player is already started.

I want the player to zoom to 100% for every video when not in fullscreen(I have that enabled) and switching from HD to SD video will move the player default position to the left which really annoys me(I wish it could remember the position from the right side instead of the left).
So I'm not sure those will have the desired effect.

[SamKook]

It still goes to fullscreen with those 2 options enabled.

To make sure you understand what I mean, here's the 2 way I use the player 99% of the time.

1- Double-click on a video or use XBMC to launch mpcbe, the video goes into fullscreen, I watch it and the player exit automatically. Then I start the process again to watch another video. This is my main use of it and it works as intended in both mpc be and mpc hc.

2- a) Open the player directly without loading anything so it opens in windowed mode(so far both mpc be and mpc hc act the same).
b) Then open a video so I can watch it and do some other stuff on my computer at the same time. This is the step where mpc be and mpc hc differ.
Mpc hc won't go to fullscreen and this is exactly what I want since I'll continue to work on other things.
Mpc be on the other hand will always switch to fullscreen every time you open a video, regardless of the current state the player is in so I have to switch out of fullscreen for every video I watch.
c) Open another video without closing the player. Here mpc be will once again switch to fullscreen which will force me to switch back to windowed mode manually while mpc hc will stay in windowed mode.

So what I want is for it to only switch to fullscreen when the player gets started unless no video is loaded and for it to stay in windowed mode once it's started, even if I open a new video.

[Mercury_22]

Originally Posted by SamKook

It still goes to fullscreen with those 2 options enabled.

To make sure you understand what I mean, here's the 2 way I use the player 99% of the time.

1- Double-click on a video or use XBMC to launch mpcbe, the video goes into fullscreen, I watch it and the player exit automatically. Then I start the process again to watch another video. This is my main use of it and it works as intended in both mpc be and mpc hc.

2- a) Open the player directly without loading anything so it opens in windowed mode(so far both mpc be and mpc hc act the same).
b) Then open a video so I can watch it and do some other stuff on my computer at the same time. This is the step where mpc be and mpc hc differ.
Mpc hc won't go to fullscreen and this is exactly what I want since I'll continue to work on other things.
Mpc be on the other hand will always switch to fullscreen every time you open a video, regardless of the current state the player is in so I have to switch out of fullscreen for every video I watch.
c) Open another video without closing the player. Here mpc be will once again switch to fullscreen which will force me to switch back to windowed mode manually while mpc hc will stay in windowed mode.

So what I want is for it to only switch to fullscreen when the player gets started unless no video is loaded and for it to stay in windowed mode once it's started, even if I open a new video.

If I understand you correctly then your MPC-BE settings are mess up
I use MPC-BE in the same way as you in XBMC

<playercorefactory>
  <players>
    <player name="MPC-BE" type="ExternalPlayer" audio="true" video="true">
     <filename>C:\Program Files (x86)\MPC-BE\mpc-be.exe</filename>
     <args>"{1}" /fullscreen /close</args>
     <hidexbmc>true</hidexbmc>
     <hideconsole>false</hideconsole>
     <warpcursor>none</warpcursor>
   </player>
  </players>
</playercorefactory>

but when I'm using it outside XBMC doesn't go to full screen
So you should try reset your settings (at least disable "Lunch files in full screen" option if selected) and see what happens

[ontherocks]

Originally Posted by Aleksoid1978

2 - what's wrong with .wmv playback ??

Not .wmv, it's .wma files that still have the problem. The issue is, any wma file with sampling rate greater than 48kHz, is displayed in my AVR as 48kHz. and 2 Channel files with sampling rate greater than 48kHz are displayed as Multichannel PCM 5.1 in my AVR.

It is the same issue that was present with .wav files, which you fixed that in the previous wasapi fix for bit-exact playback. So now, .wma files remain to be fixed.

[Aleksoid1978]

Originally Posted by ontherocks

Not .wmv, it's .wma files that still have the problem. The issue is, any wma file with sampling rate greater than 48kHz, is displayed in my AVR as 48kHz. and 2 Channel files with sampling rate greater than 48kHz are displayed as Multichannel PCM 5.1 in my AVR.

It is the same issue that was present with .wav files, which you fixed that in the previous wasapi fix for bit-exact playback. So now, .wma files remain to be fixed.

Test this http://aleksoid.voserver.net/MPC-BE/...EXCLUSIVE_4.7z

set the checkbox as shown in screen:

[madshi]

0x60f is actually the correct channel mask for 5.1 audio. Many tools use 0x3f, though, so I guess both should be treated identically.

[nevcairiel]

Both 0x60f and 0x3f are correct for 5.1, it just depends which standard you read. The opinions on this have changed back and forth over the years.

[Aleksoid1978]

Originally Posted by nevcairiel

Both 0x60f and 0x3f are correct for 5.1, it just depends which standard you read. The opinions on this have changed back and forth over the years.

For WASAPI output mode 5.1 need set 0x60f channel mask. if set 0x3f - device initialization failed.

[madshi]

http://msdn.microsoft.com/en-us/windows/hardware/gg463023

In earlier versions of Windows (Windows 98/Me, Windows 2000, Windows XP with SP1, and Windows Server 2003), the interpretation of the channel mask 0x3F is that it assigns the six channels in the 5.1 format to the following speaker positions: FL, FR, FC, LFE, BL, and BR. (This is the back-speaker 5.1 configuration.) However, the interpretation in Windows XP with SP2, Windows Server 2003 with SP1, and Windows Vista is different: by convention, the 5.1 format with the channel mask 0x3F is interpreted to mean the side-speaker 5.1 configuration instead of the back-speaker 5.1 configuration.

Interpreting the channel mask in this manner eliminates the requirement to introduce a second 5.1-channel format descriptor to distinguish the side-speaker 5.1 configuration from the back-speaker 5.1 configuration. These two configurations are so similar that typical users might have difficulty distinguishing between them. Although having only a single 5.1-channel format descriptor avoids confusing users, it does require hardware vendors to remember to interpret the 0x3F channel mask to mean that channels 5 and 6 are assigned to the SL and SR speaker positions instead of the BL and BR positions. In return for having to remember this special-case interpretation of the channel mask for a 5.1 stream, vendors can spare users the difficulty of distinguishing between two very similar 5.1-channel format descriptors.

So basically, 0x60f is the correct mask to use, and 0x3f should be supported, but treated as 0x60f.

Originally Posted by Aleksoid1978

For WASAPI output mode 5.1 need set 0x60f channel mask. if set 0x3f - device initialization failed.

According to the Microsoft doc linked to above, XP and Windows 2003 might need 0x3f, if the latest Service Packs are not installed yet. Maybe you should first try to use 0x60f for WASAPI and if that fails, as plan B try 0x3f, too?

[alexins]

MPC-BE v1.2.1.0 -dev build 2961 (Nightly Builds) (sourceforge)
MPC-BE v1.2.1.0 -dev build 2961 (Nightly Builds) (Dev. MPC-BE)

[Aleksoid1978]

I remade - generating channels layout depending on the number of channels. For 5.1 - 0x60f

[nevcairiel]

Originally Posted by madshi

According to the Microsoft doc linked to above, XP and Windows 2003 might need 0x3f, if the latest Service Packs are not installed yet. Maybe you should first try to use 0x60f for WASAPI and if that fails, as plan B try 0x3f, too?

Thats not a big problem, because XP has no WASAPI.