gMKVExtractGUI

[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]

Originally Posted by Hellboy.

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]

Originally Posted by gpower2

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.

Originally Posted by gpower2

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]

Originally Posted by vertigo220

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/gMKVExtra...tGUI.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!

[tormento]

Originally Posted by gpower2

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]

Originally Posted by tormento

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]

Originally Posted by vertigo220

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.

Originally Posted by vertigo220

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!

Originally Posted by vertigo220

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

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/gMKVExtra...tGUI.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:

1. Check for manual path set via cli arguments
2. Search in the .ini file for the MKVToolnix path
3. Search the current directory
4. For Windows: search the registry for an MKVToolnix installation
5. 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!

[JohnTHaller]

Hi all! Thought you'd like to know that I created a gMKVExtractGUI Portable package over at PortableApps.com after one of our users requested it. It's designed to be installed alongside MKVToolNix Portable and will automatically configure itself to use it. Links back here for the homepage and to the Buy Me a Beer 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/gMKVExtra...GUI.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!

[oniiz86]

@gpower2 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?

[gpower2]

Ah that's just the commit message 😁

In the app it remains correct 😉

https://github.com/Gpower2/gMKVExtra...bfd8d97a197f62

[Lathe]

Originally Posted by 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/gMKVExtra...GUI.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!