Log in

View Full Version : MeGUI - x264/XviD/lavc/Snow encoder with MP4/MKV/AVI output & audio


Pages : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 [15] 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63

Liisachan
15th October 2005, 19:38
QuickTime doesn't like some of High Profile things. Try Config->Main->AVC Profiles->Main Profile.
Furthermore, QuickTime doesn't like MPEG-2 AAC (this problem was in QT6 and apparently not fixed in QT7). If you use psytel/faac/foobar2000 and get .aac file. it's not MPEG-4 AAC but MPEG-2 AAC by default. If you are using faac, make sure to output in .mp4 or, if you have to output in .aac for some reason, use "--mpeg-vers 4" to make QT happy.

stratocaster
15th October 2005, 19:56
QuickTime doesn't like some of High Profile things. Try Config->Main->AVC Profiles->Main Profile.
Furthermore, QuickTime doesn't like MPEG-2 AAC (this problem was in QT6 and apparently not fixed in QT7). If you use psytel/faac/foobar2000 and get .aac file. it's not MPEG-4 AAC but MPEG-2 AAC by default. If you are using faac, make sure to output in .mp4 or, if you have to output in .aac for some reason, use "--mpeg-vers 4" to make QT happy.

Thank you guys for replying.
As for the hints you gave me Liisachan, does it mean than I could manage somehow to make an MP4[H.264, AAC] file rendered by meGUI playable on QuickTime an on the new iPod ? or I must simply forget it as mentioned by Sharktooth?

Liisachan
15th October 2005, 20:09
you can. try "Config->Main->AVC Profiles->Main Profile" in megui (x264)

Doom9
16th October 2005, 15:14
Perhaps I have founded another bug; in the audio encoder configuration it seems to be impossible setting a negative value in the delay correction textbox. I suppose that this textbox has a pattern that accept only numeric values but in this case is not possible to digit the sign minus.It's not a bug, it's a feature in a way.. standard textboxes allow any kind of input, I limited it to numeric input only. I'm not much a fan of entering the delays in the first place but a big believer into dgindex's naming scheme that contains the delay.. if you have such a file, even if the delay is negative, it's being properly picked up.

I just got back from my holiday and need to get over the jetlag and lack of sleep first, but for now I have approved berrinam's bugfix build in the development thread: http://forum.doom9.org/showthread.php?t=95863&page=19&pp=20

I'm sorry I disappeared so quickly, but 1.5 days before the start of my holidays I got sick and thus couldn't take proper care of all the details that needed to be taken care of for my absence :/

ChronoCross
16th October 2005, 18:32
I'm not sure if this is a bug or it's already been reported but if you use the X button to close MeGUI after your queue is clear(finished encoding not the clear button) when you reload MeGUI those jobs reappear. If you go to file Exit this does not occur.

haubrija
16th October 2005, 19:40
I finally got around to upgrading to 0.2.2.6 last nite and the latest build of x264. Set up my normal 2 pass mode, doing an auto encode for 1/5 DVD size. My final file however ended up being a 328mb file. Looking through the log, there seems to be some weird oddities (at least to my untrained eye :))

Generating jobs. Desired size: 901120 bytes
Setting desired size of video to 901120 bytes
Generating jobs. Desired size: 901120 bytes
Setting desired size of video to 901120 bytes
Generating jobs. Desired size: 716800 bytes
Setting desired size of video to 716800 bytes
Next job job1-1 is an audio job. besweet commandline:
"C:\MP4 Encoding\BeSweetv1.5b29\besweet.exe" -core( -input "D:\PS\1 AC3 T01 3_2ch 448Kbps DELAY 0ms.ac3" -output "D:\PS\audio.mp4" -logfile D:\PS\audio.besweet.log ) -azid( -c normal ) -bsn( -6chnew -vbr_extreme -codecquality_high -aacprofile_he ) -ota( -d 0 -g max )
successfully set up audio encoder and callbacks for job job1-1
----------------------------------------------------------------------------------------------------------

Log for job job1-1

besweet: "C:\MP4 Encoding\BeSweetv1.5b29\besweet.exe" -core( -input "D:\PS\1 AC3 T01 3_2ch 448Kbps DELAY 0ms.ac3" -output "D:\PS\audio.mp4" -logfile D:\PS\audio.besweet.log ) -azid( -c normal ) -bsn( -6chnew -vbr_extreme -codecquality_high -aacprofile_he ) -ota( -d 0 -g max )

BeSweet v1.5b30 by DSPguru.
--------------------------

[00:00:00:000] Initializing...
[00:00:00:000] -- Initializing...

[01:39:32:128] |

SR: 48000, Table idx: 4 - start 13, stop 10
SR: 48000, Table idx: 4 - start 13, stop 10
SR: 48000, Table idx: 4 - start 13, stop 10
SR: 48000, Table idx: 4 - start 13, stop 10
SR: 48000, Table idx: 4 - start 13, stop 10
SR: 48000, Table idx: 4 - start 13, stop 10
[01:39:32:128] Finalizing...
[01:39:32:128] Conversion Completed !

Visit DSPguru's Homepage at :
http://DSPguru.doom9.net/

----------------------------------------------------------------------------------------------------------
job job1-1 has been processed. This job is linked to the next job: job1-2
this series of jobs starts with an audio job and is followed by regular twopass video jobs
The audio job is named job1-1 the first pass job1-2 and the second pass job1-3
The second pass job has a desired final output size of 901120 bytes and video bitrate of 700 kbit/s
The size of the first audio track is 195056554 bytes
Desired video size after substracting audio size is -191059Setting the desired bitrate of the subsequent video jobs to -262 kbit/s
Next job job1-2 is a video job. encoder commandline:
"C:\MP4 Encoding\x264.exe" --pass 1 --bitrate -262 --stats "D:\PS\1.stats" --bframes 2 --no-b-adapt --b-pyramid --subme 1 --weightb --analyse none --qpstep 1 --me dia --progress --no-psnr --output NUL "D:\PS\1.avs"
successfully set up video encoder and callbacks for job job1-2
----------------------------------------------------------------------------------------------------------

Log for job job1-2

avis [info]: 688x368 @ 23.98 fps (143188 frames)
x264 [info]: using cpu capabilities MMX MMXEXT SSE 3DNow!
x264 [info]: slice I:920 Avg QP:10.01 size: 55101
x264 [info]: slice P:48241 Avg QP:10.00 size: 37746
x264 [info]: slice B:94027 Avg QP:11.50 size: 19958
x264 [info]: mb I I16..4: 25.1% 0.0% 74.9%
x264 [info]: mb P I16..4: 23.4% 0.0% 0.0% P16..4: 73.6% 0.0% 0.0% 0.0% 0.0% skip: 3.1%
x264 [info]: mb B I16..4: 9.1% 0.0% 0.0% B16..8: 53.7% 0.0% 0.0% direct:33.2% skip: 4.1%
x264 [info]: kb/s:5021.0

Actual bitrate after encoding without container overhead: 125055.23

----------------------------------------------------------------------------------------------------------
job job1-2 has been processed. This job is linked to the next job: job1-3
Next job job1-3 is a video job. encoder commandline:
"C:\MP4 Encoding\x264.exe" --pass 2 --bitrate -262 --stats "D:\PS\1.stats" --ref 4 --bframes 2 --no-b-adapt --b-pyramid --subme 6 --weightb --analyse all --8x8dct --qpstep 1 --progress --no-psnr --output "D:\PS\VIDEO.mp4" "D:\PS\1.avs"
successfully set up video encoder and callbacks for job job1-3
----------------------------------------------------------------------------------------------------------

Log for job job1-3

avis [info]: 688x368 @ 23.98 fps (143188 frames)
x264 [info]: using cpu capabilities MMX MMXEXT SSE 3DNow!
mp4 [info]: initial delay 250 (scale 2997)
x264 [info]: slice I:920 Avg QP:22.95 size: 10080
x264 [info]: slice P:48241 Avg QP:25.75 size: 1694
x264 [info]: slice B:94027 Avg QP:27.46 size: 515
x264 [info]: mb I I16..4: 33.9% 55.6% 10.5%
x264 [info]: mb P I16..4: 4.5% 4.7% 0.5% P16..4: 26.1% 3.4% 0.8% 0.1% 0.0% skip:59.9%
x264 [info]: mb B I16..4: 0.4% 0.8% 0.1% B16..8: 14.8% 0.4% 0.4% direct: 0.8% skip:82.2%
x264 [info]: 8x8 transform intra:51.2% inter:51.3%
x264 [info]: ref P 64.4% 17.0% 13.7% 4.9%
x264 [info]: ref B 73.3% 14.3% 8.3% 4.1%
x264 [info]: kb/s:186.8

Actual bitrate after encoding without container overhead: 4655.03
desired video bitrate of this job: -262 kbit/s - obtained video bitrate: 189.230153687069 kbit/s
----------------------------------------------------------------------------------------------------------
job job1-3 has been processed. This job is linked to the next job: job1-4
Next job job1-4 is a mux job. mp4box commandline:
"C:\MP4 Encoding\mp4box.exe" -add "D:\PS\VIDEO.mp4" -add "D:\PS\audio.mp4" -chap "D:\PS\VIDEO_TS\VTS_01 - Chapter Information - OGG.txt" -fps 23.976 -new "D:\PS\PS.mp4"
successfully set up muxer and callbacks for job job1-4
----------------------------------------------------------------------------------------------------------

Log for job job1-4

IsoMedia import - track ID 1 - Video (size 688 x 368)
IsoMedia import - track ID 1 - Audio (SR 48000 - 6 channels) - SBR AAC
IsoMedia import - track ID 2 - media type odsm sub-type odsm
IsoMedia import - track ID 3 - media type sdsm sub-type sdsm
Saving D:\PS\PS.mp4: 0.500 secs Interleaving

----------------------------------------------------------------------------------------------------------
Muxjob ended and deletion of intermediate files is activated
----------------------------------------------------------------------------------------------------------

Log for job job1-4

IsoMedia import - track ID 1 - Video (size 688 x 368)
IsoMedia import - track ID 1 - Audio (SR 48000 - 6 channels) - SBR AAC
IsoMedia import - track ID 2 - media type odsm sub-type odsm
IsoMedia import - track ID 3 - media type sdsm sub-type sdsm
Saving D:\PS\PS.mp4: 0.500 secs Interleaving
an exception ocurred when trying to read from stdout: Object reference not set to an instance of an object.
----------------------------------------------------------------------------------------------------------

It seems that MeGui is trying to set my bitrate at -262 kbit/s which seems odd.

Also, I had two other jobs set up. However, even after this job finished, those two jobs didn't go. Let me know if you need any more info.

berrinam
16th October 2005, 21:10
It looks like you have the same problem described by max-holz here (http://forum.doom9.org/showthread.php?p=724074#post724074) and on the development thread. Try using the version posted here (http://forum.doom9.org/showthread.php?p=724251#post724251)

haubrija
17th October 2005, 17:34
It looks like you have the same problem described by max-holz here (http://forum.doom9.org/showthread.php?p=724074#post724074) and on the development thread. Try using the version posted here (http://forum.doom9.org/showthread.php?p=724251#post724251)

Thanks berrinam, that was one of my problems. I ran an encode with 2.2.6a last nite without any problems.

However, I'm still having an issue with MeGui not going to the next job in the queue. I set up two Automated 2-pass encodes and after the first finished, the second failed to start. Its still in the queue, it just didn't automatically start the second job after the first job.

berrinam
17th October 2005, 21:51
Perhaps the first pass had an error? That would cause the queue to stop. If not, please post a log.

haubrija
17th October 2005, 23:16
Perhaps the first pass had an error? That would cause the queue to stop. If not, please post a log.

I can see now I was extremly unclear from my post above, sorry about that.
Here's my issue.

I use MeGui to generate a set of jobs for one backup, then use MeGui to generate another set of jobs for the next backup. For example, I set my first backup to do a 2 pass AutoEncode for x264. This generates four jobs, labeled (I beleive, not in front of encoding machine right now) 1-1,1-2,1-3 and 1-4. Then, I set up my second backup using the same 2 pass AutoEncode and MeGui set them up as 2-1,2-2,2-3 and 2-4. I then press Start.

Now 1-1, 1-2, 1-3 and 1-4 all finish fine. However, the jobs on my second backup never start. This used to work with 2.2.4 as MeGui would continue processing until all jobs were done.

If you look at the look I posted above, you'll see I generated 3 backups. Now after the first backup was done, MeGui doesn't continue to the jobs for the second set of backups. There does seem to be an error for job 1-4:
an exception ocurred when trying to read from stdout: Object reference not set to an instance of an object. I don't know if that's the issue or not.

I have a log for 2.2.6a that I can post when I get home if necessary. Let me know if I was unclear.

Doom9
18th October 2005, 07:16
I don't know if that's the issue or not. It is.. if a job errors out, the queue is stopped. And since that error happens when mp4box cannot be properly started or exits immediately, something is wrong with the mp4box commandline (or the files you're trying to mux) and the log is a must.. as is running the commandline from a command prompt to see if there are any other messages that point towards the error.

Doom9
19th October 2005, 21:49
alright, the subme 7 support is now included in the latest build.

Doom9
23rd October 2005, 20:51
a new build is up. main features are improvements in the queue, x264 configuration and support for the --crf switch in x264

Sharktooth
23rd October 2005, 21:08
Doom9, the --aq switch was removed in the new patch.
the there are only 2 options now, aq-strenght and aq-sensitivity. setting strenght to something other than 0 just enables AQ.

Doom9
23rd October 2005, 22:00
I've updated the AutoQ feature.

Wishbringer
24th October 2005, 12:30
0.2.2.8a 10/23/2005
new: support for the x264 constant quality feature

I thought it used percentage input and inserted 75 like in AutoGK and got a filesize of 4 MB for a whole 90 mins film.
What range is usefull for that new feature?

Sharktooth
24th October 2005, 13:32
@wishbringer: the quantizer.

@doom9: thanks:)

Rafik
24th October 2005, 16:34
Hello everybody !
First, please excuse my english (I'm from Algeria but live in Tunisia). For two years, i used XviD and Ogg Vorbis for my encodings but i lately discovered this codec (x.264) and i find that it's a very impressive one. Thank you for this codec and for MeGui (i use it with GK).
My problem is that when i encode with High Profile (it can w/MP), MPC 6.4.8.4 cannot read it. i have the latest A/V codecs (and all softs relative).
Merci (Oops !), thank you for your help.

Sharktooth
24th October 2005, 16:40
there are some options of the high profile (like custom quantization matrices) that open source decoders doesnt still support. you need to use Nero (sometimes buggy) or Moonlight/Elecard decoders to playback those HP streams made with custom matrices.
However that support is coming and soon even the opensource decoders will support the custom matrices.

Rafik
24th October 2005, 16:47
I don't think that i have used this type ofcustom matrix. Is it automatically employed with HP ?

Sharktooth
24th October 2005, 17:30
no. then you need the latest CVS build of ffdshow.

Rafik
24th October 2005, 21:50
Thank you M. Sharktooth for replying. Are you the one who create x.264 ? Vous êtes un vrai génie ! I go to sourceforge to bring this CVS build of ffdshow but i haven't understand anything. Can you give me a direct link ? i have downlowded the latest version of ffdshow but it doesn't work anyway ...
other questions :
1. what about AAC vs Ogg ?
2. what about a detailed guide for Megui ? now it becomes a great -little complicated- soft (it pursuit the same way of GK in its evolution).
3. will High Profil give me a significant amelioration of quality ?
Thank you.

Sharktooth
24th October 2005, 22:00
Well, i didnt "create" x264, i just build the sources and make the binaries available for windows users.
Get ffdshow from here: http://www.aziendeassociate.it/cd.asp?dir=/ffdshow
or search the doom9 forum for other builds.
the other questions:

1- it depends if you want to use .mp4 container or not. if you're going to use MKV then use Ogg because from the "blind-tests" it was the best audio codec for quality.
2- i just created a thread that may be of help: http://forum.doom9.org/showthread.php?t=101813
3- Yes it will.

Rafik
24th October 2005, 23:16
thank you a lot !
see you soon.

bob0r
25th October 2005, 01:32
Next job job1 is a video job. encoder commandline:
"x264.exe" --crf 26 --ref 8 --mixed-refs --aq-strength 2.0 --aq-sensitivity 22.0 --bframes 4 --b-pyramid --filter -2,-2 --subme 7 --weightb --analyse all --8x8dct --b-bias 4 --progress --no-psnr --output "I:\cap\_x264\test.mp4" "I:\cap\_x264\cap.avs"
successfully set up video encoder and callbacks for job job1
----------------------------------------------------------------------------------------------------------

Log for job job1

avis [info]: 640x352 @ 25.00 fps (7957 frames)
x264 [info]: using cpu capabilities MMX MMXEXT SSE 3DNow!
mp4 [info]: initial delay 2 (scale 25)

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

Can anyone test these settings too?
After the encode Status = error, and the test.mp4 does not play.

Sharktooth
25th October 2005, 02:11
AQ is broken... but not for everyone... bah...

Egh
25th October 2005, 05:44
Seems there's very minor interface bug in last MeGUI version.

If lossless is chosen, Quantizer editbox is disabled, as it should.

But if MeGUI is restarted using same profile, then the editbox is enabled despite "Lossless" being checked. So you can enter value there and thus it's CQ mode now :P

Sharktooth
25th October 2005, 18:27
There's another interface bug. When selecting Main or Baseline Profile, even if 2nd pass or Automated 2-pass is set the Bitrate box gets always resetted to 26.
Selecting High Profile works as expected.

smok3
26th October 2005, 21:40
weird crash on 2nd pass (trying to encode with x264, video only) megui 0.2.2.8, avisynth 2.55, log file:
---------------------------------
Generating jobs. Desired size: 48234496 bytes
No audio encoding. Calculating desired video bitrate directly.
Setting video bitrate for the video jobs to 599 kbit/s
Setting desired size of video to 48164864 bytes
Next job job1-1 is a video job. encoder commandline:
"x264.exe" --pass 1 --bitrate 599 --stats "D:\path\avs.stats" --analyse p8x8,b8x8,i4x4 --progress --no-psnr --output NUL "D:\path\avs.avs"
successfully set up video encoder and callbacks for job job1-1
----------------------------------------------------------------------------------------------------------

Log for job job1-1

avis [info]: 512x384 @ 25.00 fps (16066 frames)
x264 [info]: using cpu capabilities MMX MMXEXT SSE SSE2 3DNow!
x264 [info]: slice I:95 Avg QP:22.51 size: 13430
x264 [info]: slice P:15971 Avg QP:25.90 size: 2916
x264 [info]: mb I I16..4: 32.1% 0.0% 67.9%
x264 [info]: mb P I16..4: 4.5% 0.0% 2.8% P16..4: 39.9% 15.8% 3.0% 0.0% 0.0% skip:34.0%
x264 [info]: kb/s:595.7

Actual bitrate after encoding without container overhead: 595.72

----------------------------------------------------------------------------------------------------------
job job1-1 has been processed. This job is linked to the next job: job1-2
Next job job1-2 is a video job. encoder commandline:
"x264.exe" --pass 2 --bitrate 599 --stats "D:\path\avs.stats" --analyse p8x8,b8x8,i4x4 --progress --no-psnr --output "D:\path\avs.mp4" "D:\path\avs.avs"
successfully set up video encoder and callbacks for job job1-2
----------------------------------------------------------------------------------------------------------

Log for job job1-2

avis [info]: 512x384 @ 25.00 fps (16066 frames)
x264 [info]: using cpu capabilities MMX MMXEXT SSE SSE2 3DNow!
mp4 [info]: initial delay 0 (scale 25)
x264 [error]: More input frames than in the 1st pass
Assertion failed: frame >= 0 && frame < rc->num_entries, file encoder/ratecontrol.c, line 467

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

----------------------------------------------------------------------------------------------------------
The current job contains errors. Skipping chained jobs

QuadraQ
27th October 2005, 04:27
I'm trying to get MeGUI up and running, and I downloaded all the necessary software and set up the directories in MeGUI. However, the link for bse_FAAC.dll isn't working because the files have expired. I did a search and found the dll, but I think it's an old version, because when I choose the FAAC option in MeGUI the audio starts to encode, but quits immediately. It works OK when using the Nero encoder. If someone could point me to the latest version of the bse_FAAC.dll I'd appreciate it.

For video, I don't know what's going wrong. It starts the first pass and the status dialog box comes up, but never changes. There's lots of hard drive activity and when I check the task manager it shows that x265.exe is using ninety-some percent of the processor, but even after four hours the pass isn't complete. (I know from using AutoAC that it doesn't take THAT long on my machine.) The status screen hasn't changed, and the x264 app and hard drive activity are just the same, so it seems that it's hanging on something. Any ideas? :confused:

Here is a pic to illustrate what I mean:
http://www.mindspring.com/~quadra2/MeGUI%20Problem.PNG

It just stays like this indefinitely.

Here are my settings:
http://www.mindspring.com/~quadra2/MeGUI%20Settings.PNG

Help! I want to get MeGUI working, so that I can start backing up my DVD collection to mp4 files that I can watch on my xbox. Thanks.

Doom9
28th October 2005, 16:40
@QuadraQ: where is the most important of all, ... the logfile? take the x264 commandline from there, start a command prompt (start - run - type "cmd" and press enter), paste the commandline and press enter, then see what is happening.

QuadraQ
29th October 2005, 01:47
The "logs" directory in my MeGUI directory is empty, so how do I get the command line without a log?

jellysandwich
29th October 2005, 02:54
The "logs" directory in my MeGUI directory is empty, so how do I get the command line without a log?

You can get the command line through MeGUI itself. There's a button that says "Show commandline."

js

QuadraQ
29th October 2005, 07:28
OK here is the command line:

"x264.exe" --pass 2 --bitrate 1129 --stats ".stats" --aq-strength 0.5 --no-cabac --analyse p8x8,b8x8,i4x4 --progress --no-psnr --output "C:\SONY\VIDEO_TS\The Net.mp4" "C:\SONY\VIDEO_TS\The Net.avs"

and the error I'm getting at the command line:

C:\Program Files\x264>"x264.exe" --pass 2 --bitrate 1129 --stats ".stats" --aq-s
trength 0.5 --no-cabac --analyse p8x8,b8x8,i4x4 --progress --no-psnr --output "C
:\SONY\VIDEO_TS\The Net.mp4" "C:\SONY\VIDEO_TS\The Net.avs"
avis [info]: 640x352 @ 0.00 fps (165080 frames)
x264 [error]: ratecontrol_init: can't open stats file
x264_encoder_open failed

I'm not sure if this is what you wanted. I don't use the command line much.

berrinam
29th October 2005, 08:46
avis [info]: 640x352 @ 0.00 fps (165080 frames)
Something's up with your AviSynth file; the framerate should not be 0. See if you get the same framerate with (a) other avisynth files, or (b) other programs, like VirtualDub(mod). Also, if you know what the framerate should be, try adding assumefps(25.0) to the end of your avisynth file, replacing 25.0 with the correct framerate.

x264 [error]: ratecontrol_init: can't open stats file
x264_encoder_open failedThis shouldn't be the problem, because it is just due to the way MeGUI handles stats files.

Doom9
29th October 2005, 11:04
This shouldn't be the problem, because it is just due to the way MeGUI handles stats files.But without a first pass, it'll never work. The framerate is definitely the first thing to look into, but if that doesn't work out, please try a valid first pass commandline (just change encoding mode to 2pass first pass.. your settings won't be changed but if you configure automated 2 or 3 pass.

berrinam
29th October 2005, 11:27
This shouldn't be the problem, because it is just due to the way MeGUI handles stats files.
What I meant was that this problem was caused because of the incomplete commandline given in the x264 config dialog, which isn't actually a problem when it comes to encoding, as the stats file is filled in.

Of course, you're right; a first pass is definitely needed.

QuadraQ
29th October 2005, 20:02
OK, I switched to "2pass - 1st pass" copied the command line and ran it. Still had 0 fps but this time x264 actually launched and started doing something (Although like you said 0 fps is still wrong, and it seems to me that x264 should probably just quit if given that invalid fps.) Basically the disk activity went out the roof and x264 started sucking down all the processor time like I previously described.

What doesn't make sense to me, is that in the bitrate calculator window of MeGUI it said 25 fps when I first opened it up (which is wrong BTW, since this is not a PAL encoded video, or even a "true" NTSC 30 fps, but a film source which should be 23.976 fps). I changed it to 23.976 to reflect that this is a film source, and had it acount for 128 kbps AAC audio and clicked save. I guess those settings didn't reflect in the command line I pulled from the codec configuration window.

Doom9
29th October 2005, 20:24
you do need to fill out the name of the stats file in this case.. the commandline you get in the codec configuration screen is not complete. Did you try all the things berrinam suggested? Also, next time please just copy&paste the contents from the commandline window (and only the part that does matter.. starting with the commandline).

QuadraQ
29th October 2005, 21:38
OK I edited the avs file (didn't realize there was so little in there) and added the line berrinam suggested, so that the contents of my avs file are this:

mpeg2source("C:\SONY\VIDEO_TS\VTS_01_1.d2v")
crop(4,0,-8,-2)
LanczosResize(640,352)
assumefps(23.976)

and then I gave the stats file a name in the command line and this is what I got:

C:\Program Files\x264>"x264.exe" --pass 1 --bitrate 759 --stats "test.stats" --a
q-strength 0.5 --no-cabac --subme 1 --analyse none --me dia --progress --no-psnr
--output NUL "C:\SONY\VIDEO_TS\The Net.avs"
avis [info]: 640x352 @ 23.98 fps (165072 frames)
x264 [info]: using cpu capabilities MMX MMXEXT SSE 3DNow!
encoded frames: 826/165072 (0.5%), 23.42 fps

So it looks like it's working now at least from the command line.

So at least I've learned a few things. Still I'm not sure why the AVS script didn't have the fps information in it in the first place. What else should I try now? I appreciate your help.

berrinam
29th October 2005, 23:59
Well, if it works in the commandline, it should almost definitely work from MeGUI, too.

As to the problem with AviSynth, see if other AviSynth scripts also signal 0fps (I doubt it, considering that it worked when you added assumefps(...)), or try using the same script with VirtualDub. OTOH, perhaps it is just an unusual source.

QuadraQ
30th October 2005, 00:25
I've got MeGUI working on it now. I'll let you know what the results are. Assuming it works, then the next thing is to figure out why the avs script created in MeGUI didn't include the fps...

hpn
30th October 2005, 03:19
A small bug: When I start MeGUI, specify the avs then click "Config", it's initialized with ABR mode with bitrate 26, instead of bitrate 700. Switching to Const.quantizer then back to ABR fixes the bitrate to its normal value.

EDIT: oops, it's been posted above by ST, sorry

QuadraQ
31st October 2005, 00:46
OK, just an update. MeGUI did finish the job of creating the video mp4 file this time using the automated two-pass option and the "fixed" avs script (see previous posts). However the video file is corrrupt or something. When I try to play it I get a garbled scene from the movie, and then Media Player Classic crashes. (Same results for any other media players I've tried.) So I'm going to have to create a small test so that I can quickly test things. (It took all night to finish the encoding job for the entire movie.)

I'm not sure why I'm having so much trouble getting MeGUI Setup. From what I can tell, MeGUI is THE tool for creating x.264 mp4 files, but I guess I'm cursed.

Any suggestions would be appreciated. Thanks.

acidsex
31st October 2005, 01:15
Finally got around to playing with this a little today and I must say, I am VERY impressed with Doom9 and others work on this. Took a couple minutes getting used to the layout and finding where everything is but once that was under control I was off to encoding in no time. Still waiting for encode to finish but if the finished encode comes out well, I may have found my new favorite encode tool.

I am assuming Doom9 is accepting donations for all of this hard work and if so, where do I send?

Awesome work and much appreciation from this user. :)

Blue_MiSfit
31st October 2005, 02:20
So erm... little problem here. I am trying to run an x264 comptest - CQ18 with the following settings:

keyframe interval: 240
6 refs, mixed
3 bframes, pyramid, adaptive
deblock 0,0
cabac
rdo2
weighted prediction, chroma me
all macroblock options
otherwise all defaults

I am using MeGUI 0.2.2.8 downloaded off this forum 5 minutes ago, and the latest x264 package from x264.nl, v348.

My avs script works perfectly fine, tested with vdub and core media player.

The problem is as follows. I queue the job, targeting MP4. input and output files are perfectly valid. When I go to the queue and start the job, it starts for a moment and then exits immediately. Here is the log:


Next job job1 is a video job. encoder commandline:
"C:\Program Files\x264\x264.exe" --qp 18 --keyint 240 --min-keyint 24 --ref 6 --mixed-refs --aq-strength 0.5 --bframes 3 --b-pyramid --subme 7 --weightb --analyse all --8x8dct --progress --no-psnr --output "E:\Movies Work 2\New Jack City\New Jack City.mp4" "E:\Movies Work 2\New Jack City\New Jack City.avs"
successfully set up video encoder and callbacks for job job1
----------------------------------------------------------------------------------------------------------

Log for job job1

unknown option (


wtf? :)

Any ideas? Everything was working perfectly fine before when I had 0.2.2.6, which interestingly enough had the option to DISABLE adaptive quant. I noticed this error before whenever I tried to use adaptive quant, and so I had always just disabled it. Now with 0.2.2.8, there is no option to disable adaptive quant (that I have noticed)

I guess my questions are
1) why is using AQ crashing things?
2) how can I disable it with 0.2.2.8


Just tried manually CLI encoding, it crashes saying something about unknown option. Removing "--aq-strength 0.5" from the commandline makes the encode start normally.

I read also that AQ is broken for some, but not all. What's the latest on this?


Thanks all
~MiSfit

QuadraQ
31st October 2005, 05:41
OK I created a small test d2v file and then opened it up in MeGUI just to test the AviSynth Script Creator function. I load the d2v file and the click the Suggest Resolution check box, which selects a resolution of 640 x 352. I then click the Auto Crop button which checks the crop checkbox and chooses a value of 2 for the right and bottom of the image. (The Input DAR is 16:9 and the Resize Filter is Lanczos (Sharp) which I never changed.) I then click the Edit tab to see what the AVS script will be and this is what I find:

mpeg2source("C:\TWO_WEEKS_NOTICE\VIDEO_TS\Test.d2v")
crop(0,0,-2,-2)
LanczosResize(640,352)

So again the fps is missing. Any ideas why? The d2v project was manually generated from DGIndex 1.4.4.

berrinam
31st October 2005, 05:59
@Blue_MiSfit: bob0r's builds at x264.nl don't support AQ. If you want AQ, try Sharktooth's builds from the sticky. If you want to disable AQ, set strength to 0.0

@QuadraQ: Do you mean that, when you encode it, it signals 0.0fps, as before? There is nothing wrong with the generated script, and you seem to have had the same problem with two films, so there is probably something wrong with either DGIndex or AviSynth on your computer. Try reinstalling them.

Doom9
31st October 2005, 08:54
I am assuming Doom9 is accepting donations for all of this hard work and if so, where do I send?Not for the software specifically, but since it's me doing it in both cases, you can go here: http://www.doom9.org/donate.htm

@QuadraQ: if it's still not clear: adding assumefps to an AviSynth script is a workaround for what you're encountering. It is most likely an issue with your AviSynth installation and is definitely not a MeGUI issue. If you load your script in the main window, then go to the calculator, that's when MeGUI will show what it found out with regards to the framerate.. it uses that for calculations and mp4 muxing (unless you manually specify another framerate). If the fps value in the calculator is wrong (you absolutely must load your AviSynth script before entering the calculator), then that once again hints at an AviSynth problem and you should get the same fps report when opening the script in VirtualDub because both use AviFile to get the file properties.

QuadraQ
1st November 2005, 02:58
@QuadraQ: if it's still not clear: adding assumefps to an AviSynth script is a workaround for what you're encountering. It is most likely an issue with your AviSynth installation and is definitely not a MeGUI issue. If you load your script in the main window, then go to the calculator, that's when MeGUI will show what it found out with regards to the framerate.. it uses that for calculations and mp4 muxing (unless you manually specify another framerate). If the fps value in the calculator is wrong (you absolutely must load your AviSynth script before entering the calculator), then that once again hints at an AviSynth problem and you should get the same fps report when opening the script in VirtualDub because both use AviFile to get the file properties.

I just got back from work, and to give you and update of what I discovered last night, you are right (of course). I'm basically sure that the problem at this point it the DGIndex dll or program. The reason I say that is that if I manually create the d2v file from within DGIndex 1.4.4 and then load it in MeGUI to create the AVS script it works fine. However if I try to create the d2v project file from within MeGUI, then I experience the problems previously described. So I'm going to try downloading the latest version of DGIndex and then make sure that I have the latest version of the dll everywhere it's supposed to be installed.

BTW how exactly does that work, as far as the integration of DGIndex and MeGUI?