MeGUI: bug reports and feature requests

[tebasuna51]

...so I’ll stay with NicAudio for the remainder of this series of files.

I make the last's versions of NicAudio, thanks for apreciate it, but it is very limited for now, the same is make by LSMASH and plus do support for EAC3, AAC, DTS-HD, TrueHD, FLAC, OPUS ... we can't compare them.

[kedautinh12]

x265 3.5.0.57 mod by Patman
https://github.com/jpsdr/x265/releases

[kedautinh12]

dgdecnv_246
https://www.rationalqm.us/dgdecnv/binaries/

[Sharktooth]

Guess what? I'm back.

[VoodooFX]

Guess what? I'm back.

Does it mean more XviD matrices, or the pile of MeGUI's bugs fixed? :)

[Sharktooth]

Does it mean more XviD matices, or the pile of MeGUI's bugs fixed? :)
It means i've to catch up first

[LigH]

Guess what? I'm back.

I remember that name! :cool: Welcome back!

[Barough]

Guess what? I'm back.

Great to too see that your around again Sharktooth :)

[kedautinh12]

dgdecnv_246.zip 2022-11-11
https://www.rationalqm.us/dgdecnv/binaries/

[kedautinh12]

MKVToolNix v72.0.0
https://mkvtoolnix.download/windows/releases/72.0.0/
https://mkvtoolnix.download/doc/NEWS.md

[StainlessS]

DGDecNV 264 (2022-11-29)
No major problem but,
DGDecNV 246 (2022-11-29)

Thanks.

[Barough]

@StainlessS
As u said..... not a major problem, but it's been fixed now. Thnx for the heads up. :)

[kedautinh12]

x265 v3.5+71 Mod by Patman
https://github.com/jpsdr/x265/releases

[kedautinh12]

x265 v3.5+75 from Barough :D
https://www.mediafire.com/file/w8xufft0b475b1t

[kedautinh12]

x265 v3.5+75 Mod by Patman
https://github.com/jpsdr/x265/releases

[kedautinh12]

Mediainfo 22.12
x86: https://mediaarea.net/download/binary/libmediainfo0/22.12/MediaInfo_DLL_22.12_Windows_i386_WithoutInstaller.7z
x64: https://mediaarea.net/download/binary/libmediainfo0/22.12/MediaInfo_DLL_22.12_Windows_x64_WithoutInstaller.7z

[kedautinh12]

MKVToolNix v73.0.0
https://mkvtoolnix.download/windows/releases/73.0.0/
https://mkvtoolnix.download/doc/NEWS.md

[kedautinh12]

DGMPGDec 2.0.0.8
https://www.rationalqm.us/dgmpgdec/

[kedautinh12]

x265 v3.5+85 Mod by Patman
https://github.com/jpsdr/x265/releases

[guest]

x265 v3.5+85 Mod by Patman
https://github.com/jpsdr/x265/releases

So what are going to be the differences between this release & Barough's link ??

One seems to have a "new" aq mode option(s).

And do the AVX2 optimised builds make any difference ??

I'd just like a good set of commands that are best for HDR 4K encodes.

I just enabled AVX 512 in x265, on my 7950X yesterday, not sure if it makes that much difference, just a nice to have :D

[StainlessS]

And do the AVX2 optimised builds make any difference ??

It actually says,
x265 with Patman mods (AVS, AQ-MODE 5, ...)
which means it can directly read AVS script files.
I did not see anything about AVX2 (but did not go looking for it).
No idea what the aq mode is.

[LigH]

Be careful with AVX512, see RipBot264 thread (https://forum.doom9.org/showthread.php?p=1981271#post1981271).

[guest]

It actually says,

which means it can directly read AVS script files.
I did not see anything about AVX2 (but did not go looking for it).
No idea what the aq mode is.

Have just tried this, and it doesn't "play nice" with RipBot :(

--aq-mode <0|1|2|3|4>
Adaptive Quantization operating mode. Raise or lower per-block quantization based on complexity analysis of the source image. The more complex the block, the more quantization is used. These offsets the tendency of the encoder to spend too many bits on complex areas and not enough in flat areas.

disabled
1. AQ enabled
2. AQ enabled with auto-variance (default)
3. AQ enabled with auto-variance and bias to dark scenes. This is recommended for 8-bit encodes or low-bitrate 10-bit encodes, to prevent color banding/blocking.
4. AQ enabled with auto-variance and edge information.

[guest]

Be careful with AVX512, see RipBot264 thread (https://forum.doom9.org/showthread.php?p=1981271#post1981271).

Very interesting, LigH, I will take note of the temps ;)

But they already run "stinking" hot :scared:

[StainlessS]

I think that AVX2 was a bit borked [EDIT: well non-optimal] in Haswell (Gen 4), and was not properley fixed until 1 or 2 generations later [gen 6 I think].

[kedautinh12]

x265 v3.5+85.1 Mod by Patman
https://github.com/jpsdr/x265/releases
Btw: after 7950x, he buy i9-13900KF. Rich oldman :D

[kedautinh12]

--aq-mode <0|1|2|3|4|5>
Adaptive Quantization operating mode. Raise or lower per-block quantization based on complexity analysis of the source image. The more complex the block, the more quantization is used. These offsets the tendency of the encoder to spend too many bits on complex areas and not enough in flat areas.

disabled
1. AQ enabled
2. AQ enabled with auto-variance (default)
3. AQ enabled with auto-variance and bias to dark scenes. This is recommended for 8-bit encodes or low-bitrate 10-bit encodes, to prevent color banding/blocking.
4. AQ enabled with auto-variance and edge information.
5. AQ enabled with auto-variance with edge information and bias to dark scenes.

[kedautinh12]

So what are going to be the differences between this release & Barough's link ??

One seems to have a "new" aq mode option(s).

And do the AVX2 optimised builds make any difference ??

I'd just like a good set of commands that are best for HDR 4K encodes.

I just enabled AVX 512 in x265, on my 7950X yesterday, not sure if it makes that much difference, just a nice to have :D

clang-AVX2 more speed than just AVX2. If you want more speed try here with znver 2 (for AMD ryzen 3950x - 7950x) and with skylake (for i9-13900KF) maybe
https://github.com/DJATOM/x265-aMod/releases

[guest]

x265 v3.5+85.1 Mod by Patman
https://github.com/jpsdr/x265/releases
Btw: after 7950x, he buy i9-13900KF. Rich oldman :D

Hi k, yep, not so rich oldman...

It was eating me up, I just had to try an Intel CPU, (after years of AMD), so I got a basic MSI motherboard, a B660 Tomahawk, and I have to say, I am not all that impressed with the 13900KF, it is noticeably slower than the 7950X, and run's hotter.

So I will stick with AMD's !!!

[guest]

clang-AVX2 more speed than just AVX2. If you want more speed try here with znver 2 (for AMD ryzen 3950x - 7950x) and with skylake (for i9-13900KF) maybe
https://github.com/DJATOM/x265-aMod/releases

Thanks for the info, I think I might have tried these a while back, and didn't see any improvement, and this build is pretty old, now :(

Not convinced that AVX2 & AVX512, do all that much, might be just "hype" !!

[kedautinh12]

Thanks for the info, I think I might have tried these a while back, and didn't see any improvement, and this build is pretty old, now :(

Not convinced that AVX2 & AVX512, do all that much, might be just "hype" !!

I'm try with znver2 and it's faster than 20-25% with my r5-5600h and faster than znver3. You don't know movie from torrent site, they still use very old x265 3.5 than i shared. Somtime they use 2.9, 3.3, 3.4 with newest movies :D

[guest]

I'm try with znver2 and it's faster than 20-25% with my r5-5600h and faster than znver3. You don't know movie from torrent site, they still use very old x265 3.5 than i shared :D

OK, well if you see that improvement with your CPU, then maybe I should give it another try, I guess the build "age" doesn't matter all that much, if it works :)

You're right about the different builds still being used.

One interesting dilemma I have is that because RipBot264 has this awesome Distributed Encoding feature, if I use a Ryzen the client PC, and the 13900KF is one of the Servers, ALL the servers use the info & builds from the Client PC, so a zenver2, might not be "used" to advantage on the 13900KF, so I guess all I can do it give it another try.

[kedautinh12]

OK, well if you see that improvement with your CPU, then maybe I should give it another try, I guess the build "age" doesn't matter all that much, if it works :)

You're right about the different builds still being used.

One interesting dilemma I have is that because RipBot264 has this awesome Distributed Encoding feature, if I use a Ryzen the client PC, and the 13900KF is one of the Servers, ALL the servers use the info & builds from the Client PC, so a zenver2, might not be "used" to advantage on the 13900KF, so I guess all I can do it give it another try.

For i9-13900KF, you need use skylake ver

[guest]

For i9-13900KF, you need use skylake ver

Correct, I'll see what happens. :D :thanks:

[guest]

For i9-13900KF, you need use skylake ver

Hi k,

Well, I have done a LOT of x265 testing today, and here are the results, feel free to pass them on.

https://forum.doom9.org/showthread.php?p=1981517#post1981517

[guest]

--aq-mode <0|1|2|3|4|5>
Adaptive Quantization operating mode. Raise or lower per-block quantization based on complexity analysis of the source image. The more complex the block, the more quantization is used. These offsets the tendency of the encoder to spend too many bits on complex areas and not enough in flat areas.

disabled
1. AQ enabled
2. AQ enabled with auto-variance (default)
3. AQ enabled with auto-variance and bias to dark scenes. This is recommended for 8-bit encodes or low-bitrate 10-bit encodes, to prevent color banding/blocking.
4. AQ enabled with auto-variance and edge information.
5. AQ enabled with auto-variance with edge information and bias to dark scenes.

aq 5 certainly slows the process down, approx 25% :(

[kedautinh12]

aq 5 certainly slows the process down, approx 25% :(

AQ is about quility not about speed. You know :D

[guest]

AQ is about quility not about speed. You know :D

1,600 posts :D

Yes, quality is always at the sacrifice of speed :(

[guest]

x265 v3.5+87 Mod by Patman
https://github.com/jpsdr/x265/releases

[tebasuna51]

Please use the new thread Sticky: New versions of free soft used in the GUI's (https://forum.doom9.org/showthread.php?t=184719) to announce new versions of soft than can be used for other GUI's, not only MeGUI.

Please let this thread for only MeGUI related bugs/feature request.

[simple_simon]

I was excited when I opened MeGUI the other day and saw that there were updates but sad again when I realized that this (https://forum.doom9.org/showpost.php?p=1965672&postcount=7094) still wasn't fixed.

[Barough]

I was excited when I opened MeGUI the other day and saw that there were updates but sad again when I realized that this (https://forum.doom9.org/showpost.php?p=1965672&postcount=7094) still wasn't fixed.

Then make a bug report on MeGUI's Sourceforge page

[simple_simon]

Then make a bug report on MeGUI's Sourceforge page

I did. Almost a year ago. I don't even see it listed as "open" or "pending" there now though.

[Barough]

Make a reply in your bug report. That could help

[pooksahib]

For the first time in a long time my MeGUI has been updated (10 updates in all). But now the preview screen just isn't right - the 'Go to frame' button (and others) are cut off by the bottom border and I'm sure there's something different about the right side too. Is there a setting to change the preview dimensions? Thanks

[LeXXuz]

Not to my knowledge. Do you use a zoom setting higher than 100% in your Windows screen settings?

[pooksahib]

Yes, I do (125%). However, reverting to default only partially fixed the issue as more - but not all - of the buttons are now visible.

[pooksahib]

Double post, not sure why that happened.

While I'm here, just to be clear - it's just the preview window that's been cut down by the recent updates. All other MeGUI interfaces are still fine.

[LeXXuz]

Don't know what version you used before, but it's not from the recent updates. It's a rather old issue.
I have this for years now since I need a zoom factor above 100 on some of my screens.
And as long as I still have parts of the preview button to click on, I learned to live with it.
Don't expect any fix to this since MeGUI development is pretty much dead.

[pooksahib]

Thanks for that. It's sad - and odd - about the stopping of development given that MeGUI is such a great program. Also odd, I think, is how my copy (with autoupdate ticked) hasn't done any updating in a couple of years and then gave me 10 updates yesterday...