MeGUI - x264/XviD/lavc/Snow encoder with MP4/MKV/AVI output & audio

[gaspah]

im having a bit of trouble, all my encodes are coming out with pink, green and various coloured speckles and blocks randomly bliping frequently and simultaneously on the screen.

i'm using x264 on the default settings after install (*scratchpad*) with the only change is it set to medium speed from fast encoding. Also tried [Unrestricted 2-pass HQ].

All I've done is installed megui and allowed it to update itself with all its necessary addons rather than install them separately/manually. Using mp4 file format, and [Nero AAC: NDAAC-HE-Multichannel-HQ 192kbps] not that that is relevant as i did one without audio. I'm using Autoencode and d2v creator with .vob files. Using [Clever Anamorphic encoding] just cropping the black areas, no resize but [suggest resolution (mod16)] is ticked. Everything else is untouched from defaults. thanks.

EDIT: also tried various sources of .vob files with the same problem. all the sources are clean when played from the hdd.

[Dark Alchemist]

The update server is not being updated. You can try putting in MeGUI's settings kurtnoise's update server (http://kurtnoise.free.fr/MeGUI/). So you can use latest x264 from http://x264.nl/, and latest dev MeGUI from SF.net (http://sourceforge.net/projects/megui/files/). If you need a patched x264 build then take a look at this (http://forum.doom9.org/showthread.php?t=130364&page=114) topic.Removing the current update servers in 1055 and changing it to http://kurtnoise.free.fr/MeGUI/ then updating the stuff it wanted to did fix the bug.

:thanks:

[popper]

The update server is not being updated. You can try putting in MeGUI's settings kurtnoise's update server (http://kurtnoise.free.fr/MeGUI/). So you can use latest x264 from http://x264.nl/, and latest dev MeGUI from SF.net (http://sourceforge.net/projects/megui/files/). If you need a patched x264 build then take a look at this (http://forum.doom9.org/showthread.php?t=130364&page=114) topic.

putting http://kurtnoise.free.fr/MeGUI/ in the options/settings/'extra config' and clicking 'configure servers' finds 11 updates so thats good....

however im getting these reported errors on meGUI startup but i cant seem to find them in any log ? so heres a screenshot if that helps solve this.

it doesnt seem to be effecting the GUI use after its cleared though, very odd.

http://i25.tinypic.com/b9dv10.jpg

thanks XhmikosR

[XhmikosR]

Upload the screenshot to an image hosting site like http://tinypic.com/.

[XhmikosR]

Post the error and your OS info at the MeGUI's Bugs tracker (https://sourceforge.net/tracker/?group_id=156112&atid=798476).

[popper]

Post the error and your OS info at the MeGUI's Bugs tracker (https://sourceforge.net/tracker/?group_id=156112&atid=798476).
done.
http://sourceforge.net/tracker/?func=detail&aid=2853195&group_id=156112&atid=798476

[Kurtnoise]

however im getting these reported errors on meGUI startup but i cant seem to find them in any log ?
did you have installed any .Net Framework before to run MeGUI ?

[Ice Dragon]

megui 0.3.1.1055 is currently burning the subs directly on the video frame.
Is there a way to force megui to just copy the sub in to the output container ?? :confused:
Please help :confused:

[Kurtnoise]

Just use any muxers from the Tools menu...

[Ice Dragon]

Just use any muxers from the Tools menu...
Sorry i think i was not clear enough.

Currently i am encoding via somewhat long process.
For example i have an mkv media file with inbuilt sub that i want to encode.
So at present i am doing
* Demuxing the source to two separate files i.e. media and sub.
* encoding the new media file(without sub)
* Finally muxing the above mentioned sub to the output media to get the final output.

The source i mentioned are mkv files with srt subs. So if i directly encode them in megui the subs are getting hardcoded (burned directly on the video frame).

So what i wanted to know was, is there a way to skip the initial demuxing process.
That is megui directly copying the subs inside the source container to final output container (soft sub).

[gaspah]

i'm still unable to cure this problem with the speckles, blips and blocks that have invaded my encodes.. here are the x264 configuration that I last used but still having problems

program --preset fast --tune film --pass 3 --bitrate 700 --stats ".stats" --slow-firstpass --thread-input --output "output" "input"

Modes:
Turbo - No
Lossless - No
Automated 3pass
Bitrate - 700
AVC Profiles - Autoguess
AVC Level - Unrestricted/Autoguess
Tunings - Film
Presets - Fast
No advanced settings

i create d2v files with the tool provided, currently using Anamorphic with 'undercrop to mod16', no resize, PAL 1.82 16:9.

anyone pls help me?

[nurbs]

Use DGsplit to cut a small sample from the vob where the problem is visible. Post it on mediafire or another site like that. Then we can at least find out if the issue is your file or something else.

[Ice Dragon]

Sorry i think i was not clear enough.

Currently i am encoding via somewhat long process.
For example i have an mkv media file with inbuilt sub that i want to encode.
So at present i am doing
* Demuxing the source to two separate files i.e. media and sub.
* encoding the new media file(without sub)
* Finally muxing the above mentioned sub to the output media to get the final output.

The source i mentioned are mkv files with srt subs. So if i directly encode them in megui the subs are getting hardcoded (burned directly on the video frame).

So what i wanted to know was, is there a way to skip the initial demuxing process.
That is megui directly copying the subs inside the source container to final output container (soft sub).
Anyone :confused:

[gaspah]

Use DGsplit to cut a small sample from the vob where the problem is visible. Post it on mediafire or another site like that. Then we can at least find out if the issue is your file or something else.

I have tried it with 5 different sources, all presenting the same issue, replaying of the source .vob files that have been put in the directory where dgindex is reading them from shows no problems, side by side the difference in glitches is very noticeable. I'm going to try with lossless ticked tonight see if that helps.

Also the .vob files that i'm translating to my pc are of a bit of a personal nature and wouldn't feel comfortable sharing them with the general public. I can say with certainty that the source files are clean. Thanks for trying to help tho.

[Kurtnoise]

So what i wanted to know was, is there a way to skip the initial demuxing process.
not in the current releases...

@gaspah: without samples, we can't help you...

[Ice Dragon]

not in the current releases...
Ok thanks for the info.

Also thanks for the update server :thanks:

[XhmikosR]

@Kurtnoise: Can you remove from the NicAudio_r204 the folder Sources and uNicAudio_204? Also rename the readme file as it was in NicAudio_203.zip in order to not place duplicate files in the Avisynth Plugins folder? I'm talking about the zip in the mirror (http://kurtnoise.free.fr/MeGUI/) you've set up.

[m3mbran3]

i'm still unable to cure this problem with the speckles, blips and blocks that have invaded my encodes.. here are the x264 configuration that I last used but still having problems

program --preset fast --tune film --pass 3 --bitrate 700 --stats ".stats" --slow-firstpass --thread-input --output "output" "input"

Modes:
Turbo - No
Lossless - No
Automated 3pass
Bitrate - 700
AVC Profiles - Autoguess
AVC Level - Unrestricted/Autoguess
Tunings - Film
Presets - Fast
No advanced settings

i create d2v files with the tool provided, currently using Anamorphic with 'undercrop to mod16', no resize, PAL 1.82 16:9.

anyone pls help me?

I can almost certainly say it is because of your encoding settings. A bitrate of 700kbps for a DVD source is rather low and using the Fast preset will not help matters. I suggest your trim a section of video and run a few different encodes until you get a result that you are happy with.

i.e. start encoding at 2000kbps and scale it back until you get an acceptable result. Also rather than doing a 3pass on Fast preset do a 2pass on Medium for better results / similar encode times.

[Kurtnoise]

@Kurtnoise: Can you remove from the NicAudio_r204 the folder Sources and uNicAudio_204? Also rename the readme file as it was in NicAudio_203.zip in order to not place duplicate files in the Avisynth Plugins folder? I'm talking about the zip in the mirror (http://kurtnoise.free.fr/MeGUI/) you've set up.
done...

[gaspah]

I can almost certainly say it is because of your encoding settings. A bitrate of 700kbps for a DVD source is rather low and using the Fast preset will not help matters. I suggest your trim a section of video and run a few different encodes until you get a result that you are happy with.

i.e. start encoding at 2000kbps and scale it back until you get an acceptable result. Also rather than doing a 3pass on Fast preset do a 2pass on Medium for better results / similar encode times.

i tried doing it again with a 3min chunk and finished with a 230mb file, i don't think it was the bitrate as what i was encoding was set to a specific size, ie 700mb per hour increased or decreased depending on which file i was encoding. I set my 3min encode to 700mb to remove all doubt on my mind that the size/bitrate had something to do with the equation. The output file came out just as dirty as all the rest.

@gaspah: without samples, we can't help you...
do you have a suggestion of a small dvd ifo that i can download, encode and return? something that'll be ideal to encode to display such errors? i'm certain that this will happen with any dvd ifo with this encoder behaving as it is at present.

thankyou both for replying to my query. :thanks:

[Kurtnoise]

after you have ripped your DVD on the hard drive, cut a sample from VOB files uisng DGSplit and upload it somewhere (mediafire.com or something...)

[PzSniper]

THIS tool is AMAZING! Inspector Gadget helped me appreciate what magics MeGui can do!

[PzSniper]

Seems someone deleted my post for MeGUI donation, very rude! No pm, no explain.

Thanx :(

[Kurtnoise]

all admins from MeGUI SF webpage need to have a registered paypal account to enable donations. For the moment, I'm the only one...If you still want to give some money, just ping Doom9 himself via http://www.doom9.org/donate.htm

[BlindBandit]

MeGUI need the Zune HD profile in there next update : )

[XadoX]

Is there a way to show the used options of the new megui profiles. So I can quick check if a special option is used in the choosen profile.

[Kurtnoise]

you better wait the next update (both build & presets)...

[XadoX]

Thanx.

[ChibiBoi]

i used the megui bitrate calculator to get my encode to 175mb, with the xvid hq profile, it imported the calculated bitrate into the profile settings, but when i encode, the video comes out at 280mb! is there any way to fix this?

[AMED]

I've found a very very small bug when the avisynth editor loads any avisynth profile that has the overcrop to achieve mod 16 enabled. the overcrop will not be applied unless the user clicks the clever anamorphic drop down and reselects overcrop.

how to reproduce,

1. Open Avisynth editor and create a new profile that has Overcrop enabled.
2. Select the newly created profile in the avisynth profile drop down and close avisynth creator.
3. reopen the avisynth and look at where it says crop.
4. now click on the clever anamorphic drop down box and reselect overcrop, now look where it says crop (it should now say crop (will be rounded up to mod16)

if you make multiple profiles that have overcrop enabled, and go through them the overcrop will still not activate unless you reselect it in the clever anamorphic drop down box.

using MeGUI v0.3.1.1056

http://img59.imageshack.us/img59/2231/overcrop1.png (http://img59.imageshack.us/i/overcrop1.png/)

[LeonLanford]

just tried to use megui again today, last time I used megui was last year, now it has some annoying errors, like the auto update doesn't update to the newest x264 which resulted in rc lookahead error and cannot exit error, every time I want to exit I got his problem

http://img17.imageshack.us/img17/4425/68387191.th.jpg (http://img17.imageshack.us/i/68387191.jpg/)

I have to use task manager to close megui, too bad it used to be good..

[RunningSkittle]

just tried to use megui again today, last time I used megui was last year, now it has some annoying errors, like the auto update doesn't update to the newest x264 which resulted in rc lookahead error and cannot exit error, every time I want to exit I got his problem

...

I have to use task manager to close megui, too bad it used to be good..

Yes, current updates break megui
Use this update server instead...
http://kurtnoise.free.fr/MeGUI/

[bob0r]

@Kurtnoise

http://forum.doom9.org/showthread.php?p=1333794#post1333794

Can you fix an installer on sourceforge which updates from latest update server? For x264.nl
Can you fix x264 encoding options if any aren't correct?

[LeonLanford]

Yes, current updates break megui
Use this update server instead...
http://kurtnoise.free.fr/MeGUI/

@Kurtnoise

http://forum.doom9.org/showthread.php?p=1333794#post1333794

Can you fix an installer on sourceforge which updates from latest update server? For x264.nl
Can you fix x264 encoding options if any aren't correct?

look like I'll leave megui, I just wanted some new settings in megui and what I got is malfunctioning program, too bad but bye :(

[Nightshiver]

I wouldn't call it quits this soon. As you may have not heard, the dev(s)? were/are on break still. At least, sharktooth is.

[Taurus]

look like I'll leave megui, I just wanted some new settings in megui and what I got is malfunctioning program, too bad but bye :(
Here, on my side of the fence, everything works as expected :D.
Sure, there are some little bugs and quirks.
But nothing to worry about.
Thanks to everybody involved in making such a nice GUI.
And of course to all the devs who made all the tools under the hood:thanks:.

[Kurtnoise]

@Kurtnoise

http://forum.doom9.org/showthread.php?p=1333794#post1333794
Thanks to Richard Berg, I can upload files on megui.org now...I'll make an update asap. My own webpage will be probably dedicated to the MeGUI kbr builds.

Can you fix an installer on sourceforge which updates from latest update server? For x264.nl
Can you fix x264 encoding options if any aren't correct?
I've no time to do that yet...So, updates and bugfixes from me are postponed for the moment. Yeah, I've a real life.


btw, the sources are available. So, learn & play if you think it's too long...:rolleyes:

[bob0r]

All x264.nl needs is a megui version with the correct update server added. So in the future the countless bug reports because of outdated versions doesn't happen.

I am in between moving 4 houses, fixing my own and work also. Still i can find a few minutes to update stuff.

If you really have no time, ill try to make my own installer again, though it's been a long time ago! :)

[Kurtnoise]

before updating, I prefer to fix x264 bugs first...I hope before the end of this week.


btw, you cannot compare your free time management with mine...

[Claymore]

Dunno it's my first or second post - doesn't matter. I'll only say thanks for this excellent frontend and support of it.

@kurtnoise: Take your time - making good things is lasting longer. If somebody'll declares this posts as spam: How about relaxing and trinking coffee?

greetings

[wolfbane5]

I recently upgraded from vista x86 to windows 7 x64. I've been using MeGUI for awhile now, but have a couple of questions:

1. Any way I can utilize the x264 x64 or avisynth x64 (<-does this exist?) in MeGUI or is it strictly x86 based?

2. I noticed I never had DGVC1Index. Where can I find that?

Thanks in advance for your help.

[cweb]

I recently upgraded from vista x86 to windows 7 x64. I've been using MeGUI for awhile now, but have a couple of questions:

1. Any way I can utilize the x264 x64 or avisynth x64 (<-does this exist?) in MeGUI or is it strictly x86 based?

2. I noticed I never had DGVC1Index. Where can I find that?

Thanks in advance for your help.

Re 2 - You can get it from Neuron2's website (http://neuron2.net/mine.html)...

[wolfbane5]

I have a 640 MB 8800 GTS and it looks like it only supports VP1 and VP2 is required for DGVC1Index. Is there another way I can index VC1 files with MeGUI? I currently have to revert to another encoding program to encode VC1 files.

[Inspector.Gadget]

ffmpeg source 1 or 2, DSS2() with ffdshow set to "WMV9" for VC-1...

[magic144]

yeah, I just use DSS with a .grf file to control the filters (typically ONLY source + the Windows built-in WMV DMO Decoder - remove the renderer)

still not sure about the whole frame-accurate business wrt DSS vs DSS2 vs FFmpeg source, etc
this thread leaves me more, rather than less confused
http://forum.doom9.org/showthread.php?t=147086

since I only tend to use whole-movie VC-1 .mkvs extracted (via eac3to) directly from my source discs, with no trims/edits, maybe that's why I've not had an issue using only DSS - though I am using multi-threaded x264 encoding

[Inspector.Gadget]

DSS2 is frame-accurate, DSS is generally not. FFMS is a whole different animal.

[magic144]

there seemed to be some confusion in the thread to which I linked:
there was some contention that DSS2 can be seen to go 'blocky' if seeking to open-GOP - is this an issue with VC1-in-mkv?, or does it only apply to MPEG2 material??

any reason why I've NOT run into any issues with VC1 material using DSS in multi-threaded x264?

cheers,
m

[Inspector.Gadget]

That's a decoder problem, or the file is corrupt. If you're only doing linear operations: e.g., not a lot of seeking or scrubbing - then you're probably OK with DSS. But DSS2 is known to be frame-accurate, so there's no reason not to prefer it over DSS (except in audio applications, where generally NicAudio is preferable anyway).

[magic144]

thanks IG - will give it a go next go-round

[wolfbane5]

I've never used DSS or DSS2 before, so I'm completely unfamiliar with it. Are there any guides on it, or perhaps a wikibook?

[unknownsoldierX]

I'm trying to convert a few files so they will play on a slightly under-powered system. They are 1080p, but the PC can only manage to play 1080i.

Here's what I'm dealing with:

Format : Matroska
File size : 1.02 GiB
Duration : 13mn 30s
Overall bit rate : 10.8 Mbps
Writing application : mkvmerge v2.9.8 ('C'est le bon') built on Aug 13 2009 12:49:06
Writing library : libebml v0.7.7 + libmatroska v0.8.1

Video:

ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L5.0
Format settings, CABAC : Yes
Format settings, ReFrames : 5 frames
Muxing mode : Container profile=Unknown@5.0
Codec ID : V_MPEG4/ISO/AVC
Duration : 13mn 29s
Bit rate : 10.3 Mbps
Width : 1920 pixels
Height : 1072 pixels
Display aspect ratio : 16:9
Frame rate : 23.976 fps
Resolution : 24 bits
Colorimetry : 4:2:0
Scan type : Progressive
Bits/(Pixel*Frame) : 0.210
Stream size : 998 MiB (96%)

Audio:

ID : 2
Format : AC-3
Format/Info : Audio Coding 3
Codec ID : A_AC3
Duration : 13mn 30s
Bit rate mode : Constant
Bit rate : 224 Kbps
Channel(s) : 2 channels
Channel positions : L R
Sampling rate : 48.0 KHz
Video delay : 22ms
Stream size : 21.6 MiB (2%)

I set MeGUI to encode the video using x264: DXVA-HD-HQ with a file size of 450MB and a bitrate of 4657Kbps. Is that a good bitrate for 1280x720?

Also, I get no audio. Following a tutorial, I used the .avs file as the input. Set to encode using Nero AAC: NDAAC-HE-64Kbps. The resulting audio file is only 437KB, and it's 13.5 minutes of silence.

Here's my .avs file:

DirectShowSource("D:\Temp\zms.mkv", fps=23.976, audio=true, convertfps=true)
TDecimate(cycleR=1)
#crop
Lanczos4Resize(1280,720) # Lanczos4 (Sharp)
#denoise

ConvertToYV12()


Thanks.

[moneytoy]

you might need an upgrade of microsoft net framework

[Zergrinch]

Something's very wrong with meGUI, after I changed the update server into the .fr one, and applied the updates.

First, a bunch of windows like this pop up.
http://upload.jetsam.org/images//MeGUI-Errors-A.jpg

meGUI then appears to start normally, but trying to update gives this:
http://upload.jetsam.org/images//MeGUI-Errors-B.png

I'm basically left with only SNOW and XVid profiles.

:scared:

[salatoimikud]

I have XviD size problem. When i want 175 mb XviD file then after encoding and muxing comes only 140mb. 350mb comes only 260mb :(

How fix this?

I use megui 0.3.1.1056

[Alex_080]

Something's very wrong with meGUI, after I changed the update server into the .fr one, and applied the updates.

First, a bunch of windows like this pop up.
http://upload.jetsam.org/images//MeGUI-Errors-A.jpg

meGUI then appears to start normally, but trying to update gives this:
http://upload.jetsam.org/images//MeGUI-Errors-B.png

I'm basically left with only SNOW and XVid profiles.

:scared:

I have the same problem when i update to new version please help!!

[Zergrinch]

I downloaded 0.3.1.1056 from the link in this thread opening, and ran the updates on the .FR server. This time, I told it not to upgrade to 1057.

It seems to work.

[shaumux]

It seems that 1057 has some problems with the x264 and its profiles.
Other than that everything seems to work

[mozzle]

It seems that 1057 has some problems with the x264 and its profiles.
Other than that everything seems to work

That's a joke, right?

[shaumux]

That's a joke, right?

NO i only get errors posted above with the x264 profiles,
even if i delete them and reinstall them

[salatoimikud]

hi,

Please share megui core_0_3_1_1056.zip

Thank You

[twist3d]

how about everyone who has problems with 1057 and the profiles, read the troubleshooting thread... :search:
http://forum.doom9.org/showthread.php?p=1338540#post1338540

[TheSane]

Hi,

MeGui is a great tool and not easy to understand.
I have done a few test encodings to get a good result.
Now i have done a Blu Ray recode with the following result:

General
Complete name : X.mkv
Format : Matroska
File size : 17.9 GiB
Duration : 2h 7mn
Overall bit rate : 20.0 Mbps
Writing application : x264
Writing library : Haali Matroska Writer b0

Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4.1
Format settings, CABAC : Yes
Format settings, ReFrames : 5 frames
Muxing mode : Container profile=Unknown@4.1
Codec ID : V_MPEG4/ISO/AVC
Duration : 2h 7mn
Bit rate : 19.6 Mbps
Nominal bit rate : 20.0 Mbps
Width : 1 920 pixels
Height : 816 pixels
Display aspect ratio : 2.35:1
Frame rate : 23.976 fps
Resolution : 24 bits
Colorimetry : 4:2:0
Scan type : Progressive
Bits/(Pixel*Frame) : 0.522
Stream size : 17.5 GiB (98%)
Writing library : x264 core 78 r1318 fe83a90
Encoding settings : cabac=1 / ref=5 / deblock=1:-1:-1 / analyse=0x3:0x133 / me=umh / subme=8 / psy=1 / psy_rd=1.0:0.0 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=2 / 8x8dct=1 / cqm=0 / deadzone=21,11 / chroma_qp_offset=-2 / threads=6 / nr=0 / decimate=1 / mbaff=0 / constrained_intra=0 / bframes=3 / b_pyramid=0 / b_adapt=2 / b_bias=0 / direct=3 / wpredb=0 / keyint=250 / keyint_min=25 / scenecut=40 / rc=2pass / mbtree=0 / bitrate=20000 / ratetol=1.0 / qcomp=0.60 / qpmin=10 / qpmax=51 / qpstep=4 / cplxblur=20.0 / qblur=0.5 / ip_ratio=1.40 / pb_ratio=1.30 / aq=1:1.00

It's the unrestricted Extra Quality profile is used with the extended Settings.

The problem with the result is, that i can't jump to an position in the film, the player (zoom, media player classic, vlc) freeze an hang up.
How can i fix this?

[bob0r]

If there will be no new MeGui version during next week, with a working update server and working x264 settings, i will remove it from x264.nl

Too much complaints and double "bug" reports are being posted.

[magic144]

I tend to agree (with twist3d).
1057 IS a perfectly working version.
The problem is that there has been a disconnect between MeGUI and the legacy profiles (all of which are broken with the advent of 1057).

The best solution would be if the update server(s) had new (compatible) profiles available.

Otherwise, I guess people will be left on their own to invent their own new profiles. There are now also some limitations on what can be done in the x264 MeGUI profiles, since 1057 is now "aware" of the x264 command-line parameter rules and thwarts attempts to make individual settings contradict the overriding preset.

Personally, I am interested in producing DXVA-compatible encodes, so I have used the old DXVA HD HQ profile as a starting point and re-tooled it for 1057 as best as I can tell how. The profiles given in the mentioned post are indeed compatible with the syntax for 1057 and can be used as valuable starting points.

A *very* good place to learn about the role of the presets and parameters is right here:-
http://mewiki.project357.com/wiki/X264_Settings

I hope that MeGUI doesn't suffer too much because of this glitch.

how about everyone who has problems with 1057 and the profiles, read the troubleshooting thread... :search:
http://forum.doom9.org/showthread.php?p=1338540#post1338540

[Ruriko]

I get this error: malloc of size 439296 failed
How to fix this?

[Inspector.Gadget]

Nobody will help you with Rule 6 content. You've been here three and a half years, you should know that.

[salatoimikud]

ok i have problem.
I put my computer windows 7 home premium, installed megui 0.3.1.1056 and if i want create x264 mkv then i get error
[Error] An error occurred: x264 [error]: could not open input file 'G:\encode2\movie.avs'

How fix this? reinstall deosnt help.

[Inspector.Gadget]

Post your AVS Script and also run the source file through MediaInfo and copy and post the output of the "text" view here. Both blocks of text should be in codeboxes, which you can use by clicking "Go Advanced" when posting.

[salatoimikud]

Megui Log:

--[NoImage] Job commandline: "C:\Program Files\megui\tools\x264\x264.exe" --profile high --level 3.1 --preset fast --pass 1 --bitrate 1139 --stats "G:\encode3\skyla_-_ayo_technology.stats" --thread-input --output NUL "G:\encode3\skyla_-_ayo_technology.avs"
--[Information] [10.11.2009 17:37:32] Encoding started
--[Error] An error occurred: x264 [error]: could not open input file `G:\encode3\skyla_-_ayo_technology.avs'
--[NoImage] Standard output stream
--[NoImage] Standard error stream
--[Information] [10.11.2009 17:37:33] Job completed

AVS Script:
DGDecode_mpeg2source("G:\encode3\skyla_-_ayo_technology.d2v", cpu=4, info=3)
ColorMatrix(hints=true, interlaced=true, threads=0)
AssumeTFF().FieldDeinterlace()
crop( 10, 80, -12, -76)

BicubicResize(720,400,0,0.5) # Bicubic (Neutral)
#denoise



Mediainfo File info:
General
Complete name : G:\skyla_-_ayo_technology_(lpcm_pal_po-sl).vob
Format : MPEG-PS
File size : 181 MiB
Duration : 3mn 16s
Overall bit rate : 7 736 Kbps
Writing library : encoded by TMPGEnc 4.0 XPress Version. 4.3.1.222

Video
ID : 224 (0xE0)
Format : MPEG Video
Format version : Version 2
Format profile : Main@Main
Format settings, Matrix : Default
Duration : 3mn 16s
Bit rate mode : Variable
Bit rate : 5 893 Kbps
Nominal bit rate : 8 000 Kbps
Width : 720 pixels
Height : 576 pixels
Display aspect ratio : 4/3
Frame rate : 25.000 fps
Standard : PAL
Colorimetry : 4:2:0
Scan type : Interlaced
Scan order : Top Field First
Bits/(Pixel*Frame) : 0.568
Stream size : 138 MiB (76%)
Writing library : TMPGEnc XPress 4.3.1.222

Audio
ID : 160 (0xA0)
Format : PCM
Format settings, Endianness : Big
Format settings, Sign : Signed
Muxing mode : DVD-Video
Duration : 3mn 16s
Bit rate mode : Constant
Bit rate : 1 536 Kbps
Channel(s) : 2 channels
Channel positions : Front: L R
Sampling rate : 48.0 KHz
Resolution : 16 bits
Stream size : 35.9 MiB (20%)

[Inspector.Gadget]

Do you get the same error when using ONLY MPEG2Source("G:\encode3\skyla_-_ayo_technology.d2v") ?

[rack04]

It could be the special characters in the file name.

[salatoimikud]

Do you get the same error when using ONLY MPEG2Source("G:\encode3\skyla_-_ayo_technology.d2v") ?

I found problem. I installed avisynth again and now works :)

[rudiev]

Hi all. I'm new here and using me gui for about 1,5 month now. I like the program, very easy to use. But I made a clean installation with windows 7 x64(from vista x64). I installed the latest avisynth, me gui, k-lite coedec pack(5.4.4). I updated megui with the auto-update function.
The first problem I got was when i wanted to convert a h.264 blu-ray rip to a .mkv file. I used the dxva-hd-insane profile and adjusted the bitrate to 12100 kbs, no other changed to this profile. I got the first error saying it couldn't use the " --rc-lookahead 40" option . Never had this before with the original x264.exe, but I downloaded the newest x264.exe from x264.nl and replaced it. It worked, which before on my old vista installation wouldn't work. The other side was that the encoding now took a lot more time(10 hours for the first step on a intel E8200 @ 3.2 GHz), and i got a large mbtree file, while the option in the profile stated " --no-mbtree". Ok, it encoded, and even the colors of the .mkv file look more like the original blu-ray then before with the other 'olde' version of x264.exe.
An other problem is when I try to open a blu-ray rip which is encoded with WVC1 or the older MPG2 with the AVS script creator. I got the error "Avisynth script error: DirectShowSource: Timeout waiting for graph to start.".
If I remember good I also had problems opening WVC1 sources on the old installation with vista.

At K-Lite codec pack I ran the program "Preferred DirectShow Filter Tweakers for Windows 7" to change some 32-bit directshow filters from microsoft to ffdshow, but no result.

I have a other machine running windows 2003 server x64 with megui, k-lite 5.2, avisynth. And tried to openen the WVC1 and MPG2 sources but on this machine I don't got any problems.
So are there other people having problems with Windows 7? Or are there some known problems with windows 7(x64)?

Kind regards,

[Frank_UK]

I have noticed that MEGUI has not updated for ages. The update site is still hosting v1051
It used to update a couple of times aweek.

[rudiev]

I have noticed that MEGUI has not updated for ages. The update site is still hosting v1051
It used to update a couple of times aweek.

You can download v1056 and after installation you can use the megui updater to update.

Maybe the author doesn't have that much time to keep it updated as frequently as before. As long as he/she will update it once in a while i'm happy :)

[rudiev]

I'm a little bit further with one problem, encoding orginal blu-ray with WVC1 to x264. I used the program GraphStudio, http://blog.monogram.sk/janos/tools/monogram-graphstudio/ , to see the links that are used to render the video. On my Windows 7 x64 machine the WVC1 blu-ray is rendered thru the 'WMVideo Decoder DMO', while on my Windows 2003 x64 is is rendered thru 'ffdshow Video Decoder'. I think here's the problem why Avisynth isn't able to open the WVC1 source. Anyone have idea's to change this of have a solution for this? It isn't possible in the Win7DSFilterTweaker where i can only choose Microsoft..

[Redsandro]

You can download v1056 and after installation you can use the megui updater to update.

Multiple people on the forum say that, but for me it doesn't work.

Especially check the core current and update version: (image attachment pending approval)
http://forum.doom9.org/attachment.php?attachmentid=10498&stc=1&d=1258497203

[rudiev]

Multiple people on the forum say that, but for me it doesn't work.

Especially check the core current and update version: (image attachment pending approval)
http://forum.doom9.org/attachment.php?attachmentid=10498&stc=1&d=1258497203

Then there should be a problem with your connection, just tested the download and it worked.
Site: http://www.sf.net/projects/megui
Direct link: http://downloads.sourceforge.net/project/megui/megui-development/0.3.1.1056/megui-0.3.1.1056-setup.exe?use_mirror=garr
Mirror: http://sourceforge.net/settings/mirror_choices?projectname=megui&filename=megui-development/0.3.1.1056/megui-0.3.1.1056-setup.exe
Else send me a private message with your email and i can email it to you if you want.

Edit: at another megui thread i red that people are using v1057, don't know where to get that one, gonna ask them, post it here later.
http://forum.doom9.org/showthread.php?t=105920&page=251

[Redsandro]

Thanks, that's indeed the one I found and am using.
I don't know why the image isn't approved yet so I guess you cannot see it, but it sais in the update dialog:
Core Existing Version: 0.3.1.10.56
Core Latest Version: 0.3.1.10.51

So if I update, I am back to the 'broken' version, even though this one seems to have the same problem.

If I remove settings.xml and autoupdate.xml, it sais nothing for Existing Version, but after update it is back to the way it is now.

So I don't have a connection problem and I've downloaded the new version just fine, but there's simply no change in the dead updates. It's like the 'bad update server' is hardcoded in the registry and I cannot find it.

-edit-

I cannot find that .57 either, maybe some internal test build?

[rudiev]

@Redsandro
I now see that i have the same:
Core Existing Version: 0.3.1.10.56
Core Latest Version: 0.3.1.10.51
I assume it is a bug, cause it also sais:
There is 0 file that can be updated.
So i again assume that it's alright.
But when i downloaded v1056 and ran the updater there where, if i remember good, 42 updates to update, and it did so without any problems.

In the other thread where i asked for version v1057 the anwser was that v1057 is a development version, so that why i wont update, unless you configure the updater to use development version, but remember these could be unstable and could have problems.
You can change to development and add extra update servers in the AutoUpdateServerConfigWindows:
Options -> Settings (or CTRL+S) -> tab Extra Config -> button Configure Servers.
You can add new updates servers and if you change the drop down box 'Auto-update server' to development you can update, if you want, to the development and maybe unstable version 1057. For me there are 'There are 15 files that can be updated.'.

[Redsandro]

Thanks for the explanation. I also had many updates the first time but I noticed they all update to the same versions I already have for a few months now.

I prefer not to use unstable releases, but if I cannot find a fix soon I think I will try .57.

[rudiev]

I'm a little bit further with one problem, encoding orginal blu-ray with WVC1 to x264. I used the program GraphStudio, http://blog.monogram.sk/janos/tools/monogram-graphstudio/ , to see the links that are used to render the video. On my Windows 7 x64 machine the WVC1 blu-ray is rendered thru the 'WMVideo Decoder DMO', while on my Windows 2003 x64 is is rendered thru 'ffdshow Video Decoder'. I think here's the problem why Avisynth isn't able to open the WVC1 source. Anyone have idea's to change this of have a solution for this? It isn't possible in the Win7DSFilterTweaker where i can only choose Microsoft..

I found the solution:
This should be the solution, worked with me:
1. Enable vc-1 in ffdshow. You can do this by starting the ffdshow video decoder configuration: startmenu -> programs -> k-lite codec pack -> configuration -> ffdshow video decoder configuration -> codecs -> scroll down to format VC-1 -> click on disable(or other decoder) and change it to libavcodec.
2. Run the Win7DSFilterTweakers. Startmenu -> programs -> k-lite codec pack -> tools -> Win7DSFilterTweakers -> scroll down 32-bit directshow filters to 'set as default VC-1decoder' and select ffdshow.
3. Change splitter for .m2ts files. Startmenu -> programs -> k-lite codec pack -> configuration -> manage preferred source filters -> scroll to .m2ts files and choose Haali.
4. Restart megui and it should be working, else reboot pc.
Enjoy!

[Emulgator]

Despite the issues I'd like to play around a bit with MeGUI 1057 and newer x264 versions.
Since 1057 seems to have been withdrawn from kurtnoise's server and sourceforge's as well
I kindly ask if somebody could share a 1057 link or the 1057 file.

[userix]

Thanks for your replies. :)

I apologize for not being specific in my initial post. The file I am encoding is from one of my anime DVDs. It's not that the whole encode is crappier, only the beginning of the episode, which starts with a static scene, and then cuts to another static scene. On the Q6600 encodes, those 2 static scenes seem blockier (noisier) when compared to the old Dell encode. The rest of the encode, including future static scenes, seem fine afterwards. What gets me is why are the aforementioned static scenes encoded on my Q6600 blockier than those of my old Dell encode?

I have attached screenshots taken using MPC of the two static scenes I am talking about. The noise in the first scene is subtle, but you can clearly see the difference between the 2nd static scene. Of course, when watching it in full screen, the differences stand out much more.

In addition, when I encode the video using 2-pass xvid encoder with same bitrate on the Q6600, the 2 static scenes are the same quality as the Dell encode. It seems only when I use x264 encoder on my Q6600, I get crappier results. Boggles the mind.



I'm pretty sure. I downloaded the same stable version to both computers, then proceeded to update it to the newest files available at the same time. Therefore, the profiles I downloaded through the update module are the same. I double check the command line arguments being fed and they are identical on both machines.



I haven't looked at the logs specifically, but I figure if I create the d2v and avs script files in the same exact manner on both machines, I should get the same results, right? Bitrates are set the same for both comps. The size of the video encodes aren't exactly the same, but it's only off by 200k-300k. I have CCCP codec pack installed on both comps and use MPC to playback the files. I am not sure what you mean by using the decoder for encoding. MEGUI uses the x264.exe file it gets from the update, which is located in the MEGUI tools folder.



I can rule out the decoding issue for playback, because I took the old Dell encoded file and played it on my Q6600 and it looks great, just like on my Dell. I played the Q6600 encoded video on the Q6600 and the old dell and it looks the same: blockier static screens at the beginning of the video.

Sorry for raising the dead, but does anyone know why this happens? I am still trying to figure this out after all these months. Hit the view button by my name to see the screenshots I am referring to.

[Djon]

Despite the issues I'd like to play around a bit with MeGUI 1057 and newer x264 versions.
Since 1057 seems to have been withdrawn from kurtnoise's server and sourceforge's as well
I kindly ask if somebody could share a 1057 link or the 1057 file.

Option -> Settings -> Extra config, Auto Update -> Configure servers -> Auto-update servers: Development
And of course after that, Options -> Update

[mozzle]

This has reached a new level as far as "inmates running the the asylum" goes. But yeah, people,, let's own this!!!

[magic144]

personally, I'd like to see the return of Kurtnoise and/or Sharktooth and the returning of this ship to the capable hands of its ex-captains!
it is a real shame that this very good proj is going a little stale in this apparent vacuum

*EDIT*
having said that,
I tried 1057 out for the first time last night (properly) and all was A-OK still (using my own tailored profile).
I manually uprev'd x264 to its newest version - if anything, it is significantly faster now thanks to x264 recent improvements

[Emulgator]

I kindly ask if somebody could share a 1057 link or the 1057 file.

Option -> Settings -> Extra config, Auto Update -> Configure servers -> Auto-update servers: Development
And of course after that, Options -> Update


Thanks, Djon !

[sfk]

pls help me

i m rip Audio VBR with MeGUI Modern Media Encoder ther give me error

pl help me what to do .........

see in following pics

http://i47.tinypic.com/6nqyzd.jpg

http://i45.tinypic.com/2vubjuf.jpg

[Inspector.Gadget]

Post the actual log as well as a MediaInfo "Text" report about your source file.

[rtjnyoface]

Are we no longer able to drag and drop files on megui in Win7? I'm using 1056 and it works just fine on xp but not win7. Any ideas?

[stax76]

It runs with higher privileges then the drop source so the OS don't send messages to the drop target because of security concerns. It's a never ending story, users even have been banned for requesting a UAC fix. I made several posts giving detailed technical information how to fix, it's not difficult.

[rtjnyoface]

Oh. Sorry. Got a link to your solution?

[Ruriko]

Is there a way to batch create avs? I'm really lazy to create a avs for each video cause I want to queue about 50 videos

[Redsandro]

DGIndex has an option to specify a template to use with created output files, and an option for exiting after finishing. With these options you can script-use it anyway you want.

DGIndex -IF=[in.mpg] -OF=[out] -AT=[template.avs] -EXIT

I've created a VBS script to automatially index+avs all mpeg files in a right-clicked folder.
http://www.rednet.nl/vision/articles/196

Ofcourse it's something different with .avi files, but feel free to use that script and adopt it to your personal needs.
In stead of using DGIndex you could use your own routine to write .avs. Something like:
Set avsFile = fso.OpenTextFile(newName, 2, True)
Select Case format
Case "avi"
avsFile.WriteLine("AviSource(""" & src & """)")
Case Else
avsFile.WriteLine("directShowSource(""" & src & """, audio=true, fps=" & fps & ")")
End Select
avsFile.WriteLine("EnsureVBRMP3Sync()")
avsFile.WriteLine("Trim(0,0)")
avsFile.WriteLine("return last")
avsFile.WriteLine("")
avsFile.Close

VBscript is very annoying to write, but not hard to adapt.

[THEAST]

Wow, after months of waiting and checking this topic again and again, I just got a whole new set of updates for MeGUI! Very big thanks to zathor who is working on this project now, God bless you mate, God bless you. Hope we wouldn't have to wait months for new updates anymore!

[magic144]

indeed -great news to see this up and running again!

[Dogway]

sorry - wrong thread, I was for troubleshooting

[jfromeo]

I see MeGUI contains tsMuxer, eac3to and mkvmerge. Can it be used for DTS-HD MA/TrueHD/LPCM demuxing and later MKV remuxing?

[Ryu77]

I am trying to set-up the latest MeGUI with x264...

I keep getting the error "--[Error] An error occurred: x264 [error]: invalid argument: b-pyramid = --direct" For some reason x264 is having trouble with the command to enable b-pyramid.

I have tried using a few different builds but I need to use Jeeb's patch as I need --nal-hrd for Blu-ray compliancy.

Is there any way I can overcome this error to enable b-pyramid?

[Zathor]

I am trying to set-up the latest MeGUI with x264...

I keep getting the error "--[Error] An error occurred: x264 [error]: invalid argument: b-pyramid = --direct" For some reason x264 is having trouble with the command to enable b-pyramid.

I have tried using a few different builds but I need to use Jeeb's patch as I need --nal-hrd for Blu-ray compliancy.

Is there any way I can overcome this error to enable b-pyramid?

Please switch to the development update server.
More information:
http://forum.doom9.org/showthread.php?t=151159

[Ryu77]

Please switch to the development update server.
More information:
http://forum.doom9.org/showthread.php?t=151159

Thank you...

It's all working perfectly now. :)

[THEAST]

Okay, now that MeGUI is up and running again, I thought I'd report two small bugs I have found, this is not the wrong place, is it?

1. In x264 encoding options>Analysis tab, the description for "No Mixed Reference Frames" actually refers to Mixed Reference Frames and even the default value is written as "Enabled" in there while the default value for "No Mixed Reference Frames" should be disabled, right? Well, I thought this might confuse some people or maybe it is right the way it is?:confused:

2. In AVS script creator>Filters tab, if "Source is anime" is checked before analyzing the source, "mode=1" is not added to the script even if analysis is done right afterwards and is only added if it's checked after analysis.

Again thanks to Zathor for reviving MeGUI and also Kurtnoise and Sharktooth who spent hours of their time on this project.

[Zathor]

1. In x264 encoding options>Analysis tab, the description for "No Mixed Reference Frames" actually refers to Mixed Reference Frames and even the default value is written as "Enabled" in there while the default value for "No Mixed Reference Frames" should be disabled, right? Well, I thought this might confuse some people or maybe it is right the way it is?:confused:

2. In AVS script creator>Filters tab, if "Source is anime" is checked before analyzing the source, "mode=1" is not added to the script even if analysis is done right afterwards and is only added if it's checked after analysis.

Thank you for your report. Both things have been fixed in my dev build.

[THEAST]

Great, thank you.:)

[Ryu77]

I have recently just started doing encodes with a newer x264 encoder. I hadn't previously upgraded in a while as I was unaware of the development server.

Anyway, I started using the new x264 with MeGUI and was excited about the results MB tree may bring... But I have some disappointment. The encodes seem broken on my LG BD370 Blu-ray player. There seems to be a break up of pixels present (large squares etc.) as if B-frames or something along those lines are not being decoded correctly. The odd thing is these play perfectly on my PS3. In the past I have never had an issue with encodes on the LG BD370.

Here is my command line...

program --profile high --preset fast --pass 2 --bitrate 1500 --stats "D:\Applications\MeGUI\x264 Log" --thread-input --keyint 25 --min-keyint 1 --b-adapt 2 --b-pyramid strict --ref 4 --qpmin 8 --vbv-bufsize 20000 --vbv-maxrate 24000 --rc-lookahead 24 --me umh --direct auto --subme 8 --partitions all --trellis 2 --no-dct-decimate --no-fast-pskip --aud --nal-hrd --mvrange 511 --sar 1:1 --output "output" "input"

And this is what Media Info shows...

cabac=1 / ref=4 / deblock=1:0:0 / analyse=0x3:0x133 / me=umh / subme=8 / psy=1 / psy_rd=1.0:0.0 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=2 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=0 / chroma_qp_offset=-2 / threads=6 / sliced_threads=0 / nr=0 / decimate=0 / mbaff=0 / constrained_intra=0 / bframes=3 / b_pyramid=1 / b_adapt=2 / b_bias=0 / direct=3 / wpredb=1 / wpredp=2 / keyint=24 / keyint_min=1 / scenecut=40 / rc_lookahead=24 / rc=2pass / mbtree=1 / bitrate=8553 / ratetol=1.0 / qcomp=0.60 / qpmin=8 / qpmax=51 / qpstep=4 / cplxblur=20.0 / qblur=0.5 / vbv_maxrate=24000 / vbv_bufsize=20000 / ip_ratio=1.40 / aq=1:1.00

I am encoding for DVD media (AVCHD). Is there anything that looks wrong here?

I can post a clip if it would help.


Edit: I just noticed there was a version 2 of the x264 Jeeb's 1376 build. Would this be one of the bugs that are fixed?

[nurbs]

The problem isn't mb-tree, it's weighted p-prediction. The default mode, wpredp=2, does frame reordering which isn't supported by some players (http://x264dev.multimedia.cx/?p=212#more-212). A workaround is using --weightp 1. This isn't a bug in x264, but in the decoder hardware.
AFAIK there is nothing that stops you from using frame reordering in the blu-ray or avchd spec so you might actually run into store bought discs that won't work on your player, although there haven't been any reports on that yet.

[Ryu77]

The problem isn't mb-tree, it's weighted p-prediction. The default mode, wpredp=2, does frame reordering which isn't supported by some players (http://x264dev.multimedia.cx/?p=212#more-212). A workaround is using --weightp 1. This isn't a bug in x264, but in the decoder hardware.
AFAIK there is nothing that stops you from using frame reordering in the blu-ray or avchd spec so you might actually run into store bought discs that won't work on your player, although there haven't been any reports on that yet.

Ahhh... So it is. I can see now that is the only variable with the command line. Thank you! I didn't think it was MB tree though, I only mentioned that previously as that was the reason for my update. I prob should have noticed the difference in the command line myself. I had a feeling it was something to do with frame ordering/decoding but the fact that the PS3 played them fine threw me off a bit.

After reading Dark Shikari's diary, it makes more sense as I can see that it is a problem with a few decoders and that the encoder itself is not to blame.


EDIT: Ok, I just did a short encode with --weightp 1 and the problem is still there. Any other ideas what could be causing this?

I currently have my short test encode in a Matroska container (as the LG BD370 supports mkv), could this cause any problems?

I am about to try an encode with --weightp 0 (disabled) and will report back with the results.


EDIT # 2: Yep, did the trick! So for future reference pertaining to anyone with the LG BD370 and I would guess the BD390 (and quite possibly the other decoders mentioned in Dark Shikari's Diary), the command must be --weightp 0 (which disables weighted P-frame prediction).

[surma884]

Thank you for your report. Both things have been fixed in my dev build.

Is this a good place to suggest features? Currently the bitrate calculator doesn't list the other DVD sizes, such as the ones here: http://en.wikipedia.org/wiki/DVD

You will notice that there are DVD1, DVD2, DVD3, DVD4, DVD10, DVD14, etc. I need to create some DVD14s from a Bluray, but it is hard to determine the exact size. In the Bitrate Calculator for DVD9 it says 8152MB, but when I click Select Size it says 8.0GB. There's no way an mkv has 152MB of overhead. So why is it different? I can't seem to figure out the equation. The Wiki page says that DVD9 = 8.54GB. I know the file system has an over head, so the other value 7.95GiB seems correct as all my DVD9 mkvs are about ~7.94.

Can you add those DVD sizes to the calculator? Or if anyone knows, can they tell me how to calculate the value for Select Size, so the end result is 12.33GiB?

Thanks

[bnshrdr]

Keep in mind that to convert from GB to MB you take GB * 1024, as there are 1024 MB per GB.

[surma884]

Keep in mind that to convert from GB to MB you take GB * 1024, as there are 1024 MB per GB.

Aaaahhhh! That makes sense...thanks. I found this unit converter online that gave me the MiB for a DVD18, and when I put it in the calc, it came out to 15.90GB, which is correct. FYI, the size was 16281MiB to get 15.90GB.

Thanks again!

[quantum5uicid3]

those are just two sided dvds, so its gonna have to be two files anyway

[coolalibaba]

hi all,
Sorry I'm a newbie for video encoding. I have a video with mp42 encoding. When I try to enqueue the job I just get this error:
"Your AviSynth clip has the following problem:
Error in AviSynth script:
AVISource: couldn't locate a decompressor for fourcc MP42
(E:\Download\Video\yunshan02.avs, line 1)"

The avs file is very simple:

AVISource("E:\Download\Video\yunshan02.avi", audio=false)
#deinterlace
#crop
#resize
#denoise


What should I do? any suggestion will be appreciated.

[Guest]

AVISource("E:\Download\Video\yunshan02.avi", audio=false) You cannot discuss this here, per forum rule 6.

[salatoimikud]

i have question.

When i use Megui version 0.3.1.1056 then i have
x264 DXVA-SD-Insane profile 2 pass encoding FPS ~22

But when i use 0.3.3.0 then same profile 2 pass encoding FPS is only ~3.

What the hell? :devil:

:stupid:

[Zathor]

i have question.

When i use Megui version 0.3.1.1056 then i have
x264 DXVA-SD-Insane profile 2 pass encoding FPS ~22

But when i use 0.3.3.0 then same profile 2 pass encoding FPS is only ~3.

What the hell? :devil:

:stupid:
Please post the log file for both encodings. I assume you are using the same avs source?

[salatoimikud]

Please post the log file for both encodings. I assume you are using the same avs source?

Here is my logs.

[nurbs]

The encodes use different settings.
From .1056:
--preset fast--bitrate 1000
From the new one
--preset fast --bitrate 1000 --b-adapt 2 --ref 8 --merange 32 --me tesa --direct auto --subme 8 --trellis 2 --no-dct-decimate
I've removed command line parameters that don't influence speed. Especially the --me parameters kill speed for little quality gain.

[salatoimikud]

The encodes use different settings.
From .1056:

From the new one

I've removed command line parameters that don't influence speed. Especially the --me parameters kill speed for little quality gain.

And how i remove these?

[nurbs]

Select the profile, click "config", go to the "misc" tab, hit "default settings", drag the preset slider to fast (main tab), select level 3.1 in the dropdown menu, done.

If you need --aud for some reason and if MeGUI doesn't add it automatically for .264 output there is a checkbox for it in the analysis tab. If you don't know what --aud is you probably don't need it.

[Neillithan]

I haven't updated MeGUI for a while and I finally decided to get around to it.

I noticed there were new presets, some of which I dig, some of which I don't. I've noticed an immediate issue. Every single preset defaults to a constant quality unless it explicitly says "2 pass" in the preset name.

I REALLY hope this isn't on purpose, as it deters beginners from making a good variable bitrate video. Most of the time, beginners will simply choose the default settings and if constant quality is the default, guess what? Every single video they will make will be retardedly huge and won't look nearly as good as a good variable bitrate video. This is up to the creators of the preset to fix, not a beginner. This is an extremely bad thing that needs to be fixed RIGHT now.

Also, the DXVA presets have been renamed to "DXVA (Unrestricted)" and the unrestricted presets appear to have been removed. Beforehand, I could suggest to people that they should use the DXVA presets because they use restricted settings. Now, the DXVA presets are labeled as Unrestricted. Can you see where I'm going with this? Those very same people are going to come back to me with questions regarding what preset they should choose and I will have to listen to them say, "but you said never to use the unrestricted presets". I've had to modify my video tutorials to compensate for the preset name changes once already, now I'm going to just say screw it because it's likely I will need to do that every 6 months.

What is the point of continuously renaming the presets in an effort to become as accurate as possible if every 6 months they will just get renamed again for the same damn reason?

This is a real issue, not just a fantasy I've pulled out of my ass. You guys need to choose GOOD preset names that have consistency all across the board and are easily comprehensible by the average beginner. What you have "now" is absolutely not beginner friendly or easily comprehensible. See examples below.

I am a long time user and I refuse to choose a quality based on its name of "standard" or "extra". If I choose standard, it might choose some values that I deem too low. The word "standard" doesn't in any way reflect what I feel is "standard" when it comes to values. "I" will be the judge of what is standard based on my own opinion of what's "standard" or... "average".

I suggest picking a permanent name for the presets and instead of using the naming scheme "standard, high quality, insane quality", you settle on something much more human friendly to understand. Ex: Numbers. Quality 1 (Fast), Quality 2 (Normal), Quality 3 (Above Normal)... etc. This will solve 2 problems in 1. First, it will make the qualities appear in an natural sorting order of Fastest to Longest encoding time. Also, it will make choosing the right quality easy for beginners AND long time users.

I realize complaining about the preset names is a petty thing, but they aren't even included with program when you download it, they have to be downloaded via the internal program updater. I get beginners asking me how to use MeGUI and I ALWAYS start off with, "download the latest updates from the auto updater". I KNOW they didn't do that and it's imperative they do that in order to gain BASIC functionality of the program via presets. Until a decent list of appropriately named presets are included with MeGUI, I have EVERY right to consider this a high priority issue.

I absolutely despise turning people to an easier to use program for x264 encoding because most easy programs lack a lot of great functionality that can only be found in MeGUI. I might be doomed to that fate forever unless you guys figure out who your target audience is, rather "SHOULD be".

Thanks,
-Neil

[stax76]

@Neillithan

Seems you know little to nothing about x264, how would you complain about profile names, write video tutorials or even use a advanced application like MeGUI without little to no experience?

[Taurus]

@Neillithan

I haven't updated MeGUI for a while and I finally decided to get around to it.

So you dont know about all the hazzles with MeGui going on for the last months?
Thanks to Zathor there is light at the end of the tunnel. Please read more and stop complaining.

This is an extremely bad thing that needs to be fixed RIGHT now.....
You guys need to choose GOOD preset names that have consistency
all across the board and are easily comprehensible by the average beginner.

Dont shout. Read the forum rules.

You dont have to use MeGui if you're not satisfied with the everlasting and ongoing development in the gui and x264.
Why dont you write your own presets, test them with your friends, and share them with the community.
If you're in the know it should be fairly easy for you.

[Neillithan]

@Neillithan

I haven't updated MeGUI for a while and I finally decided to get around to it.

So you dont know about all the hazzles with MeGui going on for the last months?
Thanks to Zathor there is light at the end of the tunnel. Please read more and stop complaining.

This is an extremely bad thing that needs to be fixed RIGHT now.....
You guys need to choose GOOD preset names that have consistency
all across the board and are easily comprehensible by the average beginner.

Dont shout. Read the forum rules.

You dont have to use MeGui if you're not satisfied with the everlasting and ongoing development in the gui and x264.
Why dont you write your own presets, test them with your friends, and share them with the community.
If you're in the know it should be fairly easy for you.

Why don't you stop being an elitist prick and agree with some truth. The fact of the matter is, MeGUI is never in a perfect working state because the "ongoing development" prevents it from reaching that kind of status.

I'm tired of having MeGUI work and then suddenly I have to relearn it because the developers decided to change some settings. I do not stand alone with this either. Lots of people have expressed their discontent with the way MeGUI is developed. One minute, it's working, the next it's not due to an update. It's in this constant alpha state, it's never in a 100% totally usable state.

Also, I am not "new" to MeGUI, I have been using it for at least 2 years. I have a pretty good visual of how MeGUI has changed over these couple of years and I have seen it go from totally acceptable, working condition to barely functional and back again. It's a miracle when there isn't a problem with it. I have even gone as far to snapshot my MeGUI installation as a fallback in case the autoupdater decides to update some perfectly working files to some malfunctioning files.

Also, I gave up trying to alert the MeGUI devs that their x264 Lossless preset was broken, which I even explained how to fix... and months went by without a response or an update that fixes the preset. It's an easy fix, you just change one thing in the preset and blamo, it works... It's not hard. For that to be an ongoing issue for months is totally unacceptable.

The very non subtle point I'm making is, MeGUI is not in any condition to use on any kind of reliable basis due to the nature of its auto-updating constantly breaking things. I wish it would not do that, and I can express my feelings about the matter in good natured way or an irritated way... it makes no difference. MeGUI is always going to be this way.

So EXCUSE me if I'm right and you don't like it.

-Neil

[Atavarius]

Why don't you stop being an elitist prick and agree with some truth. The fact of the matter is, MeGUI is never in a perfect working state because the "ongoing development" prevents it from reaching that kind of status.

I'm tired of having MeGUI work and then suddenly I have to relearn it because the developers decided to change some settings. I do not stand alone with this either. Lots of people have expressed their discontent with the way MeGUI is developed. One minute, it's working, the next it's not due to an update. It's in this constant alpha state, it's never in a 100% totally usable state.

Also, I am not "new" to MeGUI, I have been using it for at least 2 years. I have a pretty good visual of how MeGUI has changed over these couple of years and I have seen it go from totally acceptable, working condition to barely functional and back again. It's a miracle when there isn't a problem with it. I have even gone as far to snapshot my MeGUI installation as a fallback in case the autoupdater decides to update some perfectly working files to some malfunctioning files.

Also, I gave up trying to alert the MeGUI devs that their x264 Lossless preset was broken, which I even explained how to fix... and months went by without a response or an update that fixes the preset. It's an easy fix, you just change one thing in the preset and blamo, it works... It's not hard. For that to be an ongoing issue for months is totally unacceptable.

The very non subtle point I'm making is, MeGUI is not in any condition to use on any kind of reliable basis due to the nature of its auto-updating constantly breaking things. I wish it would not do that, and I can express my feelings about the matter in good natured way or an irritated way... it makes no difference. MeGUI is always going to be this way.

So EXCUSE me if I'm right and you don't like it.

-Neil

So STFU and make and release a profile set?

[Inspector.Gadget]

Neillithan, grow up. Don't complain about how hard MeGUI is for beginners while touting your own purported insight and experience. I have Zathor's MeGUI build working perfectly here and have since moving to the constructd server.

I have EVERY right to consider this a high priority issue.

This is FOSS. You have the "right" to use something else or to fork a new project.

[Neillithan]

So STFU and make and release a profile set?

No. Does it bring you solace to know that you're an idiot?

[Neillithan]

Neillithan, grow up. Don't complain about how hard MeGUI is for beginners while touting your own purported insight and experience. I have Zathor's MeGUI build working perfectly here and have since moving to the constructd server.



This is FOSS. You have the "right" to use something else or to fork a new project.

I have the right to tell you you're also an idiot.

[Atavarius]

No. Does it bring you solace to know that you're an idiot?

You are complaining about something you can easily rectify yourself with minimal effort to a guy who was nice enough to release updates to a dead program. So ummm yeah about that idiot thing...

[Neillithan]

MeGUI is dead? Yeah.. about that first thing I said, I haven't updated the program in months, nor have I read anything online about it during that time period. HOW AM I SUPPOSED TO KNOW THIS.

Congratulations, you're now the third idiot in a row to say something COMPLETELY useless to me. Oh wait, you already did say something completely useless to me. Congratulations on furthering your idiocy.

[Inspector.Gadget]

Yeah.. about that first thing I said, I haven't updated the program in months, nor have I read anything online about it during that time period. HOW AM I SUPPOSED TO KNOW THIS.

We're working on typing out this telegram just as fast as we can, sport. In the meantime maybe you can get ahold of this newfangled "Google" thing the kids are all talking about.

Bottom line, MeGUI has a few bugs that Zathor and some other contributors are working diligently to fix. Any other problems are solely the responsibility of the end user not being diligent enough when researching and/or being ignorant of their DirectShow environment.

[Taurus]

MeGUI is dead? Yeah.. about that first thing I said, I haven't updated the program in months, nor have I read anything online about it during that time period. HOW AM I SUPPOSED TO KNOW THIS.

Congratulations, you're now the third idiot in a row to say something COMPLETELY useless to me. Oh wait, you already did say something completely useless to me. Congratulations on furthering your idiocy.
Constructive criticism or trolling?
You have to decide.

[Ryu77]

Neillithan, honestly mate you began this conversation with an (as you call it) elitist attitude.

You basically spoke like the developers have the responsibility to serve you. You mentioned that at one stage you told the developers how to fix something and they didn't. If you really have a grasp on MeGUI/x264, why didn't you fix it yourself? I mean, creating a preset is pretty basic stuff. You could easily just make your own as others have also suggested. I have actually done this to make life easier for those that have asked for my help.

http://www.mediafire.com/file/tt1mj4m21j4/Ryu77%20MeGUI%20x264%20profiles.zip

Could you link us to this guide you have created as I would be interested to see the level of information provided.

[blsbball]

Neillithan, honestly mate you began this conversation with an (as you call it) elitist attitude.

You basically spoke like the developers have the responsibility to serve you. You mentioned that at one stage you told the developers how to fix something and they didn't. If you really have a grasp on MeGUI/x264, why didn't you fix it yourself? I mean, creating a preset is pretty basic stuff. You could easily just make your own as others have also suggested. I have actually done this to make life easier for those that have asked for my help.

http://www.mediafire.com/file/tt1mj4m21j4/Ryu77%20MeGUI%20x264%20profiles.zip

Could you link us to this guide you have created as I would be interested to see the level of information provided.

Thanks for the presets. Unfortunately when I try to use them the encoding video window shows up but never actually begins encoding where as the default presets begin instantaneously. Any ideas? Thanks again

[Ryu77]

Thanks for the presets. Unfortunately when I try to use them the encoding video window shows up but never actually begins encoding where as the default presets begin instantaneously. Any ideas? Thanks again

You need to go into the x264 setup window and allocate a place for the log/stats file... Then all should be good.

Just to be clear, these presets are only for AVCHD & Blu-ray. Of course they can be used for regular encoding but AVCHD & Blu-ray is their intended use.

Also, the faster presets aren't all that fast. I know I could have made them faster, with lower quality settings but I value quality too much. Please feel free to change anything to your own preference.

[blsbball]

You need to go into the x264 setup window and allocate a place for the log/stats file... Then all should be good.

Just to be clear, these presets are only for AVCHD & Blu-ray. Of course they can be used for regular encoding but AVCHD & Blu-ray is their intended use.

Also, the faster presets aren't all that fast. I know I could have made them faster, with lower quality settings but I value quality too much. Please feel free to change anything to your own preference.

Thank you very much. Where exactly is the x264 setup window? And I intend on using your DVDrip preset. Im sure I will see good results.

[Ryu77]

Thank you very much. Where exactly is the x264 setup window? And I intend on using your DVDrip preset. Im sure I will see good results.

My DVDrip preset is something that I quickly made with minimal changes from the AVCHD preset. A couple things were altered to be more suitable for SD material. You may find a better (faster) DVD preset from the server. That being said, I know my preset will give great results due to x264 being such a great encoder but you may be able to get away with less optimal quality settings without any discernible difference.

In regards to the setup window...

http://i291.photobucket.com/albums/ll301/Ryu77_photo/Help2.jpg

[magnatique]

I think I may have found a bug :

I just needed to dual boot my Core I7 with XP on my original Windows7 partition. I made it boot out on H:\, so whenever I am in the winxp environment programs install on H:\

MeGui Updater always tries to run the updates on the c:\program files\megui position, not the H:\

[andrew_seul]

I got the same problem like you and I fixed it by reinstalling MeGUI completely :)

[magnatique]

I got the same problem like you and I fixed it by reinstalling MeGUI completely :)

Yeah, I copied the folder over from my c:\ win7 to my XP :)



I do have another bug but investigating on my own... seems to be random, unsure if it is when I am connected remotely to my box, or just a new problem when using the new vfw4x264.exe to pipe, but I get some D3d error on line 216 or something

[HeadlessCow]

Try opening up the AutoUpdate.xml file in the megui directory and replacing all the references to your old location with your new location.

[Neillithan]

An excerpt from a conversation I had with a friend regarding MeGUI.

[18:11] Neil: go to Options > Update
[18:11] jomi294: im there
[18:11] jomi294: but i already updated everything
[18:12] jomi294: and imported everything
[18:12] jomi294: overwrote everything
[18:12] Neil: go to profile collections on the left
[18:12] jomi294: ok im there
[18:12] jomi294: i see 4 items
[18:12] Neil: check Tx264
[18:12] Neil: right click it > force reinstall
[18:12] jomi294: done
[18:12] Neil: try it
[18:13] jomi294: yeah
[18:13] jomi294: it gives me the preset importer
[18:13] jomi294: but it sthe same ones i already have
[18:13] jomi294: theres some missing
[18:13] Neil: right click check all?
[18:13] jomi294: i only see the DXVA note
[18:13] jomi294: for the unrestricted profile
[18:13] jomi294: i remember with my old install
[18:13] jomi294: there were some other presets that had that DXVA thing
[18:13] jomi294: i even think you were the one that told met o use that
[18:13] jomi294: Extra Quality
[18:13] jomi294: setting
[18:13] Neil: yes, what has happened is, some douchebag decided to redo all of the presets
[18:14] jomi294: :o
[18:14] Neil: i complained about it at the doom9 forum, and AS USUAL
[18:14] jomi294: oh gg
[18:14] Neil: i'm taken as a fool
[18:14] Neil: check this out
[18:14] jomi294: ok
[18:14] jomi294: which profile shoudl i choose then
[18:14] jomi294: you must remember the one i m talking about
[18:14] jomi294: it had some DXVA tag
[18:14] jomi294: but it wasn't unrestricted
[18:14] jomi294: and it was Extra Quality
[18:14] Neil: use one of the ps3 or the xbox 360 profiles
[18:15] jomi294: what about the 2 pass
[18:15] jomi294: is that worse or better
[18:15] Neil: 2 pass is ALWAYS better
[18:15] jomi294: lol
[18:15] jomi294: nevermind
[18:15] jomi294: that was xvid
[18:15] Neil: also, be careful
[18:15] Neil: megui has defaulted to a constant quality in its presets
[18:16] Neil: only the presets that explicitly say 2 pass are 2 pass
[18:16] jomi294: so i choose
[18:16] jomi294: x264: PS3 - 2-pass
[18:16] Neil: for god knows what reason, somebody decided it should work that way. i also complained about that, but i think we know how that went

And for anyone that is curious, I am FULLY aware you can change the quality to "2-pass" in any of the presets. The point is, the default is constant quality, and in my honest to god opinion, that is full of retards.

[Atavarius]

Ah the arrogant ponce is back.

[18:13] Neil: yes, what has happened is, some douchebag decided to redo all of the presets

No some very nice person decided to take a dead program and continue its development because it was a fairly widely used tool. Another very nice person decided to redo the profiles because the old ones were very much out of date and did not make full use of new and updated x264 features.

[18:14] Neil: i complained about it at the doom9 forum, and AS USUAL

No you demanded that people change all their work so it was easier for you. Newsflash chief, the people that make these tools usually do not make them for paid jobs. They do it in their spare time for the betterment of the community. They owe you NOTHING. If I were you I would be thanking Zathor and the profile makers for making MeGUI usable again. As you have been told before, making your own profiles is extremely easy. All the relevant information is out there and can be found in oh a 5 minute Google search and some reading. I am sorry if you lack the capability to do either of these.

[18:14] Neil: i'm taken as a fool

No you were taken exactly as you are. An arrogant fool who refuses to do anything for himself. If you had come on and simply said something like:

Hey guys, is there any chance of getting a profile with these features (insert whatever it is you wanted here).

Someone would either have made it for your or pointed you exactly where you need to go to do it yourself. However I myself am disinclined to help you in anyway do to your rudeness and arrogance.

[18:15] Neil: 2 pass is ALWAYS better

This right here tells me everything I need to know. You have no idea at all what you are talking about and I doubt you would listen is anyone explained it to you.

[18:16] Neil: for god knows what reason, somebody decided it should work that way. i also complained about that, but i think we know how that went

Yes someone did. Someone with the intelligence or internet savvy to understand the options and make their own profiles. And who was also kind enough to share them. Again, you should be thanking them for making your favorite tool relevant again.

[Inspector.Gadget]

The point is, the default is constant quality, and in my honest to god opinion, that is full of retards.

You don't know better than the x264 developers, who ALWAYS tell people to use CRF when they don't need a specific file size. Nobody cares what you think, so stop posting this nonsense blend of off-topic idiocy and erroneous statements. Go away.

[Neillithan]

Ah the arrogant ponce is back.



No some very nice person decided to take a dead program and continue its development because it was a fairly widely used tool. Another very nice person decided to redo the profiles because the old ones were very much out of date and did not make full use of new and updated x264 features.

Do you think they could have done this in a way that doesn't annoy 5000 people?



No you demanded that people change all their work so it was easier for you. Newsflash chief, the people that make these tools usually do not make them for paid jobs. They do it in their spare time for the betterment of the community. They owe you NOTHING. If I were you I would be thanking Zathor and the profile makers for making MeGUI usable again. As you have been told before, making your own profiles is extremely easy. All the relevant information is out there and can be found in oh a 5 minute Google search and some reading. I am sorry if you lack the capability to do either of these.

First of all, I didn't demand anything. I used phrases like, "you need to" or "I suggest". That in no way implies that I'm demanding anything. If I was demanding, I would use phrases such as, "I demand" or begin telling you guys what to do without any kind of introductory phrase.

Understandably, "You need to" can be so easily misconstrued with demanding, but that is just my way of saying, "Please" without the courtesy.

I then proceeded to list examples for possible preset names, but nobody seemed to notice that.

No you were taken exactly as you are. An arrogant fool who refuses to do anything for himself. If you had come on and simply said something like:

Hey guys, is there any chance of getting a profile with these features (insert whatever it is you wanted here).

Someone would either have made it for your or pointed you exactly where you need to go to do it yourself. However I myself am disinclined to help you in anyway do to your rudeness and arrogance.

I don't WANT your help. I don't want a user from this forum to come to my rescue and create presets that perfectly suit me. What I "suggested" is a means to create better "default" presets to be downloaded through the auto updater in MeGUI. But seeing as one would have to be somebody of high status and recognition, that would, otherwise, never happen.


This right here tells me everything I need to know. You have no idea at all what you are talking about and I doubt you would listen is anyone explained it to you.

Does it excite you to know that you can pick out the ones that don't know everything there is to know about video encoding? Why not try something more interesting. Try figuring out which ones don't care enough to know everything. Then I'll be impressed. Or maybe I won't... due to the not caring part... You can never tell!

You make no effort to cite examples of why you think I have no idea of what I'm talking about.

Atavarius: I will just say this guy doesn't know what he's talking about so that I can appear like I know what I'm talking about. Golden!

Yes someone did. Someone with the intelligence or internet savvy to understand the options and make their own profiles. And who was also kind enough to share them. Again, you should be thanking them for making your favorite tool relevant again.

Well, this so called person with "intelligence or internet savvy" (I love how you put that word "or" in there) fucked up. It took less than 2 weeks for someone to come to me with questions regarding the new presets, to which I had to tell him to use a different preset than which he was accustomed to. I foresaw the future and I will continue foreseeing it so long as this new person with "intelligence or internet savvy" continues working on MeGUI.

This person you speak of should fess up and fix the presets. Oh, but please don't misconstrue that with demanding.


You don't know better than the x264 developers, who ALWAYS tell people to use CRF when they don't need a specific file size. Nobody cares what you think, so stop posting this nonsense blend of off-topic idiocy and erroneous statements. Go away.

The developers ALWAYS tell people to use CRF because ... why? File size? So what you're suggesting is, CRF can create videos of unpredictable size due to it being... better? Not to put words in your mouth, but that does look like that's what you're implying.

Maybe the reason they suggest CRF is because 2 pass is loosely integrated, meaning it requires more work, which MeGUI seems to have simplified with it's "automated 2-pass" function. Please somebody! Give me the answer!

Straight from the MeWiki (http://mewiki.project357.com/wiki/X264_Settings#crf):
When comparing a CRF encode to a 2pass encode at the same bitrate, the CRF encode will be marginally lower quality. On the other hand, it will have taken significantly less time, because the 'first pass' from a 2pass encode was skipped. On the other other hand, it's impossible to predict the bitrate a CRF encode will come out to (without actually performing the encode or a portion of it). It's up to you to decide which rate-control mode is better for your circumstances.

Oh so this is about semantics? You don't like the way I used the word "always". Maybe I should have phrased it like this:

2-pass has better quality, which therefore makes it better from a "quality" standpoint, but unless you know what the f*ck you're doing, you're better off using CRF. Yes?

Okay then, with that logic, why in gods name is CRF the default mode if MeGUI has simplified the use of multiple passes, therefore making multiple passes accessible to people whom are inexperienced at video encoding and compression techniques?

The answer is simple. The x264 devs are philosophical bastards that try to influence the populous with their "ways".

Or perhaps it's only this new guy with "intelligence or internet savvy" that has brought this upon us? I'm finished trying to guess.

-Neil

[Dark Shikari]

2-pass has better quality, which therefore makes it better from a "quality" standpoint, but if you know what the f*ck you're doing, you're better off using CRF. Yes?The information is wrong. Given the same amount of encoding time, CRF is superior to 2-pass at the same bitrate. Given the same settings rather than the same time, they're effectively identical within margin of error. My recent tests show that CRF generally has a very slight edge, albeit the difference is so small that you'd have to have OCD to care.Okay then, with that logic, why in gods name is CRF the default mode if most people are inexperienced at video encoding and compression techniques?Because the most common questions by inexperienced users is "what bitrate should I use?". It is better to give users what they expect (a consistent quality) than leave them guessing what bitrate to use. This isn't unique to x264: many other open source encoders default to constant quality or constant quantizer mode: Theora, for example. Furthermore, the most popular x264 GUI, Handbrake, also defaults to constant quality mode and has done so for quite some time.

2-pass takes more time and requires the user to specify a bitrate. Anything that requires more input from the user obviously cannot be default, since the default should require minimum possible user input. If bitrate mode is default, it requires more user input, and thus requires users to know more about video compression in order to encode a video. This is bad, as x264 should be as accessible to casual users as possible.The answer is simple. The x264 devs are philosophical bastards that try to influence the populous with their "ways".Or you're just trolling.

[Atavarius]

Do you think they could have done this in a way that doesn't annoy 5000 people?

Really the only annoyed person I have seen is you.

I don't WANT your help. I don't want a user from this forum to come to my rescue and create presets that perfectly suit me. What I "suggested" is a means to create better "default" presets to be downloaded through the auto updater in MeGUI. But seeing as one would have to be somebody of high status and recognition, that would, otherwise, never happen.

This is exactly what you want. You want "better" presets. "Better" as defined by you. MAKE YOUR OWN.

You make no effort to cite examples of why you think I have no idea of what I'm talking about.

I don't need to cite anything, anyone who has read your posts quite clearly sees you make no effort to inform yourself or else by now you could have *GASP* made your own profiles.

Well, this so called person with "intelligence or internet savvy" (I love how you put that word "or" in there) fucked up. It took less than 2 weeks for someone to come to me with questions regarding the new presets, to which I had to tell him to use a different preset than which he was accustomed to. I foresaw the future and I will continue foreseeing it so long as this new person with "intelligence or internet savvy" continues working on MeGUI.

This person you speak of should fess up and fix the presets. Oh, but please don't misconstrue that with demanding.

You know your attitude make me understand why so many open source projects die.

Straight from the MeWiki:
Quote:
When comparing a CRF encode to a 2pass encode at the same bitrate, the CRF encode will be marginally lower quality. On the other hand, it will have taken significantly less time, because the 'first pass' from a 2pass encode was skipped. On the other other hand, it's impossible to predict the bitrate a CRF encode will come out to (without actually performing the encode or a portion of it). It's up to you to decide which rate-control mode is better for your circumstances.
Oh so this is about semantics? You don't like the way I used the word "always". Maybe I should have phrased it like this:

2-pass has better quality, which therefore makes it better from a "quality" standpoint, but unless you know what the f*ck you're doing, you're better off using CRF. Yes?

Okay then, with that logic, why in gods name is CRF the default mode if MeGUI has simplified the use of multiple passes, therefore making multiple passes accessible to people whom are inexperienced at video encoding and compression techniques?

The answer is simple. The x264 devs are philosophical bastards that try to influence the populous with their "ways".

Or perhaps it's only this new guy with "intelligence or internet savvy" that has brought this upon us? I'm finished trying to guess.

-Neil

So you CAN do research! I am shocked, shocked I tell you. Make your own profiles and post them if you think this imaginary issue is affecting so many users.

Now you've been told straight from the x264 development team. So maybe you can stop trolling and actually contribute something? Either way, I am through with you. You make no effort to contribute to this thread but complaining MeGUI development will continue and the only unsatisfied people will be you and your friend.

[Dark Shikari]

Now you've been told straight from the x264 development team. So maybe you can stop trolling and actually contribute something? Either way, I am through with you. You make no effort to contribute to this thread but complaining MeGUI development will continue and the only unsatisfied people will be you and your friend.To be honest, I don't think your attitude is helping the situation here either...

It is important that discussions about technical issues remain technical. If you start attacking each other (this goes for both of you), nothing will get done.

[Neillithan]

The information is wrong. Given the same amount of encoding time, CRF is superior to 2-pass at the same bitrate. Given the same settings rather than the same time, they're effectively identical within margin of error. My recent tests show that CRF generally has a very slight edge, albeit the difference is so small that you'd have to have OCD to care.Because the most common questions by inexperienced users is "what bitrate should I use?". It is better to give users what they expect (a consistent quality) than leave them guessing what bitrate to use. This isn't unique to x264: many other open source encoders default to constant quality or constant quantizer mode: Theora, for example. Furthermore, the most popular x264 GUI, Handbrake, also defaults to constant quality mode and has done so for quite some time.

2-pass takes more time and requires the user to specify a bitrate. Anything that requires more input from the user obviously cannot be default, since the default should require minimum possible user input. If bitrate mode is default, it requires more user input, and thus requires users to know more about video compression in order to encode a video. This is bad, as x264 should be as accessible to casual users as possible.Or you're just trolling.

More user input? A bitrate is already specified when you choose any of the multiple pass modes. You would be a fool to stick with the default bitrate, which (to my knowledge) is 1000. 1000 is far too low to make a decent encode, depending on the source, which lets be honest... more and more videos are in at least 720p res now.

Just because an acceptable quality is chosen for constant quality, doesn't mean it requires any less user input. I think in bitrates, not values between 1 and 64. What the heck is 21 out of 64? Is that like 32%? The average joe schmoe is not going to know what "21 constant quality" represents, nor will they know which number to use.

Your point is moot.

[Dark Shikari]

Just because an acceptable quality is chosen for constant quality, doesn't mean it requires any less user input. I think in bitrates, not values between 1 and 64. What the heck is 21 out of 64? Is that like 32%? The average joe schmoe is not going to know what "21 constant quality" represents, nor will they know which number to use.

Your point is moot.You seem to be implying that most users change the default quality setting. As in the case of Handbrake, the vast majority of users do not. They just want it to work.

You "think in bitrates", but you are not a normal, casual user. An average user does not know what a bitrate is. An average user wants the program to re-encode his file and give a good quality result. This means the program should, without any tweaking whatsoever, always generate a good quality result. For a GUI, this means the user should be able to click "ipod" and click "encode", and get a quality video for his iPod. For a CLI, this means that "x264 input -o output" should generate a good result. If the user has to click anyone else, the program has failed to serve its purpose.

Of course, it is not unreasonable to design a program for advanced users, but if your goal is to serve casual users (which your goal appears to be, by your statements), you should design the program accordingly.

I suggest you stop attacking everyone in this thread, as your attitude is not helping the situation or MeGUI as a project. Declaring everyone else to be wrong does not win you anything other than anger and annoyance: it doesn't make MeGUI better, nor does it convince anyone of your ideas. I have nothing against different opinions, and had you expressed them in a less vicious and obnoxious manner, perhaps I might have been more likely to agree with you.

[Neillithan]

You seem to be implying that most users change the default quality setting. As in the case of Handbrake, the vast majority of users do not. They just want it to work.

You "think in bitrates", but you are not a normal, casual user. An average user does not know what a bitrate is. An average user wants the program to re-encode his file and give a good quality result.

I suggest you stop attacking everyone in this thread, as your attitude is not helping the situation or MeGUI as a project.

Which is why I DO NOT suggest Handbrake!

[Atavarius]

To be honest, I don't think your attitude is helping the situation here either...

It is important that discussions about technical issues remain technical. If you start attacking each other (this goes for both of you), nothing will get done.

Agreed DS, and apologies to all. His tone just really got under my skin.

Neil,

Honestly, I would like to help, and I am sure many in the community here are willing. You've laid out what you want in a profile, so put a few together and post them here. People can go over them and critique and you can distribute them at your leisure. If you want help in building them, then layout to us that devices you are shooting for and what encoding methods (well I guess your preference for 2 pass has been established:p) you want to use.

[Neillithan]

Agreed DS, and apologies to all. His tone just really got under my skin.

Neil,

Honestly, I would like to help, and I am sure many in the community here are willing. You've laid out what you want in a profile, so put a few together and post them here. People can go over them and critique and you can distribute them at your leisure. If you want help in building them, then layout to us that devices you are shooting for and what encoding methods (well I guess your preference for 2 pass has been established:p) you want to use.

I can only tell you what I would like to see for presets. More than a year ago, I would use the Unrestricted presets, which were formerly named simply "x264 2-pass extreme" or something to that nature. In an effort to avoid creating L5.1 AVC videos, I started using the DXVA presets. In the latest update of MeGUI, the DXVA presets have been renamed (or changed) to Unrestricted (DXVA).

I have not yet researched what makes the new DXVA presets "Unrestricted", but in an effort to retain consistency across all platforms, I started using and suggesting the PS3-Xbox360 preset.

Also, to further complicate things, there are new AVCHD presets. I don't know much about AVCHD other than a video encoded and formatted as a Blu Ray structure can be burned to DVDs and played in most Blu Ray players.

Whether or not that makes them incompatible with the Xbox360, or other hardware media streamers, I don't know... but in an effort to choose the least harmless preset, it is becoming annoying to rediscover the presets every 6 months and at the same time, it is a growing concern for me and the people I teach how to use MeGUI. They tend to come back to me with questions regarding the presets, which is already a very annoying topic.

I assumed the DXVA presets were the golden ones that work on anything, but now that they have been renamed to "Unrestricted", I'm not so sure anymore.

So in addition to teaching the fundamentals of bitrates and multiple pass encodings, I have to teach something totally irrelevant like x264 presets.

I consider myself acquainted to video encoding and MeGUI based on a few years of experience with different programs and trial and error. I possess no means to create my own presets, nor do I WANT to, which I have stated more than once now.

-Neil

[Atavarius]

I don't think you're ever going to really get a profile that will work 100% on every decoder out there. Especially since some of the hardware decoders get pretty touchy on what setting can be used.

From a quick glance at the 2-pass DXVA profile, you can simply change the AVC level to whatever level you wish and it will no longer be unrestricted. From there you just need to enter whatever bitrate you calculated and you should be fine. If you want more specific you will have to tailor a profile to your specific decoder.

[Neillithan]

After some experimentation, I can say that Constant Quality has confirmed all of my suspicions.

I used a 21second 1080p 30fps video (No Audio) captured from Unreal Tournament 3, which has lots of motion, so its compressibility should be very difficult.

Using the "Unrestricted (DXVA) Insane" Preset, it created an 82MB file. Average bitrate: 31,000

Using the "Unrestricted (DXVA) Balanced" Preset, it created a 42MB file. Average bitrate: 17,000

Using the "Unrestricted (DXVA) Standard" preset, it created a 35MB file. Average bitrate: 14,000

Each of these files exceeds a 10,000 bitrate, which allow me to explain why this is bad.

Unless your computer meets 1 or more of these 3 requirements, it will have difficulty playing this video.

1. At least a dual core CPU
2. GPU acceleration for video decoding of AVC videos.
3. A super fast software decoder like CoreAVC

Why is this bad? Because by being lazy and using Constant quality, the filesizes are MUCH larger than a 2-pass encoding with a specified bitrate less than 10,000 and they are much more difficult to decode due to the high bitrates.

By imposing Constant Quality on most presets, you are making non tech savvy users to MeGUI create videos that are 1. Much larger than they need to be and 2. Much more CPU intensive to decode, given the source material.

By using 2-pass and learning how bitrate influences filesize and decoding requirements, you leave nothing up to chance. This is the way MeGUI used to work. 2-pass was the default selection.

On top of that, the bitrate calculator can give you a really good idea of what the resulting filesize will be, and it offers to implant the bitrate into your video preset.

To make matters worse, when selecting a preset that defaults to constant quality, if you attempt to use the bitrate calculator to implant a bitrate, rather than select 2-pass as the default mode, it selects ABR, which is something I have never seen MeGUI do!

I cannot begin to express how faulty MeGUI has become.

-Neil

[Dark Shikari]

...CPU intensiveness depends on the maximum bitrate, not the average. If you want to attempt to avoid situations where videos have overly intensive segments, you need to have VBV on by default as well.

This of course will create situations in which some difficult portions of videos need a lot more bitrate than the maximum, will look bad, and people will complain about them.

There's no such thing as a free lunch.

[nurbs]

Why is this bad? Because by being lazy and using Constant quality, the filesizes are MUCH larger than a 2-pass encoding with a specified bitrate less than 10,000 and they are much more difficult to decode due to the high bitrates.

By imposing Constant Quality on most presets, you are making non tech savvy users to MeGUI create videos that are 1. Much larger than they need to be and 2. Much more CPU intensive to decode, given the source material.

You got a high bitrate because it is 1080p video game footage. That's not exactly easy to encode. If you had used another clip the resulting bitrate might have come out as 5 Mbps and then your 10 Mbps clip would be 1. Much larger than it needs to be and 2. Much more CPU intensive to decode, given the source material. I doubt that you can determine the compressibility of the clip just by looking at the source material.

To make matters worse, when selecting a preset that defaults to constant quality, if you attempt to use the bitrate calculator to implant a bitrate, rather than select 2-pass as the default mode, it selects ABR, which is something I have never seen MeGUI do!

I cannot begin to express how faulty MeGUI has become.

You could begin by filing a bug report (http://sourceforge.net/tracker/?group_id=156112&atid=798476), which you haven't bothered doing yet.

It's the same with the profiles. Instead of just complaining you could make your own. Maybe you can post them somewhere on the forum so the people you teach and the 5000 people the situation annoys according to you get something out of it.

[Neillithan]

I created profiles with my limited knowledge. I basically used the DXVA Unrestricted 2-pass preset as a starting point. I changed it from "autoguess" to "High". I created profiles for each individual preset (medium, slow, slower etc...). I named them in a way so that they appear in numerical order in the "Encoder Settings" dropdown menu.

Here they are.

http://www.filefront.com/15571911/Neil%27s%20x264%20dxva%202-pass%20profiles.zip

I understand what the new profiles and preset slider are designed to do. They're designed to simplify the "Encoder Settings" dropdown menu, but that is not ideal in my opinion. The dropdown menu shows an "at a glance" view of the individual profiles". If the "Encoder Settings" dropdown had individual presets for the different speeds, I wouldn't be forced to use the "Config" to adjust the speed or complexity of the profile.

It would be better if there were 2 dropdown menus so that a "basic" set of profiles are selectable using the "Medium" preset as default. The second dropdown menu would allow you to choose a second list of profiles that change the preset to whatever speed you prefer (Medium, slow, slower etc...).

That may complicate things, but if you consider the current way profiles work, it's really bad. If you try to configure a profile to change the preset to whatever speed you want, it bugs you to save the preset. Maybe I don't want to save the preset just so I can choose a different speed, which is why I suggest the "multiple dropdown lists" idea.

Also, as another suggestion, it might be worth it to change some terminology in the GUI. Instead of "presets", why not consider "speed" or "complexity". Speed more closely resembles the naming scheme for "Slow", "Slower"... "Complexity" is more accurate (in my opinion). The word "preset" is too ambiguous. You could also just insert the word "Speed" before the word "Preset": Speed Presets.

-Neil

[Neillithan]

You got a high bitrate because it is 1080p video game footage. That's not exactly easy to encode. If you had used another clip the resulting bitrate might have come out as 5 Mbps and then your 10 Mbps clip would be 1. Much larger than it needs to be and 2. Much more CPU intensive to decode, given the source material. I doubt that you can determine the compressibility of the clip just by looking at the source material.

Yes, I am well aware that the video footage I used was extremely difficult to encode. That's why I used it as an example. Whether it's a high action packed scene of a movie, or a video of Unreal Tournament, the probability of getting an extremely high bitrate outweighs the benefits of using constant quality. I remember watching a video that was created in Vegas that used a film grain effect. More than likely, using Constant Quality on any video that has a manual film grain effect like that would produce a high bitrate video.

The very unsubtle point I'm making is, Constant Quality is not ideal for most situations, whereas 2-pass most certainly is and should be the default method, as it has been for most of MeGUI's existence.

You could begin by filing a bug report (http://sourceforge.net/tracker/?group_id=156112&atid=798476), which you haven't bothered doing yet.

It's the same with the profiles. Instead of just complaining you could make your own. Maybe you can post them somewhere on the forum so the people you teach and the 5000 people the situation annoys according to you get something out of it.

Done.

[nurbs]

I basically used the DXVA Unrestricted 2-pass preset as a starting point. I changed it from "autoguess" to "High". I created profiles for each individual preset (medium, slow, slower etc...).
If you only have medium and slower presets setting the profile to high doesn't change anything, because these presets create high profile output anyway. Even if they didn't why would you want to indicate a higher profile than the stream was encoded at? If you want to ensure higher compatibility to old DXVA hardware and standalone hardware players you should set the level to 4.1 and add the necessary VBV parameters if you haven't done that already.
Instead of "presets", why not consider "speed" or "complexity".
Because the command line parameter is --preset and changing the GUI label to something different would likely be confusing instead of helpful.
Whether it's a high action packed scene of a movie, or a video of Unreal Tournament, the probability of getting an extremely high bitrate outweighs the benefits of using constant quality. I remember watching a video that was created in Vegas that used a film grain effect. More than likely, using Constant Quality on any video that has a manual film grain effect like that would produce a high bitrate video.
Well, yes, getting an extremely high bitrate can be a result of constant quality depending on the source. That's the point of using CRF after all. The video gets as much bitrate as is needs without the user having to worry about it.
If you want a lower bitrate for a grainy video while keeping most of the details your best bet is some avisynth filters (MCTemporalDenoise, MVDegrain, ect.) to get rid of at least part of the grain before encoding. If you are okay with a less accurate representation of the source in general you can encode everything including other clips without grain at a higher CRF value and save some space.
The very non subtle point I'm making is, Constant Quality is not ideal for most situations, whereas 2-pass most certainly is and should be the default method, as it has been for most of MeGUI's existence.
For the average user 2-pass is ideal in exactly one situation, when you have space constraints e.g. a DVD. If you use hardware decoders or you have a slow CPU your best chance is constraining the encode to Profile@Level+VBV and you can do that with CRF as well as 2-pass. At the same time you don't have to do any extra setup. With 2-pass you still have to pick a bitrate. If you have space constraints you have no choice anyway. If you don't you can't really know if you are wasting bits or starving the encode without a compressibility test.

[quantum5uicid3]

we need like a 12 step program for life without the sharktooth profiles or something

[stax76]

The defaults in x264 are very good, StaxRip uses them 1:1, constant quality mode is the default in x264 and in StaxRip it's the default since years even before x264 existed, it's the only mode I use and recommend since years. Thinking 2pass mode is more efficient then constant quality mode is one of the most common misconceptions and because of this StaxRip has a help button right besides the Mode option explaining the difference:

Generally there are two popular encoding modes, quality based and 2pass. 2pass mode allows to specify a bit rate and file size, quality mode doesn't, it works with a rate factor and requires only a single pass. Other terms for quality mode are constant quality or CRF mode in x264.

Slow and dark sources compress better then colorful sources with a lot action so a short, slow and dark movie requires a smaller file size then a long, colorful source with a lot action and movement.

Quality mode works with a rate factor that gives comparable quality regardless of how well a movie compresses so it's not using a constant bit rate but adjusts the bit rate dynamically. So while the same rate factor can be applied to every movie to achieve a constant quality this is not possible with 2pass mode because every movie requires a different bit rate. Quality mode is much easier to use then 2pass mode which requires a longer encoding time due to 2 passes and a compressibility check to be performed to determine a reasonable image and file size which also requires more expertise.

It's a common misconception that 2pass mode is more efficient than quality mode. The only benefit of 2pass mode is hitting a exact file size. Encoding in quality mode using a single pass will result in equal quality compared to a 2pass encode assuming the file size is identical of course.

Quality mode is ideal for hard drive storage and 2pass mode is ideal for size restricted mediums like CD's and DVD's. If you are still not sure which mode to use then it's probably better to use quality mode.

So yes, of course it's true that 2pass requires more effort and experience.

Users should really not rely on profiles made by a GUI but try to understand x264 directly and build their own profiles. Since presets and tunings were introduced there aren't many excuses any longer that this is difficult, maybe because of devices but devices can be integrated in the GUI in a similar way presets and tunings are integrated in x264, that is much better than having device options only in profiles, also devices will be integrated in x264 since ease of use is a primary design goal for x264.

MeGUI is designed for experienced users and don't take care of newbies, this has been stated by various MeGUI developers in the past, this causes newbies a lot of problems, instead of complaining they either need to learn or use a application designed for them.

[quantum5uicid3]

i guess ill add:

as ive said before

maybe im wrong, but im yet to be corrected, dxva in itself is not restricted. specific decoders, maybe all atis still?, and older nvidia video cards have limitations @4.1. a $80 low profile 9600gt and mpc-hc does not. --level 4.1 should be sufficient if unrestricted is cause u problems. ( it is on my 8400gs) ive asked for the current state of dxva from the ati side of the fence but never heard anything. basically my view was that the 9600gt's are pretty shitty at this point in the world of video. if they can handle it, then i think it would be silly to keep encoding vids to conform to programmer's laziness and a decision to do so would be more specific then a general rule.

im the douchebag(heh) that made the presets stepping on the shoulders of sharktooth, kurtnoise, the x264 dev peeps, and all the other smart people here in about 10minutes using kurtnoise's device settings spreadsheet specifically. i never asked for any credit for them or deemed them as a seamless transition from sharktooth's. im far from an expert compared to others around here and realize they are far from perfect and others are encouraged to recreate them or make specific suggested fixes(adding "speed" in front of preset probably isn't going to happen though)(i think "slow" and "fast" etc. denote speed in the presets clearly enough) :)

the only documentation i wrote and will write:

the megui profiles now are just device settings. i chose imho a logical constant quality crf range going from 17-23 in increments of 1.5 and a 2pass. users must change --preset(amount of time dedicated to encode) and --tune(type of source) to their needs still. with the maturity of crf 2pass is only needed to hit a certain file size. certain options ensuring device compatibility are forced in the "custom commandline" field. this prevents user error and allows the preset to be changed while maintaining required options.

[Neillithan]

@nurbs

It does seem like a good idea to limit the profile and VBV if there are hardware constraints. The new presets in MeGUI default to the Medium preset mode, unless the preset is for a specific device... which is good because Medium doesn't create too complex of an encode for the non tech savvy user.

However, some people might be tempted to choose some of the slower presets, which most of the time will botch things from device compatibility and computer performance point of view. Choosing the "placebo" preset will most of the time create an L5.1 video unless you manually specify the Level and restrict the profile to High. Also, I'm well aware the Placebo preset is not going to do much compared to the slower preset. For instances like that, it would be more beneficial to use a profile (especially for the DXVA profiles) that restrict those couple of things.

To top it off, it would be interesting to have an intelligent VBV now that CRF is deemed the new default in MeGUI. Rather than leave the VBV at "0", perhaps there could be an option in MeGUI that automatically determines the VBV based on the source material. I've seen videos that have an average bitrate of 10,000 but have a peak bitrate of 70,000. That should never happen, no matter how short the segment in the video is. That is less likely to happen in a 2-pass encode even without VBV manually specified, which is why I suggest it. Now that I am aware of VBV, I will be using it a lot more. Obviously if my target bitrate is 10,000, I will want to specify a VBV between 20,000 to 30,000, right? It all depends what the user chooses for the bitrate.

@quantum5uicid3,
yes, the 4.1 restriction of older video cards has a lot to do with why I think the DXVA profiles should be restricted, or at the very least, offer a second set of Restricted DXVA profiles to avoid that issue. Not to mention, (to my knowledge) all hardware decoders like the PS3, Xbox 360, popcorn hour (you name it) do not support L5.0 or L5.1. As stated by Dark Shikari in past threads, they can't due to physical limitations. Even if you don't intend to watch your video on a hardware media streamer, that doesn't mean you should encourage the bad practice of creating Ultra high level videos. They only serve to pollute. I'm always downloading videos from Quakeunity.com and own-age.com in the MP4 or MKV container to find that the user created an L5.1 video. That probably was his own fault for not understanding the inner workings of AVC, but the blame can't be placed entirely on him, agreed?

It seems clear to me that you guys are going to stick with CRF, even though 2-pass has been commonplace in MeGUI for years now... I'm beating a dead horse at this point. The least you can do is take my suggestions under consideration and offer a set of profiles that work on a variety of devices, that do not break compatibility if you choose a preset higher than medium.

Thanks,
-Neil

[nurbs]

I've seen videos that have an average bitrate of 10,000 but have a peak bitrate of 70,000. That should never happen, no matter how short the segment in the video is. That is less likely to happen in a 2-pass encode even without VBV manually specified, which is why I suggest it. Now that I am aware of VBV, I will be using it a lot more. Obviously if my target bitrate is 10,000, I will want to specify a VBV between 20,000 to 30,000, right? It all depends what the user chooses for the bitrate.
VBV parameters don't depend on your target bitrate, they depend on the playback device. VBV maxrate is a function of profile and level that is supported, e.g. hp@4.1 has a maxrate of 62500 kb/s. x264 can't do anything unless both maxrate and buffer size are specified. The buffer size depends on the playback device. As a rule of thump people generally select the same buffer size as the maximum bitrate. One should probably keep in mind that blu-ray uses maxrate and bufsize that is lower than hp@4.1 if that is the target. It would be interesting to know if that matters for hardware compatibility, but I wouldn't think so.
Your 10 Mb/s average 70 Mb/s maximum scenario could still happen with hp@4.1 and blu-ray encodes (if I remember the blu-ray numbers correctly).
Furthermore 2-pass and CRF should have almost the same bitrate distribution given the same average bitrate so I doubt the peak would be much lower.

Not to mention, (to my knowledge) all hardware decoders like the PS3, Xbox 360, popcorn hour (you name it) do not support L5.0 or L5.1.
Actually it is sometimes 4.1 with more reference frames allowed. My 80€ WD TV (http://www.wdc.com/de/products/wdtv/) can allegedly decode 1080p with 16 refs and I guess it's not the only device using that particular decoder chip. I love that player. Handles vobsubs in 720p mkv perfectly Personally my encodes top out at hp@3.1 so I never really tested the limits.

In principle I agree that there should be a hardware profile that is limited to hp@4.1 for maximum compatibility. (If there isn't already. I don't know since I don't use the profiles.)

[HeadlessCow]

ive asked for the current state of dxva from the ati side of the fence but never heard anything.

ATI (at least the 3450 and 4670 I have) limits DXVA decodes to level 4.1. (might not care about the VBV settings, I never encode high enough bitrate for them to matter).

[Lyle_JP]

An excerpt from a conversation I had with a friend regarding MeGUI.

Was there a reason for this post other than to act like a dick? If you don't like MeGUI's direction you're certainly free to write your own GUI and post it here. That actually might be a useful post.

[rudiev]

I updated to megui 0.3.3 and ran an megui update. But when I want to encode to x264 it uses vfw4x264.exe, and this doesn't work with my profile. How can I use the x264.exe which I used before with the old megui? I can't find it in the settings.

[rudiev]

I updated to megui 0.3.3 and ran an megui update. But when I want to encode to x264 it uses vfw4x264.exe, and this doesn't work with my profile. How can I use the x264.exe which I used before with the old megui? I can't find it in the settings.

I updated the x264.exe from x264.nl, now version 1442, but it generated an error in megui, could not create process or something. Now I renamed the vfw4x264.exe to #vfw4x264.exe.org and renamed the x264.exe to vfw4x264.exe and it works all fine now.
Why does megui uses vfw4x264.exe? It's a small program so I think it calls x264.exe to do the encoding, but with the new x264.exe it doesn't work.

[Zathor]

I updated the x264.exe from x264.nl, now version 1442, but it generated an error in megui, could not create process or something. Now I renamed the vfw4x264.exe to #vfw4x264.exe.org and renamed the x264.exe to vfw4x264.exe and it works all fine now.
Why does megui uses vfw4x264.exe? It's a small program so I think it calls x264.exe to do the encoding, but with the new x264.exe it doesn't work.

Please post the error log and your system details. vfw4x264 is used as a wrapper for x64 x264.

[rudiev]

Please post the error log and your system details. vfw4x264 is used as a wrapper for x64 x264.

Strange, now it is working. also updated x264_64.exe with the latest one from x264.nl, now version 1416 for 64 bit.

The error log is:

[Warning] Log
-[Information] Versions
--[NoImage] MeGUI Version : 0.3.3.0
--[NoImage] OS : Windows Seven x64 (6.1.0.7600)
--[NoImage] Latest .Net Framework installed : 3.5 SP1 (3.5.30729.4926)
--[NoImage] Avisynth Version : 2.6.0.1
-[Information] Log for job1 (video, loadm2ts.avs -> )
--[Information] [18-2-2010 13:09:36] Started handling job
--[Information] [18-2-2010 13:09:36] Preprocessing
--[NoImage] Job commandline: "C:\Program Files (x86)\MeGUI\tools\x264\vfw4x264.exe" --profile high --level 4.1 --preset slow --tune film --pass 1 --bitrate 14400 --stats "G:\src\Heat.1995.BluRay.1080p.DTS.Remuxed.dxva-KNiCKER.stats" --slow-firstpass --thread-input --ref 8 --vbv-bufsize 50000 --vbv-maxrate 50000 --rc-lookahead 60 --subme 9 --partitions all --trellis 2 --no-dct-decimate --sar 1:1 --output NUL "G:\src\loadm2ts.avs"
--[Information] [18-2-2010 13:09:36] Encoding started
--[NoImage] Standard output stream
--[NoImage] Standard error stream: Error: Failed to create process <2>!
--[Information] [18-2-2010 13:09:37] Job completed
-[Warning] Log for job1 (video, loadm2ts.avs -> )

But now it's working, vfw4x264.exe is using the x264_64.exe. Maybe i gonna test how much the difference is using the 32 bit or 64 bit of x264.exe. Does someone maybe have some reference movie file to test?

[rudiev]

Ok, here the results of a little testing. I found a .m2ts file on an bluray. Here's the MediaInfo information:



General
ID : 0
Complete name : G:\src\00015.m2ts
Format : BDAV
Format/Info : Blu-ray Video
File size : 453 MiB
Duration : 5mn 50s
Overall bit rate : 10.8 Mbps
Maximum Overall bit rate : 48.0 Mbps

Video
ID : 4113 (0x1011)
Menu ID : 1 (0x1)
Format : VC-1
Format profile : AP@L3
Duration : 5mn 50s
Bit rate : 9 051 Kbps
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate : 23.976 fps
Resolution : 8 bits
Colorimetry : 4:2:0
Scan type : Progressive
Bits/(Pixel*Frame) : 0.182
Stream size : 378 MiB (83%)

...

There were also three AC-3 audio codings and two subtitle stream, but I left those out of the MediaInfo because it has not value.


Used version x264.exe , downloaded from x264.nl
32 bit: x264 core:85 r1442 781d300
64 bit: x264 core:84 r1416 fcf70c2

Computer
Intel Quadcore Q9450 2,66GHz @ 3,2GHz
8 GB RAM
Using cpu capabilities: MMX2 SSE2Fast SSSE3 FastShuffle SSE4.1 Cache64
MeGUI Version : 0.3.3.0
OS : Windows Seven x64 (6.1.0.7600) (Windows 2008 R2)
Latest .Net Framework installed : 3.5 SP1 (3.5.30729.4926)
Avisynth Version : 2.6.0.1


Command lines

--[NoImage] Job commandline: "C:\Program Files (x86)\MeGUI\tools\x264\vfw4x264.exe" --profile high --level 4.1 --preset slow --tune film --pass 1 --bitrate 14400 --stats "G:\src\test_xx-bit.stats" --slow-firstpass --thread-input --ref 4 --vbv-maxrate 50000 --sar 1:1 --output NUL "G:\src\test.avs"

--[NoImage] Job commandline: "C:\Program Files (x86)\MeGUI\tools\x264\vfw4x264.exe" --profile high --level 4.1 --preset slow --tune film --pass 2 --bitrate 14400 --stats "G:\src\test_xx-bit.stats" --thread-input --ref 4 --vbv-maxrate 50000 --sar 1:1 --output "G:\src\test_xx-bit.mkv" "G:\src\test.avs"



Encoding megui 0.3.3 with vfw4x264.exe using x264_64.exe

Time FPS
Job1 7:28 18,68 FPS
Job2 5:19 26,28 FPS



Encoding megui 0.3.3 with x264.exe 32 bit (renamed it to vfw4x264.exe)

Time FPS
Job1 7:46 18,01 FPS
Job2 5:37 24,97 FPS


Conclusion
There are little difference in encoding time using the 32 bit or 64 bit version of x264.exe. Job1 is 3,9% faster with 64 bit compare to 32 bit. Job2 is 5,3% faster with 64 bit compare to 32 bit.
The 64 bit could go even faster because the vfw4x264.exe process is consuming a little CPU power

[karasu]

Hello,

I'm trying to recompress a 4Go MKV using Megui. Here's my avs file :

DirectShowSource("H:\Movie.mkv", fps=23.976, audio=false, convertfps=true)

mergechroma(blur(1.3)) # Little Noise

loadplugin("C:\Program Files\AviSynth 2.5\plugins\FFT3DFilter\fft3dfilter.dll")
FFT3DFilter(bt=-1, sharpen=1.2)



In Megui, I load my avs file, the preview windows pops up and show me a proper frame of the movie.
I set up my x264 settings and enqueue it.
I have an error when I launch the encoding :

[Error] An error occurred: avs [error]: DirectShowSource: couldn't create filter graph:
[Error] An error occurred: x264 [error]: could not open input file `H:\Movie.avs'

I can play my avs file in MPC.

Can you help me?

[TheProfosist]

was wondering where i can request features since that thread is closed. i would like to request FLAC encoding support and save frames to file or to clipboard in the preview window

[Inspector.Gadget]

I'm trying to recompress a 4Go MKV using Megui.

What is a "4Go MKV", what's in it, and how did you make it?

[Zathor]

was wondering where i can request features since that thread is closed. i would like to request FLAC encoding support and save frames to file or to clipboard in the preview window

You can request new features here:
http://sourceforge.net/tracker/?group_id=156112&atid=798479

Flac support is already on the list.

[karasu]

What is a "4Go MKV", what's in it, and how did you make it?

AVC1 1280x544 and AC3 audio

[Inspector.Gadget]

OK, but that still doesn't tell us the sort of details relevant to figuring out why DSS isn't working. What program did you use to make the MKV container? What was the writing library? What did you use to encode the AVC stream and did you use any exotic options? Etc. My initial suspicion is that you don't have a system-wide (versus internal to MPC) DirectShow matroska splitter and/or H.264 decoder, but if that proves incorrect, then it's down to something weird with the file itself.

[karasu]

MPC uses ffdshow libavcodec (cccp) with Haali Media Spliter. I did not create the source file.

I didnt understand why Megui is capable to show me the preview windows of my avs but crashes when starting the actual encoding process.
Megui work great when I rip my own dvds with d2v project files.

I have remuxed the mkv file with MMG v2.9.9 but always the same error.

[Inspector.Gadget]

I did not create the source file.

Sorry, you're on your own, per the forum rules (http://forum.doom9.org/forum-rules.htm). If you'd like to clarify the origin of the material with a mod via private message and the mod clears it, then we can discuss the file.

[xxxomxxx]

hi all

how can i force MeGui to use more CPU - while encoding mine is running at 40% CPU & RAM?

thanks

[karasu]

how can i force MeGui to use more CPU - while encoding mine is running at 40% CPU & RAM?

can you paste here your avs file? (I suspect a non-multithreaded filter)

[karasu]

I have tried with a MKV file encoded myself (with megui) from a DVD I have bought. with the same avs file (with corrected filepath of course).
The avs file is playable in MPC with Haali Media Splitter and FFDSHOW.

Megui display properly the preview window when I load the avs file.

But I always get the same error when starting the queue.

Megui is up to date.

[Robertus]

with 0.3.4.0 when i open bitrate calculator and i set a size, when i close and reopen bitrate calculator , the size disappears... why!?

old version didn't have this problem... someone have a solution?

[Ruriko]

When I try to load any video in the AVS script creator megui just closes. Megui was working fine for the past 3months and now this happens!

[ZEXEL]

need function for next release MegUI:
# auto-delete .AVS + source file
hope it can be reality... :thanks:

[blubberbirne]

need function for next release MegUI:
# auto-delete .AVS + source file
hope it can be reality... :thanks:

hm, and what happens when your outfile is crap?

[ZEXEL]

hm, and what happens when your outfile is crap?
let it be...

[Floatingshed]

Can anyone please help. My XVID encodes will only play on a standalone player for 6 seconds if encoded with MeGUI (XVID Encraw) but they are fine using Virtualdub and XVID with the same settings! I've tried them on a friend's, entirely different player too, same result.
Does that ring any bells with anyone, please?

[handsomejack]

with 0.3.4.12 when i was encoding it showed error
Runtime error!
Program: C:\Program files\megui\tools\x264\x264.exe
abnormal program termination
I used 0.3.4.0,too; but no use. but when i use 0.3.1.1053, it's ok.

PS: Sorry for my bad english :p

[LigH]

@ Floatingshed:

Might be possible that the tools used by MeGUI (ffmpeg / mencoder) don't create optimal AVI containers (which might lack of some indexing), which could be fixed by remultiplexing them using e.g. AviMux-GUI or VirtualDub.

But without a detailed technical analysis it is impossible to answer your question - you did not even mention your used container (I can only guess it's AVI because most SAP won't be able to play anything else, and VirtualDub doesn't create anything else either).
__

@ handsomejack:

Different MeGUI versions might use different x264 revisions - which may require different command line options.

Furthermore you did not mention any system details, e.g. if you have a 64-bit Windows.
__

Details, details, details. ;)

[Ryu77]

I have noticed something strange as of recent...

I can not seem to change my x264 log file name or location through MeGUI anymore. When I click on the little button next to the log file absolutely nothing happens (MeGUI/Config/Misc/). The strange this is, if I press the button below the log file for the qp file, this seems to work fine.

Has anyone else experienced this? Is there a fix for it?

[unknownsoldierX]

What is the proper way to select audio input? Say if my source is an AVI with xvid and mp3. I use the script creator. Then, under audio input, I select the AVI. The resulting file does not have audio.

Do I have to demux a file before using MeGUI?

[quantum5uicid3]

@floatingshed

megui uses the most recent squid_80 build of xvid_encraw.exe for mkv output and xvidcore.dll 1.2.2. there arent known issues with the squid_80 build, but try using a more recent build. even downloading the 1.2.2 from this site will have an updated xvid_rawenc.exe. you will lose mkv output though.

http://www.xvidvideo.ru/xvid-video-codec/

edit: i guess it could be a problem with avimuxgui v1.17.8.3 too

@handsomejack
plz let autoupdate update everything unless you know what your doing.

@Ryu77
looks like a bug to me

@unknownsoldierX
yes megui can transcode the audio directly from a container. it sounds like your missing the steps of enqueuing and running the audio job seperately and muxing the newly created files together

[simonrule]

can any one give me tutorials in how can make high quality small size

[unknownsoldierX]

@unknownsoldierX
yes megui can transcode the audio directly from a container. it sounds like your missing the steps of enqueuing and running the audio job seperately and muxing the newly created files together

I must have. I got it to work by using auto encode. How would I manually add demux to the queue?

Also, I'm converting an MP4 with AVC/AAC to an xvid/mp3 AVI. The video is 40min. long and the preprocessing took 17min. What was it doing for that time?

[Inspector.Gadget]

can any one give me tutorials in how can make high quality small size

x264 --crf 18. Please make more of an effort to write in standard English and define your question precisely: both "high quality" and "small size" are totally subjective.

[unknownsoldierX]

I just converted an MP4 with AAC audio to AVI, and the resulting file does not have audio. I'm running Win7 32bit.

[Adub]

How did you convert it? We need a LOT more information before we can help you.

simonrule: This is kind of a loaded question. In short, use a high quality X264 profile with a low bitrate.

[unknownsoldierX]

Loaded the MP4 into the AVS creator and saved the AVS without making any changes. Loaded the MP4 as the audio input. Selected 'Xvid Const. Quantiser 2 Fast', and 'LAME MP3 128ABR'. Hit AutoEncode. Changed container to AVI. Hit queue.

Checked that the queue had audio, video, and mux jobs. Hit start.

[Havokdan]

Sorry, delete the post for me

[Zathor]

I can not seem to change my x264 log file name or location through MeGUI anymore. When I click on the little button next to the log file absolutely nothing happens (MeGUI/Config/Misc/).

Thanks, fixed in 0.3.4.13

[handsomejack]

@ Floatingshed:

Might be possible that the tools used by MeGUI (ffmpeg / mencoder) don't create optimal AVI containers (which might lack of some indexing), which could be fixed by remultiplexing them using e.g. AviMux-GUI or VirtualDub.

But without a detailed technical analysis it is impossible to answer your question - you did not even mention your used container (I can only guess it's AVI because most SAP won't be able to play anything else, and VirtualDub doesn't create anything else either).
__

@ handsomejack:

Different MeGUI versions might use different x264 revisions - which may require different command line options.

Furthermore you did not mention any system details, e.g. if you have a 64-bit Windows.
__

Details, details, details. ;)

oh, my bad :p . I 'm using XP SP3 32bit. So what x264 revision i should use because i used auto update in megui and it updated for me.

[Floatingshed]

@ Floatingshed:

Might be possible that the tools used by MeGUI (ffmpeg / mencoder) don't create optimal AVI containers (which might lack of some indexing), which could be fixed by remultiplexing them using e.g. AviMux-GUI or VirtualDub.

But without a detailed technical analysis it is impossible to answer your question - you did not even mention your used container (I can only guess it's AVI because most SAP won't be able to play anything else, and VirtualDub doesn't create anything else either).




Hi, Thanks for you input. Sorry I've been so long replying, been travelling.

I've done a bit more work on this and discovered that the problem is not encraw but the muxing. If I mux in Vdub all is well, if I mux in megui I'm back to the standalone player stopping after 6 seconds. Clearly the avimux_gui settings can be altered in the config.ini.amg file but I don't know where to start.

Any more help would be greatly appreciated. Thanks.

[Floatingshed]

I've been playing...
It turns out that avimux_gui is set to make opendml files and that is what the standalone doesn't like. I have changed that setting and all is now well, I think.
Have I done something silly? Is opendml necessary for anything other than files over 2Gb?
Thanks.

[Whiznot]

I tried to use MeGUI to convert a WMV file and discovered that the format was not supported. Is there a way to convert WMV files with MeGUI?

[Taurus]

@Whiznot
What kind of wmv file 7/8/9 VC1......?:confused:
Just import it to the AVS Script Creator,
and if there is any directshow decoder for your file available, it should just be doing fine.

[Whiznot]

Thanks for the reply Taurus. MediaInfo reports the video stream as VC-1 (WMV3). I am new to MeGUI and so far the app has been confusing. I will play around with it some more and try to import it into the script creator. I would be grateful if you could point me to a good tutorial

EDIT: Well, I stumbled into learning how to encode my file with my chosen settings. MeGUI lets me easily maintain the proper aspect ratio while converting to the highest resolution supported by my DIVX capable Philips DVP5990.

[alexVS]

Hi all!
My Megui version is 0.3.4.0
I have some hitches in my work with megui (x264 encoding)

First, I can't update x264.exe (32bit) with megui updater, so I got to download it manually from x264.nl web site.
The previous version was x264 core:80 r1376M (1 147 392 bytes)
The new version is x264 core:93 r1542 (6 373 376 bytes)
Have I done it allright? (I have some doubt about file sizes and compatibility with megui)

Second, I encode the file with "Numbers of B-frames: 3", "Number of reference frames: 3". But Mediainfo shows
Format settings, ReFrames : 4 frames
Why?

Writing library : x264 core 93 r1542 5b86182
Encoding settings : cabac=1 / ref=3 / deblock=1:-1:-1 / analyse=0x3:0x113 / me=hex / subme=7 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=1 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-2 / threads=3 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / constrained_intra=0 / bframes=3 / b_pyramid=2 / b_adapt=1 / b_bias=0 / direct=1 / wpredb=1 / wpredp=2 / keyint=250 / keyint_min=25 / scenecut=40 / intra_refresh=0 / rc_lookahead=40 / rc=abr / mbtree=1 / bitrate=3500 / ratetol=1.0 / qcomp=0.60 / qpmin=10 / qpmax=51 / qpstep=4 / ip_ratio=1.40 / aq=1:1.00 / cabac=1 / ref=3 / deblock=1:-1:-1 / analyse=0x3:0x113 / me=hex / subme=7 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=1 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-2 / threads=3 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / constrained_intra=0 / bframes=3 / b_pyramid=2 / b_adapt=1 / b_bias=0 / direct=1 / wpredb=1 / wpredp=2 / keyint=250 / keyint_min=25 / scenecut=40 / intra_refresh=0 / rc_lookahead=40 / rc=abr / mbtree=1 / bitrate=3500 / ratetol=1.0 / qcomp=0.60 / qpmin=10 / qpmax=51 / qpstep=4 / ip_ratio=1.40 / aq=1:1.00

And the last thing: I encode my hockey game using DXVA (unrestricted HQ profile) 1280x720@50p
Mediainfo show the result Format profile as High@L3.2
I heard somewhere, that most of standalone players (I don't have such player right now) require L4.1. Should I set level as 4.1 before encoding, or L3.2 should be playable as well?

:thanks:

[dje33]

Hi
I have a litte probleme when i want to encode H264/ACC to Xvid/MP3
I have Windows seven 64bits

I have no probleme to encode H264 to Xvid

But when i encode AAC to MP3 i have an error

http://hfr-rehost.net/http://self/pic/a9b571558c431390c5d49d838fafa5aa78560502.png

How can i fix this ?
I try to install CoreACC filter but i have the same probleme.

[tebasuna51]

...
I have Windows seven 64bits
But when i encode AAC to MP3 i have an error

How can i fix this ?
I try to install CoreACC filter but i have the same probleme.

Try open the .aac file with Graphedit to see the filters than your DirectShow system uses to open aac files.

Or use BeHappy and BassAudioSource method to recode aac.

[dje33]

Try open the .aac file with Graphedit to see the filters than your DirectShow system uses to open aac files.

Or use BeHappy and BassAudioSource method to recode aac.

Graphedit can't render the file :(

i don't understand because i can play the file in windows media player and in media player classic.

[doc_dvxm]

Graphedit can't render the file :(

i don't understand because i can play the file in windows media player and in media player classic.


I am using meGUI on 32 Bit Win 7 OS. A few days a go I have a same problems like you. The problem was resolved with installing the latest K Lite Mega Codec (vers 6.00) (and of'coz running codec tweak tool).

Sorry, if I'm hijacking the thread.

Cheerz.

[Marc05]

When I try to load a file in AVS Script Creator, I get an error saying "unable to render file". I have the latest x86/x64 ffdshow and avisynth installed so I'm not sure what's wrong. However, I can still load an avs script from the main MeGUI window and queue it. Anyone have any ideas?
Also, the 32bit version works fine, it's the 64 bit that gives me the problem.

[Zathor]

When I try to load a file in AVS Script Creator, I get an error saying "unable to render file".

Which kind of file are you talking about?

[handsomejack]

hi, after update, my megui have problem like this

http://www.mediafire.com/imgbnc.php/63c8db5cb4e399f42886273411f398346g.jpg

i did many ways to solve this problem like: update MVC++, update x264, update k-lite mega codec,... but no use. However, when i downgrade megui to 3.1.1052, it 's normal.
Ah, i 'm using Win Xp Sp3
PS: sorry for my bad english

[Zathor]

It seems that the screenshot is missing.

[handsomejack]

what is missing? :confused:

[Zathor]

Now it's there. At the time of my posting there has been no screenshot in your posting.

x264.exe is crashing. You can try other builds of x264 (at the end of this thread: http://forum.doom9.org/showthread.php?t=130364) and you should try to run the x264 command line found in your log in the command window directly without megui. If it still crashs MeGUI is not the problem.

[handsomejack]

i copy this (http://forum.doom9.org/showpost.php?p=1408799&postcount=3258) into C:\Program Files\MeGUI\tools\x264 but it 's just error. And i don't know how to use the command line :confused:

[OneWhoSink]

Hi.
I dunno if you guys still updating the proogram's ver.
But, i'll show you the prob, maybe its just me:
Running:
OS: Windows 7 32Bit (Language: [Dunno if it matters] Hebrew).
Memory: 2GB RAM.
Processor: Q6600 @ 2.40GHz.
Graphics Card: HD4890.
^Just gave you anything i thought might affect the encoding process (if there's something missing, ask).

Ok, so the main problem is that when i add the Script.avs to Program [Either by drag&drop or by using the program's box], It immediately crash with no error or anything, unless you consider this: http://img37.imageshack.us/img37/9799/89114674.jpg
[yes, it's hebrew, but ithe conclusion means the problem is some "Error Module: i263_32.drv_unloaded" file]
as an error.

So, if you know the problem by looking at it, it'd be cool, and if not, it'll be nice if you could make the next ver. work with Windows 7.

Thanks in advance, OWS.

[Zathor]

Are there any special (=Hebrew) signs in the path of your avs script? Try to save it for example in the root of one drive.

And Windows 7 is supported since ever (or at least a very long time). 0.3.5 will very likely released today but do not expect that this will solve your problem.

[OneWhoSink]

No, there's nothing "hebrewish" there except an ".ass" file i told the program to open like this:
LoadPlugin("D:\......................\VSFilter.dll")
TextSub("E:\........................\Hebrew.ass")
TextSub("E:\........................\Kanji.ass")
TextSub("E:\........................\Romaji.ass")
[^Which now tells you the purpose of the encoding]
"Try to save it for example in the root of one drive"
what do you mean? i dont get to use the program, it crashs O_O", there's no file to save..

Thanks again, OWS.

[Zathor]

Are you able to open the avs file with other programs (e.g. like VirtualDub)?

[Bi11]

As I understand it, MeGUI had x264 presets, which really consisted of x264 speed/quality tradeoff settings, like Fast/Low and Slow/HQ. Once a preset was chosen, the user would set a bitrate to meet their quality/size tradeoff.
Thus, you had to juggle between two overlapping tradeoffs.

Now, x264 has built-in speed presents, which are "independent" of the quality of the output if CRF (i.e. "quality") is constant.
So now there is no tradeoff between speed and quality! :eek:
However, the tradeoff between quality/size still remains, but now the final size is hard to guess.
The old MeGUI presets could be emulated by using the built-in speed presets and 2-pass to specify a size/bitrate, but now the speed/quality tradeoff presents itself again.
Thus, once the final size/bitrate is predetermined, then CRF is as useless and as different from size/bitrate as a Formula 1 is to a Rolls-Royce.

So it seems there is actually a speed/quality/size tradeoff (i.e. decision) to make every time you do an encode.
Strict "speed" choices are determined by x264 presets and strict "size" choices are determined by bitrate.
2-pass reduces the "quality" choices to speed/quailty tradeoff, i.e. preset & bitrate decision.
CRF reduces the "quality" choices to quality/size tradeoff, i.e. CRF alone (speed is now "independent" of quality); the final bitrate is determined by the complexity of the source video being encoded, the final size is determined by both bitrate and length of video i.e. size = bitrate*duration.

[Zathor]

Selecting a target file size anywhere will result in a 2 or 3pass encode using the selected profile (without the encoding mode of couse).

You can follow up the profile discussion here (please post your answer there):
http://forum.doom9.org/showthread.php?t=154334

[OneWhoSink]

yes, i am able to open it using VirtualDub\Windows Media Player or any other program except Media Player Classic =o

Which just makes everything weirder @_@

OWS.

[BLKMGK]

Recently I updated meGUI via the autoupdate. Now none of my existing profiles are working and I cannot tell which are new and which aren't. I see errors in my logs like this -> [Error] An error occurred: x264 [error]: invalid argument: nal-hrd = --b-pyramid

Since x.264 updated I suspect options for the commandline have changed. I'd like to purge the old presets and try to get something sane working so I can sort which of the new presets suit me. I need to encode TV shows at SD quality from HD recordings but high bitrate with a size target and BD at as high a quality as I can stand. In the past I've managed to do this without much trouble but now I cannot tell what presets are good and which aren't. :eek: Multiple time consuming failures and I'm stuck.

I found what appeared to be presets in the allprofiles sub directory and moved them along with the associated xml file there. I forced a reinstall and import of the profiles. Nothing appeared in this directory and I still have the old profiles. Doing a text search in the directory for strings I see in the profile name brings back nothing but the files I backed up :rolleyes:

Fairly frustrated here, do I need to simply wipe out my install and start over? :mad: I've been running meGUI for a good long time, there could be leftover files from past updates? :confused:

[Zathor]

The x264 profiles are stored in allprofiles\x264. In order to edit them outside of MeGUI or see changes you have done in MeGUI you have to close MeGUI (changes from within MeGUI will only be written there while closing).
The nal-hrd syntax has changed. Replace every --nal-hrd with --nal-hrd vbr.

[BLKMGK]

The x264 profiles are stored in allprofiles\x264. In order to edit them outside of MeGUI or see changes you have done in MeGUI you have to close MeGUI (changes from within MeGUI will only be written there while closing).
The nal-hrd syntax has changed. Replace every --nal-hrd with --nal-hrd vbr.

Ah, thank you! Closing and reopening meGUI does seem to have solved the issue. I got an error closing it telling me that al profiles wasn't empty but I was able to close. When I looked back in there all of the new profiles were there with a timestamp equal to when I'd recycled meGUI - and my backup directory was gone too. (lol)

Reopening meGUI I still see the old profiles though so I guess all was not lost! I better understand what it's doing though and I think I will be able to fix things up - thank you!

[kartman_canada]

I've searched around and not really been able to find an answer so I'm going to pose my question here.

I have been using the '"x264: Bluray - 2pass" preset for a while now. My build of x264 is 1649. Not too long ago (after an update of x264) my preset started causing x264 to error out due to the "--nal-hrd" option. There is no nal-hrd value in the command line generated by the preset which I assumed meant that it was to just use the default.

My guess is that the more recent builds of x264 require a nal-hrd option be explicitly set (no assumed default). Is this correct?

I'm encoding my DVDs/HD-DVDs/BDs for playback on my PS3 and HTPC. Anyways, I guess I need the following:
1) what exactly does --nal-hrd do? I read the x264 page but the info there is not general enough for me.
2) do I need it?
3) if I need it, what was the default in older x264 builds if --nal-hrd was on the command line but no option was explicitly set?

With the answers above, I'm going to modify my profile to correct the issue. I realize this is really an x264 question but the profile is part of MeGUI. Is my profile out of date or unsupported?

many thanx.

[Inspector.Gadget]

--nal-hrd vbr, according to zathor in the other thread.

[kartman_canada]

--nal-hrd vbr, according to zathor in the other thread.

Many thanx... sorry, "other thread"... I assumed I wasn't alone with this issue but didn't find the thread you mention when searching... must have been using the wrong keywords.

[B.F.]

I had a little problem with MeGui.
If the application crash (buggy avisynth filters mostly), no matter how many time and jobs have passed, it saves nothing but job list.
No encoding profile changes, no logs, no MeGUI settings changes.

[Guest]

Don't use buggy Avisynth filters.

[B.F.]

Sometimes it the only one can do the job.
Btw DGMultiDecodeNV is one of them.

[Guest]

Do you have any bug reports to direct me to?

[Inspector.Gadget]

DGMultiDecodeNV is very stable. Older builds of meGUI didn't interface with it properly (hence the "Use CUVIDServer" option in MeGui), but I've had no issues in a LONG time.

[B.F.]

Do you have any bug reports to direct me to?
For what?
Don't really interested in hardware decoding, since it depends on the hardware and drivers sability. And version with software decoding is dropped.

[Guest]

For what? You said this:

"Btw DGMultiDecodeNV is one of them."

Were you just trying to irritate me or do you have something to report about that?

[tebasuna51]

Maybe B.F. don't know you are the DGIndexNV author.

[unknownsoldierX]

When I try to convert a .mp4 with AAC to MP3, I get no audio. Do I need to install anything extra?

[tebasuna51]

When I try to convert a .mp4 with AAC to MP3, I get no audio. Do I need to install anything extra?
Put your log file :logfile:

[unknownsoldierX]

Here is the audio portion of the log. I canceled the job once the audio job was done. The resulting MP3 was silent.

[Warning] Log
-[Information] Versions
--[NoImage] MeGUI Version : 0.3.5.0
--[NoImage] OS : Windows Seven Ultimate Edition x86 (6.1.0.7600)
--[NoImage] Latest .Net Framework installed : 4.0 (4.0.30319)
--[NoImage] Avisynth Version : 2.5.8.5
-[Information] Log for job1 (audio, P18.mp4 -> P18.mp3)
--[Information] [6/27/2010 6:48:31 PM] Started handling job
--[Information] [6/27/2010 6:48:31 PM] Preprocessing
--[NoImage] Avisynth script
---[NoImage] DirectShowSource("H:\P18.mp4", video=false)
---[NoImage] EnsureVBRMP3Sync()
---[NoImage] 6<=Audiochannels(last)?x_stereo1a6edad3ffe64c138c8a83b14de188e1(ConvertAudioToFloat(last)):last
---[NoImage] Normalize()
---[NoImage] 32==Audiobits(last)?ConvertAudioTo16bit(last):last
---[NoImage] return last
---[NoImage] function x_stereo1a6edad3ffe64c138c8a83b14de188e1(clip a)
---[NoImage] {
---[NoImage] fl = GetChannel(a, 1)
---[NoImage] fr = GetChannel(a, 2)
---[NoImage] c = GetChannel(a, 3)
---[NoImage] lfe = GetChannel(a, 4)
---[NoImage] sl = GetChannel(a, 5)
---[NoImage] sr = GetChannel(a, 6)
---[NoImage] l_sl = MixAudio(fl, sl, 0.2929, 0.2929)
---[NoImage] c_lfe = MixAudio(lfe, c, 0.2071, 0.2071)
---[NoImage] r_sr = MixAudio(fr, sr, 0.2929, 0.2929)
---[NoImage] l = MixAudio(l_sl, c_lfe, 1.0, 1.0)
---[NoImage] r = MixAudio(r_sr, c_lfe, 1.0, 1.0)
---[NoImage] return MergeChannels(l, r)
---[NoImage] }
--[NoImage] Commandline used: --abr 128 -h - "{0}"
--[Information] [6/27/2010 6:48:31 PM] Encoding started
--[Information] [6/27/2010 6:48:31 PM] Encode thread started
--[Information] [6/27/2010 6:48:32 PM] Avisynth script environment opened
--[Information] [6/27/2010 6:48:32 PM] Script loaded
--[Information] Output Decoder
---[NoImage] Channels: 2
---[NoImage] Bits per sample: 16
---[NoImage] Sample rate: 32000
--[NoImage] Commandline: D:\Programs\MeGUI\tools\lame\lame.exe --abr 128 -h - "H:\P18.mp3"
--[Information] [6/27/2010 6:48:32 PM] Encoder process started
--[NoImage] Output from encoder via stderr
---[NoImage] LAME 3.98.2 32bits (http://www.mp3dev.org/)
---[NoImage] CPU features: MMX (ASM used), SSE (ASM used), SSE2
---[NoImage] Using polyphase lowpass filter, transition band: 15613 Hz - 16000 Hz
---[NoImage] Encoding <stdin> to H:\P18.mp3
---[NoImage] Encoding as 32 kHz j-stereo MPEG-1 Layer III (8x) average 128 kbps qval=2
--[Information] [6/27/2010 7:09:59 PM] Postprocessing
---[Information] Deleting intermediate files
--[Information] [6/27/2010 7:09:59 PM] Job completed

[tebasuna51]

Here is the audio portion of the log. I canceled the job once the audio job was done. The resulting MP3 was silent.

- First try resample the audio to 48 KHz (SampleRate: Change to 48000 Hz), some players have troubles with 32 KHz. Always recommended for hardware players.

- If this don't work maybe your DirectShow settings can't manage the audio decode. We never can't know how work DirectShowSource on each computer.

Then you can try:

1) Decode the audio using NeroAacDec:
NeroAacDec -if "H:\P18.mp4" -of "H:\P18.wav"
and encode H:\P18.wav to mp3

2) If you have Foobar2000 try play H:\P18.mp4. If work then use 'Convert' to obtain the mp3.

3) Extract the audio from your .mp4 (like .aac or .m4a) using Yamb, and recode the audio using BeHappy-BassAudioSource

[unknownsoldierX]

I tried MeGUI on another machine and it produced audio from P18.mp4. But it sounds like Alvin And The Chipmunks played at high speed. Here is the log:

[Information] Log
-[Information] Versions
--[NoImage] MeGUI Version : 0.3.5.0
--[NoImage] OS : Windows Seven Ultimate Edition x86 (6.1.0.7600)
--[NoImage] Latest .Net Framework installed : 4.0 (4.0.30319)
--[NoImage] Avisynth Version : 2.5.6.0
-[Information] Log for job1 (audio, P18.mp4 -> P18.mp3)
--[Information] [6/28/2010 8:25:36 AM] Started handling job
--[Information] [6/28/2010 8:25:36 AM] Preprocessing
--[NoImage] Avisynth script
---[NoImage] DirectShowSource("D:\P18.mp4", video=false)
---[NoImage] EnsureVBRMP3Sync()
---[NoImage] 6<=Audiochannels(last)?x_stereoea59049e0f6f4710834e17dac3bc52d0(ConvertAudioToFloat(last)):last
---[NoImage] SSRC(48000)
---[NoImage] Normalize()
---[NoImage] 32==Audiobits(last)?ConvertAudioTo16bit(last):last
---[NoImage] return last
---[NoImage] function x_stereoea59049e0f6f4710834e17dac3bc52d0(clip a)
---[NoImage] {
---[NoImage] fl = GetChannel(a, 1)
---[NoImage] fr = GetChannel(a, 2)
---[NoImage] c = GetChannel(a, 3)
---[NoImage] lfe = GetChannel(a, 4)
---[NoImage] sl = GetChannel(a, 5)
---[NoImage] sr = GetChannel(a, 6)
---[NoImage] l_sl = MixAudio(fl, sl, 0.2929, 0.2929)
---[NoImage] c_lfe = MixAudio(lfe, c, 0.2071, 0.2071)
---[NoImage] r_sr = MixAudio(fr, sr, 0.2929, 0.2929)
---[NoImage] l = MixAudio(l_sl, c_lfe, 1.0, 1.0)
---[NoImage] r = MixAudio(r_sr, c_lfe, 1.0, 1.0)
---[NoImage] return MergeChannels(l, r)
---[NoImage] }
--[NoImage] Commandline used: --abr 128 -h - "{0}"
--[Information] [6/28/2010 8:25:37 AM] Encoding started
--[Information] [6/28/2010 8:25:37 AM] Encode thread started
--[Information] [6/28/2010 8:25:37 AM] Avisynth script environment opened
--[Information] [6/28/2010 8:25:39 AM] Script loaded
--[Information] Output Decoder
---[NoImage] Channels: 2
---[NoImage] Bits per sample: 16
---[NoImage] Sample rate: 48000
--[NoImage] Commandline: D:\Programs\MeGUI\tools\lame\lame.exe --abr 128 -h - "D:\P18.mp3"
--[Information] [6/28/2010 8:25:39 AM] Encoder process started
--[NoImage] Output from encoder via stderr
---[NoImage] LAME 3.98.2 32bits (http://www.mp3dev.org/)
---[NoImage] CPU features: MMX (ASM used), 3DNow! (ASM used), SSE (ASM used), SSE2
---[NoImage] Using polyphase lowpass filter, transition band: 16452 Hz - 17032 Hz
---[NoImage] Encoding <stdin> to D:\P18.mp3
---[NoImage] Encoding as 48 kHz j-stereo MPEG-1 Layer III (12x) average 128 kbps qval=2
--[Information] [6/28/2010 8:31:43 AM] Postprocessing
---[Information] Deleting intermediate files
--[Information] [6/28/2010 8:31:43 AM] Job completed

Using foobar2000 works, and it keeps the sample rate at 32kHz. Here is the mp3 file it made:

General
Complete name : H:\P18.mp3
Format : MPEG Audio
File size : 22.6 MiB
Duration : 40mn 15s
Overall bit rate : 78.6 Kbps
Writing library : LAME3.98r

Audio
Format : MPEG Audio
Format version : Version 1
Format profile : Layer 3
Mode : Joint stereo
Mode extension : MS Stereo
Duration : 40mn 15s
Bit rate mode : Variable
Bit rate : 78.6 Kbps
Minimum bit rate : 32.0 Kbps
Channel(s) : 2 channels
Sampling rate : 32.0 KHz
Stream size : 22.6 MiB (100%)
Writing library : LAME3.98r
Encoding settings : -m j -V 2 -q 0 -lowpass 16 --vbr-new -b 32

I muxed using AVI Mux GUI and the A/V sync is perfect. So that's one file down, but it a lot more work than letting MeGUI do everything.

[tebasuna51]

I tried MeGUI on another machine and it produced audio from P18.mp4. But it sounds like Alvin And The Chipmunks played at high speed.
...
Using foobar2000 works, and it keeps the sample rate at 32kHz.
...
I muxed using AVI Mux GUI and the A/V sync is perfect. So that's one file down, but it a lot more work than letting MeGUI do everything.

Yes, seems your DirectShow system don't work properly with AviSynth and mp4.

[unknownsoldierX]

I'm just did a fresh install of Windows and directx on my main machine a few days ago. And it's weird that I would have problems on two different machines.

[Lighto]

I'm just did a fresh install of Windows and directx on my main machine a few days ago. And it's weird that I would have problems on two different machines.

Since you're on 7, have you tried using the win7dsfiltertweaker tool?

[MNCvn]

Hi everyone,

I've a problem with new meGUI (version 0.3.5.0). With the old version, it have many PSP profile for me to choose and convert. The output file very good to play on my PSP (3000). But with the new one, It has only one PSP profile, and the output file CAN NOT play in my PSP. I make many time and change many parameters but i'm still not lucky. And I think this is the problem:
Format settings, ReFrames : 4 frames
I use other app to make mp4 file for my PSP, and this parameter is always 3 (maximum).
Although, the PSP profile of meGUI set the --ref equal 3 but the output file is always 4. Maybe it's error of x264 encoder, but the XmediaRecode (which one is use the same x264 encoder version of meGUI don't have this problem). ==> I really don't know why.

The info of the output file make by XmediaRecode:
General
Complete name : D:\Convert Video\Gia tri doi nguoi A.mp4
Format : MPEG-4
Format profile : Sony PSP
Codec ID : MSNV
File size : 7.36 MiB
Duration : 1mn 1s
Overall bit rate : 1 011 Kbps
Encoded date : UTC 2010-06-29 08:33:28
Tagged date : UTC 2010-06-29 08:33:28

Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : Main@L3.0
Format settings, CABAC : Yes
Format settings, ReFrames : 3 frames
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 1mn 1s
Bit rate mode : Variable
Bit rate : 900 Kbps
Width : 480 pixels
Height : 272 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 25.000 fps
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.276
Stream size : 6.40 MiB (87%)
Writing library : x264 core 100
Encoding settings : cabac=1 / ref=3 / deblock=1:0:0 / analyse=0x1:0x111 / me=hex / subme=7 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=0 / me_range=16 / chroma_me=1 / trellis=0 / 8x8dct=0 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-2 / threads=3 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / constrained_intra=0 / bframes=0 / weightp=0 / keyint=250 / keyint_min=25 / scenecut=40 / intra_refresh=0 / rc_lookahead=40 / rc=abr / mbtree=1 / bitrate=900 / ratetol=1.0 / qcomp=0.60 / qpmin=10 / qpmax=51 / qpstep=4 / vbv_maxrate=2000 / vbv_bufsize=2000 / ip_ratio=1.40 / aq=1:1.00 / nal_hrd=none
Encoded date : UTC 2010-06-29 08:33:28
Tagged date : UTC 2010-06-29 08:33:28

Audio
ID : 2
Format : AAC
Format/Info : Advanced Audio Codec
Format version : Version 4
Format profile : LC
Format settings, SBR : No
Codec ID : 40
Duration : 1mn 0s
Bit rate mode : Variable
Bit rate : 128 Kbps
Channel(s) : 2 channels
Channel positions : Front: L R
Sampling rate : 48.0 KHz
Stream size : 953 KiB (13%)
Encoded date : UTC 2010-06-29 08:33:28
Tagged date : UTC 2010-06-29 08:33:28

The info of the output file make by MeGUI:
General
Complete name : D:\Convert Video\Gia Tri Doi Nguoi\Gia tri doi nguoi A-muxed.mp4
Format : MPEG-4
Format profile : Sony PSP
Codec ID : MSNV
File size : 7.87 MiB
Duration : 1mn 6s
Overall bit rate : 988 Kbps
Encoded date : UTC 2010-06-28 08:40:51
Tagged date : UTC 2010-06-28 08:40:51

Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : Main@L3.0
Format settings, CABAC : Yes
Format settings, ReFrames : 4 frames
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 1mn 6s
Bit rate mode : Variable
Bit rate : 900 Kbps
Maximum bit rate : 2 610 Kbps
Width : 352 pixels
Height : 240 pixels
Display aspect ratio : 1.396
Original display aspect ratio : 1.398
Frame rate mode : Constant
Frame rate : 29.970 fps
Standard : NTSC
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.355
Stream size : 7.07 MiB (90%)
Title : Imported with GPAC 0.4.6-DEV (internal rev. 5)
Writing library : x264 core 100 r1659 57b2e56
Encoding settings : cabac=1 / ref=3 / deblock=1:0:0 / analyse=0x1:0x111 / me=hex / subme=7 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=1 / 8x8dct=0 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-2 / threads=3 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / constrained_intra=0 / bframes=3 / b_pyramid=2 / b_adapt=1 / b_bias=0 / direct=1 / weightb=1 / open_gop=0 / weightp=2 / keyint=250 / keyint_min=25 / scenecut=40 / intra_refresh=0 / rc_lookahead=40 / rc=2pass / mbtree=1 / bitrate=900 / ratetol=1.0 / qcomp=0.60 / qpmin=10 / qpmax=51 / qpstep=4 / cplxblur=20.0 / qblur=0.5 / ip_ratio=1.40 / aq=1:1.00
Encoded date : UTC 2010-06-28 08:40:51
Tagged date : UTC 2010-06-28 08:40:52

Audio
ID : 2
Format : AAC
Format/Info : Advanced Audio Codec
Format version : Version 4
Format profile : LC
Format settings, SBR : No
Codec ID : 40
Duration : 1mn 6s
Bit rate mode : Variable
Bit rate : 96.0 Kbps
Maximum bit rate : 112 Kbps
Channel(s) : 2 channels
Channel positions : Front: L R
Sampling rate : 44.1 KHz
Stream size : 781 KiB (10%)
Encoded date : UTC 2010-06-28 08:40:51
Tagged date : UTC 2010-06-28 08:40:52

Please take a look at bold and underline lines.


The question: How do I set the parameter for x264 to make file can play on my PSP??? (meGUI 0.3.5.0). I know i can use XmediaRecode, but i want to know and I really love meGUI.

Thanks.