MeGUI: General Questions and Troubleshooting Thread

[dimzon]

Ok, I just tried encoding the video only and this is what the log says:

And I triple checked that x264 was pointing correctly. In the queue it shows up as done. Being a newb sucks.
:readrule: :readfaq: :logfile: :script:

[Doom9]

what's wrong with this picture:
Starting job job2-2 at 1:07:41 AM
...
Processing ended at 1:07:43 AMWithout any knowledge whatsoever, 2 seconds is pretty darned fast for encoding time, don't you think? So, even though you know nothing of megui and x264, you should reasonably conclude that something went wrong during video encoding.. it just never takes two seconds.. never ever ever ever ever. I mean your audio took 30 minutes, and generally video is a lot more complex than audio. So then you could for instance head over to the bug report thread (http://forum.doom9.org/showthread.php?t=105160) and look at point to be done. 1) not found, 2) you did that, 3) you forgot that, lucky for you the issue here is rather self-explanatory. 5) you forgot about that, 6) I don't see a build number anywhere (/me makes a mental note to consider putting the build number in the log.. it's such a little thing but people just love to forget it.. it's pathological really), 7) it's not megui but you couldn't know that, that is, unless you performed 8). It's really simple. If something doesn't work out, perform steps 1 to 8 and make your post thereafter. Nobody can guarantee that this will help, but experience shows that in a large portion of all cases, it allows to pinpoint the problem without further ado, and that saves everyone time and effort.

[spunch]

Did anyone ever hear of files spontaneously disappear when using the oneclick encoder, right after doing the muxing job? I can't figure this thing out. I'm probably missing something, new to MeGUI and all.

I know everything goes well untill the muxing job, I can even pause the job and watch the video, but as soon as it gets to muxing the file with the *_Video.mkv prefix, it disappears and nothing else seems to be outputted.

I tried:
MeGUI-0.2.3.2063-Stable
MeGUI-0.2.3.2092-Dev
MeGUI.NETv2.0_Bins_0.2.3.2033

The rest of my toolbox:
lame3.98a3
MP4Box_20060217
mkvtoolnix-unicode-1.6.5
x264-Lite_r408
MeGUI-x264_generic_profiles_v20


----------------------------------------------------------------------------------------------------------
job job2-1 has been processed. This job is linked to the next job: job2-2
Starting job job2-2 at 00:48:02
Job is a mux job. Commandline:
-o "F:\videoshit\dad.mkv" -A -S "F:\videoshit\dad_Video.mkv" --no-clusters-in-meta-seek
successfully set up muxer
Processing ended at 00:48:02
----------------------------------------------------------------------------------------------------------

Log for job job2-2


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

[berrinam]

Did anyone ever hear of files spontaneously disappear when using the oneclick encoder, right after doing the muxing job?How about the option in Settings which says 'delete intermediate files after successful encoding', or something like that? My guess is that you have that checked, so after the mux job is completed, the intermediate files are deleted, of which *_Video.mkv is one.

It would normally leave the muxed file, but judging by this:
Starting job job2-2 at 00:48:02
...Processing ended at 00:48:02
the mux job didn't complete (nothing takes 0 seconds).

The problem is that this job isn't properly being detected as errored. You need to work out what is wrong with your mkv muxing. Check if it is set up properly, etc.

[nufan292]

what's wrong with this picture:
Without any knowledge whatsoever, 2 seconds is pretty darned fast for encoding time, don't you think? So, even though you know nothing of megui and x264, you should reasonably conclude that something went wrong during video encoding.. it just never takes two seconds.. never ever ever ever ever. I mean your audio took 30 minutes, and generally video is a lot more complex than audio. So then you could for instance head over to the bug report thread (http://forum.doom9.org/showthread.php?t=105160) and look at point to be done. 1) not found, 2) you did that, 3) you forgot that, lucky for you the issue here is rather self-explanatory. 5) you forgot about that, 6) I don't see a build number anywhere (/me makes a mental note to consider putting the build number in the log.. it's such a little thing but people just love to forget it.. it's pathological really), 7) it's not megui but you couldn't know that, that is, unless you performed 8). It's really simple. If something doesn't work out, perform steps 1 to 8 and make your post thereafter. Nobody can guarantee that this will help, but experience shows that in a large portion of all cases, it allows to pinpoint the problem without further ado, and that saves everyone time and effort.
Will do this weekend, thanks for the response.

[nufan292]

Well, I was bored so I tried a newer build of MeGuii and guess what . . . got some love. Thanks.

[spunch]

Uhh the frustration... I'm trying to encode a few clips using the oneclick encoder and MeGUI is giving me a few problems... I have two jobs, both are entirely identical except for 3 lines, one works fine, the other crashes MeGUI without any indication of what may have happened.

A file comparison reveals these differences:


Compare: (<)F:\encoding\MeGUI-0.2.3.2095-Dev\job1.xml (5391 bytes)
with: (>)F:\encoding\MeGUI-0.2.3.2095-Dev\job2.xml (5396 bytes)

5,8c5,8
< <Name>job1</Name>
< <Priority>IDLE</Priority>
< <Status>WAITING</Status>
< <Position>0</Position>
---
> <Name>job2</Name>
> <Priority>IDLE</Priority>
> <Status>WAITING</Status>
> <Position>1</Position>

12,15c12,15
< <Commandline>"F:\encoding\dgmpgdec146\DGIndex.exe" -AIF=[F:\STASHTESTS\I2_STASH05_VTS_01_032.VOB] -OF=[F:\STASHTESTS\I2_STASH05_VTS_01_032] -exit -OM=0</Commandline>
< <AutoForceFilm>true</AutoForceFilm>
< <LoadSources>false</LoadSources>
< <AudioTrackID1>-1</AudioTrackID1>
---
> <Commandline>"F:\encoding\dgmpgdec146\DGIndex.exe" -AIF=[F:\STASHTESTS\I2_STASH05_VTS_01_032.VOB] -OF=[F:\STASHTESTS\I2_STASH05_VTS_01_032] -exit -OM=1 -TN=1</Commandline>
> <AutoForceFilm>true</AutoForceFilm>
> <LoadSources>false</LoadSources>
> <AudioTrackID1>0</AudioTrackID1>


I need the sound on these clips and I can't figure out what's causing this unprompted crash.

I also noticed MeGUI takes a lot of resources at the beginning of job1, right before it fires up x264.exe. In the first few 10-20 seconds MeGUI jumps from 30mb ram consumption to 200mb, and max out my CPU. It's definitely not dgindex, it's a short clip and it takes dgindex less than a second to do it's thing, and it's not lame.exe either, since there is no audio on job1. It is something internal, process explorer reveals some thread called mscrowks.dll!CreateApplicationContext+0xc461, could anybody tell me what it is?

job2.xml in its entirety:


<?xml version="1.0"?>
<Job xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xsi:type="IndexJob">
<Input>F:\STASHTESTS\I2_STASH05_VTS_01_032.VOB</Input>
<Output>F:\STASHTESTS\I2_STASH05_VTS_01_032.d2v</Output>
<Name>job2</Name>
<Priority>IDLE</Priority>
<Status>WAITING</Status>
<Position>1</Position>
<Start>0001-01-01T00:00:00</Start>
<End>0001-01-01T00:00:00</End>
<FPS>0</FPS>
<Commandline>"F:\encoding\dgmpgdec146\DGIndex.exe" -AIF=[F:\STASHTESTS\I2_STASH05_VTS_01_032.VOB] -OF=[F:\STASHTESTS\I2_STASH05_VTS_01_032] -exit -OM=1 -TN=1</Commandline>
<AutoForceFilm>true</AutoForceFilm>
<LoadSources>false</LoadSources>
<AudioTrackID1>0</AudioTrackID1>
<AudioTrackID2>-1</AudioTrackID2>
<DemuxMode>1</DemuxMode>
<ForceFilmThreshold>95</ForceFilmThreshold>
<PostprocessingProperties>
<AutoDeinterlace>true</AutoDeinterlace>
<AutoDeriveAR>true</AutoDeriveAR>
<SignalAR>false</SignalAR>
<HorizontalOutputResolution>640</HorizontalOutputResolution>
<Container>1</Container>
<OutputSize>-1024</OutputSize>
<SplitSize>0</SplitSize>
<AR>A1x1</AR>
<AvsSettings>
<Template>&lt;input&gt;
&lt;deinterlace&gt;
&lt;crop&gt;
&lt;resize&gt;
&lt;denoise&gt;
</Template>
<ResizeMethod>Lanczos</ResizeMethod>
<DenoiseMethod>MinimalNoise</DenoiseMethod>
<Deinterlace>false</Deinterlace>
<Denoise>false</Denoise>
<IVTC>false</IVTC>
<MPEG2Deblock>false</MPEG2Deblock>
<ColourCorrect>false</ColourCorrect>
</AvsSettings>
<AudioSettings>
<AudioCodecSettings xsi:type="MP3Settings">
<ImproveAccuracy>true</ImproveAccuracy>
<SourceIsMultichannel>false</SourceIsMultichannel>
<EncodeViaBeSweet>false</EncodeViaBeSweet>
<ForceDecodingViaDirectShow>false</ForceDecodingViaDirectShow>
<DownmixMode>StereoDownmix</DownmixMode>
<BitrateMode>ABR</BitrateMode>
<Bitrate>128</Bitrate>
<Delay>33</Delay>
<DelayEnabled>true</DelayEnabled>
<AutoGain>true</AutoGain>
<Quality>50</Quality>
</AudioCodecSettings>
<AudioCodecSettings xsi:type="MP3Settings">
<ImproveAccuracy>true</ImproveAccuracy>
<SourceIsMultichannel>false</SourceIsMultichannel>
<EncodeViaBeSweet>false</EncodeViaBeSweet>
<ForceDecodingViaDirectShow>false</ForceDecodingViaDirectShow>
<DownmixMode>StereoDownmix</DownmixMode>
<BitrateMode>ABR</BitrateMode>
<Bitrate>128</Bitrate>
<Delay>33</Delay>
<DelayEnabled>true</DelayEnabled>
<AutoGain>true</AutoGain>
<Quality>50</Quality>
</AudioCodecSettings>
</AudioSettings>
<VideoSettings xsi:type="x264Settings">
<EncodingMode>0</EncodingMode>
<BitrateQuantizer>1000</BitrateQuantizer>
<KeyframeInterval>250</KeyframeInterval>
<NbBframes>0</NbBframes>
<MinQuantizer>10</MinQuantizer>
<MaxQuantizer>51</MaxQuantizer>
<PARX>0</PARX>
<PARY>0</PARY>
<Turbo>false</Turbo>
<V4MV>false</V4MV>
<QPel>false</QPel>
<Trellis>false</Trellis>
<CreditsQuantizer>40</CreditsQuantizer>
<Logfile>.stats</Logfile>
<CustomEncoderOptions />
<FourCC>1</FourCC>
<Zones />
<PSNRCalculation>false</PSNRCalculation>
<noFastPSkip>false</noFastPSkip>
<NoiseReduction>0</NoiseReduction>
<MixedRefs>false</MixedRefs>
<X264Trellis>0</X264Trellis>
<NbRefFrames>1</NbRefFrames>
<AlphaDeblock>0</AlphaDeblock>
<BetaDeblock>0</BetaDeblock>
<SubPelRefinement>0</SubPelRefinement>
<MaxQuantDelta>4</MaxQuantDelta>
<TempQuantBlur>0</TempQuantBlur>
<BframePredictionMode>0</BframePredictionMode>
<VBVBufferSize>-1</VBVBufferSize>
<VBVMaxBitrate>-1</VBVMaxBitrate>
<METype>0</METype>
<MERange>16</MERange>
<NbThreads>1</NbThreads>
<MinGOPSize>25</MinGOPSize>
<Profile>0</Profile>
<Level>15</Level>
<IPFactor>1.4</IPFactor>
<PBFactor>1.3</PBFactor>
<ChromaQPOffset>0</ChromaQPOffset>
<VBVInitialBuffer>0.9</VBVInitialBuffer>
<BitrateVariance>1.0</BitrateVariance>
<QuantCompression>0.6</QuantCompression>
<TempComplexityBlur>20</TempComplexityBlur>
<TempQuanBlurCC>0.5</TempQuanBlurCC>
<SCDSensitivity>40</SCDSensitivity>
<BframeBias>0</BframeBias>
<Deblock>false</Deblock>
<Cabac>false</Cabac>
<WeightedBPrediction>false</WeightedBPrediction>
<AdaptiveBFrames>false</AdaptiveBFrames>
<BFramePyramid>false</BFramePyramid>
<BRDO>false</BRDO>
<biME>false</biME>
<ChromaME>false</ChromaME>
<P8x8mv>true</P8x8mv>
<B8x8mv>true</B8x8mv>
<I4x4mv>true</I4x4mv>
<I8x8mv>false</I8x8mv>
<P4x4mv>true</P4x4mv>
<AdaptiveDCT>false</AdaptiveDCT>
<Lossless>false</Lossless>
<QuantizerMatrix />
<QuantizerMatrixType>0</QuantizerMatrixType>
</VideoSettings>
<CustomAR>1</CustomAR>
<ChapterFile />
<FinalOutput />
<AviSynthScript />
<AudioLanguages>
<string />
<string />
</AudioLanguages>
</PostprocessingProperties>
</Job>

[Doom9]

I need the sound on these clips and I can't figure out what's causing this unprompted crash.I take it job2 crashes, and job1 does not, is that correct? Which dgindex version are you using? And could you run both commandlines from the commandprompt to see if there's anything you might see that you don't get in megui?
It is something internal, process explorer reveals some thread called mscrowks.dll!CreateApplicationContext+0xc461, sounds like that's when it creates the x264.exe process. Since you know diff and process explorer, any chance you could step through private void UpdateGUIStatus(StatusUpdate su) in Form1.cs.. you should see the line where that behavior stems from.. but since x264.exe takes 200mb iirc it's not surprising that the memory usage goes up like that.. it may just be the way of starting a process from within the .NET framework. If you keep watching the RAM usage, doesn't that additional ram simply transfer over to x264.exe once it shows up in the process list?

[spunch]

I take it job2 crashes, and job1 does not, is that correct? Which dgindex version are you using? And could you run both commandlines from the commandprompt to see if there's anything you might see that you don't get in megui?
Yes, job2 is the one that's failing, possibly because of something to do with the audio. Although, even when it fails it outputs the dgindex .d2v and .ac3 files just fine. There are no differences between them and files created manually in dgindex. using the command line works just how you'd expect it to work. Same .d2v and a playable .ac3.

You should know that when I generated these jobs I changed some of the defaults in the OneClickEncoder window:
* Target filesize from 1 CD (700mb) to Don't Care (-1)
* Checked Automatic Deinterlacing
* Contrainer from MP4 to MKV
* Used a custom MP3 audio profile.

I'm using dgmpgdec v1.4.6, MeGUI-0.2.3.2095-Dev (also tried on MeGUI-0.2.3.2063-Stable with same results), mkvtoolnix v1.6.5, lame3.98a3, and a freshly installed and patched Windows XP SP2.

I also tried it on several different VOB clips (from the same source) that resulted in the same crash.

If you keep watching the RAM usage, doesn't that additional ram simply transfer over to x264.exe once it shows up in the process list?
It's exactly what happens.

[dimzon]

@spunch
Does you possible to encode resulting AC3 into MP3 via MeGUI using AviSynth audio ?

[spunch]

I tried NAAC, still crashing...

[dimzon]

I tried NAAC, still crashing...
No, you doesn't understand me

Although, even when it fails it outputs the dgindex .d2v and .ac3 files just fine. There are no differences between them and files created manually in dgindex. using the command line works just how you'd expect it to work. Same .d2v and a playable .ac3.
Run MeGUI and create simple Audio encoding job (using obtained AC3)
If MeGUI still crash trying to encode this AC3 try to switch to BeSweet encoding.
If MeGUI doesn't crash on AC3 encoding via BeSweet it means problem is in AviSynth audio compression
In this case try to create such AVS script:

NicAc3Source("myfile.ac3")

and try to play this AVS file via any DirectShow player...

[spunch]

MeGUI does not crash at a simple audio encoding job, no matter how I do it.

MeGUI continues to crash, even when I encode job2 audio via BeSweet.

[dimzon]

MeGUI does not crash at a simple audio encoding job, no matter how I do it.
Good

MeGUI continues to crash, even when I encode job2 audio via BeSweet.
Can you provide smallest as possible VOB file (below 20MB) to reproduce this error? Seems like we (developers) must debug MeGUI...

[Doom9]

Used a custom MP3 audio profile.But that implies that you should get an audio job, yet you mentioned you have none, and that's really weird. Is it too much to hope for that you can also manage a debugger besides processexplorer?

[spunch]

What do you mean an audio job? It's a OneClick job. As I understand it, a OneClick job is responsible for creating 3 different jobs, for video audio and muxing. MeGUI is too quick to crash so I can't really see if it created those jobs.

I'll see what I can do about debugging, never really done it before. I uploaded a VOB clip as well. www.hayarealestate.com/temp/I2_STASH05_VTS_01_032.VOB. Please let me know when you're done downloading.

[spunch]

So are you planning on downloading it anytime soon?

[Doom9]

well.. whenever I have time to do something, I work on refactoring and what I have on my HD is in no way capable of even launching the one click mode at this point so even if I wanted, I just couldn't try it.

[dimzon]

So are you planning on downloading it anytime soon?
I will download it next night (i'm @ office now and i can't download multimtdia content here)

[spunch]

I've been putting it off for a long time already, could anyone with debugging knowledge just download the clip I provided and try to encode it using the job2.xml file I mentioned above?

[Doom9]

@spunch: I'm still waiting for a reply to the questions I asked in my first reply right after you posted your problem report.

[spunch]

I think I answered all your questions already. If I wasn't clear before:
I take it job2 crashes, and job1 does not, is that correct?
Yes. MeGUI handles job1 (video only) just fine, job2 (video+audio) is the one that crashes, 2 seconds after I press the Start button.

Which dgindex version are you using?
dgmpgdec v1.4.6

could you run both commandlines from the commandprompt to see if there's anything you might see that you don't get in megui?
Running both commandlines from the commandprompt does not reveal anything that might suggest that dgindex is the source of the problem, both commandlines work fine.

any chance you could step through private void UpdateGUIStatus(StatusUpdate su) in Form1.cs
Sorry, I would not know how to do that.

[cc979]

I think I answered all your questions already. If I wasn't clear before:

Yes. MeGUI handles job1 (video only) just fine, job2 (video+audio) is the one that crashes, 2 seconds after I press the Start button.


dgmpgdec v1.4.6


Running both commandlines from the commandprompt does not reveal anything that might suggest that dgindex is the source of the problem, both commandlines work fine.


Sorry, I would not know how to do that.

i've noticed dgindex crashes if it does not have dvd-decrypt info file using the 1click method

but it is fine if you manually use dgindex to create d2v file

[berrinam]

i've noticed dgindex crashes if it does not have dvd-decrypt info file using the 1click methodArgh! Why don't you report this kind of thing as a bug in the Bug Report thread, instead of just coping with it? It's best if we know about the bugs, so that we can fix them.

[spunch]

How am I suppose to give you a bug report when megui crashes with no error or output and I have no debugging expertise? I gave you the file in question, I gave you the job in question, why not take 5 minutes and try to recreate this crash yourselves? It really doesn't take much effort, you don't have to wait and encode the whole video, simply if you see megui doesn't crash in the first 5 seconds after starting the job then it is something wrong with my setting and I could stop bugging you.

[ChronoCross]

How am I suppose to give you a bug report when megui crashes with no error or output and I have no debugging expertise? I gave you the file in question, I gave you the job in question, why not take 5 minutes and try to recreate this crash yourselves? It really doesn't take much effort, you don't have to wait and encode the whole video, simply if you see megui doesn't crash in the first 5 seconds after starting the job then it is something wrong with my setting and I could stop bugging you.

because this is the wrong thread for bug-reports. plus not all of us have an apparently infinite amount of time to do testing. you should show some more respect else you should just keep your mouth shut.

[berrinam]

@spunch and ChronoCross: I think you guys misunderstood me. When I read spunch's post, I immediately tested it myself, found the bug, fixed it, posted a new version:

0.2.3.2105 5 March 2006
Commit by berrinam:
- Fixed bug with OneClick processing which caused a fatal KeyNotFoundException when the stream info file was missing

I was simply frustrated by the fact that cc979 seemed to be thinking "OK, it crashes for me, but if I do this workaround it doesn't bother me". If everyone thinks that way, then we never find out about the bugs in the first place and we never fix them as a result. It seems to me that the only reason that we found out about this problem was as a result of cc979 giving advice to spunch. Since cc979 knew about this problem, he could have told us about it earlier, and the whole problem would have been avoided.

I can see that cc979 might not have wanted to bother us, but trust me, we really want you to tell us about the bugs, as long as you read the bug-reporting guidelines first and show a little common sense.

How am I suppose to give you a bug report when megui crashes with no error or output and I have no debugging expertise?You don't need expertise, just read the guidelines, as I said above.

I'm sorry if I caused some confusion.

Summary:
If you think you have found a bug in MeGUI, please don't just ignore it and hope someone else will mention it. Read the Bug Reporting guidelines, and then make a good bug report on the bug report thread

[spunch]

Sorry and thank you for fixing this bug! You have to understand this is my first time using megui so I initially thought I perhaps misunderstood some commonsense guideline and was doing something wrong. Considering megui didn't even output an error message, I turned to the troubleshooting thread.

Thank you again!

[cc979]

Argh! Why don't you report this kind of thing as a bug in the Bug Report thread, instead of just coping with it? It's best if we know about the bugs, so that we can fix them.

opps, sorry - thought it was known

[Shootist]

I am not able to use megui x264 (x264.nl build 457) anymore. Everytime I want to config the gui by clicking the "config" button it crashs. I am using winxp sp2 without any other patches + .net framework 2.0 (file version says 2.0.50727.42).

The 424 build is the last build I used which worked.
I have no idea what I am doing wrong. Any ideas? Thank you.

[desta]

I've been using MeGUI 0.2.3.2090, with no problems, and I just started a new project. I'd already created my d2v file with DGIndex 1.4.5 (which had correctly reported my vobs as PAL, Progressive), so I went ahead and used the AVS Script Creator in MeGUI. I told it to analyze the frames.. it did, and also came back as progressive.

At this point, it occured to me to see if there was a newer version of MeGUI - I went off and quickly found Chronocross' latest 0.2.3.2107 build, so downloaded that, set it up and started again from the AVS Creator.

This time the analysis came back saying...

"Source type: Source is declared hybrid progressive/interlaced. This should be deinterlaced by a deinterlacer that tries to weave it before deinterlacing. Source is hybrid bff and tff at 12 bff and 15 tff."


... Why's it suddenly changed? I've gone through the source myself and I honestly can't see the slightest bit of interlacing.

I've more than likely not given enough information, so let me know if anything else is needed, and I'll give it. Suggestions greatly appreciated.

[berrinam]

I don't think anything should have changed in regards to that. I'm posting an update which will display some information for debugging, so can you run it with that and show me your results?

Also, it doesn't sound like you are using a very large source, since there are only 27 analyzed sections. How long is it?

[berrinam]

Version with extra debugging here:

http://rapidshare.de/files/14890306/megui-2108.zip.html

[desta]

Thanks for the reply.

Well, I just tried that (there was only the MeGUI.exe itself in that zip) and it came back with...

"Source type: For your reference:
Progressive Sections: 58
Interlaced Sections: 4
Partial Static Sections: 122
Film Sections: 0
Source is declared hybrid progressive/interlaced. This should be deinterlaced by a deinterlacer that tries to weave it before deinterlacing."

As with the previous attempt, it runs it's first analysis, runs againly slowly, giving those results.

To answer your question, the source is 61mins long. It's actually the Star Wars: Clone Wars - volume 2 (animated). I have tried both setting and not setting MeGUI to 'Source is Anime'. Both results come back the same. I actually encoded volume 1 with MeGUI 0.2.3.2090 - which was also progressive.

The only thing I can think of, just off the top of my head, that's different from the last time I did an encode is that I added the TDeint.dll to my avisynth plugins folder, but like I said, I ran this new project through 2090 before I downloaded the latest version, and it came back as progressive that time.


Update: I've just updated to DGIndex 1.4.6 and x264 459 (I was using 408), created a new d2v file, and the results are still the same - MeGUI 2090 says progressive, whilst 2107 & 8 say hybrid. DGIndex itself still says progressive. I've noticed though that I can't use the "--aq-strength 0.8 --aq-sensitivity 15" command with the new x264.. which is a shame, cuz it solved quite a few issues I had with previous encodes.

[berrinam]

I remember now that I made a slight change to the script which should have made it more accurate.

Firstly, I don't know what your source is, so perhaps MeGUI's detection is in fact correct. In particular, the opening or end credits might be interlaced while the rest is progressive. If you know how to recognise deinterlacing, it would be good if you could check it.

Secondly, your results are very close to being declared wholly progressive (if there had been 61 or more progressive sections then that would have been the result). Setting the thresholds correctly so they trigger in the right place and don't in others is perhaps the hardest part, and I have not been able to do this properly, because I didn't have many sources. If you are sure that MeGUI is wrong, perhaps you (or I) could alter the settings so that it is less sensitive to small variations.

Something else which would be good to try is AutoGK. I made Source Detection constantly comparing my results to AutoGK's results. MeGUI's Source Detection should be up to 100 times faster, and I hope most of the results should be the same. I'm interested in what AutoGK says in its analysis.

I'm also interested by the fact that Partial Static Sections is so much higher than the rest, and I suspect this is because of your source being an animatedd source. As I said, I have had many problems with Source Detection due to lack of sample sources, anime sources being one of them. I suspected that they may be a problem due to their low actual framerate, I wasn't sure. I don't think there's much you can do about that, though.

[desta]

Well, I'm definitely no expert on the subject, so any worthwhile input I can offer is somewhat limited unfortunately. However, I did quickly start it up to do an encode in AutoGK, just to see what script would be generated, and I noticed this...

[07/03/2006 20:52:52] AutoGK 2.26
[07/03/2006 20:52:52] OS: WinXP (5.1.2600).2
[07/03/2006 20:52:52] Job started.
[07/03/2006 20:52:52] Input file: F:\Video\Projects\Star Wars\Clone Wars\Vol 2\VIDEO_TS\VTS_01_1.VOB
[07/03/2006 20:52:52] Output file: F:\Video\Projects\Star Wars\Clone Wars\Vol 2\VIDEO_TS\VTS_01_1.avi
[07/03/2006 20:52:52] Output codec: XviD
[07/03/2006 20:52:52] Audio 1: Audio Stream 1 AC3
[07/03/2006 20:52:52] Subtitles: none
[07/03/2006 20:52:52] Format: .AVI
[07/03/2006 20:52:52] Target size: 1400Mb
[07/03/2006 20:52:52] Custom resolution settings: fixed width of 704 pixels
[07/03/2006 20:52:52] Custom audio settings: Original
[07/03/2006 20:52:52] Started encoding.
[07/03/2006 20:52:52] Demuxing and indexing.
[07/03/2006 20:54:20] Processing file: F:\Video\Projects\Star Wars\Clone Wars\Vol 2\VIDEO_TS\VTS_01_1.VOB
[07/03/2006 20:54:20] Processing file: F:\Video\Projects\Star Wars\Clone Wars\Vol 2\VIDEO_TS\VTS_01_2.VOB
[07/03/2006 20:54:20] Processing file: F:\Video\Projects\Star Wars\Clone Wars\Vol 2\VIDEO_TS\VTS_01_3.VOB
[07/03/2006 20:54:20] Source resolution: 720x576
[07/03/2006 20:54:20] Found PAL source.
[07/03/2006 20:54:20] Source aspect ratio: 16:9
[07/03/2006 20:54:20] Color correction enabled.
[07/03/2006 20:54:20] Analyzing source.
[07/03/2006 20:58:00] Source is considered to be interlaced.
[07/03/2006 20:58:00] Output will contain 91544 frames
[07/03/2006 20:58:00] Audio1 size: 87,870,720 bytes (83.80 Mb)
[07/03/2006 20:58:00] Overhead: 610,304 bytes (0.58 Mb)
[07/03/2006 20:58:00] Video size: 1,379,525,376 bytes (1315.62 Mb)
[07/03/2006 20:58:00] Running compressibility test.
[07/03/2006 21:03:47] Duration was: 5 minutes 47 seconds
[07/03/2006 21:03:47] Speed was: 13.18 fps.
[07/03/2006 21:03:48] Compressibility percentage is: 88.29
[07/03/2006 21:03:48] Chosen resolution is: 704x400 ( AR: 1.76 )
[07/03/2006 21:03:48] Predicted comptest value is: 88.29%
[07/03/2006 21:03:48] Running first pass.


... From that I loaded up a basic script with KernelDeint included (as it seemed that's what AutoGK used), ran it back through Vdub Mod, and it showed a hell of a lot of interlacing. I changed the script to use Decomb's Telecide(), and it showed less interlacing, even though it still detected it... though that was using a threshold of 25.

The interlacing mainly seems to occur on scenes with a lot of bold black lines, and obvious movement - which for anime is quite a bit. In this particular movie, the black outlines are fairly jagged anyway... I'm not sure what the correct term would be, hehe. The main bulk of each frame is progressive (ie, backgrounds, etc), but once you've got characters on the screen, it starts seeing it as interlaced.

[berrinam]

Well, the detection of MeGUI was right, anyway, which is pleasing. However, I'm surprised that it showed interlacing WITH KernelDeint included. Also, I'm surprised that the source is only detected as 4 interlaced sections out of 62. What's the feasibility of somehow giving me a small sample to experiment with? PM me about it if you want.

[desta]

PM sent :)

[foxyshadis]

Is MeGUI really supposed to be taking over ctrl-c so that you can't copy text without the mouse anymore? In the main interface it brings up the chapter editor, in the rest it just doesn't do anything at all. Or is it just a recent "oops"?

[berrinam]

It's been noted and is on the feature request list:
Resolve clashes between hotkeys
Description: See http://forum.doom9.org/showthread.ph...292#post770292
Status:

[dimzon]

Is MeGUI really supposed to be taking over ctrl-c so that you can't copy text without the mouse anymore? In the main interface it brings up the chapter editor, in the rest it just doesn't do anything at all. Or is it just a recent "oops"?

Yeah, I really don't like how does it look && feeel too. I think we must perform massive mainform GUI rearranging/redesign. Doom9, do You agree?
I think we can create non-working new GUI prototype (just create new WindowsApplication && try to draw new GUI) to discuss about it.

[foxyshadis]

Oh! I didn't put that title together with my problem, thank you.

[Chainmax]

Is there any difference between ChronoCross's build and the one available in sourceforge?

[ChronoCross]

yes my is updated once a day if there are updates. the one on sourceforge is not the current revision. other than that they are identical.

[chipzoller]

Sorry for so much forum-hopping. I'll stick with this one from now on.

This is a repost of my original question:

This looks like it has become the unofficial support thread, so if this question I post is inappropriate, please do move it.

I have several AVIs I ripped from my DVDs (complete James Bond special editions) all of whose fps is 23.976. I know FFMpeg and any apps based on this have problems with this because it doesn't understand frame rates past the hundredths place, but I seem to be getting sync issues in my muxed MP4 file. When I created the AVS script the frame rate was listed at 23.975....and fiddy thousand more places afterwards and had sync issues (the video is slower than the audio) and so manually changed the script to 23.976 with no difference.

Here is the original script:

DirectShowSource("F:\Bond Movies\Diamonds are Forever.avi",fps=23.9759856527702,audio=false)
#blank deinterlace line
#crop
LanczosResize(320,176) # Lanczos (Sharp)
#denoise


I would gladly re-rip straight into a d2v project file except the DVDs aren't currently with me. Also, I encoded these long ago with DivX 4.x and verified the frame rate with Gspot and through a media player.

Does this sound familiar to anyone?


Second part:

My x264 encoding always fails with meGUI but not with other x264 apps.

Log:

Log for job job1-1

Channels=2, BitsPerSample=16, SampleRate=48000Hz
C:\Documents and Settings\Chip Zoller\Desktop\megui\faac.exe -b 112 -o "C:\Documents and Settings\Chip Zoller\Desktop\Mega Man X5 Intro.mp4" -P -X -R 48000 -B 16 -C 2 --mpeg-vers 4 -Freeware Advanced Audio Coder
FAAC 1.24.1 (May 17 2005) UNSTABLE

Average bitrate: 112 kbps
Quantization quality: 100
Bandwidth: 12490 Hz
Object type: Low Complexity(MPEG-4) + M/S
Container format: MPEG-4 File Format (MP4)
Encoding - to C:\Documents and Settings\Chip Zoller\Desktop\Mega Man X5 Intro.mp4
frame | elapsed | play/CPU
3338 | 12.2 | 5.83x



----------------------------------------------------------------------------------------------------------
job job1-1 has been processed. This job is linked to the next job: job1-2
No desired size. Continuing without making any changes.
Starting job job1-2 at 9:48:15 AM
Job is a video job. encoder commandline:
"C:\Documents and Settings\Chip Zoller\Desktop\x5.avs" -ovc x264 -x264encopts bitrate=700:nocabac:4x4mv:i4x4:qp_step=4:direct_pred=1 -o "C:\Documents and Settings\Chip Zoller\Desktop\x5.264" -of rawvideo
successfully started encoding
Processing ended at 9:48:16 AM
----------------------------------------------------------------------------------------------------------

Log for job job1-2

MEncoder dev-CVS-050928-16:38-3.4.2 (C) 2000-2005 MPlayer Team
CPU: Intel Pentium 4/Xeon/Celeron Foster (Family: 8, Stepping: 7)
Detected cache-line size is 64 bytes
CPUflags: Type: 8 MMX: 1 MMX2: 1 3DNow: 0 3DNow2: 0 SSE: 0 SSE2: 0
Compiled with runtime CPU detection - WARNING - this is not optimal!
To get best performance, recompile MPlayer with --disable-runtime-cpudetection.

Exiting... (error parsing cmdline)
Error: Unrecognized commandline parameter detected.

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

[Sharktooth]

your mencoder build is too old. also why using mencoder to encode with x264? get a recent x264 build instead.

[chipzoller]

your mencoder build is too old.

Is the build from 01/01/2006 that is 8,205,824 bytes the most current build?

[chipzoller]

Also, I downloaded and encoded a file with Sharktooth's iPod profile for meGUI and each file I encode (the only thing I change is the bitrate, down to 200 and 2-pass automatic) does not play on my iPod. Can anyone confirm that this profile works for them?

[ChronoCross]

it works. plays fine on my friends ipod.

[chipzoller]

Ok I figured out why. I generated an AVS script from a 4:3 AR AVI file. The resize had 352x240, but when I put in the AR as 4:3 then ticked "suggest resolution" the x-axis filled in at 320 and y-axis at 240, but the resulting AVS script saved it as 352x240, so while the file encoded that resolution isn't supported with that AR. Is this perhaps a bug in the script generation?

Sorry folks...it works.