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

Aleksoid1978
11th March 2019, 00:10
Version 1.5.3 (build 4455) beta

A few settings tried
https://imgur.com/a/EgG4AhK

Filtros externos = external filters

I changed that area by adding LAV and selecting PREFER, but that didn't help, still crackling.

Try reset settings and delete all external filters. Just for test.

P.S. Check on latest SVN - https://yadi.sk/d/hlf1lfC8mKU58/!_last

Perenista
11th March 2019, 04:57
Try reset settings and delete all external filters. Just for test.I was looking for this and couldn't find (reset to factory settings). Where should I go?

Aleksoid1978
11th March 2019, 05:17
I was looking for this and couldn't find (reset to factory settings). Where should I go?

Options -> Miscellaneous -> Settings management

Grimsdyke
11th March 2019, 10:20
I love the dual-audio out feature of BE !! But unfortunately I do need much more gain on HDMI (=> connected to TV) than on 5.1-Analog (=> connected to Amplifier).
Would it be possible to add a second slider so that gain could be adjusted independently ?

Aleksoid1978
11th March 2019, 10:25
I love the dual-audio out feature of BE !! But unfortunately I do need much more gain on HDMI (=> connected to TV) than on 5.1-Analog (=> connected to Amplifier).
Would it be possible to add a second slider so that gain could be adjusted independently ?

Volume slider ?? If so - not.

Manni
11th March 2019, 10:40
I love the dual-audio out feature of BE !! But unfortunately I do need much more gain on HDMI (=> connected to TV) than on 5.1-Analog (=> connected to Amplifier).
Would it be possible to add a second slider so that gain could be adjusted independently ?

If you need more volume on HDMI it could be because you are converting to LPCM before sending to the AVR. If it's an option in your setup, try to bitstream audio over HDMI, volume tends to be higher in that case. But then of course you have no volume control from MPC.

Grimsdyke
11th March 2019, 10:50
@Aleksoid. I mean: Options -> Audio -> Sound Processing -> Volume Control -> GAIN. Would need one slider for each audio out.
@Manni. Thanx, I will check that.

Aleksoid1978
11th March 2019, 11:05
Dual audio not working for bitstreaming + PCM output.

Only bitstream or PCM

Grimsdyke
11th March 2019, 11:18
Bitstreaming over HDMI seem to be not louder on my equipment.

Manni
11th March 2019, 11:42
Bitstreaming over HDMI seem to be not louder on my equipment.

It's not always the case, but it was worth checking :)

beter
22nd March 2019, 00:33
Update for translation of Chinese traditional and Dutch
https://www.sendspace.com/file/x1lt1i

Anima123
22nd March 2019, 03:36
Using recent mpc-be builds (till 4455, didn't test latest), the progress bar will not appear for a while after starting playback the video, and certainly not be able to enter full-screen mode by Alt-Enter.

mkver
22nd March 2019, 21:44
DVBSUB subtitles are usually displayed until the next subtitle packet (often an empty subtitle that just says "Stop displaying the previous subtitles") is due for display. If a file does not contain these end-of-display subtitles, MPC-BE crashes. Such files can be produced by e.g. splitting files with mkvmerge. It doesn't seem to matter whether the DVBSUB packet (in Matroska) is in a SimpleBlock or a BlockGroup with an explicit nonzero duration or a BlockGroup with a zero duration. Here (https://www.dropbox.com/s/cp0i7s6f198l30m/DVBSUB.Zero.Duration.mkv?dl=0), here (https://www.dropbox.com/s/vkkeqp5lxds4dof/DVBSUB.Nonzero.Duration.mkv?dl=0) and here (https://www.dropbox.com/s/hq8mtspzrq47cy6/DVBSUB.SimpleBlock.mkv?dl=0) are samples for this. I can sometimes produce crashes if I am near the end of a transport stream with DVBSUBs as active subtitles, so this doesn't seem to be limited to Matroska, although it is not so easy to reproduce the crash there.

(If a DVBSUB in a BlockGroup has a nonzero duration, then actually this should be used as the duration; it should override the duration implied by the next subtitle packet. (The reason I am treating a BlockGroup with a zero duration specially is that FFmpeg has a bug in that it writes duration zero if the duration is unknown.))

Arm3nian
23rd March 2019, 10:13
If I seek before a file starts to play initially, MPC-BE stops responding. Same if I seek a second time too quickly after the first one. Turning off wait for render queue in madVR makes it better, but it still crashes. This has been happening ever since the UI change. I've tried nightlies of MPC-BE and LAV for a month but it does the same thing.

Also, before the UI change, if I had 2 screens connected, and I switched the file to fullscreen, and pulled the display plug on one of them, it would automatically continue playing on the other display. Doesn't do that anymore.

Aleksoid1978
23rd March 2019, 10:44
DVBSUB subtitles are usually displayed until the next subtitle packet (often an empty subtitle that just says "Stop displaying the previous subtitles") is due for display. If a file does not contain these end-of-display subtitles, MPC-BE crashes. Such files can be produced by e.g. splitting files with mkvmerge. It doesn't seem to matter whether the DVBSUB packet (in Matroska) is in a SimpleBlock or a BlockGroup with an explicit nonzero duration or a BlockGroup with a zero duration. Here (https://www.dropbox.com/s/cp0i7s6f198l30m/DVBSUB.Zero.Duration.mkv?dl=0), here (https://www.dropbox.com/s/vkkeqp5lxds4dof/DVBSUB.Nonzero.Duration.mkv?dl=0) and here (https://www.dropbox.com/s/hq8mtspzrq47cy6/DVBSUB.SimpleBlock.mkv?dl=0) are samples for this. I can sometimes produce crashes if I am near the end of a transport stream with DVBSUBs as active subtitles, so this doesn't seem to be limited to Matroska, although it is not so easy to reproduce the crash there.

(If a DVBSUB in a BlockGroup has a nonzero duration, then actually this should be used as the duration; it should override the duration implied by the next subtitle packet. (The reason I am treating a BlockGroup with a zero duration specially is that FFmpeg has a bug in that it writes duration zero if the duration is unknown.))

Thanks - fixed.

Aleksoid1978
23rd March 2019, 10:45
If I seek before a file starts to play initially, MPC-BE stops responding. Same if I seek a second time too quickly after the first one. Turning off wait for render queue in madVR makes it better, but it still crashes. This has been happening ever since the UI change. I've tried nightlies of MPC-BE and LAV for a month but it does the same thing.

Also, before the UI change, if I had 2 screens connected, and I switched the file to fullscreen, and pulled the display plug on one of them, it would automatically continue playing on the other display. Doesn't do that anymore.

1 - reset settings.
2 - try without LAV and madVR.

Anima123
23rd March 2019, 19:33
Using recent mpc-be builds (till 4455, didn't test latest), the progress bar will not appear for a while after starting playback the video, and certainly not be able to enter full-screen mode by Alt-Enter.

Just tried the latest nightly and found the problem has gone. Thanks a lot!

mkver
24th March 2019, 11:42
Thanks - fixed.
Works fine in 4466. Thanks.

Klaus1189
1st April 2019, 08:31
Thank you very much for 1.5.3 :)

v0lt
1st April 2019, 09:12
MPC-BE 1.5.3 (build 4488) stable (https://sourceforge.net/projects/mpcbe/files/MPC-BE/Release%20builds/1.5.3/)

MPC-BE 1.5.4 Nightly builds: main file store (https://yadi.sk/d/hlf1lfC8mKU58), alternative (https://yadi.sk/d/r7JYQ2NjHvE4lA)
Also new and old versions can be found on VideoHelp.com (https://www.videohelp.com/software/MPC-BE).

filler56789
1st April 2019, 09:36
MPC-BE 1.5.3 (build 4488) stable (https://sourceforge.net/projects/mpcbe/files/MPC-BE/Release%20builds/1.5.3/)

:thanks:

chros
1st April 2019, 10:06
Thanks guys, I'll start to use it during the next couple of days and report back :)

ryrynz
1st April 2019, 11:24
Very nice release. Excellent work.

GCRaistlin
1st April 2019, 16:52
Is there any chance that these feature requests (http://forum.doom9.org/showpost.php?p=1865267&postcount=6073) will be implemented?

JarrettH
2nd April 2019, 03:21
What is new or fixed in 1.5.3?:confused:

Edit-found it in the log the installer comes with

Aleksoid1978
2nd April 2019, 05:21
Info about release on first page of this thread :)

v0lt
2nd April 2019, 06:14
What is new or fixed in 1.5.3?:confused:

Edit-found it in the log the installer comes with
https://sourceforge.net/p/mpcbe/code/HEAD/tree/tags/release_1.5.3/docs/Changelog.txt

Manni
2nd April 2019, 13:20
Thanks for the new version, keep up the good work!

P.J
4th April 2019, 13:36
I have a video file that MPC-BE can't play it unless I add LAV+Splitter Source as external filter :confused:

General
Format : MPEG-4
Commercial name : DVCPRO HD
Format profile : QuickTime
Codec ID : qt 2005.03 (qt )
File size : 1.23 GiB
Duration : 3 min 42 s
Overall bit rate : 47.6 Mb/s
Encoded date : UTC 2006-12-23 23:14:13
Tagged date : UTC 2007-08-22 07:25:41
Writing library : Apple QuickTime

Video
ID : 4
Format : DV
Commercial name : DVCPRO HD
Codec ID : dvhp
Duration : 3 min 42 s
Bit rate mode : Constant
Bit rate : 46.0 Mb/s
Width : 1 280 pixels
Original width : 960 pixels
Clean aperture width : 936 pixels
Height : 720 pixels
Clean aperture height : 702 pixels
Display aspect ratio : 2.40:1
Original display aspect ratio : 16:9
Clean aperture display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 (23976/1000) FPS
Original frame rate : 59.940 (59940/1000) FPS
Standard : NTSC
Color space : YUV
Chroma subsampling : 4:2:2
Scan type : Progressive
Original scan type : Interlaced
Original scan order : Bottom Field First
Compression mode : Lossy
Bits/(Pixel*Frame) : 2.083
Time code of first frame : 00:00:00:00
Time code source : Subcode time code
Stream size : 1.19 GiB (97%)
Language : English
Encoded date : UTC 2007-08-22 07:25:41
Tagged date : UTC 2007-08-22 07:25:41
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709

SeeMoreDigital
4th April 2019, 15:58
I have a video file that MPC-BE can't play it unless I add LAV+Splitter Source as external filter :confused:

Playing DV (Digital Video) within an Apple container on a Windows computer can be a bit 'hit and miss' at the best of times. Have you tried re-muxing to the MKV container?

P.J
4th April 2019, 19:35
Playing DV (Digital Video) within an Apple container on a Windows computer can be a bit 'hit and miss' at the best of times. Have you tried re-muxing to the MKV container?

I have many DV videos with mov container that play fine except this one.
LAV+Splitter Source plays it fine too.

SeeMoreDigital
4th April 2019, 20:01
I have many DV videos with mov container that play fine except this one.
LAV+Splitter Source plays it fine too.It's not a regular DV file it's a DVCPRO HD file with 4:2:2 chroma sub-sampling. It's most likely 10-bit too...

Aleksoid1978
4th April 2019, 21:58
Upload some files.

P.J
5th April 2019, 07:19
Upload some files.

Here you are: https://drive.google.com/open?id=14YuBH6_eYf_tz27-T3_70G2pM6n-PDCn

SeeMoreDigital
5th April 2019, 09:44
Here you are: https://drive.google.com/open?id=14YuBH6_eYf_tz27-T3_70G2pM6n-PDCnIt appears that the DVPRO HD sample contains some damaged frames between 5017-5023...

Aleksoid1978
5th April 2019, 09:46
Here you are: https://drive.google.com/open?id=14YuBH6_eYf_tz27-T3_70G2pM6n-PDCn

Thanks - fixed.

P.J
7th April 2019, 06:09
Thanks - fixed.

:thanks:

tormento
7th April 2019, 14:50
Is it only me or the latest versions get lot of time when launching?

Klaus1189
7th April 2019, 14:54
Which latest versions? Latest stable or latest nightlies?

ryrynz
7th April 2019, 21:21
Is it only me or the latest versions get lot of time when launching?

I don't get why you just didn't download the stable 1.5.3 release and just test for yourself. Nobody has mentioned anything and most of us use SSDs so many apps are basically instant.

tormento
8th April 2019, 09:37
I don't get why you just didn't download the stable 1.5.3 release and just test for yourself. Nobody has mentioned anything and most of us use SSDs so many apps are basically instant.
Downloaded both stable and nightly. Same effect. Tried to delete every .ini and other setting and at first launch it's almost instant, from the second, when settings are saved, get slower. I have 2 Samsung 850 Pro here, so storage is not the bottleneck.

Aleksoid1978
8th April 2019, 10:14
Is it only me or the latest versions get lot of time when launching?

Only for you.

Qotscha
8th April 2019, 12:27
Is it only me or the latest versions get lot of time when launching?

Same thing for me too. Tested nightlies (x64) and 1.5.3.4373 (https://yadi.sk/d/hlf1lfC8mKU58/1.5.3.4373) seems to be the last build launching practically instantly. Builds starting from 1.5.3.4378 (https://yadi.sk/d/hlf1lfC8mKU58/1.5.3.4378) take several seconds.

tormento
8th April 2019, 12:32
Same thing for me too.
Thanks for the working version hint.

I confirm it is opening instantly for me too (x64 version).

lvqcl
8th April 2019, 16:58
1.5.4.4508: startup time < 1 second.

BetA13
8th April 2019, 22:43
hy all,

i have a little problem with Subtitles in h265 Files..
they allways display in White and default size, if try to change anything in the Standart style, lets say color to red, it doesnt change it, same with the Size.
Using the standart internal subtitle renderer in MPC BE..

With h264 Files it does work like it should..

is there a reason for that? maybe a limitation of some sort?

https://i.imgur.com/nH1yGXF.png

Use Standart style is enabled..


or should i use a different subtitle renderer? If yes, wich would be recommend?

Thanks..

ryrynz
8th April 2019, 22:45
1.5.4.4508: startup time < 1 second.But do you have the slow startup on the build stated (4378)?

Aleksoid1978
9th April 2019, 01:45
hy all,

i have a little problem with Subtitles in h265 Files..
they allways display in White and default size, if try to change anything in the Standart style, lets say color to red, it doesnt change it, same with the Size.
Using the standart internal subtitle renderer in MPC BE..

With h264 Files it does work like it should..

is there a reason for that? maybe a limitation of some sort?

https://i.imgur.com/nH1yGXF.png

Use Standart style is enabled..


or should i use a different subtitle renderer? If yes, wich would be recommend?

Thanks..

Subtitles style work only for text's subs. As i see on screen - it's PGS or VOBSUB subtitle. Show MediaInfo for this file.

BetA13
9th April 2019, 02:06
Media Info - Subtitles part:

Text
ID : 3
Format : PGS
Codec ID : S_HDMV/PGS
Codec ID/Info : Picture based subtitle format used on BDs/HD-DVDs
Duration : 3 min 37 s
Bit rate : 48.6 kb/s
Count of elements : 128
Stream size : 1.26 MiB (1%)
Title : Uncle.Buck.1989.x265
Language : English
Default : No
Forced : No


Looks like PGS..
So, with an seperate external subtitle this would work? like srt? etc...

And for vobsubs, would there be another way to modify the subs? as in using a different subtitle renderer?

sorry for the questions, but i never really used subtitles, wich i do now increasingly..

Thanks for the Help :)

Qotscha
9th April 2019, 04:48
But do you have the slow startup on the build stated (4378)?
Every build (or at least 1.5.3 stable, 1.5.4.4508, and a couple of others I tested) since 4378 seems to take significantly longer time to start compared to 4373 (~5 s vs ~0.5 s). So probably there is something in commits 4374 - 4378 which has an effect on startup times at least for me and tormento.

I looked at these commits and there seems to be quite a lot of code changes in 4374 (https://sourceforge.net/p/mpcbe/code/4374/) "Change: Transfer code from branches / playlist to the main branch." (Google translation). The other commits include changes to PlaylistNameDlg.cpp/.h introduced in 4374.