Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
27th April 2015, 10:49 | #3201 | Link |
MKVToolNix author
Join Date: Sep 2002
Location: Braunschweig, Germany
Posts: 4,278
|
And the inputs for tag/chapter/timecode/segmentinfo files. Etc. Basically everywhere which is not a file dialog.
__________________
Latest MKVToolNix is v83.0 If I ever ask you to upload something, please use my file server. |
6th May 2015, 01:13 | #3202 | Link |
Registered User
Join Date: Mar 2011
Posts: 131
|
Where is the option to ignore the AC3 core track from being included from a TrueHD track?
EDIT: Nevermind, I'm an idiot. Obviously you can just uncheck the AC3 stream in the Input options... Last edited by Megalith; 6th May 2015 at 03:47. |
6th May 2015, 01:55 | #3203 | Link |
Registered User
Join Date: Sep 2012
Posts: 366
|
MakeMKV is complaining bitterly about any VC-1 track that has been remux using MKVMerge, so far the only difference I can see using MKVInfo is that the first frame in the MKVMerge file is 33 bytes longer for some reason. The file was originally created by MakeMKV then remuxed by MKVMerge, so is this added 33 bytes expected?
http://www.makemkv.com/forum2/viewtopic.php?f=8&t=9039 |
10th May 2015, 15:12 | #3204 | Link | |
MKVToolNix author
Join Date: Sep 2002
Location: Braunschweig, Germany
Posts: 4,278
|
MKVToolNix v7.9.0 released
Hey,
I've released MKVToolNix v7.9.0. First of all a note to all Windows users: I've renamed the downloads slightly. They're now named e.g. mkvtoolnix-32bit-7.9.0-setup.exe etc. The difference is that 64bit builds use …-64bit-… instead of …-amd64-… and that the 32bit builds include their architecture (-32bit-) in their name for the first time. This was done in order to reduce the confusion sown by the term »amd64« which denotes the processor architecture but not the manufacturer. Many people weren't aware of that differentiation. As for the changes in this release: A couple of important bugs have been fixed, e.g. a very old bug in handling MPEG-1/2 video preventing the detection of such tracks; if --sync was used at the same time as --default-duration then --sync was ignored; mkvinfo's exit codes were wrong (this may trip up frontends using mkvinfo!); handling of E-AC3 in MPEG transport stream in certain situations etc. See below for all the details. Since the previous release a serious amount of work has gone into the new GUI, MKVToolNix GUI. It has reached a state in which I consider it fit for wider use. I've therefore removed the preview warning and included it in all the packages that I provide (both Windows and Linux). If everything goes according to plan then the next release, 8.0.0, will see the old GUI (mmg, mkvmerge GUI) be marked as being deprecated – meaning there will be a popup message warning you about this fact when you start mmg. Two releases later, with 8.2.0, the old GUI will finally be removed among with all support for the wxWidgets toolkit. Of course all of this depends on the number and seriousness of bugs found in the new GUI Therefore these plans are not set in stone. Changes for package maintainers: configure will now detect the presence of the Qt libraries version 5.2.0 or later by default and use them if they're found. This means that at the moment both GUIs (mmg and MKVToolNix GUI) will be built unless you tell configure otherwise. There are several switches that deal with the various toolkits:
The two different frontends for mkvinfo are mutually exclusive with the Qt-based version taking precedence over the wxWidgets-based version. Here are the usual links: the MKVToolNix home page, the Windows installer and portable version and the source code. All binaries that I provide have been uploaded already. Here's the full ChangeLog since the previous release: Quote:
__________________
Latest MKVToolNix is v83.0 If I ever ask you to upload something, please use my file server. |
|
10th May 2015, 16:22 | #3205 | Link |
契約者
Join Date: Jun 2008
Posts: 1,576
|
Hey guys. I just tried new MMG GUI and have a few questions. All of these might not be implemented yet, I'm totally fine with that, but I'm still curious.
1) In "Tracks, chapters, tags and attachments" form, how do I re-arrange stream positions? 2) How do I terminate muxing mid-way? 3) How do I disable statistics? (Such as NUMBER_OF_FRAMES, NUMBER_OF_BYTES, _STATISTICS_WRITING_APP etc.) |
10th May 2015, 16:26 | #3206 | Link |
Anime addict
Join Date: Feb 2009
Location: Spain
Posts: 673
|
Any tool for converting mmg option file to new version (mtxcfg)??
__________________
Intel i7-6700K + Noctua NH-D15 + Z170A XPower G. Titanium + Kingston HyperX Savage DDR4 2x8GB + Radeon RX580 8GB DDR5 + ADATA SX8200 Pro 1 TB + Antec EDG750 80 Plus Gold Mod + Corsair 780T Graphite |
10th May 2015, 16:27 | #3207 | Link | |
Registered User
Join Date: Dec 2002
Posts: 5,565
|
Quote:
3. Output options, Additional options (bottom right corner), check --disable-track-statistics |
|
10th May 2015, 16:27 | #3208 | Link |
Registered User
Join Date: Aug 2002
Location: France, Paris
Posts: 672
|
Please don't, such statistics are useful for people who get your file (and they use so little place in the file).
__________________
Want to know all about your media files? http://mediaarea.net/MediaInfo |
10th May 2015, 16:37 | #3210 | Link | ||
契約者
Join Date: Jun 2008
Posts: 1,576
|
Ouch... should have tried this myself... >__<
Quote:
Quote:
Code:
Format : Matroska Format version : Version 4 / Version 2 File size : 221 MiB Duration : 8mn 47s Overall bit rate : 3 506 Kbps Encoded date : UTC 2015-05-10 15:20:02 Writing application : mkvmerge v7.9.0 ('Birds') 64bit Writing library : libebml v1.3.1 + libmatroska v1.4.2 DURATION : 00:08:47.744000000 NUMBER_OF_FRAMES : 24738 NUMBER_OF_BYTES : 6590628 _STATISTICS_WRITING_APP : mkvmerge v7.9.0 ('Birds') 64bit _STATISTICS_WRITING_DATE_UTC : 2015-05-10 15:20:02 _STATISTICS_TAGS : BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES |
||
10th May 2015, 16:41 | #3211 | Link | |
MKVToolNix author
Join Date: Sep 2002
Location: Braunschweig, Germany
Posts: 4,278
|
Quote:
__________________
Latest MKVToolNix is v83.0 If I ever ask you to upload something, please use my file server. |
|
10th May 2015, 16:42 | #3212 | Link |
MKVToolNix author
Join Date: Sep 2002
Location: Braunschweig, Germany
Posts: 4,278
|
No, and none will be coming. It's too much work, and I have a lot of things still left to implement that I consider of higher priority. Sorry.
__________________
Latest MKVToolNix is v83.0 If I ever ask you to upload something, please use my file server. |
10th May 2015, 16:48 | #3213 | Link | |
MKVToolNix author
Join Date: Sep 2002
Location: Braunschweig, Germany
Posts: 4,278
|
Quote:
Note further that the track's duration (»Duration«) is yet another of those pieces of information that won't be available if you disable the statistics. The track's duration is also different from the file's duration. I'm not trying to start a discussion about the (lack of) usefulness of those tags, but the facts are that without those tags there's no way to determine:
Before the tags were introduced MediaInfo used to guesstimate both a track's duration and its effective bit rate. That heuristic was often off and the source for much confusion.
__________________
Latest MKVToolNix is v83.0 If I ever ask you to upload something, please use my file server. |
|
10th May 2015, 16:54 | #3214 | Link |
Registered User
Join Date: Sep 2012
Posts: 366
|
You're not supposed to be able to see the Track Statistic tags, it's just MKVMerge/MMG/MediaInfo weren't designed to handle them properly and currently it's a mess. Duration and Number of Bytes are only already available if you either have only a single track in the file or (for Number of Bytes) have only a single Variable bitrate stream (even then if the duration of just one of the tracks is significantly less than the file duration all of MediaInfos current output is worthless).
There's also a BPS tag that you're not seeing because MediaInfo has been programed to hide it, which is what it should be doing to all of them but Zenitram hasn't gotten around to writing the necessary code yet. The Tag handling should have been fixed long ago, but no one has had the time thus far. Things will get better and your current files without the tags will become outdated. |
10th May 2015, 16:58 | #3215 | Link |
Registered User
Join Date: Aug 2002
Location: France, Paris
Posts: 672
|
And I apologize for that. It will be past soon.
__________________
Want to know all about your media files? http://mediaarea.net/MediaInfo |
10th May 2015, 17:11 | #3216 | Link | |
契約者
Join Date: Jun 2008
Posts: 1,576
|
Quote:
I think without statistics mediainfo is doing great job displaying all truly relevant information. Still, even knowing this, and the stuff that Mosu mentioned in the post above, I don't want this information to be present in my files. And if someone receives files from me, he is not supposed to do anything with them anyway (except playback of course) Last edited by Keiyakusha; 10th May 2015 at 17:14. |
|
10th May 2015, 17:23 | #3217 | Link |
Registered User
Join Date: Sep 2012
Posts: 366
|
FFMPEG needs to updated too, and MKVMerge. Be sure to remove everything in the _STATISTICS_TAGS tag and not just the individual tags for forward compatibility.
FFMPEG lists each tag twice, which is annoying and can only compound the general distaste for the tags. MKVMerge lists them twice as well, once in the "Track Info" and once in the "Track Tags" list. That should change. Actually, according to the specs "TargetTypeValue" (50/60/70) and TargetType (EPISODE/MOVIE) aren't mandatory and really shouldn't be used for the Statistic Tags. I don't know if it does already or not but MKVMerge should probably verify the tags before outputting them and ignore them if they don't pass, and NOT output the security tags (tags starting with "_"). The whole thing needs to be cleaned up before people should be expected to accept them. -edit- Oh, "TargetTypeValue" has a "default" of "50" (although looking at Tag "defaults" is dangerous business), but target type can be left out completely (and I do object to have MOVIE tags in my TV EPISODES.) Last edited by ndjamena; 10th May 2015 at 18:19. |
10th May 2015, 17:26 | #3218 | Link | |
Registered User
Join Date: Sep 2012
Posts: 366
|
Quote:
|
|
10th May 2015, 18:39 | #3219 | Link |
契約者
Join Date: Jun 2008
Posts: 1,576
|
I would care, assuming I did some research during which I figured out that they exist and what they are for. I think this is similar to x264's SEI information which some people prefer to remove (or use a modified build that doesn't creates it to begin with)
|
10th May 2015, 18:47 | #3220 | Link | |
Registered User
Join Date: Sep 2012
Posts: 366
|
Right, I figured out why I thought "TargetTypeValue" could be left out.
This is from a FFMPEG Track tag extracted using MKVExtract: Quote:
But unless I'm missing something in the specs "TargetType" should be able to be left out completely. Last edited by ndjamena; 10th May 2015 at 19:03. |
|
Thread Tools | Search this Thread |
Display Modes | |
|
|