Log in

View Full Version : Media Player Classic - BE Win32/x64


Pages : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 [96] 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235

ashlar42
18th October 2017, 23:36
Soooo... this acestream support how is it supposed to work? Does nobody know? I've searched for documentation without finding anything. The player does not accept an acestream://hexaddress format if I input it through the Open File/URL dialog with Acestream engine running in background.

Aleksoid1978
19th October 2017, 02:11
But also to be fair, since the previous "efficiency improvement" adapted from MPC-HC, the support for some of the drawing tags(\p<0/1/..> ) on both MPC-BE and MPC-HC is probably dropped. It is normal when using XySubfilter or very old version of MPC-BE and MPC-HC.


Thanks - fixed.

Aleksoid1978
19th October 2017, 02:13
Soooo... this acestream support how is it supposed to work? Does nobody know? I've searched for documentation without finding anything. The player does not accept an acestream://hexaddress format if I input it through the Open File/URL dialog with Acestream engine running in background.

URL like "acestream://..." is supported.

ryrynz
19th October 2017, 02:53
Since 1.5.2 is mostly small changes and bug fixes will you be releasing it this year? I think the previous update took much too long, maybe you need a Dev branch for any bigger changes
rather than making people have to run nightlies cos the last release was six months ago or something.

JarrettH
19th October 2017, 04:58
Since 1.5.2 is mostly small changes and bug fixes will you be releasing it this year? I think the previous update took much too long, maybe you need a Dev branch for any bigger changes
rather than making people have to run nightlies cos the last release was six months ago or something.

That would be nice! I switched to BE because I thought it was more active, not to be deferred to nightlies indefinitely (frankly I don't care about nightlies, the front-facing product is the stable release).

ryrynz
19th October 2017, 05:00
Yeah, I don't think there's any good reason why 1.5.2 couldn't be released in a few weeks or so. No need to drag it out, quick releases please.

ashlar42
19th October 2017, 10:44
URL like "acestream://..." is supported.I'm sorry... no. I take an acestream:// address, open it in Ace Player. Works just fine.

I stop playback in Ace Player, Ace Engine remains in the background, take the very same address, paste it in the "Open File/URL" dialog.

"Failed to render file"

Aleksoid1978
19th October 2017, 11:14
I'm sorry... no. I take an acestream:// address, open it in Ace Player. Works just fine.

I stop playback in Ace Player, Ace Engine remains in the background, take the very same address, paste it in the "Open File/URL" dialog.

"Failed to render file"

I don't know what's wrong - for me it's working.

ashlar42
19th October 2017, 13:08
I don't know what's wrong - for me it's working.Oh. Great... :(

Edit: I know what's wrong. I'm an idiot. I installed 1.5.1 on a different machine but here I still was with 1.5.0.

v0lt
19th October 2017, 19:34
@ryrynz
If someone does not want to use night builds, do not use it. But bug reports need to be checked for night builds.
If someone does not want to use the signed and recommended beta releases (which newer than the stable version), then this is his problem.
We will work as we like.

beter
19th October 2017, 23:24
Thanks - fixed.

Actually I should say thanks to MPC-BE team :)

nsnhd
23rd October 2017, 12:28
I tested YouTube HDR in the last stable version 2985, it's broken and madVR shows primaries BT.709
In version 2835, it's working fine, madVR shows primaries BT.2020

v0lt
23rd October 2017, 16:11
@nsnhd
Give a link. Which format do you have in the settings (or choose when playing)?

nsnhd
23rd October 2017, 18:12
In the Option->YouTube setting, I have chosen WebM, 1080/720, 60fps, HDR
And tried to play HDR URLs, such as https://www.youtube.com/watch?v=MuAmv2PsqEw&t=2s

v0lt
23rd October 2017, 18:46
@nsnhd
At me shows BT.2020. Splitter and decoder are built-in.
http://jpegshare.net/thumbs/d3/37/d3374b7b68dbcb08211b620772b88038.jpg (http://jpegshare.net/d3/37/d3374b7b68dbcb08211b620772b88038.jpg.html)

Grimsdyke
24th October 2017, 19:49
@ devs. I am not sure if anything can be done about the following but I have one blu-ray in my collection on which one of the featurettes is actually 6 minutes longer than the main movie itself. So, BE always loads the featurette because it seem to look only at the duration !!
Movie: around 95 minutes & 22 GB size.
Featurette: around 101 minutes but only around 4.2 GBs (720x576)

So, not only checking the duration but also the file size to maybe better determin what the main feature is ??
Or even better, maybe you can implement a raw/basic menu like KODI has ?
Thanks.

Aleksoid1978
24th October 2017, 23:09
You can select BD playlist in menu, after opening.

Grimsdyke
25th October 2017, 00:13
I know that, but KODI is doing this much more elegantly by preseting a menu before playing any file and it puts the correct file at the top of the list !! So KODI is able to figure out what most likely the main feature is.
And you don't think it is somewhat akward that BE considers a file on a Blu-Ray at 720x576 as the main movie at all ? Especially when a 22 GB/1080p file is also present ?

beter
25th October 2017, 01:46
There is problem when playing this file with internal DXVA decoder:
(Normal with SW decoder or with LAV decoder)
https://www.sendspace.com/file/e0g7yp

The computer is with Intel Graphic

Does the problem come back in rev. 3013?
I encounter the same problem again(Freeze on Nvidia card, strange presentation on Intel Graphics)

Aleksoid1978
25th October 2017, 02:00
Does the problem come back in rev. 3013?
I encounter the same problem again(Freeze on Nvidia card, strange presentation on Intel Graphics)

I will check. Confirm.

P.S. Fixed in rev. 3035, thanks for report.

Klaus1189
27th October 2017, 14:08
Hi Devs,
is it possible to enhance WebVTT support? Like this sample:
00:00:11.261 --> 00:00:12.762 align:start size:78% position:22%
Test 1

00:00:12.762 --> 00:00:14.347 size:88% position:56%
Test 2

00:00:14.347 --> 00:00:17.308 align:end position:100%
Test 3

If you're interested and it is possible on technical side, let me know to send you a sample file. :)

Aleksoid1978
27th October 2017, 14:13
Hi Devs,
is it possible to enhance WebVTT support? Like this sample:
00:00:11.261 --> 00:00:12.762 align:start size:78% position:22%
Test 1

00:00:12.762 --> 00:00:14.347 size:88% position:56%
Test 2

00:00:14.347 --> 00:00:17.308 align:end position:100%
Test 3

If you're interested and it is possible on technical side, let me know to send you a sample file. :)

Right now answer is no. To add full WebVTT subtitles support - need write conversion to ASS subtitles format. And it's can be for external files - but can't for embeded subtitles.

Klaus1189
27th October 2017, 19:02
Ok, do you already have plans to write WEBVTT to ASS conversion in the near future or is it something far away?

Aleksoid1978
28th October 2017, 02:51
Ok, do you already have plans to write WEBVTT to ASS conversion in the near future or is it something far away?

Not planned. I do not see the point of spending my time for WebVTT subtitles.

chros
28th October 2017, 09:31
Thank You guys for the new version!

P.J
29th October 2017, 09:35
This video is 16:9 Bottom Field First but plays as 1:1 Top Field First :confused:
https://drive.google.com/open?id=0B8q1LB-YXE2hOEJrWVlBbUhack0


General
Format : MPEG-4
Commercial name : DVCPRO HD
Format profile : QuickTime
Codec ID : qt 2005.03 (qt )
File size : 76.6 MiB
Duration : 5s 425ms
Overall bit rate mode : Constant
Overall bit rate : 118 Mbps

Video
ID : 1
Format : DV
Commercial name : DVCPRO HD
Codec ID : dvh6
Duration : 5s 425ms
Source duration : 5s 472ms
Bit rate mode : Constant
Bit rate : 97.8 Mbps
Encoded bit rate : 115 Mbps
Width : 1 280 pixels
Clean aperture width : 1 888 pixels
Height : 1 080 pixels
Clean aperture height : 1 062 pixels
Display aspect ratio : 1.185
Original display aspect ratio : 16:9
Clean aperture display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 29.970 (29970/1000) fps
Standard : NTSC
Color space : YUV
Chroma subsampling : 4:2:2
Scan type : Interlaced
Scan type, store method : Interleaved fields
Scan order : Bottom Field First
Compression mode : Lossy
Bits/(Pixel*Frame) : 2.360
Stream size : 74.6 MiB (97%)
Source stream size : 75.1 MiB (98%)
Language : English
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709

SeeMoreDigital
29th October 2017, 11:47
This video is 16:9 Bottom Field First but plays as 1:1 Top Field First :confused:
https://drive.google.com/open?id=0B8q1LB-YXE2hOEJrWVlBbUhack0It actually contains progressive frames ;)

P.J
29th October 2017, 19:39
It actually contains progressive frames ;)

Wrong.

v0lt
29th October 2017, 19:59
This video is 16:9 Bottom Field First but plays as 1:1 Top Field First :confused:
https://drive.google.com/open?id=0B8q1LB-YXE2hOEJrWVlBbUhack0
Why do you say that? On such video it is difficult to understand that this is an interlace.

SeeMoreDigital
29th October 2017, 21:25
Wrong.I'm not!

huhn
29th October 2017, 22:22
well the file should be BTF there is no question doesn't change that the file is 3:2 telecine and has progressive frame obviously...

Grimsdyke
29th October 2017, 22:23
I know that, but KODI is doing this much more elegantly by preseting a menu before playing any file and it puts the correct file at the top of the list !! So KODI is able to figure out what most likely the main feature is.
And you don't think it is somewhat akward that BE considers a file on a Blu-Ray at 720x576 as the main movie at all ? Especially when a 22 GB/1080p file is also present ?

Another reason why I think that this issue needs your attention is that BE not only picks the wrong file but through auto-loading external audio it loads two different audio commentary tracks that belong to the movie and not to the featurette !!
This also is not only totally wrong but also causes 100% CPU load for a few seconds on my, unfortunately not to fast, system.

Aleksoid1978
30th October 2017, 01:47
This video is 16:9 Bottom Field First but plays as 1:1 Top Field First :confused:
https://drive.google.com/open?id=0B8q1LB-YXE2hOEJrWVlBbUhack0


General
Format : MPEG-4
Commercial name : DVCPRO HD
Format profile : QuickTime
Codec ID : qt 2005.03 (qt )
File size : 76.6 MiB
Duration : 5s 425ms
Overall bit rate mode : Constant
Overall bit rate : 118 Mbps

Video
ID : 1
Format : DV
Commercial name : DVCPRO HD
Codec ID : dvh6
Duration : 5s 425ms
Source duration : 5s 472ms
Bit rate mode : Constant
Bit rate : 97.8 Mbps
Encoded bit rate : 115 Mbps
Width : 1 280 pixels
Clean aperture width : 1 888 pixels
Height : 1 080 pixels
Clean aperture height : 1 062 pixels
Display aspect ratio : 1.185
Original display aspect ratio : 16:9
Clean aperture display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 29.970 (29970/1000) fps
Standard : NTSC
Color space : YUV
Chroma subsampling : 4:2:2
Scan type : Interlaced
Scan type, store method : Interleaved fields
Scan order : Bottom Field First
Compression mode : Lossy
Bits/(Pixel*Frame) : 2.360
Stream size : 74.6 MiB (97%)
Source stream size : 75.1 MiB (98%)
Language : English
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709


What's wrong ?? playback issue or width/height params ??

P.J
30th October 2017, 06:23
What's wrong ?? playback issue or width/height params ??

Both of Aspect ratio and Field order, I explained.
MPC doesn't read the metadata at all.

Aleksoid1978
30th October 2017, 10:02
Both of Aspect ratio and Field order, I explained.
MPC doesn't read the metadata at all.

I check this file:
Scan order : top field first fmpeg decode.
About AR - MPC-BE read correct value from container(.mov) header.
16:9 store in video stream and user can select what priority in internal video decoder properties.

P.J
30th October 2017, 10:57
I check this file:
Scan order : top field first fmpeg decode.
About AR - MPC-BE read correct value from container(.mov) header.
16:9 store in video stream and user can select what priority in internal video decoder properties.

Scan order is bottom field first in mediainfo.

Aleksoid1978
30th October 2017, 11:12
Scan order is bottom field first in mediainfo.

So what ?? As i say - ffmpeg's decoder detect(and use) scanorder is top field first.

P.J
30th October 2017, 15:32
So what ?? As i say - ffmpeg's decoder detect(and use) scanorder is top field first.

Then it doesn't relate to MPC video decoder? =/

Klaus1189
30th October 2017, 16:06
MPC-BE crashes when it starts automatically in Fullscreen, but I think I got the reason for it - I disabled screensaver and it works fine for over 100+ files since then. If you need other settings which can be part of it, let me know.

I did a fresh new installation of Win10 Pro x64 1709 on my machine and again MPC-BE crashed sometimes when starting playback.
But after I disabled screensaver, I never got a crash anymore. The crash lets Win10 to pop up a small window which I have close but no more infos are given.

huhn
30th October 2017, 16:12
try the event viewer.

@P.J
these informations can be stored in more than one place. the stream it self doesn't seem to have the correct informations primaries and other stuff like that are missing or ffmpeg can't read them.

Klaus1189
30th October 2017, 16:15
Ah OK, looks like madvr is causing this?
mpc-be64.exe
1.5.2.3040
59f157b9
madVR64.ax
0.92.8.0
59f4bfa2
c00000fd
000000000000c2a8
2694
01d350acbe0d1dad

P.J
30th October 2017, 19:33
@P.J
these informations can be stored in more than one place. the stream it self doesn't seem to have the correct informations primaries and other stuff like that are missing or ffmpeg can't read them.

LAV video decoder+MPC MP4/MOV source plays it in correct 16:9 aspect ratio, only field order needs to be fixed.

Edit: I even remuxed it in mkv but it doesn't still care about the container's metadata =/

Aleksoid1978
31st October 2017, 08:55
LAV video decoder+MPC MP4/MOV source plays it in correct 16:9 aspect ratio, only field order needs to be fixed.

Edit: I even remuxed it in mkv but it doesn't still care about the container's metadata =/

LAV Video also have options for AR, change it and see result ))

Aleksoid1978
31st October 2017, 08:56
Who say that's MI show correct for scan order ??
If playback is good and don't have artefact - maybe all ok in ffmpeg decoder.

Grimsdyke
31st October 2017, 09:47
@ Klaus1189. I think you handle the German translation so I would like to let you know that in the 'command line help' there seem to be a tab missing at the /fullscreen switch.

@Devs. The /open switch helps a little bit in what I recently reported. Is there any way to have this switch always activated ??

Klaus1189
31st October 2017, 10:18
@ Klaus1189. I think you handle the German translation so I would like to let you know that in the 'command line help' there seem to be a tab missing at the /fullscreen switch.

What version are you using? Last time german translation was changed is r2944, so 1.5.1 stable and and all builds since then should be fine.
I use a high dpi screen and it got mixed up, so in r2792+r2797+r2798 it was redesigned
see: https://forum.doom9.org/showthread.php?p=1814933#post1814933

looks fine to me :)
https://drive.google.com/file/d/0B4y5u0gBKYqbNThjbFVJM0hRTEU/view?usp=sharing

Grimsdyke
31st October 2017, 10:43
Thanks Klaus, I will always try to make sure that I use latest nightlys. O.K., here in my installation there is no space after /fullscreen - will check again with the next build.

P.J
31st October 2017, 14:18
LAV Video also have options for AR, change it and see result ))

Even google player shows correct aspect ratio.
No problem if you don't want to fix it. Then the container's info is worth nothing ;)

Grimsdyke
31st October 2017, 21:44
O.K., since I am not sure if what I posted is important enough for the devs to work on - here is my workaround in case anyone is interested.
'Run' =>
C:\Program Files\MPC-BE\mpc-be.exe E:\BDMV\STREAM\00003.m2ts /open ;Night of the living Dead_23.976

With this command the correct file is loaded paused which makes the additional loading of the external audio tracks much more smoothly !!
And since I have to have a few of these commands for other blu-rays that mpc-be has problems with on my system (see my DTS thread) I also added movie name, etc.

(Drive letters, locations, etc. may be different on other systems)

Jtacdf
1st November 2017, 03:14
Even google player shows correct aspect ratio.
No problem if you don't want to fix it. Then the container's info is worth nothing ;)

Your 1080i file playbacks, with both MPC-BE/HC, in the correct 16:9 aspect ratio when "check/use stream aspect ratio" box is ticked with LAV filter/internal video decoder.
The file container's info is being read correctly. Nothing wrong with any player.