Log in

View Full Version : MeGUI: bug reports and feature requests


Pages : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 [144] 145 146 147

Barough
28th September 2022, 06:06
Why only x86 ??

https://www.videohelp.com/software/ffmpeg


MeGUI (x86) only support 32-bit FFmpeg

kedautinh12
28th September 2022, 12:05
Why only x86 ??

https://www.videohelp.com/software/ffmpeg

You can use with megui x64 here
FFmpeg n5.1.2 (x64)
Just download ffmpeg-master-latest-win64-gpl.zip (not "shared" in name)
https://github.com/BtbN/FFmpeg-Builds/releases

kedautinh12
28th September 2022, 12:05
MeGUI (x86) only support 32-bit FFmpeg

You know Asd-g won't support avs+ x86 from now

guest
2nd October 2022, 07:29
x264-r3100-ed0f7a6

01-Oct-2022

https://artifacts.videolan.org/x264/release-win64/

StainlessS
2nd October 2022, 15:08
Why only x86 ??

https://forum.doom9.org/showthread.php?p=1959114#post1959114

x64 less support than x86 and maybe a bit more awkward, but its what I use. [must see above link]

EDIT: Maybe also read last half dozen or so pages of that thread.

Barough
5th October 2022, 16:02
Zathor have made some updates now. :)


From MeGUI's Sourceforge page
Zathor - 3 hours ago
I reverted FFMpeg back to 5.0 as the newer version did detect one of my progressive test AVS files as interlaced and therefore caused issues when encoding.

kedautinh12
5th October 2022, 17:19
Zathor have made some updates now. :)


From MeGUI's Sourceforge page

x265 and MP4Box you forgot post new ver here

kedautinh12
6th October 2022, 12:52
x264-r3101-b093bbe (06.10.2022) - https://artifacts.videolan.org/x264/

guest
6th October 2022, 13:42
x264-r3101-b093bbe (06.10.2022) - https://artifacts.videolan.org/x264/

Another build, already...:eek:

Barough
6th October 2022, 21:11
DJATOM's latest aMod x265


x265 v3.5+67+2-aMod-DJATOM
Built on October 06, 2022, GCC 12.2.0

https://github.com/DJATOM/x265-aMod/
https://github.com/DJATOM/x265-aMod/tree/aMod-3.6-pre-v2

DL :
https://www.mediafire.com/file/00ff4k6vrgjwczl

kedautinh12
7th October 2022, 01:43
DJATOM's latest aMod x265


x265 v3.5+67+2-aMod-DJATOM
Built on October 06, 2022, GCC 12.2.0

https://github.com/DJATOM/x265-aMod/
https://github.com/DJATOM/x265-aMod/tree/aMod-3.6-pre-v2

DL :
https://www.mediafire.com/file/00ff4k6vrgjwczl/

Folder win32 empty, folder win64 2 files?? Maybe your mistake

guest
7th October 2022, 02:31
Folder win32 empty, folder win64 2 files?? Maybe your mistake

Yep, both x86 & x64 in the Win64 folder...small error, I'd say.

But what I'd like to know is why the "Mediafire" executable's are so much bigger than DJAtom's ???

kedautinh12
7th October 2022, 05:51
Yep, both x86 & x64 in the Win64 folder...small error, I'd say.

But what I'd like to know is why the "Mediafire" executable's are so much bigger than DJAtom's ???

It's base what Barough use with compiler

And btw new 7950x??? Very rich. If you want throw away 3950x or 5950x, you can gift it to me :D

Lyle_JP
7th October 2022, 05:56
I'm getting an error with recent update of DGIndexNV (x64). I cannot create any AVISynth scripts with AVISynth creat using a dgi foile. I get the generic message: The video stream cannot be opened.

If I attempt to open an AVIsynth script using DGSource, I get a more informative message: DGSource: Could not open DGIndexNV.ini

There is no DGIndexNV.ini file in \MeGUI\tools\dgindexnv\

I'm currently on the x64 build (2928) on the development server.

kedautinh12
7th October 2022, 06:07
I'm getting an error with recent update of DGIndexNV (x64). I cannot create any AVISynth scripts with AVISynth creat using a dgi foile. I get the generic message: The video stream cannot be opened.

If I attempt to open an AVIsynth script using DGSource, I get a more informative message: DGSource: Could not open DGIndexNV.ini

There is no DGIndexNV.ini file in \MeGUI\tools\dgindexnv\

I'm currently on the x64 build (2928) on the development server.

I still use after updated normally. Can you turn off Megui and open again??

Lyle_JP
7th October 2022, 06:12
I still use after updated normally. Can you turn off Megui and open again??

I solved the problem. You must run the DGIndexNV indexing app as an administrator at least once after the upgrade to generate new files. After I did that, everything runs smoothly.

kedautinh12
7th October 2022, 06:21
I solved the problem. You must run the DGIndexNV indexing app as an administrator at least once after the upgrade to generate new files. After I did that, everything runs smoothly.

Or you can run megui as administrator. Everything is ok

Barough
7th October 2022, 06:23
Folder win32 empty, folder win64 2 files?? Maybe your mistake

Slight mistake on my side, fixed now.

Lyle_JP
7th October 2022, 07:54
Or you can run megui as administrator. Everything is ok

Oh, I always do that, But without the ini file generated by the DGIndexNV indexer (which I always run outside of MeGUI's file indexer), AVISynth couldn't do anything.

guest
7th October 2022, 08:02
It's base what Barough use with compiler

And btw new 7950x??? Very rich. If you want throw away 3950x or 5950x, you can gift it to me :D

Good catch, yes, it's that new I haven't actually got it yet, it's in the post, the motherboard I want isn't available for another 3 weeks, but I just had to try one, as they are SO different to anything AMD has EVER done before.

Will be keeping the other's, I want ALL the "horsepower" I can get !!! :D

I was thinking about a 12th or now 13th Gen Intel, but I'm not too sure about those E & P cores....

Rich you say...not now :rolleyes:

kedautinh12
8th October 2022, 16:56
MKVToolNix v71.0.0
https://mkvtoolnix.download/windows/releases/71.0.0/

Barough
9th October 2022, 17:22
MKVToolNix v71.1.0
https://mkvtoolnix.download/doc/NEWS.md
https://mkvtoolnix.download/windows/releases/71.1.0/

Barough
26th October 2022, 08:17
FLAC v1.4.2
https://www.mediafire.com/file/9mc58rxfh5092n7/

kedautinh12
27th October 2022, 13:52
tsMuxer latest ver
https://github.com/justdan96/tsMuxer/releases

VoodooFX
27th October 2022, 15:55
mkvtoolnix-70.0.0-64 update breaks MeGUI on Win7.

kedautinh12
27th October 2022, 16:57
mkvtoolnix-70.0.0-64 update breaks MeGUI on Win7.

You can use this ver for win 7
https://forum.videohelp.com/threads/405407-NON-OFFICIAL-Windows-builds-of-MKVtoolnix/page3#post2669522

guest
28th October 2022, 04:45
mkvtoolnix-70.0.0-64 update breaks MeGUI on Win7.

Try 71.1.0 !!!!

LigH
28th October 2022, 05:39
Why not just delete the post all together....

Because this board does not offer us generic users a "delete post" function.

Barough
28th October 2022, 07:33
I wouldn't consider Barough being "generic"....

I know I can & do delete some of my post's, when required.

I don't have such an option to delete anything so.......

guest
28th October 2022, 07:54
I don't have such an option to delete anything so.......

I just go into "edit", and the delete option is in the bottom right corner of the message window.

Barough
28th October 2022, 09:27
Well, how come I can, I wonder !?!?!

I just go into "edit", and the delete option is in the bottom right corner of the message window.

Totally missed that button. :D

Thnx :)

guest
28th October 2022, 10:12
Totally missed that button. :D

Thnx :)

:D:o:sly::p:cool:

I see you've had a bit of a "clean up", I might do the same, now.

Cheers

guest
28th October 2022, 10:13
Because this board does not offer us generic users a "delete post" function.

Ta-dah...

tebasuna51
28th October 2022, 10:17
Yes, users can delete our post, but it is a 'soft' deleted, still can be read by moderators.

I see your request in 'Reported post' and I see it was a first version of your next post and I deleted it 'phisically' to save space.

VoodooFX
28th October 2022, 10:55
You can use this ver for win 7
https://forum.videohelp.com/threads/405407-NON-OFFICIAL-Windows-builds-of-MKVtoolnix/page3#post2669522
I don't want to try anything, I want updates to not break MeGUI.

guest
28th October 2022, 10:59
Yes, users can delete our post, but it is a 'soft' deleted, still can be read by moderators.

I see your request in 'Reported post' and I see it was a first version of your next post and I deleted it 'physically' to save space.

So is there a schedule for the Mod's to clean up the deleted posts ??

LigH
28th October 2022, 13:23
Ta-dah...

Well, it's either newish, or I am getting oldish. :o

Danette
28th October 2022, 17:13
I’ve run into a problem with MeGUI, as it deals with AudioDub. It won't encode using AudioDub (video will encode, when stripped of the audio source). Several versions of MeGUI ago, I had no problems doing this. Now, it is throwing off the error message: “Number of encoded frames does not match the source.” However, the last time that I used AudioDub was also several versions of Avisynth ago, as well.

The reason that I suspect MeGUI is because AvsPmod indicates no problem with the script. Of course, it doesn’t have to encode it.

MeGui v. 2913 and AviSynth+ v. 3.7.2, both are 64-bit.
The MeGUI log file is available, if requested.

The script, simplified to focus on the problem, is:

Video=MPEG2Source("C:\Users\Main\Desktop\Videos\Frasier\Bonus\2 Demuxed\Final (1)_Track01.d2v")
Audio=DirectShowSource("C:\Users\Main\Desktop\Videos\Frasier\Bonus\3 x264, Audio & Chapters\Final (1)_Track02.ac3")
Clip1=AudioDub(Video,Audio)
Clip1

I have tried many different video and audio sources to verify that there is no issue with the source, itself. The resulting error is the same with each one.

VoodooFX
28th October 2022, 21:27
How many posts people need, never ever use "DirectShowSource", again.

Danette
28th October 2022, 23:39
I don’t know the answer to your question.

Given that a few of us probably don't spend several hours a day studying the forum, you may have to post a few more times about whatever the errors in using "DirectShowSource" are. Of course, this assumes - a BIG assumption - that you truly want to help people. However, it usually is not helpful to come on, in a pompous way, and leave your great, but nebulous, wisdom (we all already admire you).

Now, if anyone wants to help, I'm still interested. If anyone wants to impress upon me how foolish I must be for not having read through the 50 trillion posts here, I won't comment further upon such displays of personal need fulfillment.

kedautinh12
29th October 2022, 01:39
I don't want to try anything, I want updates to not break MeGUI.

Original from MKVtoolnix's author don't support win 7 anymore. If you want still use mkvmerge with megui in Win 7. You need update mkvmerge manually or disable update mkvmerge in Megui

VoodooFX
29th October 2022, 14:49
I don’t know the answer to your question.
It's an answer with the rant at front.

...not having read through the 50 trillion posts here...
Or just one most relevant "post (http://avisynth.nl/index.php/DirectShowSource)" about the filter you are using in your script.

Try reading AVI files with AviSource first. For non-AVI files, try FFmpegSource or LSMASHSource. If that doesn't work then try this filter instead.
[I would place AviSource after LSMASH and FFMS]

And there you can find other interesting things: http://avisynth.nl/index.php/External_filters#Source_Filters

Danette
29th October 2022, 15:57
When importing ac3 files in my copy of AvsPmod, there is no option, that I can find, to use anything but DirectShowSource. Perhaps there is a way to change the setting, but I have found a solution to my original problem, which makes possible DirectShowSource issues moot.

What has to be done is that the Audio line should include “,video=false” at the end. In my example, above, it would appear this way:
Audio=DirectShowSource("C:\Users\Main\Desktop\Videos\Frasier\Bonus\3 x264, Audio & Chapters\Final (1)_Track02.ac3",video=false).

I suspect, without proof, that it is a quirk of 64-bit involvement. I’ve seen other such Avisynth+ quirks between 32 and 64 bit. The “,video=false” tag-on isn’t necessary with my old 32-bit setup.

VoodooFX
29th October 2022, 17:09
When importing ac3 files in my copy of AvsPmod, there is no option, that I can find, to use anything but DirectShowSource.
But there are two options mentioned in my previous post, and other options you can find in the links...
If you want to change filters to your own drag and drop liking then configure there: AvsPmod > Options > Extension templates...

StainlessS
29th October 2022, 17:43
VX, I dont recall any particular problems with DirectShowSource and audio files, only bad where frame accuracy required video,
are you saying you've experienced or know of others with bad experience particular to audio source ?

VoodooFX
29th October 2022, 18:21
No way to remember those prehistoric times. A ~decade ago I liked NicAudio then at some moment I switched to LSMASH then to FFMS then back to LSMASH... there were some issues like audio distortions, can't remember which filter.

tebasuna51
29th October 2022, 18:21
So is there a schedule for the Mod's to clean up the deleted posts ??
Nope, this one is only by user request.

tebasuna51
29th October 2022, 18:43
VX, I dont recall any particular problems with DirectShowSource and audio files...

There are a big problem with audio and DirectShowSources:

The DirectShow System is configured to play files, not to decode files, in a system PC without conexion to a multichannel audio system the standard configuration is to downmix any audio to 2.0, also other defaults or filters, like aply DRC, etc..., can distort the audio.

If inside AviSynth we need the original audio to make any change, or not, to it, my recommended option at this moment is use LSMASH.

Danette
29th October 2022, 20:06
I don’t want to spend too much time on this, because it is a rare event where I need to use AudioDub (and my adjustment, using “video=false”, does work). Playback of the encoded file, 2-channel ac3, is fine.

In any case, on the assumption that DirectShowSource is an inferior approach, I did change to NicAudio in AvsPmod and am using it instead of DirectShowSource. Doing so does allow the elimination of the step of having to add the “video=false”, which is good. I did this before seeing the recommendation to use LSMASH, so I’ll stay with NicAudio for the remainder of this series of files.

StainlessS
29th October 2022, 20:42
... downmix any audio to 2.0, also other defaults or filters, like aply DRC, etc..., can distort the audio.

Arh yes, now I understand. (I dont actually use DSS audio anyway).
I remember someone wanting to remove [EDIT: video] blends with Exblend(), those blends originated in DirectShowSource() video source due to
auto deinterlacing and other auto stuff. Switch to non DSS source and the blends disappeared.
So, DSS audio source does similar "clever" stuff in the background. Avoid.