MeGUI Bug-Report Thread

[bob0r]

compile full-svn

x264 > config > Rate Control: --subme 7 shows up here, thats not SVN.

Edit:
*fixed* There is no x264-svn anymore.

Edit2:
Fixed, SVN readded (None SVN still does not contain AQ)

[bob0r]

x264 > config > Rate Control: Bitrate Variance up/down button works, but goes like this:
1.0 up 2.0
2.0 down 1.0
1.0 down 0.1
0.1 up 1.1
1.1 up 2.1 etc...

X.1 <-- the 1 can't be changed, unless you type it.

[bob0r]

x264 > config > Quantization:

Credits Quantizer does not update in commandline, also the Help Balloon gives an no data error. Not sure what x264.exe option this would be.

But once you change the value of this, and then like you change the number of B-frames, the commandline nor the gui itself (visual) does not update.

Only when you again change Credits Quantizer, the commandline and the gui update.

Edit:
Ooops did some more testing:
(Number of) B-frames itself is b0rked in the gui, does not update in commandline nor does it ungrey options that should be available with 3 or more B-frames.

Edit2:
B-frames part fixed, Credits Quantizer not a bug.

[berrinam]

AVS creator won't use plugin dgdecode.dll and i get error message, "There is not function mpeg2source in avisynth". Avs can use mpeg2source beacouse plugin is not loadded.
I'm running the latest version (0.2.3.2085) right here, and the script generation goes fine. Here's what I'm doing:
Load the .d2v file.
Press save
The saved file has no errors whatsoever.

Until you tell me how to reproduce your errors, as I said in the first post of this thread, I am not going to help you.

[berrinam]

compile full-svn

x264 > config > Rate Control: --subme 7 shows up here, thats not SVN.
Conditional compiling is gone. I did a search through the source code, and the only difference between compile full-svn and compile full is the "Assembly Product" property. I suppose the real bug is that compile full-svn is still supported.
x264 > config > Quantization:
...

Version? I changed the configuration dialogs in a recent version, so that is essential

EDIT: Fixed

[Doom9]

x264 > config > Rate Control: Bitrate Variance up/down button works, but goes like this:That's by design. The minimum is 0.1 and the standard step size for the up/down is 1. I figured it to be too cumbersome to go up/down in 0.1 steps.
x264 > config > Rate Control: --subme 7 shows up here, thats not SVN.Perhaps I removed too much? But I seem to remember keeping that conditional compilation statement when I removed the codec specific builds.

[berrinam]

Searching for SVN in 'Current Project' in MeGUI doesn't turn up very much :(

[leowai]

Conditional compiling is gone.
I thought that only the conditional compilation of "lite" MeGUI (MeGUI-x264-svn and MeGUI snow) are gone. Now even Megui-SVN is gone?

[Doom9]

Credits Quantizer does not update in commandline,that's because this is megui internal. It only has an effect if you define credits / intro regions, you never see this on the commandline until you create a job. This is because intro/credits are just special zones.. once you create jobs, your defined zones and the intro/credits zones are merged (you get warnings if you screwed up something), and then after the merge the entire zone commandline is created.. prior to that, you can change all you want.. you're not going to see anything.

As far as subme goes.. I checked out yesterday evening before berrinam's last commit and here's what I found in the x264ConfigurationDialog constructor:
AVCLevels al = new AVCLevels();
this.avcLevel.Items.AddRange(al.getLevels());
this.frameSize = frameSize;
#if SVN
x264SubpelRefinement.Items.Remove("7 - RDO Level 2 (Slower)");
#endif

[fight2win]

even after selecting "Shutdown after encoding" both in config. and on queue window, megui does not do so! using latest megui build!

[The Link]

If you click configure on a selected audio preset the changes you make get saved to the profile without asking. Afaik this isn't the same behaviour as before. Intended?

[bob0r]

That's by design. The minimum is 0.1 and the standard step size for the up/down is 1. I figured it to be too cumbersome to go up/down in 0.1 steps.


I see, well it feels pretty weird when you use it :)
I guess its possible when you click it goes up 0.1 each time, but when you hold the button it changes 0.1 steps up fast.
... Oh Wait, in fact, it already does..... just not with 0.1 steps :o

Going up to 100.0 only takes me like 3 seconds, so i think 0.1 steps are pretty doable, if you want to go from 0.1 to like 10.1 you use the buttons, if you go from 0.1 to 90.1, you best just type a 9 infront of the 0.

So i think it should be changed.

[bob0r]

@berrinam

"- Removed a line of conditional compilation. compile full-svn is now identical to compile full"

Why isn't compile.bat updated then?
FULL-SVN does not exist anymore, then compile.bat should be update.
Also (not that it matters anymore), but why was neroraw.exe compiled with full and not with full-svn, is this because you guys don't really pay attention to compile.bat? :)
Anyways, please make a clear up to date compile.bat.

P.S. did you see my screenshot with the deblock filter? (page 25)

@all megui devs or others that know

What x264 options/features are in megui-full that are not in x264-SVN?
I want to make a list for x264.nl so people know what options they can not use with the svn builds.

[bob0r]

2086

x264 > config > Quantization: Macroblock Options
Not possible to select All or None or Custom, well its possible, but nothing changes.
Changing profile to High Profile does not change it.

Edit:
In the same Macroblock Options
When you select --8x8dct (Adaptive DCT) (after selecting high profile) the option I8x8 becomes available, when you select it, you get: --analyse p8x8,b8x8,i4x4,i8x8 --8x8dct
Now when you unselect --8x8dct (Adaptive DCT), you get: --analyse p8x8,b8x8,i4x4,i8x8
i8x8 is still enables in the commandline, but greyed out in the gui.

[berrinam]

The SVN discrepancy probably came from my redoing of the video configuration dialogs. They were built on code from a week ago, so I'll have a look back then to see what I missed out on. I didn't realise that anything was missing. Sorry about that mistake.

As to all the x264 encoder configuration problems ..... well they're just a sign of what a mess the x264 Tri-State code is in.

[bob0r]

@berrinam

Meaning? There will be a full-svn version or not?

[dimzon]

@berrinam

Meaning? There will be a full-svn version or not?
Seems like both are the same so we does'nt need SVN version at all :rolleyes:

[bob0r]

Seems like both are the same so we does'nt need SVN version at all :rolleyes:

Then please answer this (http://forum.doom9.org/showthread.php?p=783580#post783580)

[dimzon]

is this because you guys don't really pay attention to compile.bat? :)
Yes :o
http://files.x264.nl/megui-2085-x264-config.jpg
Is this bug reproduced if you disable visual styles in windows?

[shon3i]

I'm running the latest version (0.2.3.2085) right here, and the script generation goes fine Now is working. I be using 0.2.3.2079. I found error in this new version when you use deblock in x264 comanline looks --filter 2,1 instead --filter 2:1. When i open stats file in her says that deblock is 2,2

[bob0r]

Is this bug reproduced if you disable visual styles in windows?

Yup, the text is going outside the window, also on standard windows xp settings

Edit:
http://files.x264.nl/megui-2086-x264-config-main.jpg

Edit2:
Fixed

[Doom9]

deblocking threshold, macroblock options i8x8mv vs 8dct.. all those things work fine in the second latest build I worked on (it's a couple weeks old but there shouldn't have been any changes to the x264 dialog since then): 0.2.3.2013

Afaik this isn't the same behaviour as before.I worked on that, and I didn't add any functionality, just moved around code.. pressing OK always saved the settings. If it wasn't there for a specific dialog, it's a copy/paste problem.

What x264 options/features are in megui-full that are not in x264-SVN?subme7 & adaptive quantization

[bob0r]

@Doom9

2069 (x264 rev 426) still has correct deblocking text and working macroblock options. The config tabs have been moved around, so something changed :)

I will now use megui.exe (just compile.bat) and will add --subme 7 and adaptive quantization to the notes that these options are not working with the x264.nl builds.

What cli option is adaptive quantization ?

Edit:
Oh wait adaptive quantization is the AQ patch by Haali ;)
Is it me or isn't it in the x264 config in megui?

[bob0r]

2086

x264 > config > Zones:

The Mode box is "empty", only when you select it, and select Quantizer or Weight the box is "filled"

Edit:
Also the Previe(w) and Remov(e) buttons are not correct
screenshot:
http://files.x264.nl/megui-2086-x264-config-zones.jpg

Edit2:
Fixed

[pcaca]

Bugs in bild 0.2.3.2082 and 0.2.3.2086:
1. In the main window some extensions of the file in Video Output textbox are wrong for some combinations of Codec and File Type dropdown lists. Combinations are:
Codec | File Type | Wrong Ext. | Correct Ext.
--------------------------------------------
LMP4 | MKV | avi | mkv |
LMP4 | MP4 | m4v | mp4 |
Snow | MKV | avi | mkv |
XviD | MKV | avi | mkv |
XviD | MP4 | m4v |mp4 |

2. When I want to encode to XviD in avi container, I press AutoEncode and I check the Add Audio Stream checkbox in Automatic Encoding dialog to add my own audio without encoding, the new dialog AVI muxer appears under the Automatic Encoding dialog and sometimes i can't move it because i can't see the title of the dialog. The Automatic Encoding, MP4 Muxer and MKV Muxer dialogs seems like they have always on top argument and they get on the top of all applications. Please corect the window ordering.
http://img490.imageshack.us/img490/8049/megui2hn.th.jpg (http://img490.imageshack.us/my.php?image=megui2hn.jpg)

3. In audio configuration of MP3 when i choose VBR mode i don't have any option for the quality of the encoding. There should be options for -V0, -V1,.... -V9 switches for LAME.

4. Maybe this is not a bug, but I think that MP2 files should be suported as audio input in AVI and MKV muxer dialogs. Now there is no possibility to mux MP2 file directly in AVI or MKV container without reencoding.

[berrinam]

Meaning? There will be a full-svn version or not?
Yes, unless Doom9 doesn't want it.

[bob0r]

@berrinam

So you say yes, dimzon removes it, and doom9 thinks he's having a break down because you two and filling his brain with yes=no and no=yes, right? :D

So there WILL BE A SVN version, only its gone, well i already updated x264.nl thinking there will be only 1 version, so SVN can go home.

I said subme7 and AQ are none SVN on x264.nl (even though AQ is nowhere to be found :p)

[bob0r]

2087 still exists:

x264 > config > Quantization > Macroblock Options:
When you select --8x8dct (Adaptive DCT) (after selecting high profile) the option I8x8 becomes available, when you select it, you get: --analyse p8x8,b8x8,i4x4,i8x8 --8x8dct
Now when you unselect --8x8dct (Adaptive DCT), you get: --analyse p8x8,b8x8,i4x4,i8x8
i8x8 is still enables in the commandline, but greyed out in the gui.

-----

Still exists, not a bug, but still very annoying:

x264 > config > Rate Control: Bitrate Variance up/down button works, but goes like this:
1.0 up 2.0
2.0 down 1.0
1.0 down 0.1
0.1 up 1.1
1.1 up 2.1 etc...

X.1 <-- the 1 can't be changed, unless you type it.

@all
megui-svn.exe added to x264.nl installer again (next revision, 430+)

[bob0r]

2087

x264 > config > Main/Rate Control/Quantization

Boxes inside the window don't align nicely, which makes switching between them very messy to the eye.

- the Rate Control/Rate Control window is more to the right
- the Main/General window is lower than Control/Rate Control and Quantization/Quantizers

http://files.x264.nl/megui-2087-x264-config-windows.jpg

Top and Left should be fixed values, for perfect eye comfort :)

Edit:
Fixed

[berrinam]

As far as I'm concerned, I've fixed the bugs that I was responsible for.

I know that sounds selfish, but the x264 config dialog is complex because of all the tri-state code, and the various devs don't agree on how it should work (whether disabled && checked means on or off). As a result, I have no idea what the verdict is, so I am keeping out of it*. In my redo of the codec config dialogs, I simply copied the code from the old dialog into the new dialog.

*If Doom9 says definitively what the adopted standard is for MeGUI, than I can make fixes, but I don't want to force the issue one way or the other.

In terms of alignment of the GUI, I'm not interested in that. Someone else can do it.

With respect to the Bitrate Variance up/down, I'm waiting to see what Doom9 says on that.

[leowai]

What x264 options/features are in megui-full that are not in x264-SVN?subme7 & adaptive quantization
Sorry for my stupid question about non-svn options.
I found the setting of subme7 in MeGUI, but where is the setting for the Adaptive Quantization in MeGUI? Should that be included in MeGUI (non-svn version)?

Checked: Adaptive Quantization settings is available in MeGUI old-built MeGUI-0.2.2.7 (before cvs builds) but MeGUI-0.2.3.1026 and later (cvs build) no longer provide such setting in the GUI.

[bob0r]

@berrinam

I am just reporting what i see :)
I think you did a great job on the fixes.

But yeah, i guess add the bugs to the list that won't/can't be fixed right away.
Maybe its possible for doom9 to give certain users Edit access to only 1 thread, and then a developer can edit the first post saying he will work on it.

[Doom9]

Alright, I have no problem with an SVN build.. (a dirty hack.. disable/remove some options at the end of the constructor in a CC clause).

About AQ.. I suspect sharktooth removed it when he removed it from his buids, then never readded it when he put aq back into his builds.

As far as tri-state goes: I still think it can work, but the past has shown that if multiple persons work on a form, it will cause a mess. Since I'm no longer the only one working on MeGUI, I think it's prudent that we scrap the whole tri-state idea and get back to WYSIWYG. So the dialog can be redone. Or alternatively, I take over again (at least on this part), and everybody else is hands off (that worked in the past.. and unless I'm in the middle of major refactoring I can take care off the occasional bug right away).

X.1 <-- the 1 can't be changed, unless you type it.I really don't see this as a problem at all.. I don't think every up/down should be set to provide direct access to the lowest increment/decrement. If you have a control that allows 4 digits after the decimal separator, and allowed values range from 0.0000 to 1000.0000, you're going nuts with an up/down that increments/decrements by 0.0001. In that case, I find it much more convenient to make the default in/decrement 1.0 and those that want to access will just have to resort to their keyboard. Very often, the granularity is actually too high to allow unsuspecting users to make a good choice. it's much better to let them use up/downs with large increments, and those that know exactly what the parameter does can mess around with the keyboard. Sometimes, making things harder ensures that you give the inexperienced user just enough control and allow the experienced user full control.

LMP4 | MKV | avi | mkv |
LMP4 | MP4 | m4v | mp4 |
Snow | MKV | avi | mkv |
XviD | MKV | avi | mkv |
XviD | MP4 | m4v |mp4 |
That's quite how it should be. There's no direct LMP4 -> MKV path... mencoder only does avs to AVI. Hence.. mencoder writes an avi, mkvmerge muxes that into a MKV. Same thing for mp4.. if the encoder doesn't do MP4 output, it's raw and mp4box muxes that. After the refactoring, it will be much clearer.. manual encoding will only make direct encoding paths accessible.. for anything else you have to use an automated mode where everything is done automatically for you.

Maybe this is not a bug, but I think that MP2 files should be suported as audio input in AVI and MKV muxer dialogs.That's by design.. MP2 in AVI.. /me runs away screaming. Some time in the future AVI will support two audio tracks, AC3, DTS, MP3 and AAC.. but that's it.

[bob0r]

@Doom9

And "With respect to the Bitrate Variance up/down, I'm waiting to see what Doom9 says on that." ?

Keep it, or make it less annoying?

[shon3i]

The shutdown feature not working again please fix that and in comandline says --filter 2,1 instead 2:1

[bob0r]

... and in comandline says --filter 2,1 instead 2:1
Stop reading my mind please. was about to press submit on that hehehehe :goodpost:

[Doom9]

Keep it, or make it less annoying?In this case it can be changed, but don't expect me to change the 4 digits after the separator behavior if we ever get there. Those that know what they're doing are better off with typing anyway.
There's also no point in reporting problems multiple times.. they don't get fixed faster, rather.. it makes things go slower because somebody has to read the message again.

[bob0r]

@Doom9

Ok, and yeah the buttons should be to fine tune anways, typing is always better :)

(And sometimes stuff is over read, as usually you guys answer all questions in 1 reply)


Alrighty then..... back to bug hunting!

[Kostarum Rex Persia]

Build 0.2.3.2055 not work with newest build of xvid_encraw from February 9 2006. When I start encoding, MeGUI immediately shutdown.

[ChronoCross]

Build 0.2.3.2055 not work with newest build of xvid_encraw from February 9 2006. When I start encoding, MeGUI immediately shutdown.

xvid_encraw hasn't been updated in MeGUI. Because there is no real stable place to get the builds for comparssion. Could you please use the latest dev build when making bug reports, as there have been ALOT of changes since 2055.

[Kostarum Rex Persia]

But, I looked for 0.2.3.2089 and I wasn't able to find that newest build. Can you, please, post direct download link to newest MeGUI build. Thank you.

[ChronoCross]

Unofficial MeGUI Builds (http://chronocrossdev.com/apps/megui)

For all those of you who didn't read the guide you can get my builds here.

[Kostarum Rex Persia]

ChronoCross, you just added build 2089, thank you. Before one and a half hour, build 0.2.3.2089 hasn't been on your site. Thanks again.

[edit] Remember what I was told about build 0.2.3.2055? Well, same happens with newerst build of MeGUI, 0.2.3.2089. xvid_encraw still won't work when I try to use Xvid codec from MeGUI 0.2.3.2089 ( container is MP4).

Can someone fix that bug, please.

[Drillakilla]

i started using the more commercial psp video apps but the quality was crap, then on another forum someone mentioned x264 using Megui.
Iv got all the programs i need ( mp4 box, besweet etc).


I can encode automated two pass and i get an mp4 file, the problem is whenever i try and encode 2 pass 2nd pass i get a okb mp4 file ( the encode is instant), whenever i try 2 pass 1st pass i get a .stats file ( the file size seems fine) but no mp4

i cant work out what i am doing wrong, i am really desperate to get this to work because iv heard the quality is excellent ( much better than the other psp apps)

below is more information on my encodes::



--------------------------------------------------------------------------------

My test video clip is 7 mb big and 7 seconds long

Heres my avs file i created for the encodes:

AviSource("D:\Mpegs\xvid movies\Test.avi",TRUE)
BlindPP(cpu=4)
Blockbuster(method="noise",detail_min=1,detail_max=3,variance=0.1,seed=1)
Convolution3D(1, 6, 12, 6, 8, 2.8, 0)
LanczosResize(368,208)
Undot()
TemporalSoften(2,7,7,3,2)
DCTFilter(1,1,1,1,1,1,0.5,0)
assumefps(29.00)

This is the command line i got, encoded at 2 Pass- 2nd Pass,
400 kbps


C:\Program Files\x264\x264.exe --pass 2 --bitrate 400 --stats ".
stats" --ref 2 --mixed-refs --bframes 3 --b-rdo
--weightb --subme 6 --trellis 1 --analyse p8x8,b8x8,i4x4,p4x4
--sar 360:208 --progress --no-psnr --output
"D:\PSP Test script 360 208.mp4"
"D:\PSP Test script 360 208.avs"

and the Log

Next job job1 is a video job. encoder commandline:
--pass 2 --bitrate 400 --stats "D:\PSP Test script 360 208.stats" --ref 2 --mixed-refs --bframes 3 --b-rdo --weightb --subme 6 --trellis 1 --analyse p8x8,b8x8,i4x4,p4x4 --sar 360:208 --progress --no-psnr --output "D:\hh.mp4" "D:\PSP Test script 360 208.avs"
successfully started encoding of job job1
job commandline: --pass 2 --bitrate 400 --stats "D:\PSP Test script 360 208.stats" --ref 2 --mixed-refs --bframes 3 --b-rdo --weightb --subme 6 --trellis 1 --analyse p8x8,b8x8,i4x4,p4x4 --sar 360:208 --progress --no-psnr --output "D:\hh.mp4" "D:\PSP Test script 360 208.avs"
----------------------------------------------------------------------------------------------------------

Log for job job1

desired video bitrate of this job: 400 kbit/s - obtained video bitrate: 0 kbit/s
----------------------------------------------------------------------------------------------------------



Heres the command line for 2 pass 1st pass:

C:\Program Files\x264\x264.exe --pass 1 --bitrate 400 --stats ".stats" --bframes 3 --subme 1 --analyse none --me dia --sar 360:208 --progress --no-psnr --output NUL "D:\PSP Test script 360 208.avs"

and the log:

Next job job1 is a video job. encoder commandline:
--pass 1 --bitrate 400 --stats "D:\PSP Test script 360 208.stats" --bframes 3 --subme 1 --analyse none --me dia --sar 360:208 --progress --no-psnr --output NUL "D:\PSP Test script 360 208.avs"
successfully started encoding of job job1
job commandline: --pass 1 --bitrate 400 --stats "D:\PSP Test script 360 208.stats" --bframes 3 --subme 1 --analyse none --me dia --sar 360:208 --progress --no-psnr --output NUL "D:\PSP Test script 360 208.avs"
----------------------------------------------------------------------------------------------------------

Log for job job1

avis [info]: 368x208 @ 29.00 fps (278 frames)
x264 [info]: using SAR=45/26
x264 [info]: using cpu capabilities MMX MMXEXT SSE SSE2
x264 [info]: slice I:2 Avg QP:23.50 size: 14738
x264 [info]: slice P:112 Avg QP:28.41 size: 3262
x264 [info]: slice B:164 Avg QP:30.54 size: 518
x264 [info]: mb I I16..4: 6.0% 0.0% 94.0%
x264 [info]: mb P I16..4: 2.3% 0.0% 0.0% P16..4: 89.8% 0.0% 0.0% 0.0% 0.0% skip: 7.9%
x264 [info]: mb B I16..4: 0.0% 0.0% 0.0% B16..8: 11.5% 0.0% 0.0% direct:15.7% skip:72.7%
x264 [info]: final ratefactor: 27.02
x264 [info]: kb/s:400.4

Actual bitrate after encoding without container overhead: 400.87

----------------------------------------------------------------------------------------------------------


Please could someone help me sort this out, thanks in advance for anyhelp

[berrinam]

[edit] Remember what I was told about build 0.2.3.2055? Well, same happens with newerst build of MeGUI, 0.2.3.2089. xvid_encraw still won't work when I try to use Xvid codec from MeGUI 0.2.3.2089 ( container is MP4).:readrule: :readguid: You've just broken forum rule 1:1) Read up before asking! There are tons of guides, FAQs and each forum has a dedicated Q&A thread with additional info.
I tested just now, and the link to xvid_encraw which I have in the sticky in this forum works with MeGUI 0.2.3.2089. I suspect it also works with most other versions of MeGUI, as there haven't been many changes to xvid_encraw support in MeGUI.

Can someone fix that bug, please.It's not a bug. It works. It's insulting to assume that it's a bug in MeGUI before actually trying to get it to work.


@Drillakilla: Your error isn't clear in your log. Try doing step 8 of the guidelines on the first post of this thread, and see if the error message shows up there.

[Schnoodledorfer]

Here is is how to produce what I'm talking about.


Select a 2-pass profile (I used sharktooth's HQ-slowest). Enter the filenames and click on the "Queue" button.
Set up another job. Select a 1-pass profile (I used sharktooth's 1P-Maxspeed profile) this time. Don't queue it yet, however.
Click on the Queue tab, then select the 2nd pass of the previous job, click on the "load" button. (A user might do this to check something or to load in the filenames, I suppose.)
Click on the "Queue" button. This creates a corrupt new job that's really only the second half of a 2-pass job. The settings are from the previous job, not the profile that is displayed.
Click on the CODEC "setup" button. The settings for a valid 1-pass job are displayed, but that's not what was queued just now.


This is related to changes I have requested here (http://forum.doom9.org/showthread.php?p=784405). That's a very long essay about why I would like things to be different, but I can't claim that it's really a bug. But if it's possible that a user would see settings that look valid, yet when he/she clicks on "Queue" a corrupt job with entirely different settings is queued, then I think I can use the term "bug" and I should mention it here. That's why there are two differnt posts.

[Doom9]

xvid_encraw support is still on CVS level... meaning you can't use S_O's custom builds or squid's custom builds as of yet. When refactoring is done, that will change but until you can read in the changelog that squid's build is required, don't even bother to try.

@Drillakilla: unfortunately for you, there is a situation where x264.exe exits with an error (that you can see on the commandline), but where megui is unable to read the error message and so far we have been unable to find out why this happens, and how we can prevent it. What most likely happened is that the first pass aborted at some point, then the second pass started and immediately aborted because the statsfile has a lower number of frames than the source. If you follow the reporting guidelines and post again with that info (do the step berrinam mentioned), we'll be able to tell for sure.
@schnoodledorfer: I wouldn't call that a nonsense job.. it's a valid 2 pass second pass job.. they can be created independently of the first pass. And it boils down to a user error.. when you press queue, the current settings are used for a job. Current settings are changed if a) you select a profile, b) you select another codec, c) you press OK in a codec configuration dialog, d) you press load when you have a job selected in the queue. Profiles have but one functionality really: upon selection, they update the current settings. So as long as you don't select one, nothing is applied. I admit that's not very nice if you're using the load functionality, but it can't be done another way.. you can't tie profiles to jobs.. a job has settings, not a profile. Imagine if there was a connection. You create your job, then you change your profile, then you load the job again.. so the job would dutifully show what profile it has, but it wouldn't correspond to your edited profile. You could even have the situation where you change the codec for a profile, so you'd open a huge can of worms..

Loading jobs goes hand in hand with the update button. You select a job, you press load, then you reconfigure, then you go back to the queue and press update. And yes, that gives you the possibility to royally screw things up.. e.g. turning a 2 pass second pass job into single pass job of another codec, and that will break any jobs that are dependent of your 2 pass second pass. It's also not possible to restrict such screwups without considerable extra effort (and in the process introducing many new bugs.. and you'd need new buttons as well as now you'd suddenly have to decide if you're in "edit an existing job" mode, or not, and give users the possibility to exit from that mode (and then what happens.. the job stays loaded or what?)).

So the only thing that can reasonably taken from your report (a very good one by the way.. you gave just enough detail so it can be reproduced.. I didn't even have to go through the steps since I know what happens if you preform the various options you mentioned) is to check if it's possible to make no profile selected when a job is being loaded (that's your problem with editing the settings.. all is well when you press load, but then when you press configure, first the proper settings are being loaded.. then the GUI looks at which profile was selected in the main window, and if it's of the same codec type, then it will overwrite the settings). There's an easy way around that, but it introduces other inconsistencies. I don't see any way to completely prevent any inconsistencies.

But here's what you can do: create a profile for another codec. Then in step 2, select that profile. Then you do the rest and now it will work as you expect it to.. the current profile will be one of an incompatible type, thus when you go to the codec configuration screen, the actual job's settings will be used and not overridden by any profile. Then you reconfigure, and finally you update the job (load is there to give you a chance to edit settings.. now show settings) and voila, you got it.

[foxyshadis]

Well, "--filter -2,-3" is now a legal command line, so I guess it's okay to forget about that bug now. =D

[Drillakilla]

okay i did what u guys asked, run, cmd etc. i pasted my commandline:

D:\Mpegs\psp\Me Gui\x264.exe --pass 2 --bitrate 450 --stats "D:\Mpegs\PSP Encoding\2pass.stats" --ref 2 --mixed-refs --bframes 3 --b-rdo --weightb --subme 6 --trellis 1 --analyse p8x8,b8x8,i4x4,p4x4 --sar 368:208 --progress --output "D:\Mpegs\PSP Encoding\Scripts\x264 encode.mp4" "D:\Mpegs\PSP Encoding\Scripts\x264 encode.avs"

Hit enter


then i got this error
'd:\mpegs\psp\me' is not recognised as an internal or external command, operable program or batch file.

Please can you make sence of this

[Drillakilla]

then i did something different, before i had loads of existing commands on the dos window, so i thought id close and start a new command, pasted my script and got these errors:


cannot find stats file .. straight away i figured out wehat i have been doing wrong. when i chose 2 pass 2nd pass i assumed that it did both passes for you, then i relised you have to do 2 pass first pass, then immediately afterwards do 2 pass 2nd pass ( the stats file is there to continue) then you get your mp4. god i cant believe i didnt realise ( automated 2 pass worked because it automatic)

thanks guys will get back to you and let you know how encodes went