View Full Version : Media Player Classic - BE Win32/x64
Mercury_22
20th June 2013, 05:10
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
20th June 2013, 06:21
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 (http://aleksoid.voserver.net/MPC-BE/mpc-be.exe_WASAPI_EXCLUSIVE.7z) for bit-exact playback. So now, .wma files remain to be fixed.
Aleksoid1978
20th June 2013, 06:41
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 (http://aleksoid.voserver.net/MPC-BE/mpc-be.exe_WASAPI_EXCLUSIVE.7z) for bit-exact playback. So now, .wma files remain to be fixed.
Test this http://aleksoid.voserver.net/MPC-BE/mpc-be.exe_WASAPI_EXCLUSIVE_4.7z
set the checkbox as shown in screen:
http://i.imgur.com/vWAdXYm.png
madshi
20th June 2013, 06:59
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
20th June 2013, 07:12
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
20th June 2013, 07:21
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
20th June 2013, 07:58
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.
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
20th June 2013, 08:01
MPC-BE v1.2.1.0 -dev build 2961 (Nightly Builds) (https://sourceforge.net/projects/mpcbe/files/MPC-BE/Nightly Builds (from svn trunk)/MPC-BE v1.2.1.0 -dev build 2961/) (sourceforge)
MPC-BE v1.2.1.0 -dev build 2961 (Nightly Builds) (http://dev.mpc-next.ru/index.php/topic,1595.0.html) (Dev. MPC-BE)
Aleksoid1978
20th June 2013, 08:03
I remade - generating channels layout depending on the number of channels. For 5.1 - 0x60f :)
nevcairiel
20th June 2013, 08:23
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. ;)
madshi
20th June 2013, 08:24
Haha, you're right. Where do I have my head? :)
SamKook
20th June 2013, 12:59
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
I still want them to go to fullscreen when I simply double-click a video file outside of XBMC so I want the "Launch files in fullscreen" option enabled. I simply wish there would be a way to make it behave like mpc hc.
I reset my settings with every version I install so I doubt they would be messed up.
Mercury_22
20th June 2013, 13:42
I still want them to go to fullscreen when I simply double-click a video file outside of XBMC so I want the "Launch files in fullscreen" option enabled. I simply wish there would be a way to make it behave like mpc hc.
I reset my settings with every version I install so I doubt they would be messed up.
Now I think I understand you
So what you're saying is that if the player is already open when opening a file (File -> (Quick)Open File) MPC-HC is ignoring the enabled "Launch files in fullscreen" option while MPC-BE doesn't ?
If that's so to me it looks more like a bug in MPC-HC :rolleyes:
To get the behavior you want from MPC-BE disable "Launch files in fullscreen" and modify the registry for every type of file you have associated with MPC-BE like in this example for ".mkv" [HKEY_CLASSES_ROOT\mpc-be.mkv\shell\open\command]
@="\"C:\\Program Files (x86)\\MPC-BE\\mpc-be.exe\" \"%1\" /fullscreen"
All this assuming that now I understood you correctly :)
ontherocks
20th June 2013, 17:09
Edited
SamKook
20th June 2013, 17:37
Now I think I understand you
So what you're saying is that if the player is already open when opening a file (File -> (Quick)Open File) MPC-HC is ignoring the enabled "Launch files in fullscreen" option while MPC-BE doesn't ?
If that's so to me it looks more like a bug in MPC-HC :rolleyes:
To get the behavior you want from MPC-BE disable "Launch files in fullscreen" and modify the registry for every type of file you have associated with MPC-BE like in this example for ".mkv" [HKEY_CLASSES_ROOT\mpc-be.mkv\shell\open\command]
@="\"C:\\Program Files (x86)\\MPC-BE\\mpc-be.exe\" \"%1\" /fullscreen"
All this assuming that now I understood you correctly :)
That's exactly what I meant.
From the way the option is called, I agree that it could be an mpc hc bug, but it's the perfect behavior, at least in my mind since I can't think of why you would want it to go to fullscreen once the player is already opened.
An option called "launch the player in fullscreen"(when a file is opened at the same time) would be really nice to have too.
I used to edit the registry for every file type to enable exiting the player before the "every time" option was implemented and it was so much trouble when it was updating time or it changed by itself(don't remember what was causing this though) that I don't want to do that ever again. Especially since I keep the version number in the installation folder name.
I'll probably simply use 2 different mpc be installation with ini settings instead, hoping window can pin them both properly to the taskbar.
VipZ
20th June 2013, 21:41
New Audio renderer is working great.
Any reason why this is not playing at 48000Hz,
http://i.imgur.com/CPRWcIs.jpg
2.0 plays fine at 16/24/32bit at 44100,48000,96000Hz
7.1 plays fine at 16/32bit at 48000,96000Hz
5.1 fails at bit exact with 16/32bit @ 48000Hz /w both LAV and MPC (Used both Test4 + SVN to test)
2.0 at 16/24bit at 192000Hz fails to output any sound if my sound is set at 96000Hz and works when set at 192000Hz, is this expected?
MPC-BE can crash if changing LAV Audio output settings during playback.
Let me know if you want me to test anything specific
Aleksoid1978
20th June 2013, 23:07
New Audio renderer is working great.
Any reason why this is not playing at 48000Hz,
http://i.imgur.com/CPRWcIs.jpg
2.0 plays fine at 16/24/32bit at 44100,48000,96000Hz
7.1 plays fine at 16/32bit at 48000,96000Hz
5.1 fails at bit exact with 16/32bit @ 48000Hz /w both LAV and MPC (Used both Test4 + SVN to test)
2.0 at 16/24bit at 192000Hz fails to output any sound if my sound is set at 96000Hz and works when set at 192000Hz, is this expected?
MPC-BE can crash if changing LAV Audio output settings during playback.
Let me know if you want me to test anything specific
Upload please "problem" file - i see what's happened :)
VipZ
20th June 2013, 23:56
Upload please "problem" file - i see what's happened :)
If you referring to a 192Khz sample, here's one. http://www.mediafire.com/download/ta5yg3lhkgbanr7/192Khz.flac
I tested the sample and it now works, I am pretty positive I closed other audio applications to ensure it had exclusive access.
With regards to the 5.1 issue, this is any 5.1 audio file, none work bit exact. Changing my audio output to different bit/Hz or channel count makes no difference, always plays at the shared mode setting.
The MPC-BE crashing seems to occur if the mode changed from bit exact capable to shared mode config or vice versa.
Aleksoid1978
21st June 2013, 00:56
If you referring to a 192Khz sample, here's one. http://www.mediafire.com/download/ta5yg3lhkgbanr7/192Khz.flac
I tested the sample and it now works, I am pretty positive I closed other audio applications to ensure it had exclusive access.
With regards to the 5.1 issue, this is any 5.1 audio file, none work bit exact. Changing my audio output to different bit/Hz or channel count makes no difference, always plays at the shared mode setting.
The MPC-BE crashing seems to occur if the mode changed from bit exact capable to shared mode config or vice versa.
As i understand - any 5.1 audio do not work Exclusive + bit-exact.
P.S. Test this build, i do some change for 5.1 output - http://aleksoid.voserver.net/MPC-BE/mpc-be.exe_WASAPI_EXCLUSIVE_5(test_5.1_channels_layout).7z
And this build - http://aleksoid.voserver.net/MPC-BE/mpc-be.exe_WASAPI_EXCLUSIVE_6.7z. In this build - at the start doing detect supported output format and then try to use this values.
VipZ
21st June 2013, 07:47
Awesome, v6 working with both 16/32bit :)
Reported as 0x3f
secvensor
21st June 2013, 23:53
Huge minus in adjustment:
http://i48.fastpic.ru/big/2013/0622/54/8519f4419dfbae038d86275992919f54.jpg
Start play audio in Full Screen and changes the size of a window if it has been adjusted by the previous file.
It is necessary to fix the size of a window and not to expand it on all screen if the file does not contain video and the user does not want to see any badges with the album name in the main window. Thus to leave possibility to start in Full Screen mode video file only.
VipZ
22nd June 2013, 12:09
Any chance the changes for mpc-be.exe_WASAPI_EXCLUSIVE_6 could be merged into the SVN?
It has also seemed to fix the MPC-BE crash issue and 5.1 when trying bit exact looked quite out of sync and also looks corrected with this build.
judelaw
22nd June 2013, 15:36
Start play audio in Full Screen and changes the size of a window if it has been adjusted by the previous file.
It is necessary to fix the size of a window and not to expand it on all screen if the file does not contain video and the user does not want to see any badges with the album name in the main window. Thus to leave possibility to start in Full Screen mode video file only.
try this test : http://www.mediafire.com/download/yrk7ccc77pcr8qk/mpc-be_r2967_AudioOnly_01.7z
secvensor
22nd June 2013, 18:16
judelaw
Drag and Drop works good, but double click all the same deduces in the Full screen.
judelaw
22nd June 2013, 19:44
judelaw
Drag and Drop works good, but double click all the same deduces in the Full screen.
ok, http://www.mediafire.com/download/6b9ck2er9hc2eke/mpc-be_x86_r2967_AudioOnly_02.7z
secvensor
22nd June 2013, 20:02
judelaw
It works! Thanks!
Aleksoid1978
23rd June 2013, 01:45
Any chance the changes for mpc-be.exe_WASAPI_EXCLUSIVE_6 could be merged into the SVN?
It has also seemed to fix the MPC-BE crash issue and 5.1 when trying bit exact looked quite out of sync and also looks corrected with this build.
Yes :)
SamKook
23rd June 2013, 03:17
I've been using the wasapi exclusive v6 all day and I've been experiencing 1 to 3 glitches(the audio cut for a fraction of a second with a noticeable sound) in the audio per hour long video. The glitches aren't in the files themselves since if I seek back, it plays fine.
They happen both with LAV filters and the internal decoders.
adrianmak
23rd June 2013, 05:03
is there any benefit to use x64 version?
wanezhiling
23rd June 2013, 05:12
In most case, no.
VipZ
23rd June 2013, 10:12
Yes :)
Thanks
I've been using the wasapi exclusive v6 all day and I've been experiencing 1 to 3 glitches(the audio cut for a fraction of a second with a noticeable sound) in the audio per hour long video.
Update: This occurred for me as well, seeking back and then no glitch.
Update: It seems every time bit exact cant be used directly the adjustment can results in out of sync audio, ie if I switch to using my sound card for headphones output on 5.1 audio this adjustment can result in OoS audio. Disabling bit exact or using shared mode does not seem to result in OoS audio, also ticking the use system layout seems to correct.
Aleksoid1978
23rd June 2013, 13:19
Thanks
Update: This occurred for me as well, seeking back and then no glitch.
Update: It seems every time bit exact cant be used directly the adjustment can results in out of sync audio, ie if I switch to using my sound card for headphones output on 5.1 audio this adjustment can result in OoS audio. Disabling bit exact or using shared mode does not seem to result in OoS audio, also ticking the use system layout seems to correct.
Test on svn version - http://rghost.ru/46959998
VipZ
23rd June 2013, 20:35
Test on svn version - http://rghost.ru/46959998
The above results were with the latest SVN already.
Aleksoid1978
24th June 2013, 02:22
The above results were with the latest SVN already.
Try this build - http://aleksoid.voserver.net/MPC-BE/mpc-be.exe_WASAPI_EXCLUSIVE_10.7z
if there are glitches - see if there are a file mpc-be.log on your Desktop.
If there is - to unload it for me.
SamKook
24th June 2013, 03:29
That only took 28 secs:
2013.06.23 22:28:28.603 : CMpcAudioRenderer::RenderWasapiBuffer() - Data Event, not enough data, requested: 43200[2400], available: 27648
2013.06.23 22:28:28.603 : CMpcAudioRenderer::RenderWasapiBuffer() - Data Event, not enough data, requested: 43200[2400], available: 27648
2013.06.23 22:28:28.051 : CMpcAudioRenderer::RenderWasapiBuffer() - Data Event, not enough data, requested: 43200[2400], available: 41472
2013.06.23 22:28:28.401 : CMpcAudioRenderer::RenderWasapiBuffer() - Data Event, not enough data, requested: 43200[2400], available: 0
2013.06.23 22:28:28.503 : CMpcAudioRenderer::RenderWasapiBuffer() - Data Event, not enough data, requested: 43200[2400], available: 39744
Aleksoid1978
24th June 2013, 04:00
That only took 28 secs:
2013.06.23 22:28:28.603 : CMpcAudioRenderer::RenderWasapiBuffer() - Data Event, not enough data, requested: 43200[2400], available: 27648
2013.06.23 22:28:28.603 : CMpcAudioRenderer::RenderWasapiBuffer() - Data Event, not enough data, requested: 43200[2400], available: 27648
2013.06.23 22:28:28.051 : CMpcAudioRenderer::RenderWasapiBuffer() - Data Event, not enough data, requested: 43200[2400], available: 41472
2013.06.23 22:28:28.401 : CMpcAudioRenderer::RenderWasapiBuffer() - Data Event, not enough data, requested: 43200[2400], available: 0
2013.06.23 22:28:28.503 : CMpcAudioRenderer::RenderWasapiBuffer() - Data Event, not enough data, requested: 43200[2400], available: 39744
What file you open. What filter use ???
P.S. Update build - http://aleksoid.voserver.net/MPC-BE/mpc-be.exe_WASAPI_EXCLUSIVE_11.7z, fix time in log file :)
Can you just open file and stay playback before any glitch.
About log - this usually happened after open and seeking. This should not happen on the playing time.
SamKook
24th June 2013, 04:16
What file you open. What filter use ???
Video: MPEG4 Video (H264) 1280x720 23.976fps [Video]
Audio: Dolby AC3 48000Hz 6ch 384kbps [Audio]
with LAVfilters
same thing with the internal decoders and a different file with the same specs:
2013.06.23 23:13:13.017 : CMpcAudioRenderer::RenderWasapiBuffer() - Data Event, not enough data, requested: 43200[2400], available: 27648
2013.06.23 23:13:13.018 : CMpcAudioRenderer::RenderWasapiBuffer() - Data Event, not enough data, requested: 43200[2400], available: 27648
2013.06.23 23:14:14.065 : CMpcAudioRenderer::RenderWasapiBuffer() - Data Event, not enough data, requested: 43200[2400], available: 41472
Edit: Tried v11
The first 2 lines from the following log were from when I resumed a file and the 3rd was a glitch during playback:
2013.06.23 23:19:14.400 : CMpcAudioRenderer::RenderWasapiBuffer() - Data Event, not enough data, requested: 43200[2400], available: 27648
2013.06.23 23:19:14.400 : CMpcAudioRenderer::RenderWasapiBuffer() - Data Event, not enough data, requested: 43200[2400], available: 27648
2013.06.23 23:19:36.449 : CMpcAudioRenderer::RenderWasapiBuffer() - Data Event, not enough data, requested: 43200[2400], available: 41472
Aleksoid1978
24th June 2013, 04:32
Video: MPEG4 Video (H264) 1280x720 23.976fps [Video]
Audio: Dolby AC3 48000Hz 6ch 384kbps [Audio]
with LAVfilters
same thing with the internal decoders and a different file with the same specs:
2013.06.23 23:13:13.017 : CMpcAudioRenderer::RenderWasapiBuffer() - Data Event, not enough data, requested: 43200[2400], available: 27648
2013.06.23 23:13:13.018 : CMpcAudioRenderer::RenderWasapiBuffer() - Data Event, not enough data, requested: 43200[2400], available: 27648
2013.06.23 23:14:14.065 : CMpcAudioRenderer::RenderWasapiBuffer() - Data Event, not enough data, requested: 43200[2400], available: 41472
Edit: Tried v11
The first 2 lines from the following log were from when I resumed a file and the 3rd was a glitch during playback:
2013.06.23 23:19:14.400 : CMpcAudioRenderer::RenderWasapiBuffer() - Data Event, not enough data, requested: 43200[2400], available: 27648
2013.06.23 23:19:14.400 : CMpcAudioRenderer::RenderWasapiBuffer() - Data Event, not enough data, requested: 43200[2400], available: 27648
2013.06.23 23:19:36.449 : CMpcAudioRenderer::RenderWasapiBuffer() - Data Event, not enough data, requested: 43200[2400], available: 41472
1 - Can you test with internal filters only.
2 - Can you upload a short sample on this file.
SamKook
24th June 2013, 05:04
1 - Can you test with internal filters only.
2 - Can you upload a short sample on this file.
1- Already did in my previous post(the first set of log), same result.
2- It's not specific to one file, all files I played so far did the same thing.
I tried with the following file which had 24 bit input(the same as my output) and also got a glitch less than a minute after playback which is when it happens the most often.
Video: Windows Media Video 9 1280x720 24fps 5000kbps [Raw Video 1]
Audio: WMA Pro 44100Hz stereo 440kbps [Raw Audio 0]
Aleksoid1978
24th June 2013, 06:11
1- Already did in my previous post(the first set of log), same result.
2- It's not specific to one file, all files I played so far did the same thing.
I tried with the following file which had 24 bit input(the same as my output) and also got a glitch less than a minute after playback which is when it happens the most often.
Video: Windows Media Video 9 1280x720 24fps 5000kbps [Raw Video 1]
Audio: WMA Pro 44100Hz stereo 440kbps [Raw Audio 0]
Strangely ...
P.S. I open video + run WinRar benchmark - and do not have this issue. I will got "not enough data" only at start(and after seeking).
Aleksoid1978
24th June 2013, 08:42
1- Already did in my previous post(the first set of log), same result.
2- It's not specific to one file, all files I played so far did the same thing.
I tried with the following file which had 24 bit input(the same as my output) and also got a glitch less than a minute after playback which is when it happens the most often.
Video: Windows Media Video 9 1280x720 24fps 5000kbps [Raw Video 1]
Audio: WMA Pro 44100Hz stereo 440kbps [Raw Audio 0]
Test please this 2 build and give me a log.
http://aleksoid.voserver.net/MPC-BE/mpc-be.exe_WASAPI_EXCLUSIVE_12a.7z
http://aleksoid.voserver.net/MPC-BE/mpc-be.exe_WASAPI_EXCLUSIVE_12b.7z
VipZ
24th June 2013, 14:40
Test please this 2 build and give me a log.
http://aleksoid.voserver.net/MPC-BE/mpc-be.exe_WASAPI_EXCLUSIVE_12a.7z
http://aleksoid.voserver.net/MPC-BE/mpc-be.exe_WASAPI_EXCLUSIVE_12b.7z
Thanks
Will test tonight, would you expect this to also help with the out of sync audio?
SamKook
24th June 2013, 15:22
Test please this 2 build and give me a log.
http://aleksoid.voserver.net/MPC-BE/mpc-be.exe_WASAPI_EXCLUSIVE_12a.7z
http://aleksoid.voserver.net/MPC-BE/mpc-be.exe_WASAPI_EXCLUSIVE_12b.7z
v12a behaves just like the others:
http://www.mediafire.com/?a6u9444idi9d84f
v12b always go terribly out of sync after 10+ minutes of playback with no glitch in the log, but I thought I heard some smaller than usual ones(could have been in the file though, I didn't seek back since I wanted to keep the log clean):
http://www.mediafire.com/?6d7zp794dtspb6y
Casshern
24th June 2013, 21:52
Do the settings for MPC-HC and MPC-BE peacefully coexist? Can install both on one machine, so that they behave completely independent?
SamKook
24th June 2013, 22:18
I don't remember when you're using the registry but I would guess yes.
And if you check the "Store settings to .ini file", you can have as many version of the 2 as you want at the same time.
Aleksoid1978
24th June 2013, 23:28
Do the settings for MPC-HC and MPC-BE peacefully coexist? Can install both on one machine, so that they behave completely independent?
Yes - it's use different key in registry
Aleksoid1978
24th June 2013, 23:29
v12a behaves just like the others:
http://www.mediafire.com/?a6u9444idi9d84f
v12b always go terribly out of sync after 10+ minutes of playback with no glitch in the log, but I thought I heard some smaller than usual ones(could have been in the file though, I didn't seek back since I wanted to keep the log clean):
http://www.mediafire.com/?6d7zp794dtspb6y
Thanks - i think i understand what's wrong.
Aleksoid1978
25th June 2013, 01:36
SamKook, VipZ
Try this build - http://aleksoid.voserver.net/MPC-BE/mpc-be.exe_WASAPI_EXCLUSIVE_13a.7z
About glitch & A/V Desync - i wait log file from you. It's create on Desktop.
v0lt
25th June 2013, 03:45
MPC-BE v1.2.1.0 -dev build 2972 (http://dev.mpc-next.ru/index.php/topic,1606.msg8809.html#msg8809)
Aleksoid1978
25th June 2013, 04:48
Thanks
Will test tonight, would you expect this to also help with the out of sync audio?
Can you upload examples of the file on which you are out of A/V sync. And - what decoding you use, Bitstream or PCM output ?.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.