gMKVExtractGUI

[gpower2]

Thanks for the confirmation, I will release a new official patch version in the following minutes! :thanks:

[gpower2]

Hey guys, new patch version to address the issue reported from vertigo220 regarding Dark mode!

Download link:
https://sourceforge.net/projects/gmkvextractgui/files/v2.8.1/gMKVExtractGUI.v2.8.1.7z/download

Changelog

v2.8.1

fix(dark): Possible fix of a bug with ComboBox in dark mode (thanks vertigo220!)

[vertigo220]

Thanks for the dark mode and the quick fix. Definitely much easier on the eyes. Progress bars still being white looks a bit strange, not sure if they were left that way due to difficulty getting them a different color or intentionally, though not a big deal. The "Selected File Information" box is strange because it's dark until a job is running, then it turns white, then dark again once done. Still not as bright as when the whole window is light-colored, but would be better if it stayed dark. Figured I'd point it out in case you didn't know about it, maybe it's just doing it for me.

Unrelated, one other request is to make the taskbar progress reflect the overall progress instead of the individual file progress. If I'm extracting from multiple files, I can't really tell how far along it is with it in the background, because monitoring the taskbar button only tells me the progress of whichever file it's currently on, which isn't very useful.

[vertigo220]

I'm having an issue since updating to the latest version that right-clicking takes significantly longer to open the context menu for selecting/deselecting multiple tracks when dark mode is activated. It works like normal with the menu opening immediately in light mode, but as soon as I switch to dark mode it's very slow, and switching back makes it fast again.

[oniiz86]

I'm having an issue since updating to the latest version that right-clicking takes significantly longer to open the context menu for selecting/deselecting multiple tracks when dark mode is activated. It works like normal with the menu opening immediately in light mode, but as soon as I switch to dark mode it's very slow, and switching back makes it fast again.

@vertigo220 I've just tried the latest v2.8.1 & am not witnessing this slow behaviour with Dark Mode when Right-Clicking to bring up the Context Menu, it's reasonably fast & behaves the same way whether it's Light Mode or Dark Mode.

@gpower2 I was curious if you've witnessed the above behaviour with v2.8.1 that @vertigo220 is experiencing?

Also can any of this be addressed that @vertigo220 brought up last month?

Progress bars still being white looks a bit strange, not sure if they were left that way due to difficulty getting them a different color or intentionally, though not a big deal. The "Selected File Information" box is strange because it's dark until a job is running, then it turns white, then dark again once done. Still not as bright as when the whole window is light-colored, but would be better if it stayed dark. Figured I'd point it out in case you didn't know about it, maybe it's just doing it for me.

Unrelated, one other request is to make the taskbar progress reflect the overall progress instead of the individual file progress. If I'm extracting from multiple files, I can't really tell how far along it is with it in the background, because monitoring the taskbar button only tells me the progress of whichever file it's currently on, which isn't very useful.

[gpower2]

Thanks for the dark mode and the quick fix. Definitely much easier on the eyes.

Thank you for the feedback, it's nice to hear that this change was helpful. :D

Progress bars still being white looks a bit strange, not sure if they were left that way due to difficulty getting them a different color or intentionally, though not a big deal. The "Selected File Information" box is strange because it's dark until a job is running, then it turns white, then dark again once done. Still not as bright as when the whole window is light-colored, but would be better if it stayed dark. Figured I'd point it out in case you didn't know about it, maybe it's just doing it for me.

These are both known, unfortunately to tackle them, it would require to customly render the whole controls, which is something that I am not willing to do...
I will revisit at some point to see if there is a different way to achieve the same behavior, but unfortunately my first tries were a total failure 🥲

Unrelated, one other request is to make the taskbar progress reflect the overall progress instead of the individual file progress. If I'm extracting from multiple files, I can't really tell how far along it is with it in the background, because monitoring the taskbar button only tells me the progress of whichever file it's currently on, which isn't very useful.

I thought of this myself at some point, this will probably be included in the next version, thanks!

I'm having an issue since updating to the latest version that right-clicking takes significantly longer to open the context menu for selecting/deselecting multiple tracks when dark mode is activated. It works like normal with the menu opening immediately in light mode, but as soon as I switch to dark mode it's very slow, and switching back makes it fast again.

Hmm, I guess you have a low end CPU, since I can understand why this takes longer, since in order to make all the menus in the context menu render in dark mode, I had to manually redraw every one of them...
In my case, I have a high end CPU and there was no difference, I'll see if I can find a more performant way to achieve the same behavior, thanks for the feedback!

@vertigo220 I've just tried the latest v2.8.1 & am not witnessing this slow behaviour with Dark Mode when Right-Clicking to bring up the Context Menu, it's reasonably fast & behaves the same way whether it's Light Mode or Dark Mode.

@gpower2 I was curious if you've witnessed the above behaviour with v2.8.1 that @vertigo220 is experiencing?

Also can any of this be addressed that @vertigo220 brought up last month?

I will try to find some time to work on the above requests, are you also interested in them?

[oniiz86]

I will try to find some time to work on the above requests, are you also interested in them?

@gpower2 Yes as noted by @vertigo220 above, the feature requests would be greatly appreciated, thanks for being so receptive to feedback & always improving this invaluable tool. :)

[THGhost]

Hmm, I guess you have a low end CPU, since I can understand why this takes longer, since in order to make all the menus in the context menu render in dark mode, I had to manually redraw every one of them...
In my case, I have a high end CPU and there was no difference, I'll see if I can find a more performant way to achieve the same behavior, thanks for the feedback!

Registered to say that it's definitely not a low end CPU issue. I have a high end CPU and the right-click context menu still takes a while to load when the dark mode is activated. Roughly 10 seconds. Just thought you should know. Hopefully this can be fixed :thanks:

[gpower2]

@gpower2 Yes as noted by @vertigo220 above, the feature requests would be greatly appreciated, thanks for being so receptive to feedback & always improving this invaluable tool. :)

Thanks for your kind words, always happy to offer back to this amazing community! 🤗

Registered to say that it's definitely not a low end CPU issue. I have a high end CPU and the right-click context menu still takes a while to load when the dark mode is activated. Roughly 10 seconds. Just thought you should know. Hopefully this can be fixed :thanks:

Wow, 10 secs, really? Can you share the number of tracks that you have in order to try and reproduce this locally?

[THGhost]

Thanks for your kind words, always happy to offer back to this amazing community! 🤗



Wow, 10 secs, really? Can you share the number of tracks that you have in order to try and reproduce this locally?

Well, I did say "roughly" :P Literally any file with any number of tracks.

[Hellboy.]

I have a AMD Ryzen 5 5600X 6-Core Processor and i don't see any difference between dark mode and light mode.

[THGhost]

I have a AMD Ryzen 5 5600X 6-Core Processor and i don't see any difference between dark mode and light mode.

Well I have an AMD Ryzen 9 7950X3D and I definitely do. So something is clearly wrong xD

[tormento]

It's a long time that I don't connect to my computer by RDP but, since it happened recently, I have a strange issue to report.

When connecting from a lower resolution monitor, the majority of other programs move themselves in the visible area of the screen.

gMKVExtractGUI doesn't and I had to move it manually from the status bar thru cursor keys to make it visible.

Do you think that it's a fixable bug?

[vertigo220]

These are both known, unfortunately to tackle them, it would require to customly render the whole controls, which is something that I am not willing to do...
I will revisit at some point to see if there is a different way to achieve the same behavior, but unfortunately my first tries were a total failure 🥲

No worries. Still far better, and if it's a major effort to fix these last bits it may not be worth it.

Hmm, I guess you have a low end CPU

Certainly an older CPU, but far from low-end (i7-7820X). Despite its age, I wouldn't expect something like this to be very demanding of it. Could be wrong, though, but based on other responses it seems it's something else. It's bad enough that I've given up on dark mode for now as it's just far too slow to really be usable. As with THGhost, it's at least several seconds every time. Though I just switched back to dark mode to test with different numbers and sizes of files and tracks and it seems faster, only taking between 1-2 seconds for one or two small files with few tracks to 3-4 seconds for more/larger files and more tracks. Still far slower than light mode, which is instant even with several large files with multiple tracks each, but not unbearably slow as it's consistently been up until now. Not sure what the difference is, or if it will stay like this or revert back to being slow. I'm also seeing little to no change in CPU usage when right-clicking multiple times, which further confirms that it's unlikely a CPU issue. And just going back and trying a couple more times, it took a few more seconds (closer to 7 each time), and both times the program went unresponsive for about half a second at around 5-6 seconds. Let me know if I can do anything to help test/troubleshoot.

[THGhost]

Certainly an older CPU, but far from low-end (i7-7820X). Despite its age, I wouldn't expect something like this to be very demanding of it. Could be wrong, though, but based on other responses it seems it's something else. It's bad enough that I've given up on dark mode for now as it's just far too slow to really be usable. As with THGhost, it's at least several seconds every time. Though I just switched back to dark mode to test with different numbers and sizes of files and tracks and it seems faster, only taking between 1-2 seconds for one or two small files with few tracks to 3-4 seconds for more/larger files and more tracks. Still far slower than light mode, which is instant even with several large files with multiple tracks each, but not unbearably slow as it's consistently been up until now. Not sure what the difference is, or if it will stay like this or revert back to being slow. I'm also seeing little to no change in CPU usage when right-clicking multiple times, which further confirms that it's unlikely a CPU issue. And just going back and trying a couple more times, it took a few more seconds (closer to 7 each time), and both times the program went unresponsive for about half a second at around 5-6 seconds. Let me know if I can do anything to help test/troubleshoot.

I concur with these findings. It would appear I've been working with a lot of files with lots of subtitles tracks recently; hence the 10 seconds. But using files with fewer tracks does result in faster times, but still much slower than it is without the dark mode enabled. Very odd indeed.

[gpower2]

Hello guys!

I finally found some time around to finally fix the dark mode issues.
And this time around, I had some help!
I gave Jules from Google a spin, and with its help, I managed to re-implement Dark mode from scratch!
It now supports dynamic theming (bye-bye restarts), fixes some visual issues from the previous implementation,
but most importantly, it fixes the performance issues from the Context menu!

Also, I changed the TaskBar's progress bar to reflect the total progress, instead of each individual job's.

Finally, one big change is that I moved from SourceForge to Github, something I've been meaning to do for some time,
so all new releases will be added in Github from here on out!

I will also update the inital post of the thread to avoid any issues.

Download link:
https://github.com/Gpower2/gMKVExtractGUI/releases/download/v2.9.0/gMKVExtractGUI.v2.9.0.7z

Changelog

v2.9.0

fix(progress): Update the task bar progress bar value based on the total progress and not on the individual job progress
fix(code): Switch to unboxed types and minor optimizations.
fix(gForm): Add the form handle in the remaining message boxes in gForm
feat(dark): Implement Dark Mode in a new way with a bit of help from AI (thanks Jules!)
fix(files): Fix file structure
Create README.md


I hope you enjoy this release as much as I did! Thanks for your valuable feedback! :D

[tormento]

Also, I changed the TaskBar's progress bar to reflect the total progress, instead of each individual job's.
Finally on GitHub ;)

Could you implement a double progress bar, such as MakeMKV does, with file progress AND total progress?

Thank you!

[gpower2]

Finally on GitHub ;)

Could you implement a double progress bar, such as MakeMKV does, with file progress AND total progress?

Thank you!

In the main form, this is already implemented, I am not sure that such a feature exists for the Windows TaskBar progress bar...

[vertigo220]

Very nice. All welcome changes, and especially nice to see the move away from SourceForge. A brief test had the context menu opening immediately in dark mode with a bunch of files. I'll do more extensive testing in time, but definitely looks good. I'm curious, as I hadn't heard of Jules before and can see it's very new, and I'm always interested in this kind of thing: how was it? Do you see it, and other similar projects, making it significantly faster and easier to create and improve apps?

[gpower2]

Very nice. All welcome changes, and especially nice to see the move away from SourceForge.

Yeah, it was something I wanted to do for years, just didn't have the courage to perform the migration from SVN to Git in order to keep all the commits intact.
Again, the progress of the AI tools helped a lot ironing out various issues (the official guide from Github is missing some info for edge cases) and managed to do it.

A brief test had the context menu opening immediately in dark mode with a bunch of files. I'll do more extensive testing in time, but definitely looks good.

I've also tested it with a sample of 16k tracks, and it performed exactly the same with the light theme mode, so I am quite confident in this, it's nice to hear that it works for you as well!

I'm curious, as I hadn't heard of Jules before and can see it's very new, and I'm always interested in this kind of thing: how was it? Do you see it, and other similar projects, making it significantly faster and easier to create and improve apps?

This is a very big discussion :D

Jules is one of the many AI agents that appeared lately, it has the advantage of running the tasks in a cloud VM, so it doesn't use your local resources at all.
Regarding the general use of AI and the tools, IMHO, they are great for prototyping, so you can have a working prototype from an idea extremely fast and see if it works or not, and also for tedious tasks, like writing tests, or refactoring parts of the codebase, however, they still require to be reviewed and guided by senior engineers. I am afraid of the effect that these tools will have with junior engineers and also how much of their generated code will end up in production without being actually reviewed and tested...

To summarize, they are definitely a great tool, that can offer amazing results, but only if you know what you're actually doing...

[gpower2]

Hello guys!

It seems the "Github effect" worked and got the first valid issue, which is related to the very old code of the app init and the autodetection of the MKVToolnix path.

So a new release was published, v2.9.1

Download link:
https://github.com/Gpower2/gMKVExtractGUI/releases/download/v2.9.1/gMKVExtractGUI.v2.9.1.7z

Changelog

v2.9.1


fix(init): Revamped the init sequence for detecting the MKVToolnix path and added a new button to manually trigger the auto detect sequence.
fix(logs): Fix various logs in FrmMain2 and gMKVHelper.


Notes:

The priority for setting the MKVToolnix path during the app init is now the following:


Check for manual path set via cli arguments
Search in the .ini file for the MKVToolnix path
Search the current directory
For Windows: search the registry for an MKVToolnix installation
For Linux: seatch the usr/bin folder for MKVToolnix


Also, an "Auto Detect" button was detected, in order to easily reset the directory in case a manual override was added via the form.

As always, enjoy! :D

[JohnTHaller]

Hi all! Thought you'd like to know that I created a gMKVExtractGUI Portable (https://portableapps.com/apps/music_videos/gmkvextractgui-portable) package over at PortableApps.com after one of our users requested it. It's designed to be installed alongside MKVToolNix Portable (https://portableapps.com/apps/music_video/mkvtoolnix-portable) and will automatically configure itself to use it. Links back here for the homepage and to the Buy Me a Beer (https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YZZQZYL2Y6UNG) link for donations.

[gpower2]

Hello guys!

A new version is out, v2.10.0

The most notable change, is the bundling of the latest Newtonsoft.Json assembly, which increased the total size a bit.
Other than that, one small fix and one minor feature were added.

Also, there was some preparation work, for an overall refactoring I am planning, in order to bring the codebase to latest standards, since its age is showing...

Download link:
https://github.com/Gpower2/gMKVExtractGUI/releases/download/v2.10.0/gMKVExtractGUI.v2.10.0.7z

Changelog

v2.10.0


fix(ui): Show "Extraction completed!" message in the segment info text box instead of the label status, to avoid visual clatter (thanks @dclxvplusone)
feat(chapters): Add new PBF chapter type. It automatically transforms the default XML chapter type to the PBF chapter type. Comes with no guarantees, since documentation is basically non-existent
Reorganize and refactor various parts of the code. Switch to using Newtonsoft.Json via Nuget and update to latest version


As always, enjoy! :D

[oniiz86]

@gpower2 :thanks: so much for the recent updates to your wonderful software utility, is that a typo error in the latest v2.10.0 release, Show "Exctraction completed!" message, does it actually have the correct spelling of Extraction? :D

[gpower2]

Ah that's just the commit message 😁

In the app it remains correct 😉

https://github.com/Gpower2/gMKVExtractGUI/commit/10a845d0ee7d88014d3b15cae6bfd8d97a197f62

[Lathe]

Hello guys!

A new version is out, v2.10.0

The most notable change, is the bundling of the latest Newtonsoft.Json assembly, which increased the total size a bit.
Other than that, one small fix and one minor feature were added.

Also, there was some preparation work, for an overall refactoring I am planning, in order to bring the codebase to latest standards, since its age is showing...

Download link:
https://github.com/Gpower2/gMKVExtractGUI/releases/download/v2.10.0/gMKVExtractGUI.v2.10.0.7z

Changelog

v2.10.0


fix(ui): Show "Extraction completed!" message in the segment info text box instead of the label status, to avoid visual clatter (thanks @dclxvplusone)
feat(chapters): Add new PBF chapter type. It automatically transforms the default XML chapter type to the PBF chapter type. Comes with no guarantees, since documentation is basically non-existent
Reorganize and refactor various parts of the code. Switch to using Newtonsoft.Json via Nuget and update to latest version


As always, enjoy! :D

:thanks:

[sbrblz]

Hello, I have a question about tags. Is there a reason why they are not in the listing of things to extract such as the chapters file? I notice you have to change what to extract from tracks to tags, however there does not seem to be any way to customize the output file name like the other attachments. For batch extraction I have everything extract into a separate folder for each file with customized names, but the tags.xml file just keeps the default extracted name outside of the folders.

[gpower2]

Hello, I have a question about tags. Is there a reason why they are not in the listing of things to extract such as the chapters file? I notice you have to change what to extract from tracks to tags, however there does not seem to be any way to customize the output file name like the other attachments. For batch extraction I have everything extract into a separate folder for each file with customized names, but the tags.xml file just keeps the default extracted name outside of the folders.

Basically noone ever cared enough for tags in order to check them further.

Also, tags are not like chapters, they are not tracks of the matroska file, that's why they have different handling.

Indeed, I could add Options for the tags name, in order not to have them hardcoded and in order to be able to take advantage of the directory separator, would that be OK for you?

[sbrblz]

That would be great, that way I can keep all extracted files in their separate folders when doing batch extraction.

[gpower2]

OK, this was an easy implementation, so I added it https://github.com/Gpower2/gMKVExtractGUI/commit/279ced5ecb48ce5f3cc8250cab9c80f48c1fbad4

It will be included in the next release version. Thanks for the feedback! 🤗

[sbrblz]

Thank you! :)

[gpower2]

Hello everyone! :D

Happy August, with a happy new release! :D

This is a quite big release, since I refactored a lot of the core logic, preparing for the upgrade to a newer .NET Framework version, 4.7, which will also bring the end of support for Windows XP.
I know that some folks will not be happy about that, so I tried to tackle any remaining issues and feature requests in this version, so that Win XP users will have all the goodies and not feel left out.

Changelog is one of the biggest since the first release, containing new features, fixes and the huge refactoring of the core.
That means, that I may have introduced a regression bug, so if you notice anything out of place, please mention it here, or in Github, in order for me to tackle it ASAP.

Note: You can also create issues in the Github repo, in order to have better tracking and visibility. ;)

Download link:
https://github.com/Gpower2/gMKVExtractGUI/releases/download/v2.11.0/gMKVExtractGUI.v2.11.0.7z

Changelog

v2.11.0

feat: Add tooltips and an option to disable/enable them. Closes #21 (#24)
feat: Support checking/unchecking all Forced tracks per track type.
feat: Add support for the Forced track property. Closes #20
feat: Add option for overwriting existing files when extracting. This closes #18 (#19)
feat(tags): Add output filename options for tags. Closes #12
feat: Changed the output file extension for the OGM chapter type from "ogm.txt" to "txt" in the `gMKVToolNix.MkvExtract` namespace. Closes #4

fix(linux): Fix some more possible Linux issues with P/Invoke
fix(linux): correctly fix gRichTextBox issue in Linux
fix(linux): Fix some issues in Linux by excluding paths with P/Invoke.

docs: Enhance README and add docs folder with a basic User Manual

tests: Introduce Unit Tests and refactor part of the code for testability and performance (#11)

perf: Improve context menu creation
perf: Core refactor
Huge refactor of parsing state, practically making parsing stateless
Refactored the process output handling, by using List instead of StringBuilder to avoid splitting into individual line strings afterwards
Removed file existence checks for batch requests to minimize the IO operations
Various code optimizations in string operations
Various code formatting improvements
Refactor gMKVMerge, option handling and codec private data logic (#15)
Refactor gMKVInfo, fix typos and improve parsing (#14)
Refactor gMKVExtract and related components (#13)


As always, I hope you enjoy this release as much as I did! Thank you all for your valuable feedback! :D

[THGhost]

Having completely forgotten about the slow dark mode context menu issue, I came back here and to my delight it has now been fixed :D Thanks very much :thanks:

[gpower2]

Hello everyone! :D

A new bugfix version is out, thanks to @arestarh report!

Download link:
https://github.com/Gpower2/gMKVExtractGUI/releases/download/v2.11.1/gMKVExtractGUI.v2.11.1.7z

Changelog

v2.11.1


fix: Fix issue with Job manager when adding tracks that don't have CodecPrivate data, like PGS subs. thanks arestarh

[oniiz86]

@gpower2 :thanks: so much for the recent updates, I believe it should read v2.11.1 above as well as the home page, the changelog does not mention v2.11.1 for this small revision update. ;)

[gpower2]

@gpower2 :thanks: so much for the recent updates, I believe it should read v2.11.1 above as well as the home page, the changelog does not mention v2.11.1 for this small revision update. ;)

Thanks for the support and feedback! The typos were fixed! :D

[gpower2]

Hello everyone! :D

Happy new year, with a happy new release! :D

Some nice new functionalities were added, hopefully these will help some people who want more advanced options.

Note: You can also create issues in the Github repo, in order to have better tracking and visibility. ;)

Download link:
https://github.com/Gpower2/gMKVExtractGUI/releases/download/v2.12.0/gMKVExtractGUI.v2.12.0.7z

Changelog

v2.12.0

doc: Update the user manual with the new Advanced Options.
fix: The Defaults button in Options form now resets the new Advanced Options too.
feat: Add support for raw and fullraw track extraction modes. This closes #22 (#33)
feat: Add option to disable BOM for text files (v96.0+) #31 (#32)
fix: Fix key overrides of custom TextBox controls for Ctrl+A and Ctrl+C
fix: Changed txtLog to gRichTextBox and removed unused code
feat: Add a Select button that displays the Context Menu as another entry point for it. #27 (#30)
fix: fix MkvToolnixPath detection when Settings path is empty (#29) Thanks @lapluis


As always, I hope you enjoy this release as much as I did! Thank you all for your valuable feedback! :D

[Lathe]

Hello everyone! :D

Happy new year, with a happy new release! :D

Some nice new functionalities were added, hopefully these will help some people who want more advanced options.

Note: You can also create issues in the Github repo, in order to have better tracking and visibility. ;)

Download link:
https://github.com/Gpower2/gMKVExtractGUI/releases/download/v2.12.0/gMKVExtractGUI.v2.12.0.7z

Changelog

v2.12.0

doc: Update the user manual with the new Advanced Options.
fix: The Defaults button in Options form now resets the new Advanced Options too.
feat: Add support for raw and fullraw track extraction modes. This closes #22 (#33)
feat: Add option to disable BOM for text files (v96.0+) #31 (#32)
fix: Fix key overrides of custom TextBox controls for Ctrl+A and Ctrl+C
fix: Changed txtLog to gRichTextBox and removed unused code
feat: Add a Select button that displays the Context Menu as another entry point for it. #27 (#30)
fix: fix MkvToolnixPath detection when Settings path is empty (#29) Thanks @lapluis


As always, I hope you enjoy this release as much as I did! Thank you all for your valuable feedback! :D

Thanks for all your hard work Bro! :thanks:

[oniiz86]

@gpower2 Happy New Year & thanks so very much for the new update, it's a very welcome update indeed, one small thing the current version on the home page should read v2.12.0 :thanks:

[gpower2]

@gpower2 Happy New Year & thanks so very much for the new update, it's a very welcome update indeed, one small thing the current version on the home page should read v2.12.0 :thanks:

Damn, I totally forgot about that! 😅

Fixed now, thank you so much! 🤗

[shae]

What version (range) of mkvtoolnix is required?

Thanks for the tool!

[gpower2]

What version (range) of mkvtoolnix is required?

Thanks for the tool!

Hi Shae, gMKVToolix should work with any MKVoolnix version, even ancient ones like 4.0.0

If you find any issue with any version, please report it here or in Github and I'll check it

[gpower2]

Hello everyone! :D

I am happy to announce a new release! This is a quite big once, since it introduces a long requested feature: Localization.
gMKVExtractGUI finally supports multiple languages for the UI!
The translations are in separate json files, that are read in runtime, so I split them in a separate archive, in order to avoid adding more files for people who won't want them.
The current languages supported are en, es, de, pt, pt-br, fr, el, zh-cn, zh-tw, ja, ru, it, nl, pl, tr, ro, hi, and ko.

Disclaimer: the translations were made with the use of AI, so if something feels weird in your translation, please reach out to me in Github in order to fix it!

A new Translations form was also added and can be accessed via the Options form. That way, anyone can edit the translation files, or create their own!

Apart from the new localization feature, there were several performance improvements, mainly related to the asynchronous flows,
which should bring some noticeable performance gains in long running operations.


Note: You can also create issues in the Github repo, in order to have better tracking and visibility. ;)

Download link:
https://github.com/Gpower2/gMKVExtractGUI/releases/download/v2.13.0/gMKVExtractGUI.v2.13.0.7z
https://github.com/Gpower2/gMKVExtractGUI/releases/download/v2.13.0/gMKVExtractGUI.locales.v2.13.0.7z

Changelog

v2.13.0


feat: Add localization feature (#39)

perf: Use typed synchronous extraction delegates in gMKVJob and gMKVExtract
perf: Remove DoEvents from SetTableLayoutMainStatus methods in main Form
perf: Replace task polling with continuation-based TPL in main Form.
perf: Replace thread polling with event-driven extraction completion
perf: Send async events for updating the progress and status fields in the forms.

fix(dark): Fix scrollbars in dark mode for RichTextBox.
fix(dark): Fix buttons light mode theming when switching from dark to light mode during runtime.
fix(dark): Fix status strip in dark mode for Mono runtime

fix: Fix gform DPI autoscaling and force initial DPI scaling on Mono in gForm.InitDPI. References issues #36 #41 (#42)

chore: Sanitize all files with the same line endings (CRLF) and encoding (UTF-8 without BOM) for consistency
chore: Fix public API of gMKVToolnix sevices


As always, I hope you enjoy this release as much as I did! Thank you all for your valuable feedback! :D

[Lathe]

Hello everyone! :D

I am happy to announce a new release! This is a quite big once, since it introduces a long requested feature: Localization.
gMKVExtractGUI finally supports multiple languages for the UI!
The translations are in separate json files, that are read in runtime, so I split them in a separate archive, in order to avoid adding more files for people who won't want them.
The current languages supported are en, es, de, pt, pt-br, fr, el, zh-cn, zh-tw, ja, ru, it, nl, pl, tr, ro, hi, and ko.

Disclaimer: the translations were made with the use of AI, so if something feels weird in your translation, please reach out to me in Github in order to fix it!

A new Translations form was also added and can be accessed via the Options form. That way, anyone can edit the translation files, or create their own!

Apart from the new localization feature, there were several performance improvements, mainly related to the asynchronous flows,
which should bring some noticeable performance gains in long running operations.


Note: You can also create issues in the Github repo, in order to have better tracking and visibility. ;)

Download link:
https://github.com/Gpower2/gMKVExtractGUI/releases/download/v2.13.0/gMKVExtractGUI.v2.13.0.7z
https://github.com/Gpower2/gMKVExtractGUI/releases/download/v2.13.0/gMKVExtractGUI.locales.v2.13.0.7z

Changelog

v2.13.0


feat: Add localization feature (#39)

perf: Use typed synchronous extraction delegates in gMKVJob and gMKVExtract
perf: Remove DoEvents from SetTableLayoutMainStatus methods in main Form
perf: Replace task polling with continuation-based TPL in main Form.
perf: Replace thread polling with event-driven extraction completion
perf: Send async events for updating the progress and status fields in the forms.

fix(dark): Fix scrollbars in dark mode for RichTextBox.
fix(dark): Fix buttons light mode theming when switching from dark to light mode during runtime.
fix(dark): Fix status strip in dark mode for Mono runtime

fix: Fix gform DPI autoscaling and force initial DPI scaling on Mono in gForm.InitDPI. References issues #36 #41 (#42)

chore: Sanitize all files with the same line endings (CRLF) and encoding (UTF-8 without BOM) for consistency
chore: Fix public API of gMKVToolnix sevices


As always, I hope you enjoy this release as much as I did! Thank you all for your valuable feedback! :D

Thanks for all the hard work Bro! :thanks:

[manolito]

Thanks so much gpower2, this update is amazing ... :thanks:

Made a couple of short tests, everything seems to work just fine. I also used the German translation, it is just amazing (sometimes frightening) what KI can do these days. Very impressive.

I only found a minor glitch with the translation of "drag and drop" to "Drag & Drop". The "&" character is just omitted in the translation. (Win7 64bit, the standard Unicode character set). I was unable to fix it directly, so I just replaced it with "Drag and Drop" which works fine. I am not really experienced with Unicode, so it may all be my fault...

Whatever, thanks again, I really appreciate your work.


Cheers
manolito

[Lathe]

Thanks so much gpower2, this update is amazing ... :thanks:

Made a couple of short tests, everything seems to work just fine. I also used the German translation, it is just amazing (sometimes frightening) what KI can do these days. Very impressive.

I only found a minor glitch with the translation of "drag and drop" to "Drag & Drop". The "&" character is just omitted in the translation. (Win7 64bit, the standard Unicode character set). I was unable to fix it directly, so I just replaced it with "Drag and Drop" which works fine. I am not really experienced with Unicode, so it may all be my fault...

Whatever, thanks again, I really appreciate your work.


Cheers
manolito

I'm sorry, but I'm not fully clear on what the 'Translation' thing does...? Does it translate subtitles into another language or what?

Thanks!

[manolito]

It translates the User Interface...

I am happy to announce a new release! This is a quite big once, since it introduces a long requested feature: Localization.
gMKVExtractGUI finally supports multiple languages for the UI!
The translations are in separate json files, that are read in runtime, so I split them in a separate archive, in order to avoid adding more files for people who won't want them.
The current languages supported are en, es, de, pt, pt-br, fr, el, zh-cn, zh-tw, ja, ru, it, nl, pl, tr, ro, hi, and ko.

[Lathe]

It translates the User Interface...

Oh, of course, thanks mate!

[magic144]

when i click the Translations... button, i just get the popup error (see attached image - "An error has occurred! Object reference not set to an instance of an object.") - with or without the json files present

what is going wrong?

FYI i have MKVToolNix GUI v98.0 installed

DotNetVersions reports this info for my W11 Home (25H2 Build 26200.8457) x64 system:

C:\Users\User\Desktop\DotNetVersions>DotNetVersions.exe
Currently installed "classic" .NET Versions in the system:
2.0.50727.4927 Service Pack 2
3.0.30729.4926 Service Pack 2
3.5.30729.4926 Service Pack 1
4.0.0.0
4.8.09221

[gpower2]

when i click the Translations... button, i just get the popup error (see attached image - "An error has occurred! Object reference not set to an instance of an object.") - with or without the json files present

Hello!

Can you please paste the logs from the Logs form here? Unfortunately this error is too generic to pinpoint its cause since I can not reproduce it locally...