PDA

View Full Version : MeGUI: General Questions and Troubleshooting Thread


Pages : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 [21] 22 23 24 25 26 27

rapscallion
11th November 2009, 18:22
Quick question guys.
Using avchd or Blu-ray sa preset (Megui v1051/stable) how much processing time (as a %) does enabling "deblocking" add ?

Inspector.Gadget
11th November 2009, 18:38
Deblocking is one of the most useful, most visually powerful features in x264. Disabling it is a fool's errand and often won't net you a great decrease in encoding time because deblocking is turned on and off at the decoder level as well.

Inspector.Gadget
11th November 2009, 18:39
Like I said in a previous post, I can't find the option to set the fps in AVI Mux GUI

Thanks

You SHOULDN'T NEED TO. If AMG (USED MANUALLY, WITHOUT USING MEGUI AT ALL) can't detect the FPS from the input, then either xvid_encraw is breaking the AVI header or AMG has a bug.

rapscallion
12th November 2009, 00:51
Deblocking is one of the most useful, most visually powerful features in x264. Disabling it is a fool's errand and often won't net you a great decrease in encoding time because deblocking is turned on and off at the decoder level as well.
Thanks again Mr Gadget. No, I don't intend disabling it. However for quite some time , month's ago, it was disabled. (AVCHD preset).

When I caught it, it seemned like the 2 pass processing took longer. Where a 2hr movie used to take ~3 hr 1st pass, now takes ~4 hr. 2nd Pass 7 hr> 8hr. The only change I made was enabling the deblock . This is on ver 1051.

I've pulled some of the earlier avchd's and watched them again on my SA BD player and I don't see any problems with the vid. And, I didn't remember any problems/artifacts when I originally watched others.

I'd like to upgrade Megui to a newer ver but don't have a clue what kind of presets to use for either standalone bluray or standalone avchd.

Inspector.Gadget
12th November 2009, 00:54
Have you checked with MediaInfo to make sure that deblocking is actually off in the encoded files? If not, it's yet another MeGUI bug. If so, then it's a bug in the presets.

MeGUI's presets are generally outdated in view of the new tuning system. Simply preserve the limitations for hardware compatibility and set everything else to your preference.

rapscallion
12th November 2009, 01:00
I hate to admit it but I never knew that MI had that info.
I will check for sure.

If it was off during those encodes what should I look for as far as artfacts, etc ?Thanks

Inspector.Gadget
12th November 2009, 01:06
At high enough bitrates, nothing. At lower bitrates, blocking.

rapscallion
12th November 2009, 04:12
Ok then, I guess I had high enough bitrates on those encodes so that I didn't see any blocking.
I normally encode an avchd @ 1280*720 and burn to DVD-9

I looked at a current encode, with deblocking enabled, @ 0/0 and MI shows deblock=1:0:0

An earlier encode, with it disabled, shows deblock=0:0:0 So, I'm assuming that there was no deblocking ?

Inspector.Gadget
12th November 2009, 04:55
0:0:0 is disabled. 1:0:0 is on (default). Even at high bitrates, turning off deblocking harms picture quality by sucking up bits otherwise allocated elsewhere (I believe).

rapscallion
12th November 2009, 05:09
Thanks again ! (I'm , of course ,leaving it on all the time now)...the end -:)

rapscallion
13th November 2009, 22:41
Maybe a stupid question, but I am curious.

If I encode an mkv with deblocking set to , let's say :-3:-3 and then mux to a m2ts and re encode via Megui , with deblocking disabled, will the resulting video have the deblocking from the first encode carry over, after I remux it ?

Inspector.Gadget
13th November 2009, 23:10
The deblocking is a codec feature, not a pre-pass algorithm. It works internally within x264 to improve quality rather than making a deblocking pass to blur or discard edge data before compression. So no, it won't be "preserved" by re-encoding: the decoder will apply deblocking before the data is fed to the second encoder. Remuxing won't affect it, though.

Also, according to x264 devs, -3:-3 is really overkill: not even --tune grain goes that far.

rapscallion
13th November 2009, 23:18
Thanks again ! :thanks:

The (-3) was just an example. I don't/wouldn't ever use that.

The more I learn about this, the more I realize how little I know.
So, I really appreciate your, and others, informative responses.

Inspector.Gadget
14th November 2009, 07:17
Since so many people are complaining about broken versions and incompatibility, here's what I know for certain to work:

Core 1056, Libs 1056, Data 1053, AVS Wrapper 1056, STx264 85, TXviD 10, AVS 01, Tx264 01. Everything else shouldn't break compatibility unless there's an API change; I've dropped in the latest x264 builds from x264.nl and had no problems. I'm not yet manually using weightp, but the problems there seem to be only with a select few decoders and anyway are unrelated to MeGUI itself.

mozzle
14th November 2009, 07:37
Since so many people are complaining about broken versions and incompatibility, here's what I know for certain to work:

Core 1056, Libs 1056, Data 1053, AVS Wrapper 1056, STx264 85, TXviD 10, AVS 01, Tx264 01. Everything else shouldn't break compatibility unless there's an API change; I've dropped in the latest x264 builds from x264.nl and had no problems. I'm not yet manually using weightp, but the problems there seem to be only with a select few decoders and anyway are unrelated to MeGUI itself.

Thanks for the info, Gadget. I hope Kurtnoise is still around. And I especially hope Sharktooth is doing well. I know he's had some health issues in the past. Best to all three of you!

-mozzle

LigH
14th November 2009, 11:58
@LigH

could you try the deinterlace test from hdc ? is mutuated from berrinam tool too .. but should be a little less aggressive

thanks

BHH

Sorry for the late reply, I was kept from returning home for a while.

Your analysis appears to be better (but especially the 2nd pass is a lot slower, half playback speed for my machine - AM2 3800+).

Source is declared tff by a margin of 690/41.
Analyzed 1757 sections of five frames
Found Interlace Sections: 1184 67.39%
Found progressive Sections:482 27.43%
Found Telecined Sections: 91 5.18%
Found Zero Mov: 27.43% 482
Found One Mov: 7.63% 134
Found Two Mov: 5.18% 91
Found Three Mov: 9.73% 171
Found Four Mov: 7.17% 126
Found Five Comb: 42.86% 753

The Movie is declared to interlaced


I agree to this result.

Rodger
15th November 2009, 01:35
I strongly advise everybody to use Jeeb´s Rev.1336 of x264 with Megui as I had issues with one of my players.

Pioneer BDP-LX52 didn´t play anything created with Jeeb´x Rev.1309 but again everything with the new Rev.

Seems there was something wrong with Megui builds for quite a while.

HiTM4N
15th November 2009, 11:10
Hi,

* I'm using i7 860 P55 Quad Core Hyper-Threading CPU, My Question is in meGUI config option in thread to what number I should set for Xvid encoding? as i7 860 is HT CPU?

I have heard that leave it to "0" it will be auto, but i can't get to "0" it get change back to "1".

* And also for x264, how to set it?

I have tried to search all over the net but couldn't find solution to my question.

Regards

szabi
15th November 2009, 14:30
No, I wouldn't recommend using old x264

I understood you, propable the newer can be better.
I wrote if someone prefer using the profiles in that case.
Anyway your encoding time increasing.

Otherwise I did a test for comparing the encoding time.

1.
Dvd PAL mpg2 encoding to mkv by x264 using the "unrestricted 2pass HQ" profile
used avs script:
crop( 0, 76, -4, -76)
LanczosResize(704,288)

megui.v1056 x264r1183 => 00:16:51
megui.v1056 x264r1309 => 00:21:45
megui.v1057 x264r1339 => 00:23:09

2.
Same dvd PAL mpg2 encoding to mp4 by x264 using the "Device Cellphones_PDAs-Level1.3" profile
used avs script:
crop( 0, 76, -4, -76)
LanczosResize(320,128)

megui.v1056 x264r1183 => 00:07:50
megui.v1056 x264r1309 => 00:08:23
megui.v1057 x264r1339 => 00:08:36

3.
I did not have any HD rip now, so I used uncompressed ingame video recorded by fraps. Info:1680x1050@25fps.
x264 "DXVA HD HQ" profile
used avs script:
Trim(18,3570)
ConvertToYV12()

megui.v1056 x264r1183 => 00:14:53
megui.v1056 x264r1309 => 00:21:54
megui.v1057 x264r1339 => 00:22:22

You see encoding time increasing if I use newer and newer x264 with old profile collection.
Especially the last high resolution encoding. Time almost duplicated.
Also there can be a little difference between megui 1056 and 1057.
But it is also possible the newer x264 can be slower. Is not it?

bye
szabi

Dark Shikari
15th November 2009, 14:34
That's because the defaults in x264 changed, so the same commandline won't necessarily do the same thing in both cases.

XhmikosR
15th November 2009, 14:38
It's the new features of x264 that are enabled by default, like mb-tree and weightp, that slow down the encoding. But you do gain in quality. Try using the newest x264 and use --no-mbtree and --weightp 0 in the cmd and see what speeds you'll get.

szabi
15th November 2009, 15:02
I am not familiar the correct settings of x264 especially the cmd usage.
That is why I am using these profiles.

The STx264v85 profile collection in megui was created for x264r1181.
It looks like outdated, but I do not have better way how to set up newer x264.


EDIT: I mean these profiles. click (http://forum.doom9.org/showthread.php?p=1162196#post1162196)

bye
szabi

HiTM4N
15th November 2009, 16:46
can I get help here http://forum.doom9.org/showthread.php?p=1344041#post1344041

Thanks in Advance

Carpo
16th November 2009, 12:53
to get around the profiles issue - untick 1057 and Tx264 - as its these two files that mess things up

szabi
16th November 2009, 14:14
I am using megui 1057 without any profile problem.
Install and update megui but excluding profile update.
Use these profiles (http://www.mediafire.com/?udmmwzn2nyi) modified by ncatt (http://forum.doom9.org/showthread.php?p=1338462#post1338462).
Incompability was fixed and it is working just little bit outdated.

bye
szabi

Carpo
17th November 2009, 00:45
when i tried it 1057 borked every thing, if i left that off the list everything worked fine :)

szabi
17th November 2009, 22:05
It's the new features of x264 that are enabled by default, like mb-tree and weightp, that slow down the encoding. But you do gain in quality. Try using the newest x264 and use --no-mbtree and --weightp 0 in the cmd and see what speeds you'll get.

I tried it, but no major difference in encoding time.

my setting:
x264.exe" --profile high --level 4.1 --preset slow --pass 2 --bitrate 11702 --stats "F:\x.stats" --thread-input --deblock -1:-1 --ref 4 --vbv-bufsize 50000 --vbv-maxrate 50000 --subme 7 --sar 1:1 --output "F:\x.mkv" "F:\x.avs"

"my settings": 00:39:24
"no-weightb": 00:36:19
"no-mbtree": 00:36:14
"no-weightb" "no-mbtree": 00:36:09


Unfortunately I run into an annyoing problem.
If I use DXVA HD HQ profile with new megui and x264 the parameters not going to x264 correctly.

This parameters should be sent to x264, from DXVA HD HQ profile :
program --profile high --level 4.1 --preset fast --pass 2 --bitrate 11702 --stats ".stats" --thread-input --deblock -1:-1 --ref 4 --vbv-bufsize 50000 --vbv-maxrate 50000 --me umh --direct auto --partitions p8x8,b8x8,i4x4,i8x8 --trellis 2 --output "output" "input"

and it is which really sent:
program --profile high --level 4.1 --preset fast --pass 2 --bitrate 11702 --stats ".stats" --thread-input --vbv-bufsize 50000 --vbv-maxrate 50000 --output "output" "input"

Does anyone else meet this?

bye
szabi

XhmikosR
17th November 2009, 22:18
I don't see anywhere in your command line to disable mb-tree and weightp, so of course the speed will be the same since they are enabled by default. Take a look here (http://mewiki.project357.com/wiki/X264_Settings) to see a few info regarding x264's settings. That's just for testing the speed, you are advised to keep those features enabled since they improve the quality.
As for the other issue, just stop using MeGUI until it gets fixed.

szabi
17th November 2009, 22:35
I usually use them both.
After my setting was changed by no-weightb there was 3 minutes drop. Also if no-mbtree was used almost same 3 minutes drop for my settings.
If I disabled both the gain reamin 3 minutes, not 6 as I expected.

EDIT: Ok, I did not copy-paste the entire commandline when I changed it. Only the modification switch to compare the encoding time.

by
szabi

XhmikosR
17th November 2009, 23:21
No one said that the speed gain would be proportional to the number of the default settings disabled. Anyway, use a faster preset then, or try to see which settings where exactly used by that old x264 version and try to use them.

rapscallion
18th November 2009, 06:19
to get around the profiles issue - untick 1057 and Tx264 - as its these two files that mess things up
*Do you mean 1057 core only, or data and libs as well ?

Also, should I be using the profiles via the update or the ones by ncatt (post #5025, above)
for best results via SA AVCHD and SA Bluray??

In other words, which profile is compatible w/ x264 1309? (v 1056 core)

Edit : *I since have unticked all 3

Edit#2: When installing 1056 the speed preset bar defaults to "fast" when the Wiki pg states "medium" is the default. Which one should I use ?

rudiev
18th November 2009, 12:21
On page 251 from this thread i read that people are using megui v1057, but at the download page, http://sourceforge.net/projects/megui, you only can download v1056 and i also read about x264.exe v R1339, where can i download this new version? If i use the auto updater it says that everything is updated, but i still have megui v1056 with x264.exe v R1183 Jeeb's patched build.

OroSaiwa
18th November 2009, 12:26
@rudiev You might wanna switch update servers to development if you want built 1057

rudiev
18th November 2009, 14:32
@rudiev You might wanna switch update servers to development if you want built 1057

I haven't thought off this that it is a development version. Changed it and there are updates for me. But I prefer to stay at the tested stable version or can you, and others, recommend this newer version?

:thanks: for the tip :)

rapscallion
18th November 2009, 17:58
Since so many people are complaining about broken versions and incompatibility, here's what I know for certain to work:

Core 1056, Libs 1056, Data 1053, AVS Wrapper 1056, STx264 85, TXviD 10, AVS 01, Tx264 01. Everything else shouldn't break compatibility unless there's an API change; .

When I try to update 1056, via Development, I see the following vers :

Core -OK
libs- existing 1051, latest 1057
Data-existing 1051, latest 1057
AVS wrapper-existing 1006, latest 1006

What ver of x264 do you have along w/this list, 1309?

Inspector.Gadget
18th November 2009, 23:45
Latest from x264.nl. I don't update from MeGUI 1056, at all. I simply don't use autoupdate.

rapscallion
19th November 2009, 01:31
Thanks....but, for people like me that depend on presets, that's a little too advanced.

I'm kind of in a quandry, with 1056 and x264 v1183, what are the valid prests to be using?
The ones that are installed during 1056 setup or the ncatt ones ?

Inspector.Gadget
19th November 2009, 01:34
Don't use MeGUI presets at all, they are outdated. Use x264's built-in presets and profiles, subject to limitations for non-PC devices, until the profiles are updated.

rapscallion
19th November 2009, 05:15
Then it may be back to 1051 for me because I only us non PC devices.

What about the presets mentioned in this post, they're dated 10/27/09 :

I am using megui 1057 without any profile problem.
Install and update megui but excluding profile update.
Use these profiles (http://www.mediafire.com/?udmmwzn2nyi) modified by ncatt (http://forum.doom9.org/showthread.php?p=1338462#post1338462).
Incompability was fixed and it is working just little bit outdated.

bye
szabi

Something has to be entered in the "encoder settings" box on the Megui main page ?
So, I don't quite understand how to use 264's "built in" presets and profiles.(and believe me, I searched)

Inspector.Gadget
19th November 2009, 05:35
Just use the options that are --tune whatever and --preset whateverelse. They're in the rev. 1056 config panel. You can enforce on that same page a profile and a level per your device's specs. If you require advanced settings, they're still there and will be exposed when you check the appropriate box right in the middle of the panel. If you load an old preset, and THEN check the advanced settings box, all the old defaults will still be applied to the command line (but you may now want to use MB-Tree, etc., whereas they weren't available before).

rudiev
19th November 2009, 13:03
Something has to be entered in the "encoder settings" box on the Megui main page ?
So, I don't quite understand how to use 264's "built in" presets and profiles.(and believe me, I searched)
Normally the 'encoder settings' come with a drop down box with a lot of presets. The presets should be saved in the directory 'C:\Program Files (x86)\megui\allprofiles' , where i have 13 subdirectories containing .xml files which are the presets. The presets are for audio and video. For video i have two subdirectories called 'x264' and 'XviD', these two directories contains lots of .xml files with encoding presets. These presets can i choose in the 'encoder settings' drop down box. I have attached a picture of this, but it can take some time before it's approved.
Can you check that you have these presets? In your megui installation directory, subdirectory 'allprofiles' with again subdirectories containing these .xml files.

These profile also should be updated, check the updater under 'profile collection'. STx264 should be version 85, STAudio version 16, TXviD version 10 and AVS version 01. At least this is megui showing on my pc(megui version 1056).

rapscallion
19th November 2009, 15:35
Thanks rudiev, I know all that, but other posters are saying those presets/profiles are out of date (see Inspector Gadget's post above my previous-#5038). He's saying to use x264's built in profiles/presets. Thus, my question re the main pg.

rudiev
19th November 2009, 18:31
Thanks rudiev, I know all that, but other posters are saying those presets/profiles are out of date (see Inspector Gadget's post above my previous-#5038). He's saying to use x264's built in profiles/presets. Thus, my question re the main pg.

Yeah, x264.exe have build-in profile. Run 'x264.exe --longhelp' to see all option and profiles. Also if you download the newest x264.exe (eg from x264.nl), this version has again updated profiles. I think that is what he meant.

Ow, in the newer version of x264.exe it's 'x264.exe --fullhelp'.

rapscallion
19th November 2009, 18:41
The more answers I get, the more confused I become. How does that affect the "encoder settings" box on Megui main pg ? And, the ST x264...where does that come from. Megui or x264?

And where do the ncatt profiles fit in ? My head really hurts now !

All I want to do is run 1056 w/r1183 and good/valid sa_avchd/sa_bluray presets.

Inspector.Gadget
19th November 2009, 19:08
Then use the old MeGUI profiles (what you have now), check the advanced settings box in the config window to get those options applied, and optionally apply MB-Tree by enabling it in MeGUI. You won't get the advantage of x264 developer-tuned settings, but you'll get known hardware compliance and you can always change the options not relevant to hardware compatibility to conform to the x264 presets and tunings if you wish.

szabi
19th November 2009, 19:28
Profile collection which coming with update was created in this topic: New MeGUI x264 presets (http://forum.doom9.org/showthread.php?p=1162196#post1162196) creator is Sharktooth.
Last version is v85. It is called STx264 on update list.

But these profiles were not modified for new x264.
That is why it is outdated.

In addition I wrote in previous page the settings from profile are not sent correctly to x264.

I chose DXVA HD HQ profile, sent calculated bitrate and start encoding.
When I checked the logfile encoding parameters was not from the profile, instead of that the encoder was running with in-built fast preset.
It is quite far from HQ profile settings.

Also I saw the ncatt modified profiles have same name as Sharktooth profiles but have different settings.

It is I have realized into so far.

EDIT:
Then use the old MeGUI profiles (what you have now), check the advanced settings box in the config window to get those options applied, and optionally apply MB-Tree by enabling it in MeGUI.

You are right, if you select advanced setting the parameters will be from profiles instead of preset.

bye
szabi

rapscallion
19th November 2009, 19:49
@IG and @szabi...Thank you, those were the answers I was looking for.

(btw, the Sharktooth profiles are what I've been using all along, since May, in ver 10XX>1051 )
Am still using 1051 until I was able to figure out the settings in 1056.

szabi
19th November 2009, 20:04
I also used Sharktooh profile collection so far until incompatibily with megui 1057.
In your picture I see you prefer using insane profile.
Did you check the logfile x264 really running with this settings or just fast preset?

rapscallion
19th November 2009, 22:22
Not my picture....another poster, rudiev.

szabi
20th November 2009, 07:12
Sorry for my mistake.

mallb
20th November 2009, 12:24
Which x264 version is compatible with MeGUI 1056 and STx264 v85 profiles? I'm using "1309 - Jeeb's patched build".

Carpo
20th November 2009, 16:47
that version will work fine :)

rapscallion
20th November 2009, 20:22
@carpo...although a poster mentioned a few pgs back that he had a compatibilty issue with a sa Panasonic BD player using 1309.
He changed to 1336 and said it was fine. Not tested by me.
____________________________________________________

I have a 1080i source that I tested a small clip with.
"encode interlaced" box is checked and I get this warning in the first pass :
"[warning]:interlace+direct=temporal is not implemented"

I don't see temporal anywhere in the command line, so why is this warning being generated ? (1056/r1309)

Is it better to deinterlace the source before encoding, rather than Megui is there a good program to do this that anyone can recommend?

Carpo
20th November 2009, 23:27
I use the pc and MPC-HC so i wouldn't know bout issues with that player

usmando
21st November 2009, 09:40
I'm having a strange and irritating issue with encoded x264 videos. i encode my clips for mobile occasionally.
I was using a slightly old version of megui and i noticed it stopped updating, so i downloaded the new installer and deleted my old megui folder. Now i see that the videos encoded with latest version of x264 have a strange blockiness in them... i'm quite sure it is not because of bit-rate because it occurs even with fairly high bit-rates and moderate motion scenes. I have attached a sample of encoded video...with high motion just to emphasize the effect..

http://www.divshare.com/download/9440248-9dd

i first used the patched build of x264 which comes with megui update, then tried with latest unpatched build from x264.nl but alll results are the same. plus i have to turn off "Keep some B-frames as reference" otherwise it gives error.


here is my mediainfo:
General
Complete name : C:\Users\Administrator\Desktop\tstt\testclip.mkv
Format : Matroska
File size : 2.02 MiB
Duration : 28s 160ms
Overall bit rate : 600 Kbps
Encoded date : UTC 2009-11-21 08:27:31
Writing application : mkvmerge v2.9.7 ('Tenderness') built on Jul 1 2009 18:43:35
Writing library : libebml v0.7.7 + libmatroska v0.8.1

Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L1.3
Format settings, CABAC : Yes
Format settings, ReFrames : 5 frames
Muxing mode : Container profile=Unknown@1.3
Codec ID : V_MPEG4/ISO/AVC
Duration : 28s 160ms
Bit rate : 588 Kbps
Width : 320 pixels
Height : 176 pixels
Display aspect ratio : 16:9
Frame rate : 25.000 fps
Resolution : 24 bits
Colorimetry : 4:2:0
Scan type : Progressive
Bits/(Pixel*Frame) : 0.418
Stream size : 1.98 MiB (98%)
Language : English

Dark Shikari
21st November 2009, 09:47
I'm having a strange and irritating issue with encoded x264 videos. i encode my clips for mobile occasionally.
I was using a slightly old version of megui and i noticed it stopped updating, so i downloaded the new installer and deleted my old megui folder. Now i see that the videos encoded with latest version of x264 have a strange blockiness in them... i'm quite sure it is not because of bit-rate because it occurs even with fairly high bit-rates and moderate motion scenes. I have attached a sample of encoded video...with high motion just to emphasize the effect..

http://www.divshare.com/download/9440248-9dd (http://www.divshare.com/do?wnload/9440248-9dd)Let me guess, you're using CoreAVC or an otherwise broken decoder? The video plays just fine here.

rapscallion
21st November 2009, 14:13
+1, plays fine here as well.

Flux
21st November 2009, 14:33
I have couple videos as Avisynth scripts and each of them have different resize methods and other stuff, but the video format like frame rate, color space and final resolution are identical for all. How I can combine these scripts the way that MeGUI see them as one single video? I could encode all these scripts as lossless videos and then merge them with DirectShowSource + DirectShowSource, etc. but is it really necessary to do that?

usmando
21st November 2009, 20:53
Ummm.... yes CoreAVC. whats wrong with CoreAVC? I thought it was the best decoder around. Even on my phone i use CorePlayer to watch these videos so i guess that is the issue.

stax76
21st November 2009, 21:04
There is a bug somewhere, I think related the new --weightp feature which is enabled by default. A alternative decoders from Microsoft, DivX or ffdshow might help.

usmando
21st November 2009, 22:13
So this means if i want to convert videos for my smartphone (which uses Coreplayer), i should use an older version of x264. Thanks for the help guys.

stax76
21st November 2009, 22:20
Or use --weightp 0 but I'm not sure.

Dark Shikari
21st November 2009, 22:32
Or --weightp 1. It's only 2 that's broken.

n0an
23rd November 2009, 04:49
Hello,

The bitrate calculator in meGUI calculates a value and feeds it right in the config, but the video turns out to be either really big or smaller than it was calculated to be.

For example, it calculated bitrate for a 1hr24min as 1033 kbps + 128 kbps audio, but the encoded video was at 811 kbps. That is, ~200 kbps less than what it was supposed to be.

Codec ID/Hint : XviD
Duration : 1h 24mn
Bit rate : 811 Kbps
Width : 656 pixels
Height : 272 pixels
Display aspect ratio : 2.40:1
Frame rate : 23.976 fps

Earlier on a friend's PC, the calculator calculated bitrate for a 1/3DVD video, but the resulting file size was 2.23GB or so. I re-encoded with same bitrate thrice, but still same 2.23 size. There are no updates available at the moment as well.

Is this a known bug?

P.S. I think someone had posted this in the troubleshooting thread earlier, but it went unnoticed.

n0an
23rd November 2009, 04:49
Sorry, pc froze and I double clicked :|.

rudiev
23rd November 2009, 12:36
I also used Sharktooh profile collection so far until incompatibily with megui 1057.
In your picture I see you prefer using insane profile.
Did you check the logfile x264 really running with this settings or just fast preset?

That was me using the insane profile, here the log:


--[NoImage] Job commandline: "C:\Program Files (x86)\megui\tools\x264\x264.exe" --profile high --level 4.1 --preset fast --pass 1 --bitrate 14400 --stats "X:\file001.stats" --slow-firstpass --thread-input --output NUL "X:\file001.avs"
--[Information] [20-11-2009 11:49:18] Encoding started
--[NoImage] Standard output stream
--[NoImage] Standard error stream
---[NoImage] avis [info]: 1920x1080 @ 24.00 fps (172066 frames)
---[NoImage] x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 FastShuffle SSE4.1 Cache64
---[NoImage] x264 [info]: profile High, level 4.1
---[NoImage]
---[NoImage] x264 [info]: slice I:1388 Avg QP:13.16 size:201802
---[NoImage] x264 [info]: slice P:67076 Avg QP:15.31 size:114394
---[NoImage] x264 [info]: slice B:103602 Avg QP:17.18 size: 44682
---[NoImage] x264 [info]: consecutive B-frames: 6.8% 32.3% 13.3% 47.6%
---[NoImage] x264 [info]: mb I I16..4: 49.0% 19.0% 32.0%
---[NoImage] x264 [info]: mb P I16..4: 14.2% 16.6% 8.9% P16..4: 15.8% 9.4% 2.6% 0.0% 0.0% skip:32.4%
---[NoImage] x264 [info]: mb B I16..4: 8.1% 0.0% 0.0% B16..8: 27.9% 2.3% 1.6% direct:14.2% skip:45.9% L0:28.6% L1:27.7% BI:43.7%
---[NoImage] x264 [info]: final ratefactor: 19.11
---[NoImage] x264 [info]: 8x8 transform intra:31.3% inter:28.4%
---[NoImage] x264 [info]: coded y,uvDC,uvAC intra:87.2% 70.8% 28.6% inter:28.3% 23.9% 0.6%
---[NoImage] x264 [info]: ref P L0 76.9% 23.1%
---[NoImage] x264 [info]: kb/s:14040.1
--[Information] [20-11-2009 17:54:39] Postprocessing
---[Information] Deleting intermediate files
--[Information] [20-11-2009 17:54:39] Job completed

Profile high, preset fast. Is this right or wrong? And if wrong, how to fix it? Using megui v1056, x264 1183m.

djesteban
23rd November 2009, 18:59
Profile collection which coming with update was created in this topic: New MeGUI x264 presets (http://forum.doom9.org/showthread.php?p=1162196#post1162196) creator is Sharktooth.
Last version is v85. It is called STx264 on update list.

But these profiles were not modified for new x264.
That is why it is outdated.

In addition I wrote in previous page the settings from profile are not sent correctly to x264.

I chose DXVA HD HQ profile, sent calculated bitrate and start encoding.
When I checked the logfile encoding parameters was not from the profile, instead of that the encoder was running with in-built fast preset.
It is quite far from HQ profile settings.

Also I saw the ncatt modified profiles have same name as Sharktooth profiles but have different settings.

It is I have realized into so far.

EDIT:


You are right, if you select advanced setting the parameters will be from profiles instead of preset.

bye
szabi

1057 seems to be completely broken when trying to use any form of encoder settings (i tried with the ncatt profiles).
For example:
- First, install the ncatt profiles.
- Choose a profile in the Encoder Settings drop down menu and click the Config button.
- Now, usually, to activate the custom commands of the profile you have just selected, you only need to check Advanced Settings in the x264 configuration dialog... but this time, in 1057, only b-pyramid and vbv-maxrate seems to appear.
- Now, try something else. Stay in the x264 configuration dialog, and select a profile in the Presets drop down menu at the bottom of this window... be sure to recheck Advanced Settings. Nice! Now we have the correct advanced settings listed in the command dialog for this particular profile.
- Now, click OK to confirm the changes and immediately go back in Config to see if everything stayed as-is. Unfortunately, you will notice that everything was reset to the basic command plus b-pyramid and vbv-maxrate (but no sign of the actual custom setting for the profile).

So obviously, if you don't know that and start encoding, your output will look like garbage.

1057 is broken, PLEASE fix it as it is impossible to save/create or use profile presets. PLEEEEEEEASE :(

Thanks

szabi
24th November 2009, 09:14
That was me using the insane profile, here the log:
.
.
.

Profile high, preset fast. Is this right or wrong? And if wrong, how to fix it? Using megui v1056, x264 1183m.

Hi

You have the same situation like me.
That is the correct DXVA-HD-Insane parameters:

program --profile high --level 4.1 --preset fast --pass 2 --bitrate 1000 --stats ".stats" --thread-input --deblock -1:-1 --ref 4 --vbv-bufsize 50000 --vbv-maxrate 50000 --merange 32 --me tesa --direct auto --subme 8 --partitions p8x8,b8x8,i4x4,i8x8 --trellis 2 --no-dct-decimate --output "output" "input"

In this profile red marked parameters are responsible for DXVA compatibility.
You can reach this if follow what Inspector.Gadget wrote (http://forum.doom9.org/showthread.php?p=1345529#post1345529).

Click to Config of encoder settings.
Choose your profile here from drop down box menu below.
Activate advanced settings.
Insert your bitrate.
Click OK (save or not depends on you)
Enqueue

After you start encoding go to log and mark Job commandline.
Right click on it and Edit Text -> Node
Now you can check whether parameters were sent correctly.
Hopefully yes. :)

But do not forget x264r1183 and Sharktooth profiles quite old.
Much better if you create your own profile based on new x264r1342 in-built presets.
Actually I did it.
http://img214.imageshack.us/img214/8137/meguiconfig2.gif

Bye
szabi

szabi
24th November 2009, 09:31
1057 seems to be completely broken when trying to use any form of encoder settings (i tried with the ncatt profiles).
For example:
- First, install the ncatt profiles.
- Choose a profile in the Encoder Settings drop down menu and click the Config button.
- Now, usually, to activate the custom commands of the profile you have just selected, you only need to check Advanced Settings in the x264 configuration dialog... but this time, in 1057, only b-pyramid and vbv-maxrate seems to appear.
- Now, try something else. Stay in the x264 configuration dialog, and select a profile in the Presets drop down menu at the bottom of this window... be sure to recheck Advanced Settings. Nice! Now we have the correct advanced settings listed in the command dialog for this particular profile.
- Now, click OK to confirm the changes and immediately go back in Config to see if everything stayed as-is. Unfortunately, you will notice that everything was reset to the basic command plus b-pyramid and vbv-maxrate (but no sign of the actual custom setting for the profile).

So obviously, if you don't know that and start encoding, your output will look like garbage.

1057 is broken, PLEASE fix it as it is impossible to save/create or use profile presets. PLEEEEEEEASE :(

Thanks

If you go back the Config it will not display what you set up.
An other issue which should be fixed.
I see you found the same solution like me. :)
As I wrote above ckeck the Job commandline whether parameters was sent correctly or not.
Anyway experts wrote much better if you use MB-Tree instead of B-pyramid.
Supposedly you get better quality.
But do not use them together.
Anyway which profile you would like to use if B-pyramid active?

Bye
szabi

rudiev
24th November 2009, 12:27
...
But do not forget x264r1183 and Sharktooth profiles quite old.
Much better if you create your own profile based on new x264r1342 in-built presets.
Actually I did it.
<image>

Bye
szabi

Thanks for your reply! But how did you build your own profiles based on the new x264r1342 built-in presets, now r1347 at x264.nl. I know simply to replace the x264.exe with a new one, but what else do i have to do for this. Where did you get the extra information for those new profiles?

szabi
24th November 2009, 13:43
Thanks for your reply! But how did you build your own profiles based on the new x264r1342 built-in presets, now r1347 at x264.nl. I know simply to replace the x264.exe with a new one, but what else do i have to do for this. Where did you get the extra information for those new profiles?

I forgot to check whether there is a new x264. I did not know it.
Thnx for notify me.

Info about presets is here (http://mewiki.project357.com/wiki/X264_Settings)

I am not expert that is why I used in-built presets.
I chosed preset slower and modified it to have DXVA compatibility.
You need red marked settings for it.
Also deblock was changed for little sharper picture
Finally I got this:
program --profile high --level 4.1 --preset slower --pass 2 --bitrate 10000 --stats ".stats" --thread-input --deblock -1:-1 --ref 4 --vbv-bufsize 50000 --vbv-maxrate 50000 --output "output" "input"

If gui can not read preset correctly go to Misc and click preset settings.
MeGui set up --subme 10 for preset slower but with this it should be 9. It also megui issue. That was I changed also back to 9 under Analysis button => Subpixel Refinement.
--deblock -1:-1 available under Frame-Type => deblocking Strenght: -1 and Treshold: -1 also.
--ref 4 is controlled Number of Reference Frames: 4.
--vbv-bufsize 50000 --vbv-maxrate 50000 are under Rate Control.
VBV Buffer Size: 50000 and VBV Maximum Bitrate: 50000

If you finished click new button below and create your own profile.
But do not forget if you want to use it follow the choosing step I wrote it in previous reply.

Bye
szabi

rudiev
24th November 2009, 17:54
@szabi
I'm gonna try to make this new profile. Till now i got the nasty problem that when i made a new profile and saved it and then quit megui i get an error "There was an error clearing the profile folder before deletion: The directory is not empty". After this all my profiles are gone! I have to import them again for them sharktook presets v85 zip-file.
I let you know when it done..

prOnorama
24th November 2009, 18:10
I'd just use

--level 4.1 --preset veryslow --bitrate xxxx ---vbv-bufsize 50000 --vbv-maxrate 50000

You can add --tune film, --tune grain or --tune animation for specific content

Or use --preset placebo, but that's really really slow

rudiev
24th November 2009, 18:27
@szabi
Finally got my new profile saved, played around with some setting based on the DXVA-HD-Insane:
program --profile high --level 4.1 --preset slower --pass 2 --bitrate 14400 --stats ".stats" --slow-firstpass --thread-input --deblock -1:-1 --bframes 3 --b-adapt 2 --direct auto --b-bias 0 --scenecut 40 --ref 4 --vbv-bufsize 50000 --vbv-maxrate 50000 --rc-lookahead 40 --aq-mode 1 --aq-strength 1.0 --merange 32 --me tesa --subme 9 --partitions all --trellis 2 --psy-rd 1.0:0 --no-dct-decimate --output "output" "input"

First pass take more than 2 days for 90 minutes source
Have to tune it some way :)

szabi
24th November 2009, 20:03
This is your profile:

program --profile high --level 4.1 --preset slower --pass 2 --bitrate 14400 --stats ".stats" --slow-firstpass --thread-input --deblock -1:-1 --bframes 3 --b-adapt 2 --direct auto --b-bias 0 --scenecut 40 --ref 4 --vbv-bufsize 50000 --vbv-maxrate 50000 --rc-lookahead 40 --aq-mode 1 --aq-strength 1.0 --merange 32 --me tesa --subme 9 --partitions all --trellis 2 --psy-rd 1.0:0 --no-dct-decimate --output "output" "input"

According to X264 Settings on MeWiki (http://mewiki.project357.com/wiki/X264_Settings) red marked parameters are not needed to write to commandline because they are the default settings of x264.
Green marked are default of slower preset so if you use slower preset you do not have to write to commandline them.

If you would use merange and me from slower preset instead of your own, your encoding time will increase.

EDIT: bframes 3 is also default of slower, I missed it first.

bye
szabi

prOnorama
24th November 2009, 20:48
@ szabi: you don't need to set --ref 4, it gets handled by the --level 4.1 switch, also --profile high is not needed (default) and rc-lookahead for profiles slower and up is 60 (not 40 that's for faster profiles, of course if you want that in slower profiles it's correct to specify it)

@ rudiv: --me tesa is the real speed killer here, I'd use --me uhm

szabi
24th November 2009, 22:16
If I set preset slower --ref 8 are used, I have to change back to 4 for DXVA compatibility. Unless you have smaller resolution. :cool:
Anyway I also would use default rc-lookahead 60 and me umh which is from slower profile as you wrote.

Finally I went back to my profile I wrote above. :)

bye
szabi

szabi
25th November 2009, 09:09
So this means if i want to convert videos for my smartphone (which uses Coreplayer), i should use an older version of x264. Thanks for the help guys.

For my mobile I have to use Baseline Profile with Level 1.3.
I use preset slow.
I can not use CABAC.
Reference Frames is 2.
VBV Buffer Size 2000.
VBV Maximum Bitrate 768.

program --profile baseline --level 1.3 --preset slow --pass 2 --bitrate 450 --stats ".stats" --thread-input --deblock -1:-1 --ref 2 --vbv-bufsize 2000 --vbv-maxrate 768 --output "output" "input"

It is working for me.
As I see in your info:
Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L1.3
Format settings, CABAC : Yes
Format settings, ReFrames : 5 frames
Muxing mode : Container profile=Unknown@1.3
Codec ID : V_MPEG4/ISO/AVC
Duration : 28s 160ms
Bit rate : 588 Kbps
Width : 320 pixels
Height : 176 pixels
Display aspect ratio : 16:9
Frame rate : 25.000 fps
Resolution : 24 bits
Colorimetry : 4:2:0
Scan type : Progressive
Bits/(Pixel*Frame) : 0.418
Stream size : 1.98 MiB (98%)
Language : English

Red marked one break the compatibility for my mobile.
Check this for your device: click (http://spreadsheets.google.com/pub?key=tYGTjNd0dG6P_A9z-YkFzFg&output=html)

bye
szabi

quantum5uicid3
27th November 2009, 01:14
1. use Megui 1056 from sourceforge
http://sourceforge.net/projects/megui/

2. put this as your update server
http://megui.org/auto/

3. uncheck the box to update the core, because 1057 is broken. update everything else

4. put the latest version of x264 in the \megui\tools\x264 directory overwriting the old
http://x264.nl/

5. here is the info you need to make your own megui presets
http://mewiki.project357.com/wiki/X264_Settings
http://forum.doom9.org/showthread.php?t=149711

6. The only problem I've encountered with 1056 is:
b-pyramid checkbox is broken, don't check the box that says "Keep some B-Frames for reference"


7. THIS IS WHAT YOU NEED TO DO IF YOUR STUCK USING OLD COREAVC

weightp is new and has not been implemented into megui at all yet, the x264 default of --weightp 2 doesn't play properly on CoreAVC

add either of these to the custom command line field in the Misc tab of the x264 configuration dialog
--weightp 0
--weightp 1




UNLESS YOU KNOW WHAT YOUR DOING, YOU DON'T NEED TO DO THIS PART. THE DEFAULT OF NONE IS GOOD.


the syntax for --b-pyramid changed, this is how you change the default now.

add either of these two to the custom command line field in the Misc tab of the x264 configuration dialog
--b-pyramid normal
--b-pyramid strict

Schra
29th November 2009, 02:34
Maybe it is helpful:
http://forum.doom9.org/showthread.php?p=1349678

Create a backup of your complete megui files and copy these new files into your megui directory. Beside the main program file I have included the latest x264 (r1352, patched) and one of my x264 profile files.

0.3.1.1057
- [x264Config] add support for weighted P prediction. Requires x264 revision 1327 or higher.
- [x264Config] fix issues with weighted B prediction
- [264Config] fix an issue where custom profile settings may be lost
- [x264Config] very minor cosmetic changes
- removed the UAC elevation prompt. If required please run the program as administrator
- [Util] + [FileUtil] incompatible xml files (e.g. profiles) will be moved to a backup dir
- fixed the problem of the incompatible x264 profiles. As a result the old B-Pyramid setting will be disabled
- [OSInfo] fixed a problem with the .NET detection
- [MuxStreamControl] preselect language if the filename contains the language name

I did not change the version number for obvious reasons. Hopefully kurtnoise/sharktooth/... will continue their work on this great program. Kudos to them!

Patch code is included, full source code can be requested if necessary (I do not know the GPL in every detail. If this is not sufficient please drop me a line and I will upload the full source files).

This quick fix solves not all problems regarding the x264ConfigPanel. For example the preset values are not up to date with the latest x264 version, wrong/old profiles will not be updated, ...

Create a backup of your files!

WARNING: In these few hours I could not understand the whole program code. Therefore the fix may be incomplete or new problems may arise. Nevertheless it worked for me.

By the way - joinded since 2001 and my first post has been today...

stax76
29th November 2009, 03:15
It crashes in DotNetVersionFormated.

Schra
29th November 2009, 03:35
It crashes in DotNetVersionFormated.

Right at the beginning? Strange and unwelcome start :confused:

What kind of OS/.NET do you use? I tried it only on Windows 7 x64 but this works (at least for me)

Did you put it in a 1057 directory? Please try to put it in a clean directory (only the megui.exe). It should start with no problems.

EDIT: Added a little debug code. Please download it again.

stax76
29th November 2009, 04:06
It's a array bounds issue, if you make a debug build and include the pdb file with it and write the stack trace to a log file (a stack trace should not be shown to the user with a message box) then I could tell you the exact line number where it throws since the stack trace contains line numbers then. My system is Win 7 32bit .NET 2.0, 3.5, 4.0 beta 2, I've copied your build on top of 1056.

lnatan25
29th November 2009, 07:21
If I remember correctly, the problem was due to some logger accessing something wrong. Just comment the lines of "iLogger" or whatever it was called, and it will not throw the exception. :)

Schra
29th November 2009, 14:08
It's a array bounds issue, if you make a debug build and include the pdb file with it and write the stack trace to a log file (a stack trace should not be shown to the user with a message box) then I could tell you the exact line number where it throws since the stack trace contains line numbers then. My system is Win 7 32bit .NET 2.0, 3.5, 4.0 beta 2, I've copied your build on top of 1056.

Sorry, too late yesterday and only a quick workaround. Here you can find the debug build:
removed Reason: The problem has been fixed in the newest build

If I remember correctly, the problem was due to some logger accessing something wrong. Just comment the lines of "iLogger" or whatever it was called, and it will not throw the exception. :)

Yes, you are right. It is not necessary for the program itself. At least I can find no reference beside this log entry.

edtee
30th November 2009, 06:33
Thanx, Schra, I'll give your modded code a go. Also big thanks to kurtnoise, Sharktooth, and the whole team who make megui possible. I love this tool as a great mix between power/control and ease of use. Many other tools hide more than I like. I'd rather learn, even if it means messing up an encode. Worse case is I lose some time, and gain a little knowledge.


Schra, I did a quick try of you code. Really not more than a start, and quick look around. It fails on close with a error about saving to a profile. I saw that error and your note on UAC and immediately thought that was the issue... Sure enough giving MeGui Admin on startup seems to resolve the issue for me.

Not too big a deal except... the only way I could close/exit MeGui was to open Window's task manager and end the process. Of course this all is unneeded once admin rights are given to the shortcut. Still this could be an issue to some users. I'm using Win7 64bit Pro for my OS. Let me know if you'd like more info.

Schra
30th November 2009, 19:14
It fails on close with a error about saving to a profile. I saw that error and your note on UAC and immediately thought that was the issue... Sure enough giving MeGui Admin on startup seems to resolve the issue for me.
[....]
Still this could be an issue to some users. I'm using Win7 64bit Pro for my OS. Let me know if you'd like more info.
Yes, removing UAC could cause some problems for inexperienced users. Nevertheless I am no fan of an application which demands administrative permissions on every start. In my opinion a program should run with as low permissions as possible and request admin access only if necessary. At the moment I have found two main places where admin access is required when installed to a protected directory (e.g. program files): update + program closing (write log files and profiles). Nevertheless there are a few other actions which require such an access. So the easiest thing would be to add the mandatory UAC prompt back to the program. Otherwise the complete file writing action has to be moved to a directory with write access (e.g. commonappdata for profiles/log/settings) and the update manager has to be a separate process with UAC prompt. Or - as a workaround - I could add a message box at program start indicating that the program does not have full access to the required files and folders and that it should be started with UAC. What do you prefer?



Not too big a deal except... the only way I could close/exit MeGui was to open Window's task manager and end the process.
It's a general issue with the error handling. I do not know if this works as designed. On the other hand it will require some work to change all the error handlers to a more user-friendly and common way.

lnatan25
1st December 2009, 01:57
The easiest way to fix would be to move all the updates/tools/profiles to %appdata%, one of which (Roaming or LocalLow) doesn't require Admin privileges. "But still, in order to update the main application, a UAC pop should come out. Not that it's very difficult to implement.

edtee
1st December 2009, 06:45
Regarding UAC/admin rights... Personally I have a known workaround, but you asked my opinion. I'm not a coder, so I don't truly know what the easiest programming fix is. Also I'm not confident I speak for a large number of users, but... For now, I'd say just put back in the old mandatory UAC pop-up, to escalate access.*

I agree with your philosophy of how a program should behave. However given that there have been some relatively large changes to x264's relationship to MeGui, and we seem to have lost(hopefully temporarily) some of the main coders. I'd prefer your time(generously given, thank you) go to addressing these areas first. After the app. gets back to what the community considers it's older level of some stability, these other changes could be done/addressed. Of course I don't know how much effort you want(can afford) to put into this. However if you plan to put alot of effort into this then it might make more sense for you to cleanup the code, so you can more easily improve it. In the long run I like the idea of moving out the code(ie updates) that needs a higher privilege and relocating stored data to a dir with lower restrictions. I think people would understand an update needing admin rights(via standard Windows UAC pop-up), as it's basically a program installation process(from a user's point of view).

*I ran your options by my wife, as a test of a less tech. savvy user(no reflection on my wife's intellect;) ). The message box idea didn't seem to help the confusion, as she wasn't sure she needed to give admin rights, and a wrong answer leads to the issue of not closing cleanly. I know it's a small thing, but I think people are just used to Windows pop-ups and way of doing things. Hence, it's less confusing to them, even if they may technically be doing the same thing, just asked differently.

stax76
1st December 2009, 08:59
What can be done is detecting if the startup dir is writable and restart with elevated privileges if it's not. That don't fix the issue that the application should not require admin privileges but it would be a easy fix until the admin requirements are removed. It works as follows:


[STAThread()]
public static void Main()
{
Application.SetCompatibleTextRenderingDefault(false);
Application.EnableVisualStyles();

try {
// 'Contains' is a LinQ extension method shipped with .NET 3.5 and upwards
if (!Environment.GetCommandLineArgs().Contains("-elevate"))
File.Create(Application.StartupPath + "\\writeCheck");

Application.Run(new MainForm());
} catch {
try {
Process p = new Process();
p.StartInfo.FileName = Application.ExecutablePath;
p.StartInfo.Arguments = "-elevate";
p.StartInfo.Verb = "runas";
p.Start();
} catch {
}
}
}


Download features require much work and often cause problems. I would try to avoid such features but if I had to download applications I would start a process with elevated privileges downloading it to the startup dir. It would not be a separate application but simply restarting with a command line like '-update'. It could be a second instance and if necessary the first instance could hide and block until the second instance performing the admin work terminates or the first instance terminates and the second instance take over. Things often seem difficult but aren't and there is a simple solution.

The write check is a file IO operation which slows down the startup, file IO operations should be done either after the main form was shown (there is a 'Shown' event) or with separate thread.

The users dir and the program data dir should not contain executables. Settings should be in the app data dir or in a custom dir. Microsoft has guidelines for everything. What helps much is looking at other applications, Firefox, Visual Studio, the good ones.

quantum5uicid3
1st December 2009, 10:08
.....

quantum5uicid3
1st December 2009, 10:14
.....

livetolove92
1st December 2009, 12:15
What does it mean " invalid argument b-pyramid = --b bias " ? Somebody help me plz :D. I use megui1056, x264 revision 1354 and Avisynth 2.5.7.

Kurtnoise
1st December 2009, 13:09
why you want to remove UAC ? that's not a good thing imo...


@Shra : I cannot download your patch...could you put it somewhere else ?

MatLz
1st December 2009, 13:47
@Livetolove92
It's because Megui 1056 is outdated compared to the X264 build you use.
I think you must disabled b-pyramid in the settings and write the custom command line ' --b-pyramid normal ' instead of.

Carpo
1st December 2009, 14:25
in 1056 - do people leave the profile they have selected (if the new ones p6, p7 etc) as is, or do you change the avc profiles and avc levels from auto guess to what you like, or do you leave them?

Being someone who likes the best quality i can get based on the system i have i norm use high and 4.1 - or is that overkill?

MatLz
1st December 2009, 15:48
I see a lot of users in trouble with X264 parameters.
Why not an option which completely disable the Megui codec settings to prevent the incompatibility with the often updated X264 builds?
By that I mean a 'total custom command-line' (input and output excepted)
The users could simply copy/paste the right command-line found on the forum in waiting the Megui update.
Is a stupid suggestion?

Schra
1st December 2009, 16:21
why you want to remove UAC ? that's not a good thing imo...
First of all: Great to see that you are still around and are not mad that I have (mis)compiled the source code. :)
Hopefully I have not annoyed you- my only intention was to fix a few things in order to keep this great project up and running.

Back to the UAC topic: UAC itself is a great and good thing and it should be used. But if an application demands every time administrative access even if it is not required, it would bother the user and they may disable UAC completely. I have installed MeGUI + the AviSynth plugin folder for example in locations where no admin access is necessary in order to write files. Therefore the UAC prompt is not necessary for me. It would be no problem if I could remove this prompt myself for this program only, but this is not possible because it's hard coded in the program/manifest itself.

On the other hand based upon the software design guides from Microsoft a program should not require administrative access during normal operation. Beside the update process I would declare all other operations (writing log files, profiles, ...) as "normal operation". The only - and recommended - solution is to move these files to a not protected directory like appdata. Sadly I have at the moment no link the MS software design guide to clarify which path is recommended in such a case. A drawback would be to have the files in different locations (program files, appdata, ...) which may be problematic if a user would like to have different versions of the program installed.

Nevertheless the easiest way will be to leave the program as it is (with UAC prompt). But the other solution mentioned by stax76 is a nice solution between security and coding effort.


@Schra : I cannot download your patch...could you put it somewhere else ?
I send you a PM.

prOnorama
1st December 2009, 20:29
@ Schra: I get the following error when trying to insert values for VBV Buffer Size and VBV Max Bitrate:

http://thumbnails21.imagebam.com/5824/22362a58236376.gif (http://www.imagebam.com/image/22362a58236376)


When I click it away I can enter the VBV values but I can't change the value for --rc-lookahead anymore (doesn't show up in command line). I use WinXP SP3.

Schra
1st December 2009, 23:45
@ Schra: I get the following error when trying to insert values for VBV Buffer Size and VBV Max Bitrate:

http://thumbnails21.imagebam.com/5824/22362a58236376.gif (http://www.imagebam.com/image/22362a58236376)


When I click it away I can enter the VBV values but I can't change the value for --rc-lookahead anymore (doesn't show up in command line). I use WinXP SP3.

As a workaround please do not enter any VBV values beside digits and do not delete the value.

--rc-lookahead is working if you press enter or change the focus after changing the value.

Found the problems, but I have no time to fix this now.

Carpo
2nd December 2009, 04:45
ok what with all the problems with megui not being updated atm (devs need time off too) can someone tell me if this is a good enough profile to use till everything is sorted?

--profile high --level 4.1 --preset veryslow --bitrate 1309 --thread-input --deblock 0:0 --bframes 3 --b-bias 0 --scenecut 40 --ref 4 --rc-lookahead 40 --aq-mode 1 --aq-strength 1.0 --merange 16 --subme 7 --partitions all --trellis 1 --psy-rd 1.0:0 --b-pyramid normal --output "output" "input"

All other settings in the p7 - very slow profile have been left alone, all i have changed is the level, profile, ref frame and the pyramid options (obviously the bitrate will change)

Also i notice in this version it doesnt add an analysis pass like in the 1051 version i was using, is this by design or something i am missing?

quantum5uicid3
2nd December 2009, 04:59
What you have to ask yourself is the following?
1. What is your target device?
2. How much time/cpu cycles do you have to dedicate to encoding?
3. What is the highest crf you can use to achieve satisfactory results? or do you need to have specific file size?(2pass)

nurbs
2nd December 2009, 08:07
These values are defaults, automatically set or part of preset veryslow anyway and therefore useless:
--profile high --level 4.1 --thread-input --deblock 0:0 --b-bias 0 --scenecut 40 --aq-mode 1 --aq-strength 1.0 --partitions all --psy-rd 1.0:0
These values override settings in the preset you use:
--bframes 3 --ref 4 --rc-lookahead 40 --merange 16 --subme 7 --trellis 1

Also --b-pyramid normal doesn't do anything because you didn't deactivate mb-tree RC (which you shouldn't).

All in all not that bad, but I have no idea why you use profile veryslow and then change almost everything manually back to profile medium / the defaults again. (I understand the refs and b-frames). You should also use a tuning depending on your content. (--tune film; --tune animation)

You could actually use
--bitrate 1309 --b-adapt 2 --ref 4 --partitions all --me umh --direct auto --output "output" "input"
which would be the same as your settings.

Carpo
2nd December 2009, 12:27
What you have to ask yourself is the following?
1. What is your target device?
2. How much time/cpu cycles do you have to dedicate to encoding?
3. What is the highest crf you can use to achieve satisfactory results? or do you need to have specific file size?(2pass)

1. PC - Mac - Laptop
2. As much time as it needs, i prefer quality over speed
3. I normally do 2 passes depending on the length of the movie, but if there is a better way im all for it :)

These values are defaults, automatically set or part of preset veryslow anyway and therefore useless:
--profile high --level 4.1 --thread-input --deblock 0:0 --b-bias 0 --scenecut 40 --aq-mode 1 --aq-strength 1.0 --partitions all --psy-rd 1.0:0
These values override settings in the preset you use:
--bframes 3 --ref 4 --rc-lookahead 40 --merange 16 --subme 7 --trellis 1

Also --b-pyramid normal doesn't do anything because you didn't deactivate mb-tree RC (which you shouldn't).

All in all not that bad, but I have no idea why you use profile veryslow and then change almost everything manually back to profile medium / the defaults again. (I understand the refs and b-frames). You should also use a tuning depending on your content. (--tune film; --tune animation)

You could actually use
--bitrate 1309 --b-adapt 2 --ref 4 --partitions all --me umh --direct auto --output "output" "input"
which would be the same as your settings.

All i did was change the 4 things listed in the profile already (after you tick advanced option which seems to load a lot of extra settings), most of the settings i posted above were already in p7 slow apart from the ones i changed, as to mb-tree - this says it should be enabled by default and is recommended, although i had to tick that.

Basically i am trying to get a profile that will give me great results for film and anime, of course when you know nothing about profiles and are trying to learn you are going to mess things up along the way :D

So based on the fact that i am going to be using a computer to watch it, im after best quality i can get based on the two types of genre i mainly watch, what would be an advised and/or amended profile to use?

rudiev
2nd December 2009, 13:17
I forgot to check whether there is a new x264. I did not know it.
Thnx for notify me.

Info about presets is here (http://mewiki.project357.com/wiki/X264_Settings)

I am not expert that is why I used in-built presets.
I chosed preset slower and modified it to have DXVA compatibility.
You need red marked settings for it.
Also deblock was changed for little sharper picture
Finally I got this:
program --profile high --level 4.1 --preset slower --pass 2 --bitrate 10000 --stats ".stats" --thread-input --deblock -1:-1 --ref 4 --vbv-bufsize 50000 --vbv-maxrate 50000 --output "output" "input"

If gui can not read preset correctly go to Misc and click preset settings.
MeGui set up --subme 10 for preset slower but with this it should be 9. It also megui issue. That was I changed also back to 9 under Analysis button => Subpixel Refinement.
--deblock -1:-1 available under Frame-Type => deblocking Strenght: -1 and Treshold: -1 also.
--ref 4 is controlled Number of Reference Frames: 4.
--vbv-bufsize 50000 --vbv-maxrate 50000 are under Rate Control.
VBV Buffer Size: 50000 and VBV Maximum Bitrate: 50000

If you finished click new button below and create your own profile.
But do not forget if you want to use it follow the choosing step I wrote it in previous reply.

Bye
szabi

The problem is when i want to add those extra option you mentioned i have to enable the advanced settings checbox which adds a whole lot of extra options to the command line of x264.exe. You also mentioned some settings for DXVA settings, but are these really necessary? Because I have made .mkv with only a few option:

program --profile high --level 4.1 --preset fast --pass 2 --bitrate 14400 --stats ".stats" --slow-firstpass --thread-input --output "output" "input"

When i play this file with media player classic - home cinema and check the taskmanager for the mpc-hc.exe process, is ee that i uses only a few % of cpu time. While with a .wvc file this can be up to say about 35%. CPU is a intel E8200 @ 3.2 GHz. So i'm sure it already uses DXVA without those extra settings.

MediaInfo say this about the video

Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4.1
Format settings, CABAC : Yes
Format settings, ReFrames : 2 frames
Muxing mode : Container profile=Unknown@4.1
Codec ID : V_MPEG4/ISO/AVC
Duration : 2h 25mn
Bit rate : 14.1 Mbps
Nominal bit rate : 14.4 Mbps
Width : 1 920 pixels
Height : 1 080 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.283
Stream size : 14.3 GiB (85%)
Writing library : x264 core 79 r1347 5ddd61b
Encoding settings : cabac=1 / ref=2 / deblock=1:0:0 / analyse=0x3:0x113 / me=hex / subme=6 / psy=1 / psy_rd=1.0:0.0 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=1 / 8x8dct=1 / cqm=0 / deadzone=21,11 / chroma_qp_offset=-2 / threads=3 / nr=0 / decimate=1 / mbaff=0 / constrained_intra=0 / bframes=3 / b_pyramid=0 / b_adapt=1 / b_bias=0 / direct=1 / wpredb=1 / wpredp=2 / keyint=250 / keyint_min=25 / scenecut=40 / rc_lookahead=30 / rc=2pass / mbtree=1 / bitrate=14400 / 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
Language : English

73ChargerFan
4th December 2009, 17:42
I see a lot of users in trouble with X264 parameters.
Why not an option which completely disable the Megui codec settings to prevent the incompatibility with the often updated X264 builds?
This change is major, beforehand imho the parameters didn't change that frequently. I relied on Sharktooth to understand them and create profiles, and all I'd do is change the bitrate. With him out of action, I don't know what to do. When I tried the new version, encoding was sped up by a factor of 4 and the resultant quality was lower than I desired.

Sharktooth, I'm grateful to all you've done and wish you health and happiness. Happy Holidays.

Schra
5th December 2009, 12:46
@ Schra: I get the following error when trying to insert values for VBV Buffer Size and VBV Max Bitrate:

When I click it away I can enter the VBV values but I can't change the value for --rc-lookahead anymore (doesn't show up in command line). I use WinXP SP3.

Fixed:
http://forum.doom9.org/showthread.php?p=1349678

forum king
5th December 2009, 20:04
guys i have been using the 1051 version of megui and i have not updated it at all since ...
i have a few questions if you guys can help out ..
1.. i have been using 1183 build of x264 ... which of the later builds are compatible with 1051 version and have positive results in terms of sp[eed and quality of encoding.
2.. i use unrestricted 2 pass to encode my DVDs but i donno the edges are still blurred , do you guys suggest some custom tweaks in the profiles to make the encode look sharper and with clear edges ( off course no blocks ).. i know its kinna vague , but still i would love to have a general idea.
3.. i have a quad core with 8gb ram .. what filters i should use so that the encodes give better qulaity ..
4.. any other input would be appreciated .... like which filters improve picture quality and how to apply them. whats the basic thing one should keep in mind while ripping a DVD and a HD source.

bluebebe
5th December 2009, 20:40
moin,

i think the problem with the latest dev build 0.3.1.1057 was already discussed here, but i cant find a solution for this problem:
http://img248.imageshack.us/img248/9726/megui.jpg


how can i fix the problem, that megui always delete all profiles on startup? i tried several new installations of the app, no chance to get this problem fixed. knows anyone a solution for that, because new megui builds arent forseeable in the next time.

thanks for help.

floz23
6th December 2009, 01:34
Ok, Can anyone help? I need a link to download 1051...

Thanks.

Zathor
6th December 2009, 02:19
how can i fix the problem, that megui always delete all profiles on startup? i tried several new installations of the app, no chance to get this problem fixed. knows anyone a solution for that, because new megui builds arent forseeable in the next time.

thanks for help.

Please have a look here:
http://forum.doom9.org/showthread.php?p=1349678

talen9
6th December 2009, 02:27
guys i have been using the 1051 version of megui and i have not updated it at all since ...
i have a few questions if you guys can help out ..
1.. i have been using 1183 build of x264 ... which of the later builds are compatible with 1051 version and have positive results in terms of sp[eed and quality of encoding.
2.. i use unrestricted 2 pass to encode my DVDs but i donno the edges are still blurred , do you guys suggest some custom tweaks in the profiles to make the encode look sharper and with clear edges ( off course no blocks ).. i know its kinna vague , but still i would love to have a general idea.
3.. i have a quad core with 8gb ram .. what filters i should use so that the encodes give better qulaity ..
4.. any other input would be appreciated .... like which filters improve picture quality and how to apply them. whats the basic thing one should keep in mind while ripping a DVD and a HD source.

Being still on version 1051 of MeGUI is not very smart (it's more than 8 months old, 5-6 revisions ago!); anyway, since you're already using 1051, why do you ask, in your next post, where to download it?!?

Your other questions have nothing to do with MeGUI (and they are so vague that I'm not even sure if they go along well with the forum rules (http://forum.doom9.org/forum-rules.htm)), so this is not the right place to ask them; go to Newbies forum, take your time to read some good threads and :search: ;)

Inspector.Gadget
6th December 2009, 03:21
1.. i have been using 1183 build of x264 ... which of the later builds are compatible with 1051 version and have positive results in terms of sp[eed and quality of encoding.
2.. i use unrestricted 2 pass to encode my DVDs but i donno the edges are still blurred , do you guys suggest some custom tweaks in the profiles to make the encode look sharper and with clear edges ( off course no blocks ).. i know its kinna vague , but still i would love to have a general idea.
3.. i have a quad core with 8gb ram .. what filters i should use so that the encodes give better qulaity ..
4.. any other input would be appreciated .... like which filters improve picture quality and how to apply them. whats the basic thing one should keep in mind while ripping a DVD and a HD source.

1. All of them
2. More bits and starting with basic settings reviewed by x264 devs. Try CRF 20 and --tune film.
3. None. Unless you can identify a specific problem with a source in the original, you don't need filters. MeGUI allows you to deinterlace/IVTC, crop, resize, fix the colors on some incorrectly authored MPEG-2 sources (usually unnecessary), and apply light to medium denoising (also usually unnecessary).
4. See number 3. If you have acceptable visual quality for your purposes after using enough bits and reasonable settings, you're done.

forum king
6th December 2009, 06:08
1. All of them
2. More bits and starting with basic settings reviewed by x264 devs. Try CRF 20 and --tune film.
3. None. Unless you can identify a specific problem with a source in the original, you don't need filters. MeGUI allows you to deinterlace/IVTC, crop, resize, fix the colors on some incorrectly authored MPEG-2 sources (usually unnecessary), and apply light to medium denoising (also usually unnecessary).
4. See number 3. If you have acceptable visual quality for your purposes after using enough bits and reasonable settings, you're done.

Thanks a lot mate thats a great reply :)
BTW i had used 1056 which had the latest x264 build and i had noticed that the resultant video was severly blocky , but when i reverted to 1051 which has 1183 build the video was decent with same profile and similar bit rates.. thats what has got me confused about upating megui now...
could u be kind enough to point me to the most recent totally stable build of megui as well as x264...

i have come to realise that the best version atm and totally stable without any bugs ( that coreavc incompatibility thing - The new builds after 1318 add a new version of something called weighted p frame prediction which actually breaks CoreAVC codec 1.9.5 decoding.) is 1294 of x264.

i ll be thankful for the help..

regards

Glenn :)

Inspector.Gadget
6th December 2009, 06:29
Well, no, 1294 isn't "better". Newer versions are more efficient and more feature-rich. If you're going to use a decoder with a known incompatibility, either disable weightp or (I think) you can just use --weightp 1 (but test it to see if you get any artifacts). As far as MeGUI, Schra's new 1057 build (use search) works perfectly for me. Use these instructions to configure: http://forum.doom9.org/showpost.php?p=1347626&postcount=5079

forum king
6th December 2009, 06:36
Well, no, 1294 isn't "better". Newer versions are more efficient and more feature-rich. If you're going to use a decoder with a known incompatibility, either disable weightp or (I think) you can just use --weightp 1 (but test it to see if you get any artifacts). As far as MeGUI, Schra's new 1057 build (use search) works perfectly for me. Use these instructions to configure: http://forum.doom9.org/showpost.php?p=1347626&postcount=5079
o Right , i am gonna give it a shot then.
will trouble you again dear :P
god bless
Glenn :)


EDIT 1 :

well i did the following

downloaded 1056 and installed it
updated it fully ( it didnt update to 1057 , so didnt have to do anything )
later i got the 1360 build from x264.nl and replaced it in megui directory
tried to do a rip but it showed the b pyramid error >
so deselected the keep some b frames as reference.
also added --weightp 1 in my profile.

is it all correct ? why do some people say that new profiles have to be added.
and what about 1057 patched build that u were saying , couldnt find it actually.

what do you think about this :
http://forum.doom9.org/showthread.php?p=1349678 ( coz this didnt work with me :P )


EDIT 2 :

Damn the above 1056 bresulted in a crappy blocky result.
i have reverted back to 1051
the only change i have done is i have added the latest x264 in it
using unrestricted 2 pass for encoding > deselected b pyramid option in it
and added --weightp 1 in the commandline.
is this good enough ?
if not what should i do so that i can reap the benefits of new x264 builds as they are said to be faster and produce more quality.




Ok, Can anyone help? I need a link to download 1051...

Thanks.

LOL use this link
http://nchc.dl.sourceforge.net/project/megui/megui-stable/0.3.1.1028/megui-0_3_1_1028.exe

remove the existing megui from ur PC and install this update , dont touch the update servers or anything.
you ll be back to megui 1051 after update with 1183 jeebs build for x264 ( its good ).

_Sagan
6th December 2009, 17:47
Hi,
I have a problem with the encoding. I`m starting the job and it's about 10-20 seconds and my PC shutdown. The speed of the encoding was about 0,8-1,6 FPS, normally I got on this script over 45-50 FPS. I haven`t any protection that shutdown the PC, when the usage of CPU is 100% or the temperature is very high.
What can be the problem? It crashed on every avs scripts (no meaning short, easy or hard, long). Oh yeah, I would forget, first the PC freezes for 10 sec and then shutdown.

Thanks for help.

szabi
8th December 2009, 08:46
The problem is when i want to add those extra option you mentioned i have to enable the advanced settings checbox which adds a whole lot of extra options to the command line of x264.exe.
Probably one profile was already chosen, try to start your settings this way:
Config -> choose scratchpad -> advanced settings -> Misc -> click to default settings.
Now you can start your settings clearly.

You also mentioned some settings for DXVA settings, but are these really necessary? Because I have made .mkv with only a few option:
Originally Posted by log
program --profile high --level 4.1 --preset fast --pass 2 --bitrate 14400 --stats ".stats" --slow-firstpass --thread-input --output "output" "input"

When i play this file with media player classic - home cinema and check the taskmanager for the mpc-hc.exe process, is ee that i uses only a few % of cpu time. While with a .wvc file this can be up to say about 35%. CPU is a intel E8200 @ 3.2 GHz. So i'm sure it already uses DXVA without those extra settings.

MediaInfo say this about the video
Originally Posted by MediaInfo
Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4.1
Format settings, CABAC : Yes
Format settings, ReFrames : 2 frames
Muxing mode : Container profile=Unknown@4.1
Codec ID : V_MPEG4/ISO/AVC
Duration : 2h 25mn
Bit rate : 14.1 Mbps
Nominal bit rate : 14.4 Mbps
Width : 1 920 pixels
Height : 1 080 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.283
Stream size : 14.3 GiB (85%)
Writing library : x264 core 79 r1347 5ddd61b
Encoding settings : cabac=1 / ref=2 / deblock=1:0:0 / analyse=0x3:0x113 / me=hex / subme=6 / psy=1 / psy_rd=1.0:0.0 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=1 / 8x8dct=1 / cqm=0 / deadzone=21,11 / chroma_qp_offset=-2 / threads=3 / nr=0 / decimate=1 / mbaff=0 / constrained_intra=0 / bframes=3 / b_pyramid=0 / b_adapt=1 / b_bias=0 / direct=1 / wpredb=1 / wpredp=2 / keyint=250 / keyint_min=25 / scenecut=40 / rc_lookahead=30 / rc=2pass / mbtree=1 / bitrate=14400 / 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
Language : English

If you use in-bulid preset fast --ref 2 is used which will not brake DXVA compatibility.
Also if your average bitrate is 14400, probably the values of VBV can not reach the limit of DXVA.
But I think it is better to control VBV's rather than a bad surprise might occur after long time encoding.

EDIT: Fix by Zathor (http://forum.doom9.org/showthread.php?p=1350501#post1350501)

bye
szabi

Recalled2Life
9th December 2009, 23:20
Hello,

I have been using MeGUI for 6 Encodes now with no issues. Now I am receiving an error:

"Cannot find audio or video data. Ensure that your PIDs are set correctly in the Stream menu. Refer to the User Manual for details"

I am trying to make a D2V file as the first part of the Encoding process I use. The file(s) I am working with are .m2ts Blue-Ray files. I have MeGUI v 0.3.1.1056.

http://i46.tinypic.com/xarmmd.jpg

Inspector.Gadget
10th December 2009, 00:35
How did you rip your source files? Normal Blu-ray MPEG-2 - in - M2TS content works well with DGIndex. Try making your index file with DGIndex directly and setting audio to "Demux all tracks" to rule out any typos on the audio list.

Recalled2Life
10th December 2009, 02:45
Inspector.Gadget How did you rip your source files? Normal Blu-ray MPEG-2 - in - M2TS content works well with DGIndex. Try making your index file with DGIndex directly and setting audio to "Demux all tracks" to rule out any typos on the audio list.

I used AnyDVD HD's built in ripper to rip the file. After loading the file into DGIndex Version 1.5.7, I am receiving the same error. I looked at the online manual but I was unsure on how to set the PID's even after reading it and trying.
As stated I have not encountered this problem until a few days ago.
I have tried the previous .m2ts that worked and it does still. I have 3 different .m2ts files that all seem 2 to be doing this.

Inspector.Gadget, thanks for the reply:thanks:

Inspector.Gadget
10th December 2009, 03:09
Are you sure the M2TS in question is MPEG-2 and not VC-1 or H.264?

Recalled2Life
10th December 2009, 03:17
Are you sure the M2TS in question is MPEG-2 and not VC-1 or H.264?
It is VC-1. Is this bad?

Video #1
ID : 4113 (0x1011)
Menu ID : 1 (0x1)
Format : VC-1
Format profile : AP@L3
Duration : 2h 58mn
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate : 23.976 fps
Colorimetry : 4:2:0
Scan type : Progressive

Inspector.Gadget
10th December 2009, 03:44
You can't use DGIndex for VC-1. You must use DirectShowSource() [least preferred], Haali's DSS2() [better], ffmpegsource() [better], or Neuron2's DGIndexNV and DGMultiSource() [most flexible with force film and two hardware deinterlacers, but requires a recent NVIDIA graphics card and a nominal license fee].

Recalled2Life
10th December 2009, 05:20
You can't use DGIndex for VC-1. You must use DirectShowSource() [least preferred], Haali's DSS2() [better], ffmpegsource() [better], or Neuron2's DGIndexNV and DGMultiSource() [most flexible with force film and two hardware deinterlacers, but requires a recent NVIDIA graphics card and a nominal license fee].

Sorry but I'm rather new at this so can you please elaborate on this further. ffmpegsource()

Inspector.Gadget
10th December 2009, 05:25
It's an avisynth plugin, use search to get the relevant thread. In MeGUI, you would call it (in its most basic form) in the AVS text area as:

LoadPlugin("FFMS2.dll")

FFVideoSource("Something.m2ts")

N.B.: Won't work with some weird field stuff in VC-1, but for 23.976fps progressive you'll be fine.

rudiev
11th December 2009, 15:39
I see a lot of users in trouble with X264 parameters.
Why not an option which completely disable the Megui codec settings to prevent the incompatibility with the often updated X264 builds?

Isn't this accomplished by just NOT enabling the 'advanced setting' checkbox in the encoder settings config windows?
With 'advanced settings' enabled i get the following:

program --profile high --level 4.1 --preset slow --tune film --pass 2 --bitrate 14400 --stats ".stats" --slow-firstpass --thread-input --deblock -1:-1 --bframes 3 --b-adapt 2 --direct auto --b-bias 0 --scenecut 40 --ref 8 --vbv-bufsize 50000 --vbv-maxrate 50000 --rc-lookahead 60 --aq-mode 1 --aq-strength 1.0 --merange 16 --me umh --subme 10 --partitions all --trellis 2 --psy-rd 1.0:0 --no-dct-decimate --output "output" "input"


If i uncheck the advanced setting checkbox i get the following:

program --profile high --level 4.1 --preset slow --tune film --pass 2 --bitrate 14400 --stats ".stats" --slow-firstpass --thread-input --output "output" "input"

This are only a few x264.exe presets, no special settings from megui, allthough some extra settings which are set with the 'advanced settings' checkbox enabled could be default and also enabled.

Nightshiver
11th December 2009, 18:48
It doesn't matter if you uncheck it. Those options are still enabled, you just can't see them.

Zathor
12th December 2009, 01:03
It doesn't matter if you uncheck it. Those options are still enabled, you just can't see them.

At least in the unpatched 1057 this is wrong. Only the parameters you can see will be passed to the encoder.

Carpo
14th December 2009, 20:26
You could actually use
--bitrate 1309 --b-adapt 2 --ref 4 --partitions all --me umh --direct auto --output "output" "input"
which would be the same as your settings.

@nurbs

so your saying something like this?

x264.exe --profile high --level 4.1 --preset veryslow --tune film --pass 2 --bitrate 9132 --stats ".stats" --thread-input --b-adapt 2 --ref 4 --partitions all --me umh --direct auto -o D:\test.mkv D:\gran.torino.avs 1280x720

Obviously changing the bitrate and tuning for animation when i do an anime.

All this is being done from cmdline atm as megui and dgindenv don't play nice and i have a few vc-1 movies to do

forum king
15th December 2009, 09:57
hey folks :)

ummm.. i have run into another freaky scenario:(
i donno from yesterday when i am trying running megui it just wont run..
although the megui.exe process is running in task manager but there is nothing on the desktop no user interface whatsoever

i didnt do anything no updates no upgrdaes no windows stuff
only installed and uninstalled limewire thats it then turned the system off next day whenh i opened it this started to happen.

any clues
also which version of .net frame work is required for megui i mean 2 or 2 with sp1 of 3 or 3.5..
i am thinking of reinstalling .net as well.

please guide

SeeChestlickRun
15th December 2009, 19:13
I've looked at several pages trying to find similar problem I have right now, but I can't find anything.

Everytime I start a x264 encoding, MeGUI will reach to 100 percent and stop. It never finish... why?

http://i388.photobucket.com/albums/oo329/Jhcheslik/MeGUI/untitled.jpg

Old x264 perhaps?

rapscallion
16th December 2009, 22:14
Did you look in the log ?

ariefjuga
17th December 2009, 11:53
hi, i encounter some problem while using megui
i don't know exactly what the problem is but i think its related to codec or something (like i said my friend, i dont know exactly :) )

this is the log of my job


[Error] An error occurred
-[NoImage] Exception message
--[NoImage] Error initializing audio stream decompression:
--[NoImage] The requested conversion is not possible.
--[NoImage] Check to make sure you have the required codec.
-[NoImage] Stacktrace
--[NoImage] at MeGUI.AviSynthClip..ctor(String func, String arg, AviSynthColorspace forceColorspace, AviSynthScriptEnvironment env)
--[NoImage] at MeGUI.AviSynthAudioEncoder.encode()
-[NoImage] Inner exception: null



its said that apparently i don't have the required codec, but i already install klite mega codec for it. And again it doesn't work.

i already try to change the audio encoder, but its just the same. the error still appear.

Carpo
17th December 2009, 12:13
klite is NOT a good thing to have installed so i hear, most use cccp or ffdshow

ariefjuga
17th December 2009, 12:40
klite is a good thing to have installed so i hear, most use cccp or ffdshow

so, there should be no problem isn't it? but why it's not working? :confused:

nurbs
17th December 2009, 12:47
I think Carpo made a typo. It should be "klite is not at good thing to have installed". Most people here would recommend against using codec packs in general and prefer haali splitter + ffdshow.

Carpo
17th December 2009, 14:39
indeed i did make a typo, never post before you have had your first coffee ;) fixed now though

ariefjuga
17th December 2009, 15:47
indeed i did make a typo, never post before you have had your first coffee ;) fixed now though

then what do you suggest me to do? uninstal it?

Carpo
17th December 2009, 19:33
yes and install cccp or ffdshow

_Sagan
17th December 2009, 21:46
Yo,
i wrote a few days ago:
Hi,
I have a problem with the encoding. I`m starting the job and it's about 10-20 seconds and my PC shutdown. The speed of the encoding was about 0,8-1,6 FPS, normally I got on this script over 45-50 FPS. I haven`t any protection that shutdown the PC, when the usage of CPU is 100% or the temperature is very high.
What can be the problem? It crashed on every avs scripts (no meaning short, easy or hard, long). Oh yeah, I would forget, first the PC freezes for 10 sec and then shutdown.

I resolved the problem with the shutdown of the PC, but could someone tell my why the speed of the encoding is by far slower than it normally was.
Come on, guys.
I`m counting on you.

Carpo
17th December 2009, 23:29
sounds like a hardware issue to me, something is getting upset, turns itself off or freezes so windows thinks its not there and shuts the pc down

_Sagan
18th December 2009, 00:36
Thanks Carpo,
I think maybe you have right, because recently I changed my CPU from a old Pentium 4 to a Dual-Core. I wouldn`t have even though that this could be a hardware issue. I will check the BIOS and see if everything is fine.

deng17
18th December 2009, 08:53
I have a problem when playing encoded XVIDs to my DVD player. I don't know if my player or the encoding is at fault.

I've turned off QPel and GMC. I've only turned on Packed Bitstream and Trellis Quant. I'm also sure that the audio is compatible. It's in LAME MP3 downmixed to Stereo.

Here's the problem. The video plays, yes, but it skips to the next video, which also skips, after 5 seconds.

Recalled2Life
19th December 2009, 00:31
Yo,
i wrote a few days ago:


I resolved the problem with the shutdown of the PC, but could someone tell my why the speed of the encoding is by far slower than it normally was.
Come on, guys.
I`m counting on you.
I just had this happen to me and it turned out to be the RAM. As soon as I put some new sticks in, the problem stop. I would give this a try.

Carpo
19th December 2009, 17:45
I am trying to back up my copy of mock the week too hot for tv 2, when making the avs and getting megui to scan the source its says

source type: hybrid film/interlaced. mostly interlaced
field order: top field first
deinterlace: tivtc

and it gives me this as the avs

DGDecode_mpeg2source("D:\too.hot.for.tv.2-bits.that.wont.be.broadcast.d2v", info=3)
ColorMatrix(hints=true, interlaced=true, threads=0)
tfm(order=1).tdecimate(hybrid=3)

when it has encoded the file i can still see some interlaced frames, mainly when peope are speaking or moving their hands, looks like they have lines going through their teeth and hands. Is megui not picking everything up or is this an issue with the pluggin? Do i need to change the vaules in the avs? if so what do people suggest?

heffalump
20th December 2009, 18:16
MeGUI prompted me for several updates, a couple of days ago. After updating, I am having some corrupted video problems. The original videos all play, without any error. After running through MeGUI for resizing and x264 encoding, the video looks corrupted.

The original files are 1920x1080 h.264 videos, played back using CoreAVC 1.9.5.

Here's the AviSynth script that I'm using...
DirectShowSource("E:\BDRIP\Firefly\01x05\T2_Video - .mkv", audio=false)
LanczosResize(1280,720)
ConvertToYV12()


Attached is my MeGUI log and a screen shot.

Lastly, here's the product of the above...
http://rapidshare.com/files/323557425/corrupted_video.mp4.html

Any assistance would be appreciated! Thanks! :)

nurbs
20th December 2009, 18:33
CoreAVC 1.9.5 has a bug (unsupported feature) and can't play files encoded with --weightp 2, which is the default in the current x264 versions, correctly. You can upgrade to CoreAVC 2.0 (if you don't mind paying), use a different decoder (ffdshow for instance) or encode with --weightp 1.

I downloaded your file and it plays fine.
Personally I'd recommend reducing the number of reference frames you use to 9 so you can ensure compatibility with standalone devices.

lnatan25
20th December 2009, 18:57
I think any value of --weightp that is not 0 will produce visual artifacts in CoreAVC < 2.0. :\

heffalump
20th December 2009, 19:51
CoreAVC 1.9.5 has a bug (unsupported feature) and can't play files encoded with --weightp 2, which is the default in the current x264 versions, correctly. You can upgrade to CoreAVC 2.0 (if you don't mind paying), use a different decoder (ffdshow for instance) or encode with --weightp 1.

I downloaded your file and it plays fine.
Personally I'd recommend reducing the number of reference frames you use to 9 so you can ensure compatibility with standalone devices.

I think any value of --weightp that is not 0 will produce visual artifacts in CoreAVC < 2.0. :\

You guys were right! It was the "P-frame Weighted Prediction." I disabled that and everything is right as rain, again. I've been trying to figure that problem out for several hours. I never would've thought to steer clear of the default values.

Thank you for the speedy replies! Thank you, both! :D

Kraise
20th December 2009, 21:32
I just updated megui to 1059 from 1030 or so, I'd been using the old version for a long time, quick simple noob question for the new version (I couldn't find the answer anywhere)

What do tunings do exactly? And what is this slider thing? If I leave the slider in the middle and use advance settings will it overide it? lol

nurbs
20th December 2009, 22:02
What do tunings do exactly? And what is this slider thing?
"x264 --fullhelp" will show you the description of the presets and tunings. Other command line options are applied after the presets and tunings and thus override them. Level flag restricts presets and tunings (e.g. by lowering number of reference frames), but not custom options.

There are also plenty of threads in the AVC subforum.

Dark Shikari
21st December 2009, 02:34
I think any value of --weightp that is not 0 will produce visual artifacts in CoreAVC < 2.0. :\--weightp 1 will work fine.

consultant
23rd December 2009, 18:51
Newbie here coming from using Handbrake and Staxrip and having frustrations with them so moved on to MeGui. I just want simple. In Handbrake and Staxrip I just had to set a few settings. Mainly I focused on cRF (setting it at 20 for very high quality). In the one-click encoding on MeGui (which appears to be the closest equivalent to these other two programs), I don't see a way to set -cRF? How do I set it?

Thanks!

panark
24th December 2009, 12:34
I'm using MeGUI 0.3.1.1056 with Nero Digital AAC Encoder 1.3.3.0.

Is it recommended/allowed to manually update Nero encoder to the latest version (1.5.1.0)?
Is MeGUI compatible with this latest version of Nero encoder?

Thanx in advance.

Alf Bundy
24th December 2009, 13:03
Well, I don't know with the old rev 1056.
But I've just downloaded the latest NeroAACenc (http://www.nero.com/eng/downloads-nerodigital-nero-aac-codec.php) and it works fine with the latest Megui 0.3.1.1059 (http://85.230.118.136/showthread.php?t=151159) ...

tebasuna51
24th December 2009, 18:35
NeroAacEncoder v1.5.1.0 have the same parameters than precedent version, then work without problems with MeGUI, BeHappy, eac3to, BeLight, ...

consultant
24th December 2009, 18:48
I'm wondering if MeGui is capable of this and if so, where is the documentation that explains exactly how to do it?

I've got a whole bunch of music video DVDs already ripped into chapter VOB files. I want to queue them all up to be transcoded. I want them to all be transcoded using the same encoder setting which produced a hiqh quality file that is about 1/4th the size of the VOB (I've found this equates in other programs to a cRF=10, Speed=Medium). I want meGui to automatically encode the best audio track, so if there is a stereo track and a 5.1 track, I want it to include the 5.1 track not the stereo track. I want to just load a profile and point at all the VOBs to add to the queue and hit start and let it chug away for the day.

Is this possible? I think the audio encode choice may be the sticking point. My guess is I can only do this one DVD at a time as the audio tracks vary from DVD to DVD so I assume I need to add all the VOBs to the queue for one DVD, set the audio settings and then do the same for the next DVD?

quantum5uicid3
24th December 2009, 20:37
I'm wondering if MeGui is capable of this and if so, where is the documentation that explains exactly how to do it?

I've got a whole bunch of music video DVDs already ripped into chapter VOB files. I want to queue them all up to be transcoded. I want them to all be transcoded using the same encoder setting which produced a hiqh quality file that is about 1/4th the size of the VOB (I've found this equates in other programs to a cRF=10, Speed=Medium). I want meGui to automatically encode the best audio track, so if there is a stereo track and a 5.1 track, I want it to include the 5.1 track not the stereo track. I want to just load a profile and point at all the VOBs to add to the queue and hit start and let it chug away for the day.

Is this possible? I think the audio encode choice may be the sticking point. My guess is I can only do this one DVD at a time as the audio tracks vary from DVD to DVD so I assume I need to add all the VOBs to the queue for one DVD, set the audio settings and then do the same for the next DVD?

yes, it's possible.

here's roughly how, i dunno if there's documentation on doing exactly what you're doing.
http://mewiki.project357.com/wiki/MeGUI/Basic_DVD_Ripping_Guide

consultant
24th December 2009, 20:53
I'll look at that documentation but it says in bold:

It does not cover:

* Using any of the automated features of MeGUI for video encoding.

I want to just load a profile I created with all the settings, select all the VOBs, and hit "start"

quantum5uicid3
24th December 2009, 20:59
try a different program

pdexdee
25th December 2009, 14:36
i use winxp sp3 but won't work and latest neroaac

dolphinjet
25th December 2009, 22:57
Merry x'mas everyone!

---

Recently,
I noted a problem with build 1056 (after a long time without encoding)

The megui interface become unresponsive immediately after starting the queue,
sometimes it will become responsive again after finishing the first task,
sometimes it will not even start the first task,
sometimes it crashes firefox v3.5.6 instead of itself (when megui is responsive, the two apps seems to be fighting with each other)

I think I should modify to a simpler description.

megui would crash the topmost application.

I rolled back windows to a earlier installation but the problem still persists.

I am using winXP SP3
I have re-install megui for a few times already. I've also tested build 1058 but got errors so reverted back to stable build.

megui settings:
priority low
disabled open progress window

pdexdee
26th December 2009, 16:50
as first: Merry x'mas to all people here!
what means:
when i put file says:Unable to render the file. You probably don't have the correct filters installed ....
but when i put other file first create dgindex and all other work correct,what u suggest to me?
i have version 3.1.1051 installed.
would be good to fine version with all profiles!?
i have windows xp sp3 also k lite codec full pack!

ariefjuga
27th December 2009, 12:13
just want to ask why my megui say there is no update available. But, in above i see there is people who already have the latest version of megui. My megui still 3.1.1051. Is it because there is not yet any stable upgrade version?

XhmikosR
27th December 2009, 12:22
@ariefjuga: Use this (http://forum.doom9.org/showthread.php?t=151159) build.

ariefjuga
27th December 2009, 12:36
@ariefjuga: Use this (http://forum.doom9.org/showthread.php?t=151159) build.

MeGUI: Patched Build? :confused:

Is it some kind of new MeGUI?

XhmikosR
27th December 2009, 12:42
It's the same old MeGUI except that it should work much better since Zathor has fixed a lot of bugs. Read through that topic for more details.

ariefjuga
28th December 2009, 11:28
do i have to uninstall my old megui first?

rapscallion
1st January 2010, 20:09
do i have to uninstall my old megui first?
No, you can install to a different dir and then run either ver.

FlezZ
1st January 2010, 21:00
I don't know if this is a bug but it's definitely very weird behaviour.

I set a default output directory in the settings and then enqueued 2 separate passes of encodings and started the queue.
Both of processes then started at once. However, if I removed the default directory, the processes start in sequence.

Anyone else have this?

Edit:

Ok, I don't know if these things are actually connected to each other, but I am still having the problem with the processes starting at once.
There's an error for the second encoding process in the queue:

-[Error] An error occurred: x264 [error]: ratecontrol_init: can't open stats file
-[Error] An error occurred: x264 [error]: x264_encoder_open failed

This is obviously the result of the problem, not the cause, because the 2 encoding processes start at once, and the second pass encode cant open the stats file as the first one is already using it.

Zathor
3rd January 2010, 10:52
I set a default output directory in the settings and then enqueued 2 separate passes of encodings and started the queue.
Both of processes then started at once. However, if I removed the default directory, the processes start in sequence.


Which build of MeGUI do you use?

FlezZ
3rd January 2010, 12:07
Up to this point, the newest I believe: 0.3.1.1060

Dogway
3rd January 2010, 14:17
Ive been having problems with megui since I updated the driver of the chipset on my laptop (I was having blue screens). It's a Mobile PM45 Express Chipset.
Im not totally sure that's the problem, the fact is I dont see why MeGUI should have a problem with this. I already re-installed and updated to the latest version.

I attach a picture with the problem (the stats are not showing):

http://img300.imageshack.us/img300/860/megui.th.gif (http://img300.imageshack.us/img300/860/megui.gif)

Zathor
3rd January 2010, 18:45
Ive been having problems with megui since I updated the driver of the chipset on my laptop (I was having blue screens). It's a Mobile PM45 Express Chipset.
Im not totally sure that's the problem, the fact is I dont see why MeGUI should have a problem with this. I already re-installed and updated to the latest version.


Please post your log and the avs file.

Dogway
3rd January 2010, 19:20
The avs is whatever, just a load call. This time I just used this as a dummy:

ImageSource ("D:\Rip\vlgame008106.jpg")
trim(0,5000)
Addborders(0,1,0,0)
ConvertToYV12()

*I aborted the encoding

[Warning] Log
-[Information] Versions
--[NoImage] MeGUI Version : 0.3.1.1060
--[NoImage] OS : Windows XP Professional x86 SP2 (5.1.131072.2600)
--[NoImage] Latest .Net Framework installed : 3.5 (3.5.30729.01)
--[NoImage] Avisynth Version : 2.5.8.5
-[Warning] Log for job1 (video, si.avs -> )
--[Information] [03/01/2010 18:14:35] Started handling job
--[Information] [03/01/2010 18:14:35] Preprocessing
--[NoImage] Job commandline: "C:\Archivos de programa\megui\tools\x264\x264.exe" --profile high
--preset slower --tune touhou --pass 1 --bitrate 3000 --stats "D:\Rip\si.stats" --slow-firstpass --thread-input
--threads 2 --scenecut 30 --ref 8 --aq-strength 1.0 --sar 876:875 --output NUL "D:\Rip\si.avs"
--[Information] [03/01/2010 18:14:36] Encoding started
--[NoImage] Standard output stream
--[NoImage] Standard error stream
--[Warning] Deleting aborted output
---[NoImage] Delete aborted ouptut set: True
---[NoImage] File to delete
---[Warning] Error deleting file
----[NoImage] Exception message: La ruta de acceso no tiene un formato válido.
----[NoImage] Stacktrace
-----[NoImage] en System.IO.Path.NormalizePathFast(String path, Boolean fullCheck)
-----[NoImage] en System.IO.Path.NormalizePath(String path, Boolean fullCheck)
-----[NoImage] en System.IO.Path.GetFullPathInternal(String path)
-----[NoImage] en System.IO.File.Delete(String path)
-----[NoImage] en MeGUI.core.gui.JobWorker.markJobAborted()
----[NoImage] Inner exception: null
--[Information] [03/01/2010 18:14:54] Job completed
--[Information] [03/01/2010 18:14:54] Current job was aborted

Max_Cady
11th January 2010, 11:40
crop( 2, 12, -2, -12)

Spline36Resize(720,384) # Spline36 (Neutral)

import("c:\program files\avisynth 2.5\plugins\LSFmod.v1.9.avs")

LSFMod(defaults="fast", Lmode=1, Soothe=false, strength=200)

[Error] Log
-[Information] Versions
--[NoImage] MeGUI Version : 0.3.1.1061
--[NoImage] OS : Windows XP Professional x86 SP3 (5.1.196608.2600)
--[NoImage] Latest .Net Framework installed : .x (..)
--[NoImage] Avisynth Version : 2.5.7.0
-[Information] Log for job1 (video, VTS_07_1.avs -> )
--[Information] [11.01.2010 00:39:00] Started handling job
--[Information] [11.01.2010 00:39:00] Preprocessing
--[NoImage] Job commandline: "C:\Program Files\megui\tools\xvid_encraw\xvid_encraw.exe" -i "C:\Documents and Settings\Unforgiven\Desktop\BUKOWSKİ\VTS_07_1.avs" -pass1 "C:\Documents and Settings\Unforgiven\Desktop\BUKOWSKİ\VTS_07_1.stats" -bitrate 1937 -kboost 100 -chigh 30 -clow 15 -overhead 0 -turbo -max_key_interval 250 -nopacked -vhqmode 4 -qmatrix "C:\Documents and Settings\Unforgiven\Desktop\cx\matrix\heini_mr.xcm" -imin 1 -pmin 1 -max_bframes 1 -bvhq -bquant_ratio 162 -bquant_offset 0 -bmin 1 -par 1:1 -threads 1
--[Information] [11.01.2010 00:39:06] Encoding started
--[NoImage] Standard output stream
---[NoImage] xvid_encraw - raw mpeg4 bitstream encoder written by Christoph Lampert 2002-2003
---[NoImage] Tot: enctime(ms) =18656528.00, length(bytes) = 1828671656
---[NoImage] Avg: enctime(ms) = 138.88, fps = 7.20, length(bytes) = 13613
---[NoImage] I frames: 792 frames, size = 72402/ 57342540, quants = 2 / 2.00 / 2
---[NoImage] P frames: 67152 frames, size = 20913/ 1404396207, quants = 2 / 2.00 / 2
---[NoImage] B frames: 66134 frames, size = 5548/ 366930895, quants = 3 / 3.00 / 3
---[NoImage] N frames: 252 frames, size = 7/ 2014
--[NoImage] Standard error stream
---[NoImage] Trying to retrieve width and height from input header
---[NoImage] xvid [info]: Avisynth detected
---[NoImage] xvid [info]: Input colorspace is YV12
---[NoImage] xvid [info]: Input is 720 x 384, 25.000fps (25/1), starting from frame 0
---[NoImage] xvid [info]: Number of frames to encode: 134330, Bitrate = 1937kbps
---[NoImage] xvid [info]: xvidcore build version: xvid-1.2.2
---[NoImage] xvid [info]: Bitstream version: 1.2.2
---[NoImage] xvid [info]: Detected CPU flags: ASM MMX MMXEXT SSE SSE2 TSC
---[NoImage] xvid [info]: Detected cpus = 2, threads requested = 1, threads in use = 1
--[Information] [11.01.2010 05:50:23] Postprocessing
---[Information] Deleting intermediate files
--[Information] [11.01.2010 05:50:24] Job completed
-[Error] Log for job2 (video, VTS_07_1.avs -> VTS_07_1.avi)
--[Information] [11.01.2010 05:50:25] Started handling job
--[Information] [11.01.2010 05:50:25] Preprocessing
--[NoImage] Job commandline: "C:\Program Files\megui\tools\xvid_encraw\xvid_encraw.exe" -i "C:\Documents and Settings\Unforgiven\Desktop\BUKOWSKİ\VTS_07_1.avs" -pass2 "C:\Documents and Settings\Unforgiven\Desktop\BUKOWSKİ\VTS_07_1.stats" -bitrate 1937 -kboost 100 -chigh 30 -clow 15 -overhead 0 -max_key_interval 250 -nopacked -vhqmode 4 -qmatrix "C:\Documents and Settings\Unforgiven\Desktop\cx\matrix\heini_mr.xcm" -imin 1 -pmin 1 -max_bframes 1 -bvhq -bquant_ratio 162 -bquant_offset 0 -bmin 1 -par 1:1 -threads 1 -avi "C:\Documents and Settings\Unforgiven\Desktop\BUKOWSKİ\VTS_07_1.avi"
--[Information] [11.01.2010 05:50:35] Encoding started
--[Error] An error occurred: xvid [error]: Couldn't init AVI file for writing (C:\Documents and Settings\Unforgiven\Desktop\BUKOWSKİ\VTS_07_1.avi)
--[NoImage] Standard output stream: xvid_encraw - raw mpeg4 bitstream encoder written by Christoph Lampert 2002-2003
--[NoImage] Standard error stream
---[NoImage] Trying to retrieve width and height from input header
---[NoImage] xvid [info]: Avisynth detected
---[NoImage] xvid [info]: Input colorspace is YV12
---[NoImage] xvid [info]: Input is 720 x 384, 25.000fps (25/1), starting from frame 0
---[NoImage] xvid [info]: Number of frames to encode: 134330, Bitrate = 1937kbps
---[NoImage] xvid [info]: xvidcore build version: xvid-1.2.2
---[NoImage] xvid [info]: Bitstream version: 1.2.2
---[NoImage] xvid [info]: Detected CPU flags: ASM MMX MMXEXT SSE SSE2 TSC
---[NoImage] xvid [info]: Detected cpus = 2, threads requested = 1, threads in use = 1
---[NoImage] AVIOutputFile::Init Error: Unable to open file "C:\Documents and Settings\Unforgiven\Desktop\BUKOWSKY\VTS_07_1.avi" for write: Sistem belirtilen yolu bulamıyor.
--[Information] [11.01.2010 05:50:45] Job completed


any help guys.:confused:

stax76
11th January 2010, 12:45
---[NoImage] AVIOutputFile::Init Error: Unable to open file "C:\Documents and Settings\Unforgiven\Desktop\BUKOWSKY\VTS_07_1.avi" for write: Sistem belirtilen yolu bulamıyor.

Please translate.

Max_Cady
11th January 2010, 12:52
system can not find the path specified

sorry about that.

LigH
11th January 2010, 14:08
Compare "BUKOWSKİ" with "BUKOWSKY" ... seems that some system function tried to substitute a regional Unicode character with the nearest possible ANSI character.

Avoid accented characters in file and directory names. I believe the "İ" is the problem. (Is that turkish?)

tebasuna51
11th January 2010, 14:10
system can not find the path specified
Seems a bug with chars:
...
-avi "C:\Documents and Settings\Unforgiven\Desktop\BUKOWSKİ\VTS_07_1.avi"
...
Error: Unable to open file "C:\Documents and Settings\Unforgiven\Desktop\BUKOWSKY\VTS_07_1.avi"

Until solve the problem try using paths with international chars only.

stax76
11th January 2010, 14:22
What is a international char? :)

Max_Cady
11th January 2010, 14:42
@LigH

Never before encountered such an error.Thanks for advice mate i try later and yup Turkish caracter.

MrVideo
11th January 2010, 19:37
MeGUI version 0.3.1.1056

When presented with NTSC DVD 4:3 video, MeGUI wants to use a SAR value of 28481:31250 with x264. I do not know how MeGUI comes up with that value, as that would translate to 656.20224 instead of 640. It seems as if it is working with 704 instead of 720. Even then the SAR would be 10:11, to get exactly to the required 640. For 720x480, the SAR should be 8:9.

I'm not cropping the video.

Any idea why the SAR is wrong?

Thanks

MrVideo
11th January 2010, 19:40
What is a international char? :)

I'm guessing characters that do not have the special emphasis above them.

Zathor
11th January 2010, 22:07
MeGUI version 0.3.1.1056

When presented with NTSC DVD 4:3 video, MeGUI wants to use a SAR value of 28481:31250 with x264. I do not know how MeGUI comes up with that value, as that would translate to 656.20224 instead of 640. It seems as if it is working with 704 instead of 720. Even then the SAR would be 10:11, to get exactly to the required 640. For 720x480, the SAR should be 8:9.

I'm not cropping the video.

Any idea why the SAR is wrong?

There are a few defined constants for DAR in MeGUI:
ITU16x9PAL = 1.823361
ITU4x3PAL = 1.367521
ITU16x9NTSC = 1.822784
ITU4x3NTSC = 1.367088

So your 4:3 NTSC source has a DAR value of 1.367088.

SAR will be calculated as DAR * vres / hres and that's 28481:31250 in this case.

But I am only repeating the internal code - I do not understand DAR and SAR calculations fully. It would be great if someone can point me to a site where this particullary problem is described in more detail and tell me which value is correct in this case - the one from MeGUI or MrVideo.

stax76
11th January 2010, 22:15
You are lucky you are german so you can read Brother John's Encodingwissen. His site and support helped me a lot building image related things in StaxRip.

MrVideo
11th January 2010, 22:38
So your 4:3 NTSC source has a DAR value of 1.367088.

SAR will be calculated as DAR * vres / hres and that's 28481:31250 in this case.

Is that: (DAR * vres) / hres
or: DAR * (vres / hres)

I know, they're both the same :cool:

But I am only repeating the internal code - I do not understand DAR and SAR calculations fully. It would be great if someone can point me to a site where this particullary problem is described in more detail and tell me which value is correct in this case - the one from MeGUI or MrVideo.

DAR is the Display Aspect Ratio

I forget exactly what SAR abbreviates from.

In the case of NTSC and PAL, the aspect ratios are 4:3 (1.333333) or 16:9 (1.777777). They are not what is listed. With your formula, it makes sense that the SAR comes out wrong.

Filling in the formula with the correct values results in: 1.333333 * 480 / 720 = 639.99984 / 720 = .888888666 = 8/9

The better, and more accurate way to get the SAR is not to do the math on the 4:3 first but to do: ((vres / 3) * 4) / hres

That will result in exactly .888888888888, or 8/9

Make sense?

Mizzle
12th January 2010, 09:08
Hi, I just converted my very first avi file to an mkv to test it out on Youtube.
Are there any recommended settings for the best quality or anything to get in HD there...?
(btw, atm I'm getting the 'An error occurred...' message for that video aswell)

Zathor
12th January 2010, 21:21
In the case of NTSC and PAL, the aspect ratios are 4:3 (1.333333) or 16:9 (1.777777). They are not what is listed. With your formula, it makes sense that the SAR comes out wrong.

Filling in the formula with the correct values results in: 1.333333 * 480 / 720 = 639.99984 / 720 = .888888666 = 8/9

The better, and more accurate way to get the SAR is not to do the math on the 4:3 first but to do: ((vres / 3) * 4) / hres

That will result in exactly .888888888888, or 8/9

Make sense?

Please read here:
http://forum.doom9.org/showthread.php?s=&threadid=42708

Dogway
14th January 2010, 01:11
Just bumping my question. Does anybody know how to make megui show statistics while encoding? Im using the last x264 build.

Ruriko
14th January 2010, 01:52
Does anyone know how I can make megui run on linux?

nurbs
14th January 2010, 10:53
Just bumping my question. Does anybody know how to make megui show statistics while encoding? Im using the last x264 build.
x264 doesn't show any statistics during encoding apart from bitrate, which MeGUI indicates with the projected filesize, and the encoding speed, which MeGUI already shows.

Dogway
14th January 2010, 20:10
x264 doesn't show any statistics during encoding apart from bitrate, which MeGUI indicates with the projected filesize, and the encoding speed, which MeGUI already shows.

Yes, that's why I post here, MeGUI doesn't show projected filesize, nor encoding speed.

Alf Bundy
14th January 2010, 20:22
Yes it does ... Unless you unchecked "open progress window" in Options -> Settings.

Dogway
14th January 2010, 20:41
http://img5.imageshack.us/img5/860/megui.gif

I posted this on previous page showing the problem. Everything is blank.

Zathor
14th January 2010, 20:55
Do you have the problem with other tools in MeGUI as well (like converting an audio file)?

Please post the log and execute the commandline in a cmd manually. Do you see a progress there?

Dogway
14th January 2010, 22:08
Yes, audio is ok. The log is posted in page 259, and yes command line shows progress, eta, kbps, everything.

Now I dont know if the problem is x264, or MeGui which isn't capable of translating the (last build) x264 statistics.

Zephyr_Truesdale
15th January 2010, 02:31
I'm having a problem encoding an old video with x264 and I haven't had a problem before but I think its something that the current version 0.3.1.1061 that's the problem.

nurbs
15th January 2010, 08:39
Will you tell us what the problem is or do we have to guess?

Nikolausr
16th January 2010, 11:30
Is there a way to get logs be more informative?

[Error] Log
-[Information] Versions
--[NoImage] MeGUI Version : 0.3.1.1051
--[NoImage] OS : Windows Seven x64 (6.1.0.7600)
--[NoImage] Framework used : 2.0 SP1 (2.0.50727.4927)
-[Information] Hardware
--[NoImage] CPU : Pentium(R) Dual-Core CPU E6300 @ 2.80GHz
-[Error] Log for job1 (video, VTS_05_1.avs -> )
--[Information] [1/16/2010 2:28:02 AM] Started handling job
--[Information] [1/16/2010 2:28:02 AM] Preprocessing
--[NoImage] Job commandline: "C:\Program Files (x86)\megui\tools\x264\x264.exe" --profile high --pass 1 --bitrate 1000 --stats "H:\Misc\Ripped Movies\IDIOCRACY_SIDEA\VIDEO_TS\VTS_05_1.stats" --ref 1 --no-mixed-refs --b-adapt 2 --b-pyramid --direct auto --deblock -1:-1 --subme 2 --trellis 0 --partitions none --me dia --thread-input --sar 1:1 --output NUL "H:\Misc\Ripped Movies\IDIOCRACY_SIDEA\VIDEO_TS\VTS_05_1.avs"
--[Information] [1/16/2010 2:28:03 AM] Encoding started
--[Error] An error occurred: x264 [error]: could not open input file 'H:\Misc\Ripped Movies\IDIOCRACY_SIDEA\VIDEO_TS\VTS_05_1.avs'
--[NoImage] Standard output stream
--[NoImage] Standard error stream
--[Information] [1/16/2010 2:28:03 AM] Job completed

Zathor
16th January 2010, 12:26
What do you think is missing?

Zathor
16th January 2010, 12:35
Yes, audio is ok. The log is posted in page 259, and yes command line shows progress, eta, kbps, everything.

Now I dont know if the problem is x264, or MeGui which isn't capable of translating the (last build) x264 statistics.
Because you are the only one (at least that I know) I assume that your client / software is the problem. One thing that I have noticed is that you are using Windows XP SP2. Please update to SP3 - I do not believe that this is the problem, but the support for SP2 from Microsoft will end soon (ok, 13th of July...) and there wont be security updates for SP2 anymore. Regarding the problem you could try to use other builds of x264 like the unpatched builds from x264.nl or other patched builds like from here http://komisar.gin.by/.

Dogway
16th January 2010, 12:49
Thanks for the feedback I will try to fiddle with it. About OS, I think that everything above SP2 is overdo, if I update I would to linux, but once where software pushes me to abandon XP.

msaadn
16th January 2010, 21:44
Updated to MeGUI 0.3.2.0
Win Vista Ultimate SP2

When I load an avisynth script MeGUI freezes then responds after a long time with an error.

Avisynth Script error:
DirectShowSource : Timeout waiting for graph to start.
(C:\video.avs, line1)

Taddeusz
17th January 2010, 01:58
I seem to be having a problem with the anamorphic encoding. The calculations seem to be slightly off. Not by a whole lot but by enough to be noticeable. I'm comparing MeGUI to Handbrake. MeGUI definitely gives me the better quality video but Handbrake calculates the cropped anamorphic AR properly.

I have a 16:9 DVD video that I'm cropping to 720x368. The proper display width should be 853 but MeGUI is calculating it as 875. So the video appears a bit shorter than it really should be. I can correct this by using mp4box, but I shouldn't have to.

Any way we can get this fixed? Thank you.

Inspector.Gadget
17th January 2010, 02:01
That's not actually incorrect, MeGUI has just picked sides in the ITU debate...

Taddeusz
17th January 2010, 02:02
That's not actually incorrect, MeGUI has just picked sides in the ITU debate...

Regardless, the output looks wrong in any player compared to the same video encoded using Handbrake, or compared to the original for that matter.

Edit: Ok, I see what's going on now and am now using a true 16:9 input AR. How can there be a debate about math? 16/9 equals 1.7777778 no matter how you calculate it. What new math is the ITU using to figure this stuff out?

Inspector.Gadget
17th January 2010, 02:43
Search is your friend, but basically NTSC 16:9 isn't actually perfect 16:9, and a lot of DVDs are encoded as a true 720w of content rather than a 704w + 16w padding, resulting in ambiguity,

stax76
17th January 2010, 02:50
@Taddeusz

MeGUI just defines ITU Input DAR's, that works for most common sources but gives wrong values for uncommon sources like 704x576. MeGUI allows you to enter a custom DAR and this get's persisted so it's no problem not using ITU. Regardless of what you want to use up-scaling is IMO a very bad idea.

Taddeusz
17th January 2010, 03:10
All DVD's I've ever seen, at least here in the United States, are encoded 720x480 regardless of whether they are 4:3 or 16:9. I've never seen one encoded at 704x.

stax76
17th January 2010, 03:16
You shouldn't have than any problems with MeGUI, just enter 1,777 and 1,333 as custom input DAR if you don't want to use the ITU DAR's.

Taddeusz
17th January 2010, 03:19
You shouldn't have than any problems with MeGUI, just enter 1,777 and 1,333 as custom input DAR if you don't want to use the ITU DAR's.

Yea, I finally figured that out.

Inspector.Gadget
17th January 2010, 03:53
All DVD's I've ever seen, at least here in the United States, are encoded 720x480 regardless of whether they are 4:3 or 16:9. I've never seen one encoded at 704x.

But you've likely seen plenty encoded at 704 of content and 16 of black bars, which is what I was referring to - this creates the ambiguity.

Taddeusz
17th January 2010, 04:05
But you've likely seen plenty encoded at 704 of content and 16 of black bars, which is what I was referring to - this creates the ambiguity.

Ah, so what you're saying is that the decoders automatically translate the 704 to 720 before it gets displayed? Kind of like how 1080p H.264 is actually 1088 lines but gets cropped upon playback?

Inspector.Gadget
17th January 2010, 04:49
No, I mean the actual movie is encoded at 720px width but only 704 of that is the film transfer: the other 16 pixels are padding. That's generally an easy case: crop 8 from each side, resize or retain to PAR to get about 853x480. The problem comes in when the actual content of the film takes up all 720px of width: it is unknown to the end user what process was used and whether the full 720px should occupy only ~853px, or whether with the "bonus" of an additional 16px the correct display dimensions allocate 853px of width to the innermost 704px and the rest may be displayed in addition. MeGUI simply opts to treat uncropped NTSC DVD content as allocating 704px of width to the "correct" 853w frame and any uncropped areas to outside that frame. There are better explanations in other threads.

Zathor
17th January 2010, 14:43
Updated to MeGUI 0.3.2.0
Win Vista Ultimate SP2

When I load an avisynth script MeGUI freezes then responds after a long time with an error.

Avisynth Script error:
DirectShowSource : Timeout waiting for graph to start.
(C:\video.avs, line1)
Are you able to open the file e.g. in VirtualDub? Please post your avs file.

Taddeusz
17th January 2010, 16:16
No, I mean the actual movie is encoded at 720px width but only 704 of that is the film transfer: the other 16 pixels are padding. That's generally an easy case: crop 8 from each side, resize or retain to PAR to get about 853x480. The problem comes in when the actual content of the film takes up all 720px of width: it is unknown to the end user what process was used and whether the full 720px should occupy only ~853px, or whether with the "bonus" of an additional 16px the correct display dimensions allocate 853px of width to the innermost 704px and the rest may be displayed in addition. MeGUI simply opts to treat uncropped NTSC DVD content as allocating 704px of width to the "correct" 853w frame and any uncropped areas to outside that frame. There are better explanations in other threads.

Ok then, regardless, whether the video is blocked a certain way on the encode the video itself, whether it be NTSC or PAL (720x480 or 720x576), is still encoded at 16:9 or 4:3. I just don't know how you can calculate those to be any different than 1.777778 and 1.333333. Math is math.

After cropping is another story, but before cropping 16:9 is 16:9 and 4:3 is 4:3.

stax76
17th January 2010, 16:45
Difficult topic! Search google for Aspect Ratio ITU-R BT.601

sneaker_ger
17th January 2010, 18:39
Here's a simple table if you only want to know the factors:
http://www.abload.de/img/itudar1vo7.png
left column: "commonly known" DAR
right column: ITU defined DAR

Cyberpro60
17th January 2010, 20:20
Megui fatal error. Version 0.3.2.0 [0.3.1.1-56]
I downloaded the latest version of Megui from Sourceforge to install on a Windows 2000 platform. Every time I go to run the application I get a series of the same error messages. The first one says 'Error: Could not load previous settings'. When I click 'OK' on that error message I get the following Fatal Error 'Megui encountered a fatal error and may not be able to proceed. Reason: unable to find an entry point named "IsWow64Process" in DLL kernel32.dll'. Does anybody know how to fix this error?

Inspector.Gadget
17th January 2010, 21:12
Use an OS other than W2K.

Cyberpro60
18th January 2010, 04:37
Nice but not possible in this case Inspector Gadget. Windows 2000 happens to be my network server and we are not about to change it whilst it performs everything we require of it. This server has provided me with a useful "offline" rendering platform that doesn't restrict my work on my own pc.
Besides that, I should also point out that Megui was working just fine on this platform until the most recent update a few days ago!

quantum5uicid3
18th January 2010, 05:19
security updates are going to stop in about 6 months, so you should probably start preparing for migration

Cyberpro60
18th January 2010, 09:24
Microsoft have been saying that for some time now and yet they keep extending the deadline. Meanwhile .... Megui is still not working! Anybody have some practical suggestions for fixing this problem?

lucamark
18th January 2010, 09:40
i don't think you can fix your problem without migration to another os.. There are many function (api calls) that are available only in xp, vista, 7.. like IsWow64Process (http://msdn.microsoft.com/en-us/library/ms684139%28VS.85%29.aspx).. (see Requirements..)

quantum5uicid3
18th January 2010, 10:48
there havent been any changes to windows 2000 extended support schedule, 2010 was always end of lifecycle. xp/2003 is significantly better and i'm sure you could find them dirt cheap.

Mizzle
18th January 2010, 15:24
Hi, I just converted my very first avi file to an mkv to test it out on Youtube.
Are there any recommended settings for the best quality or anything to get in HD there...?
(btw, atm I'm getting the 'An error occurred...' message for that video aswell)


Just bumping my question, hoping it'll be answered.:)
My video is playing on youtube but there isn't an HD option nor is it in great quality either...?

Pfc Joker
18th January 2010, 15:40
I'm running MeGUI 3.2.0 on Win 7 x64 and really like it. I've only had one small issue with avi muxing.
I have to either set MeGUI to run in WinXP SP3 compatibility mode, or set just avimux_gui to WinXP SP3 compatibility mode. Soon as I do either everything works like a charm.

Inspector.Gadget
18th January 2010, 16:30
AVIMux_GUI is known not to work by default on Vista and W7. At one point Kurtnoise rolled back the version by one revision to one that did; I've no idea as to whether it has since been updated again.

Abradoks
18th January 2010, 18:03
Zathor
Can you please make it possible again to change "update_cache" location? It's quite useful to keep updates separately.

trevmar
18th January 2010, 21:55
I downloaded the latest version of Megui from Sourceforge to install on a Windows 2000 platform. Every time I go to run the application I get a series of the same error messages .. unable to find an entry point named "IsWow64Process" in DLL kernel32.dll'.
.
I just got the same problem today, when I updated.
I have a decades worth of software locked to my hard drive and hardware signatures (etc) and really can't move from Win2K without spending an awful lot of time on the transition.

So I restored my old copy of MeGUI from last night's backup :)
.

Zathor
18th January 2010, 23:25
Megui fatal error. Version 0.3.2.0 [0.3.1.1-56]
I downloaded the latest version of Megui from Sourceforge to install on a Windows 2000 platform. Every time I go to run the application I get a series of the same error messages. The first one says 'Error: Could not load previous settings'. When I click 'OK' on that error message I get the following Fatal Error 'Megui encountered a fatal error and may not be able to proceed. Reason: unable to find an entry point named "IsWow64Process" in DLL kernel32.dll'. Does anybody know how to fix this error?
Sorry, did not notice before that XP SP2 is required for IsWow64Process. Will be hopefully fixed soon, but I have no Win2000 so you have to test it :rolleyes:
And to follow the oftopic discussion - anyone with Win 2000 in a productive environment should really concider an upgrade or a different OS. If MS is not extending the lifecycle you will surely have problems after the 13th of July.

Zathor
19th January 2010, 00:06
Switch to the development server or replace your megui.exe with this file:
http://megui.org/auto/megui-core_0_3_2_1_1.zip
Please report back if the problem has been fixed with this update.

trevmar
19th January 2010, 01:47
.
Yes, that replacement file worked well, Zathor. Thanks :)
.

Zephyr_Truesdale
19th January 2010, 04:08
Apparently someone else had a similar problem that I had when it couldn't find the ".avs" file. I was wondering if that problem has been fixed, sorry about my late response about the problem in an early post.

Cyberpro60
19th January 2010, 14:24
Thanks for the patch Zathor ... it did appear to work. I can now start MeGui without the previously reported error messages. I do have a new problem with DGIndex.exe though. When I try to run DGIndex I get the following message:

'The procedure entry point AttachConsole could not be located in the dynamic link library KERNEL.dll'.

Any thoughts on how to address this issue?

Zathor
19th January 2010, 17:15
When I try to run DGIndex I get the following message:
'The procedure entry point AttachConsole could not be located in the dynamic link library KERNEL.dll'.
Any thoughts on how to address this issue?
http://forum.doom9.org/showthread.php?p=1357662#post1357662

As a workaround you can use an older build od DGmpg

Zephyr_Truesdale
19th January 2010, 18:47
Is it possible to set what audio track for Nero AAC codec? Whenever I'm using VirtualDubMod 1.6.0.0 Surround to set what language each track are and I don't seem to see that option in MeGUI.

LigH
19th January 2010, 18:59
In the german doom9/Gleitz board, we got reports that with the latest MeGUI update the encoding speed went down to between 2/3 and 1/3 of the previous speed, between ~ 14th Jan and 16th Jan. Unfortunately, the users reporting this slowdown are not very experienced in reporting all technically interesting details... At least there are two distinct reports.

Of course, different settings are possible - but not very probable: There are users which don't experiment a lot, they chose a preset which works and prefer to keep it.

Are there any different defaults?

nurbs
19th January 2010, 19:21
I just looked through some of the profiles and they don't use excessively slow settings, although I don't have the old ones to compare to. Hard to tell what the issue without knowing exactly what profile they are using but there are some possibilities.
a) They still use profiles from the previous version of MeGUI which were made for x264 even before mb-tree and the preset and tuning system was in. The defaults changed since then which could explain the slowdowns. (I don't actually know if the old profiles still work with MeGUI and if the new profiles have the same name as the old ones. I think the names are different.)
b) While the new profiles don't use slow options some of them, like DXVA Insane, use low CRF values (17 in that case). Since the encoding time is proportional to the bitrate that can cause slowdowns.

Can you tell them to post the log of one of the encodes so we can take a look at the command line and speed. They should also encode their CPU speed. Alternatively a mediainfo from one of the old and one of the new encodes. (One of the old ones would be useful to know how their settings changed anyway.)

Zathor
19th January 2010, 19:29
The stable branch has been updated from x264 1183 to x264 1376. There have been a lot of new features (e.g. mbtree) which can cause a slowdown.

ZZZERO
20th January 2010, 04:30
After the latest MEGUI updates my encodes are ending up much smaller than expected although I haven't changed any settings in my profile. I compared my command lines from the logs both before and after the updates and they're quite different even though as I said I haven't changed anything in my profile.

Here's the command line as it is since the update:

C:\Program Files\megui\tools\x264\x264.exe" --profile high --crf 20 --thread-input --threads 4 --b-adapt 2 --ref 5 --subme 5 --trellis 0 --sar 1:1 --aud --output

Here's how it used to be:

"C:\Program Files\megui\tools\x264\x264.exe" --profile high --crf 20 --ref 5 --no-fast-pskip --b-adapt 2 --b-pyramid --subme 6 --trellis 0 --partitions p8x8,b8x8,i4x4,i8x8 --threads 4 --thread-input --sar 1:1 --aud --output

I really don't understand what's going on with this update and why I'm seeing such a dramatic change in my encodes. I did a 3 hour movie and it ended up about 500MB less than I would have expected and doesn't look as nice as my typical encode.

I'm using MEGUI 0.3.2.1 and x264 Jeeb's 1376 patched build v2

nurbs
20th January 2010, 08:41
Smaller size at the same crf is what happens with many sources since mb-tree was introduced half a year ago. The only thing that makes a difference for quality is subme 5 (6 activates psy-rd and 7 is the new default) and --no-fast-pskip (which shouldn't matter at all for quality since it's only activated in the placebo preset) One question do you still use an old preset or a new one that came with the updates?

ZZZERO
20th January 2010, 13:26
I use a custom profile based on one of the presets but don't use any of the presets. My file size reduction and quality loss has happened within the past week, not since six months ago. With the completely new x264 settings interface, it seems clear that MEGUI is not carrying over one's previous settings.

nurbs
20th January 2010, 13:42
If you didn't use development versions of MeGUI and you didn't replace x264 yourself then the version you have been using until last week was about 6 months old. A lot has changed since then and not all of the old settings apply anymore. You should look into the preset and tuning system and make a new profile. There is now the preset slider using presets implemented within x264 itself that lets control the speed/quality tradeoff and there are tunings for different content (film, animation, ect.) Lower the CRF value if you are not satisfied with the quality. Personally I think CRF 20 with the new defaults is fast and looks good for SD content.

If you want the same as your old version take the profile you have, turn mb-tree off, turn weighted p-prediction off and change all the other settings so they match your old profile. Turning this off will of course result in lower quality at any given bitrate. Heres a list of everything you used thats different from the defaults: --crf 20 --ref 5 --no-fast-pskip --b-adapt 2 --b-pyramid normal --subme 6 --trellis 0 --sar 1:1 --aud
Note that the b-pyramid option has changed and there are now two modes. You most likely want "normal".

Elbart_
21st January 2010, 13:44
Today, out of boredom, I encoded a tv-recording (DVB-T MPEG2 with ~3,5Mbit/s, 25fps) with both the "Iphone 2-pass" and the "Bluray 2-pass" x264-preset, and the Bluray-preset encoded almost twice as fast. Is that supposed to be the case or have I got some misconfiguration on my side?

MeGUI 0.3.3.0, Jeeb's x264 1376 v2, desired resolution 624x352

LigH
23rd January 2010, 04:12
Thank you for your guessing, nurbs; I just don't believe that MBTrees got introduces exactly between 14th and 16th Jan 2010, but a little earlier. One reported that he updated several times during the last week, but ony the last update made it slower.

But we have similar reports for StaxRip now too.

If it is true that especially x264 was not updated too regularly, then this may indeed be the reason. Quite surprising how much everything is related in a whole converting environment like MeGUI.

Unfortunately there are no useful replies so far. We will poke them again...

J-Wo
26th January 2010, 06:44
Just started to use this program to convert my DVD rips to H.264 MKV. If my audio source is 5.1 AC3, how can I tell MeGUI to do a direct stream copy of the AC3 without converting the audio?

blsbball
26th January 2010, 06:50
Does anyone notice any decrease in quality with the latest updated build and presets? It seems that even with the highest profiles quality seems to be lower than before. Im using the unrestricted DXVA profile and am seeing a definite lack in quality.