Log in

View Full Version : MeGUI: General Questions and Troubleshooting Thread


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 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 [170] 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186

LigH
27th November 2017, 08:37
Another general advice: Knowing the content of the log file will probably remove a few doubts. The final AviSynth script generated by MeGUI, used to convert the video, will be part of it.

raymondjpg
27th November 2017, 09:16
Another general advice: Knowing the content of the log file will probably remove a few doubts. The final AviSynth script generated by MeGUI, used to convert the video, will be part of it.

Thanks for the tip.

I looked at the log file and it appears that deinterlacing was applied using TIVTC.dll:

---[NoImage] LoadPlugin("D:\Software\Software\Software\Blu Ray software\MeGUI\Updated Installation from 0.35\tools\avisynth_plugin\TIVTC.dll")
---[NoImage] tfm(order=-1).tdecimate(hybrid=3)

This was after source detection found:

---[NoImage] Progressive sections: 29
---[NoImage] Interlaced sections: 17
---[NoImage] Partially Static Sections: 101
---[NoImage] Film Sections: 5
---[NoImage] Source is declared hybrid film/interlaced. Majority is interlaced.
---[NoImage] Source is hybrid bff and tff at 5 bff and 40 tff.
--[Warning] [27/11/2017 10:49:18 AM] Deinterlacing used

LigH
27th November 2017, 09:25
Quite suspicious material. If it works for you now, fine; yet I wonder if the automatic detection was reliable. It surely has its limits.

raymondjpg
27th November 2017, 11:28
Quite suspicious material. If it works for you now, fine; yet I wonder if the automatic detection was reliable. It surely has its limits.

It is a short snatch of a TV capture where I had noticed significant combing after an HEVC transcode. The Automatic Deinterlacing significantly moderated that combing in this test, so it remains to be seen if it will work just as well on other interlaced material I have. It doesn't have to be perfect as I am only compressing to save space when archiving.

nandoom
14th December 2017, 05:40
I've MeGUI v2800 and I just tried to use the DGindex. It failed with this error. Any idea what could be the problem here?

LigH
14th December 2017, 08:15
This forum takes a while to release attachments.

Could you please publish an MeGUI log file in the meantime? Possibly via a "pastebin service", or in a "CODE" block.

nandoom
15th December 2017, 05:02
Here is the log - https://pastebin.com/3XS3vbht

The pop up says - "Too many pictures per GOP (>=500) DGIndex will terminate."

I checked the "debug" in the settings but I don't see the debug info in the log.

LigH
15th December 2017, 06:44
This error message sounds like a malformed video source, possibly violating specifications.

Try to use a different decoder (e.g. FFMS2 or L-SMASH Works), software decoders may have more capacity and better tolerance than hardware accelerated decoders.

hajj_3
15th December 2017, 15:07
XviD 1.3.5 has been released.

LigH
15th December 2017, 15:08
:scared: THEY LIVE! :cool:

Does anyone still build a fresh xvid_encraw from sources (https://labs.xvid.com/source/)?
_

OK, I did (https://www.mediafire.com/folder/1mku5hvuhs3ts/Xvid). (MABS: MSYS2/MinGW-Win32, GCC 7.2.0)


/trunk/xvidcore/build/generic $ ./bootstrap.sh
/trunk/xvidcore/build/generic $ ./configure
/trunk/xvidcore/build/generic $ make
/trunk/xvidcore/examples $ make

Zetti
15th December 2017, 16:14
#LigH

I get this message when i will download your XviD build: File Blocked for Violation.

LigH
15th December 2017, 19:30
I will investigate. Right now I don't see which terms of service I may have violated.

In the meantime: VideoHelp forum attachment (https://forum.videohelp.com/threads/380072-Xvid-1-3-4-(VFW)#post2504525)

StainlessS
15th December 2017, 20:41
I will investigate. Right now I don't see which terms of service I may have violated.

In the meantime: VideoHelp forum attachment (https://forum.videohelp.com/newreply.php?do=postreply&t=380072#post2504525)

I'm just getting a blank page from videohelp.
(even FireFox Page Source show as blank)

EDIT: And "Save link as ..." tries to save "newreply.php" which is 0 bytes in size.

LigH
15th December 2017, 20:49
URL fixed; a link to reply to a thread was seriously wrong.

StainlessS
15th December 2017, 20:51
We are sweet, thanx LigH.

Zathor
16th December 2017, 09:23
:scared: THEY LIVE! :cool:

Does anyone still build a fresh xvid_encraw from sources (https://labs.xvid.com/source/)?
_

OK, I did (https://www.mediafire.com/folder/1mku5hvuhs3ts/Xvid). (MABS: MSYS2/MinGW-Win32, GCC 7.2.0)


/trunk/xvidcore/build/generic $ ./bootstrap.sh
/trunk/xvidcore/build/generic $ ./configure
/trunk/xvidcore/build/generic $ make
/trunk/xvidcore/examples $ make



Thank you very much, I have to try that later. Could you please also compile a x64 build?

LigH
16th December 2017, 13:02
Attached archive in VideoHelp post (https://forum.videohelp.com/threads/380072-Xvid-1-3-4-(VFW)#post2504525) updated (Win32 and Win64 builds from v1.3.5 source archive instead of SVN, incl. some legal files, and with max. 8192 zones).

MediaFire share will not be altered until I know why it is blocked.

Megalith
19th December 2017, 20:37
Does MeGUI's HD Streams Extractor remove AC3 dialog normalization from audio tracks by default? I am seeing at least one post that suggests it does not.

LigH
19th December 2017, 20:46
Demultiplexing should never change any bit in the exported streams. Except with explicit parameters. IMHO... :o

tebasuna51
19th December 2017, 22:42
MeGUI's HD Streams Extractor uses eac3to and, by defaulf, always remove the dialog normalization.

Unless the parameter -keepDialnorm is added.

DotJun
31st December 2017, 19:55
How do I add --tune grain in megui's x265 configuration dialogue setting? There is no drop down option for grain like the rest.

Megui version 2810.

LigH
31st December 2017, 20:07
Apparently Zathor forgot to add the "grain" tuning to x265...

-t/--tune <string> Tune the settings for a particular type of source or situation:
psnr, ssim, grain, zerolatency, fastdecode

In the meantime, you may have to add it to the custom command line in the "Misc" tab.

DotJun
1st January 2018, 07:08
Apparently Zathor forgot to add the "grain" tuning to x265...

-t/--tune <string> Tune the settings for a particular type of source or situation:
psnr, ssim, grain, zerolatency, fastdecode

In the meantime, you may have to add it to the custom command line in the "Misc" tab.


I tried to do this but I was of the understanding that - -tune was to go right after “program”, but when I add it in the extra command line box it doesn’t show up till after crf. Is this ok to do?

I also have two more questions if it’s ok to ask here.
1) what command line do I need to insert for intel iris decode compatibility?
2) is it true that I need to use the slower setting in order to take full advantage of what x265 has to offer?

SeeMoreDigital
1st January 2018, 13:21
Happy new year everyone :)

I think I must be suffering from some celebratory brain fade because I can't work out how to configure MeGUI to generate 10-bit HEVC encodes...

My 10-bit AVClossless encoded source appears to be okay as MeGUI is able to generate 8-bit HEVC encodes from it without any issues at all. So I suspect I'm not entering the correct command line information within the 'Misc' 'Custom Command Line' box.

Any helpers?

sneaker_ger
1st January 2018, 14:06
http://x265.readthedocs.io/en/default/cli.html#cmdoption-output-depth

SeeMoreDigital
1st January 2018, 14:46
http://x265.readthedocs.io/en/default/cli.html#cmdoption-output-depthMany thanks...

I should have mentioned that I have tried using some of these but in all honesty I don't understand how to use all these command lines correctly. Hence my problem :eek:

sneaker_ger
1st January 2018, 14:49
Just set:
--output-depth 10

SeeMoreDigital
1st January 2018, 15:05
Many thanks @sneaker_ger,

Oh jeez... I'm embarrassed to say that I was adding too many parameters and probably even a comma.

It's working now and generating the correct output.

It's a shame the 'x265' web site does not offer such clear examples for dummies like me.

Thanks again

sneaker_ger
1st January 2018, 15:33
The comma just marks alternatives.
I.e.:
--output-depth 10
is the same as:
-D 10

Just a shorter way to write things. (Notice these single letter parameters use only a single instead of double hyphens.)

SeeMoreDigital
1st January 2018, 15:49
Thanks again,

I know I've only got myself to blame. I should have learned all this 'command line' stuff many, many, many years ago :o

HOB
22nd March 2018, 22:53
The last update caused a problem. It updated MeGUI from 2826 to 2828 and DGindexNV from 2053(20171126) to 2053(2018310). It also updated Avisynth portable, FFmpeg and mkvmerge.

The issue is that when using DGindexNV to index it creates the audio file but does not place it on to the MeGUI main interface page, this has to be done manually. I contacted Don Graft and he didn't think it was an issue with DGindexNV, he suggested I bring up the issue here on this forum...and so, I have.

I have an MeGUI backup folder (MeGUI 2826) and I updated it to 2828 but did NOT allow DGindexNV to update, I left it at v. 2053(20171126), this worked fine so I'm at a loss for an explanation, it seems to me as if it may be and issue with the latest DGindexNV update but Don Graft didn't think so.

Any ideas?...it's NOT a big deal but just thought I'd bring it up.

videoh
22nd March 2018, 23:12
You have to enable the update by right click->Enable on DGIndexNV in the update dialog. Then you can set the checkbox and update it. I just tried it and it works fine. Please give the exact steps you do to see the problem. I updated to the server version of DGIndexNV and then just File/Open'ed an MKV with 4 audio streams and then said I want the indexer and it came up with the audio streams displayed.

I don't know why so many update items get Disabled.

HOB
22nd March 2018, 23:33
Hello videoh, thanks for replying so quickly.
DGindexNV was and is enabled as you suggest and it has updated to the latest version, it's just that the audio file is not being placed automatically into the MeGUI main page dialogue box, I have to navigate to where the audio file is and place it into the MeGUI main page manually. Not a big deal but no doubt one day I'll forget to direct it to the audio file and waste a lot of time in the process. If I fall back to the last version of DGindexNV everything works fine. From what you've said you HAVE updated to the latest DGindexNV and indexed an .MKV file and it worked fine, I wonder if this may be something peculiar with my system?...I have had issues in past that no one else seems to have, I've found work arounds but I'm thinking this may be another one of those odd problems that just effects a small percentage of MeGUI users?

In any event I DO appreciate your reply...thanks again for your feedback.

videoh
22nd March 2018, 23:39
I tried with a transport stream with only one audio and it populated it. I tried with an MKV stream with multiple ones and it did not populate any. Over to Zathor...

The only thing I can think of is that the demuxed filenames have changed in some cases. E.g. from MKV we now have things like:

Star Wars 01 La minaccia fantasma-004_track2_ita_DELAY 5ms.dts

MP4 names also changed.

@HOB

What is the type of your input stream file?

Zathor
23rd March 2018, 00:22
Thanks for the report. While I have to do a test myself, I can already say that if the file name pattern hast changed this very likely is the reason.

HOB
23rd March 2018, 14:04
A most excellent forum, quick responses from people who want to help...thanks so much Zathor and videoh. All the best to you both, all the best to you all.
Thanks again

HOB
24th March 2018, 05:18
videoh

The problem occurred with .mkv files. It DID work correctly with both .mpg and .mp4 files I tried, hope that helps.

videoh
24th March 2018, 10:47
Only MKV filenaming was changed. But there is further name changing planned. For example, I want to put the language in the name and make the format consistent between file types. So it may be better for Zathor to wait until I notify that all the changes are complete.

HOB
24th March 2018, 13:45
Thanks for the feedback videoh...I'll stay tuned for further developments.

Zathor
24th March 2018, 15:02
Only MKV filenaming was changed. But there is further name changing planned. For example, I want to put the language in the name and make the format consistent between file types. So it may be better for Zathor to wait until I notify that all the changes are complete.

Thank you very much!
I posted in your forum some points which I noticed. I hope you do not mind that I did it there and not here.
http://rationalqm.us/board/viewtopic.php?f=8&t=632

videoh
24th March 2018, 15:44
I posted in your forum some points which I noticed. I hope you do not mind that I did it there and not here.
http://rationalqm.us/board/viewtopic.php?f=8&t=632 Thanks and not a problem. I will follow up there.

andoru
25th March 2018, 20:40
Could anyone suggest any custom settings to add to x264 when encoding (literally) still image videos, without ending up with a large file?

So basically what I'm trying to do is to make a video that's a hour and a half long, and only has a still image, so basically it only has one frame that keeps repeating itself for the whole duration of the video.

While I did manage to encode this in MeGUI, I ended up with a +500MB video file, which isn't very reasonable to me, considering it's just a still image.
What I've previously done to get around this problem was to encode the video with ZMBV (Zip Motion Block Video) with AviSynth+VirtualDub. I would usually end up with a video file that's roughly double the original image's size, while with x264, I end up with a file that's hundredths of times bigger.

But since ZMBV isn't as universally supported as h.264, I'll need to make use of the former.

sneaker_ger
25th March 2018, 21:00
With CRf encoding the video will become smaller as you increase --keyint. You can go up to --keyint infinite. But be aware that seeking will then become slower. You could also reduce --fps to achieve a similar effect while possibly making seeking a tad faster.

And of course the usual: decrease CRF, use slower preset, --tune stillimage. Depending on your player there might also be a way of storing only a single image (as jpeg or H.264) as cover in the container without hurting seeking at all.

andoru
25th March 2018, 21:47
Thanks, adding --keyint with a value larger than the total amount of frames the video has, has cut the video size by half, which is a lot better, but still could do with a smaller size. While doing this, I haven't noticed any slowdowns while seeking the video (except the image disappears in VLC when minimising the window, and restoring it afterwards).
The video was already set to the lowest possible frame rate of 1 fps, and I've already set x264 to use the --tune stillimage .
I'm not sure how to set the CBR though.
Any other options I could use to minimise the file size while not compromising quality?

The great thing about ZMBV was/is that it detects if there are any changes between frames, and just copies the same frame if it's a duplicate, all while losslessly compressing the video. It's just a shame it's a bit obscure.

sneaker_ger
25th March 2018, 21:57
I'm not sure how to set the CBR though.
I didn't say "CBR". I said "CRF". The CRF value controls the quality/filesize. In MeGUI's x264 settings it's called "Encoding Mode": "Const. Quality" or "Targeting quality". Default value is 23, if you increase it further the filesize should decrease.

But:
Thanks, adding --keyint with a value larger than the total amount of frames the video has, has cut the video size by half, which is a lot better, but still could do with a smaller size.
This sounds strange. If you set --keyint infinite ("Maximum GOP size" = "0" in MeGUI) x264 will basically only encode a single picture and the rest should compress extremely well. Then it shouldn't be necessary to increase CRF.

So first try CRF encoding with infinite keyint.
If that doesn't lead to success:
How long is the file? How much of it is the video track? How much is audio/subtitles/container overhead?
Post MeGUI log and MediaInfo of input and output.

andoru
25th March 2018, 22:55
I didn't say "CBR". I said "CRF".

And that's what I meant too, sorry.

In MeGUI's x264 settings it's called "Encoding Mode": "Const. Quality" or "Targeting quality". Default value is 23, if you increase it further the filesize should decrease.

Ah, I was using "Automated 2pass".

So first try CRF encoding with infinite keyint.

Yup, not using CRF was the problem. I've now set CRF to 0 (this is what I understand to be the lossless "mode" for x264), and I now have a video file that's half the size of the image used (I assume that's because the original image is png and because of the RGB->YUV conversion). This is far better than I would've expected! And also encodes blazingly fast.

Here's the entire "command line" for the profile I used, in case anyone needs it:

program --output-depth 8 --preset slow --tune stillimage --crf 0 --no-deblock --keyint infinite --min-keyint 1 --b-adapt 0 --qpmax 69 --psy-rd 2.0:0 --output "output" "input"

Thank you very much for the help!

LigH
26th March 2018, 07:29
CRF 0 may be lossless too (indirectly via preset); but "Constant Quantizer" CQ = 0 is the documented option for lossless encoding.

Lossless encoding in H.264 is not only a still image compression, it makes also use of similarities between adjacent frames, like encoding mainly differences between them. You can compare it with Huffyuv, FFV1, Lagarith, Ut ... lossless H.264 can even compress in RGB 4:4:4 mode (https://forum.doom9.org/showthread.php?t=168999) but requires specific CLI options to do that. If it works in the most common YUV 4:2:0 mode, then you should be able to achieve even less than half the size of your PNG sources.

Personally, I would not go for lossless encoding to keep an "archival grade master" with sensible size, especially if you will compress it further with a visually efficient codec anyway. I believe that a CRF between 6 and 12 is sufficient.

HOB
26th March 2018, 17:50
My version of MeGUI is 2829 and it is not updating to 2830. Settings are:

Use Auto Update
Use development update server
Always backup files when needed

In "MeGUI - Updater" dialogue it says the "Local Version" of MeGUI is 2829 BUT...the "Server Version" also says 2829, when I know the latest version is 2830.

HOB
26th March 2018, 20:22
I just started MeGUI and this time it DID update to 2830. I tried starting MeGUI about six time earlier today, a couple of times after rebooting, and it not only didn't update but it didn't even see the newer version on the server. AFTER I posted the above I started MeGUI once again and, as I said, it DID update. I don't know if this was coincidence or due to some magic on Zathor's part, if the latter...thank you very much! ;-)

Zathor
27th March 2018, 11:15
MeGUI will only check every few hours if there are new builds available. This is in order to prevent that the servers are flooded with requests.