Log in

View Full Version : Mkvextract GUI


Pages : 1 2 3 4 [5]

Selur
13th August 2016, 08:48
@Mosu: any news regarding the S_HDMV/TEXTST subtitles?

Mosu
13th August 2016, 09:08
Actually I've been working on that a bit on and off for the last couple of weeks. The code is pretty much complete, but I need to verify it still produces the same results MakeMKV produces. At the moment I'm actually trying to get my hands on a Blu-ray containing such subtitles, but that's rather difficult. I'm waiting for an order from Amazon USA at the moment ("Van Helsing") which supposedly contains some…

mbcd
15th August 2016, 06:52
Watch your Income-Folder, you got mail ;-)

tormento
17th January 2018, 11:03
MKVToolnix 20.0 broke the toy. Any way to fix it? Any new version?

My temporary fix is to have a dir with 19.x and another with 20.x

And, please, add an option to point to MKVToolnix dir instead of wanting to coexist in the same house.

manolito
17th January 2018, 12:34
I suppose you are talking about MKVExtractGUI-2, right?

In the latest version Mosu changed the output of mkvinfo, and it looks like MKVExtractGUI-2 v 2.3.0.0 cannot read this new output format any longer.

You can use gMKVExtractGUI instead (or MKVCleaver), or you can replace the latest mkvinfo.exe with the previous version.


Cheers
manolito

sneaker_ger
17th January 2018, 12:42
Not just mkvinfo.
Version 9.7.0 "Numbers" 2016-12-27


Important notes


Deprecation warning: Several options and features are now deprecated and will be
removed at the start of 2018. These are: - mkvmerge: the options
"--identify-verbose", "--identify-for-gui", "--identify-for-mmg" and
"--identification-format verbose". Please convert existing users of these
interfaces to use mkvmerge's JSON identification output which can be invoked with
"--identification-format json --identify …". - all command line tools: the old,
proprietary format used for option files. Please convert users of this interface to
the new JSON option file format introduced in this release. - all command line tools:
the option "--check-for-updates" (the GUI will keep its online check for updates,
though). There is and will be no equivalent interface in the tools themselves. Users
of this interface can switch to retrieving the information about available updates
directly from the MKVToolNix website. The information is available as JSON and XML
files at the following URLs:
https://mkvtoolnix.download/latest-release.json.gz
https://mkvtoolnix.download/latest-release.xml.gz
https://gitlab.com/mbunkus/mkvtoolnix/blob/master/NEWS.md#version-970-numbers-2016-12-27

manolito
17th January 2018, 15:21
Not just mkvinfo.

Yes of course, but I was only talking about MKVExtractGUI-2 v. 2.3.0.0...

And to be able to continue using this tool all you need to do is keeping mkvinfo.exe (maybe the mkvinfo GUI also) from the previous version 19.0.0.


Cheers
manolito

sneaker_ger
17th January 2018, 15:27
Ah, I didn't know. These kind of utilities are supposed to use mkvmerge for identification (which removed old identification format in 20.0.0). mkvinfo may be changed on a whim.

mkver
17th January 2018, 16:19
Not to mention that there are situations in which the relevant information regarding tracks is not at the beginning of the file (in front of the clusters), but at the end (and only referenced via a seekhead) so that parsing using mkvinfo would take a long time.

tormento
18th January 2018, 16:38
I suppose you are talking about MKVExtractGUI-2, right?
Correct.
In the latest version Mosu changed the output of mkvinfo, and it looks like MKVExtractGUI-2 v 2.3.0.0 cannot read this new output format any longer.
I read it.
You can use gMKVExtractGUI instead (or MKVCleaver), or you can replace the latest mkvinfo.exe with the previous version.
MKVExtractGUI-2 is way cleaner and easier... That's why I stuck with it since years.

P.S: Why we can't extract a track from MKVToolnix GUI is a mistery to me. Right click -> save as....

gpower2
19th January 2018, 07:58
MKVExtractGUI-2 is way cleaner and easier... That's why I stuck with it since years.

I also preferred the clean interface of MKVExtractGUI-2 and that's why I developed gMKVExtractGUI with a similar interface. Have you tried it?

mastrboy
19th January 2018, 21:18
I also preferred the clean interface of MKVExtractGUI-2 and that's why I developed gMKVExtractGUI with a similar interface. Have you tried it?

And thank you for that, gMKVExtractGUI is without a doubt my preferred GUI for batch demuxing with MKVToolnix :thanks:

tormento
20th January 2018, 14:52
I also preferred the clean interface of MKVExtractGUI-2 and that's why I developed gMKVExtractGUI with a similar interface. Have you tried it?
Using now! :thanks:

manolito
14th February 2018, 19:52
Just found the latest version 2.4.0.0 by Pashin at SourceForge...

Changelog:
2.4.0.0 mkvtoolnix 20 compatibility (no earlier versions!)


Cheers
manolito

manolito
25th February 2018, 11:52
Unfortunately the latest MKVToolNix Version 21.0.0 broke MKVExtractGUI-2 again... :angry:

Looks like Mosu will change MKVInfo.exe with every new version from now on. Too bad...


Cheers
manolito

Mosu
25th February 2018, 11:56
Well, mkvinfo hasn't changed formats intentionally in release 21, and there are no planned format changes in the near future. What's changed, is that the GUI portion's been removed. Though I don't know why that should affect MKVExtractGUI-2.

Mosu
25th February 2018, 12:11
Oh, what's changed is that line endings are now \r\n on Windows instead of \n — which is a bug fix. But if MKVExtract-GUI 2 stumbles across that, then I really don't have a lot of sympathy.

Again: don't try to parse mkvinfo's output. In fact, don't write your own parsers, period. Use a standard JSON parser and let that parse mkvmerge's identification output.