MeGUI: General Questions and Troubleshooting Thread

[Kurtnoise]

already included for the next release...

[Riki]

Thanks, I just tested it and it works perfect. That saves me about 3 steps. :D

[rapscallion]

Hey guys, this may be just coincidental, but usually it takes about 3 hrs on my system to create a "stats" file and ~7 hrs for the second pass to create a rawac "264" file for the ~2hr movies that I process ~12.0 fps.

Today, after MEgui updated from 1031 to 1032, a similar movie took the 3 hrs for the *.stats file, but then less than 2 hrs to create the *.264 file processing about 22.0 fps, ~8.1gb!

Any idea why the big change/reduction in processing time ? 5hr difference is quite substantial, to say the least.

Here are logfiles, first under ver 1031 , then under 1032 that maybe someone can shed some light on :

1031:
[Information] Log
-[Information] Versions
--[NoImage] MeGUI Version : 0.3.1.1031
--[NoImage] OS : Windows XP Professional x86 SP3 (5.1.196608.2600)
--[NoImage] Framework used : 2.0 SP1 (2.0.50727.1433)
-[Information] Hardware
--[NoImage] CPU : Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz
-[Information] Log for job6 (video, ultimatum.avs -> ultimatum.264)
--[Information] [4/20/2009 4:13:53 PM] Started handling job
--[Information] [4/20/2009 4:13:53 PM] Preprocessing
--[NoImage] Job commandline: "C:\dvd_rw\megui\tools\x264\x264.exe" --pass 2 --bitrate 7574 --stats "C:\br avs\ultimatum.stats" --level 4.1 --keyint 24 --min-keyint 2 --ref 3 --mixed-refs --bframes 3 --b-adapt 2 --weightb --direct auto --subme 7 --trellis 1 --partitions p8x8,b8x8,i4x4,i8x8 --8x8dct --ipratio 1.1 --pbratio 1.1 --vbv-bufsize 16500 --vbv-maxrate 16500 --qcomp 0.5 --me umh --threads auto --thread-input --sar 1:1 --aud --progress --no-psnr --no-ssim --output "D:\ultimatum\ultimatum.264" "C:\br avs\ultimatum.avs" --mvrange 511 --nal-hrd --sar 1:1
--[Information] [4/20/2009 4:13:54 PM] Encoding started
--[NoImage] Standard output stream
--[NoImage] Standard error stream
---[NoImage] avis [info]: 1280x720 @ 23.98 fps (165735 frames)
---[NoImage] x264 [info]: using SAR=1/1
---[NoImage] x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 Cache64
---[NoImage] x264 [info]: profile High, level 4.1
---[NoImage]
---[NoImage] x264 [info]: slice I:12113 Avg QP:14.17 size: 64674
---[NoImage] x264 [info]: slice P:71832 Avg QP:15.68 size: 43895
---[NoImage] x264 [info]: slice B:81790 Avg QP:16.30 size: 31886
---[NoImage] x264 [info]: consecutive B-frames: 12.8% 38.6% 30.5% 18.1%
---[NoImage] x264 [info]: mb I I16..4: 27.3% 59.7% 13.0%
---[NoImage] x264 [info]: mb P I16..4: 4.4% 22.1% 3.9% P16..4: 20.0% 12.9% 7.1% 0.0% 0.0% skip:29.6%
---[NoImage] x264 [info]: mb B I16..4: 1.5% 8.2% 1.0% B16..8: 31.6% 3.7% 5.0% direct:10.9% skip:38.1% L0:39.1% L1:45.0% BI:15.9%
---[NoImage] x264 [info]: 8x8 transform intra:69.8% inter:52.8%
---[NoImage] x264 [info]: direct mvs spatial:85.8% temporal:14.2%
---[NoImage] x264 [info]: ref P L0 79.5% 12.9% 7.6%
---[NoImage] x264 [info]: ref B L0 87.7% 12.3%
---[NoImage] x264 [info]: kb/s:7574.0
---[NoImage] encoded 165735 frames, 6.50 fps, 7578.98 kb/s
--[Information] Final statistics
---[NoImage] Video Bitrate Desired: 7574 kbit/s
---[NoImage] Video Bitrate Obtained (approximate): 7578 kbit/s
--[Information] [4/20/2009 11:19:14 PM] Postprocessing
---[Information] Deleting intermediate files
----[Information] [4/20/2009 11:19:14 PM] Successfully deleted C:\br avs\ultimatum.stats
--[Information] [4/20/2009 11:19:14 PM] Job completed

1032:
-[Information] Log for job2 (video, supremacy.avs -> supremacy.264)
--[Information] [4/21/2009 1:07:14 PM] Started handling job
--[Information] [4/21/2009 1:07:14 PM] Preprocessing
--[NoImage] Job commandline: "C:\dvd_rw\megui\tools\x264\x264.exe" --pass 2 --bitrate 8128 --stats "C:\br avs\supremacy.stats" --level 4.1 --keyint 24 --min-keyint 2 --bframes 3 --b-adapt 2 --weightb --direct auto --subme 2 --partitions none --ipratio 1.1 --pbratio 1.1 --vbv-bufsize 16500 --vbv-maxrate 16500 --qcomp 0.5 --threads auto --thread-input --sar 1:1 --aud --progress --no-psnr --no-ssim --output "D:\supremacy\supremacy.264" "C:\br avs\supremacy.avs" --mvrange 511 --nal-hrd --sar 1:1
--[Information] [4/21/2009 1:07:14 PM] Encoding started
--[NoImage] Standard output stream
--[NoImage] Standard error stream
---[NoImage] avis [info]: 1280x720 @ 23.98 fps (155982 frames)
---[NoImage] x264 [info]: using SAR=1/1
---[NoImage] x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 Cache64
---[NoImage] x264 [info]: profile Main, level 4.1
---[NoImage]
---[NoImage] x264 [info]: slice I:11248 Avg QP:13.24 size: 67770
---[NoImage] x264 [info]: slice P:65518 Avg QP:14.52 size: 46356
---[NoImage] x264 [info]: slice B:79216 Avg QP:15.30 size: 35478
---[NoImage] x264 [info]: consecutive B-frames: 12.3% 34.8% 27.8% 25.0%
---[NoImage] x264 [info]: mb I I16..4: 54.2% 0.0% 45.8%
---[NoImage] x264 [info]: mb P I16..4: 36.6% 0.0% 0.0% P16..4: 33.9% 0.0% 0.0% 0.0% 0.0% skip:29.4%
---[NoImage] x264 [info]: mb B I16..4: 15.5% 0.0% 0.0% B16..8: 30.9% 0.0% 0.0% direct:18.0% skip:35.6% L0:29.5% L1:35.5% BI:35.0%
---[NoImage] x264 [info]: direct mvs spatial:89.1% temporal:10.9%
---[NoImage] x264 [info]: kb/s:8128.0
---[NoImage] encoded 155982 frames, 22.45 fps, 8132.95 kb/s
--[Information] Final statistics
---[NoImage] Video Bitrate Desired: 8128 kbit/s
---[NoImage] Video Bitrate Obtained (approximate): 8132 kbit/s
--[Information] [4/21/2009 3:03:12 PM] Postprocessing
---[Information] Deleting intermediate files
----[Information] [4/21/2009 3:03:12 PM] Successfully deleted C:\br avs\supremacy.stats
--[Information] [4/21/2009 3:03:12 PM] Job completed

[nurbs]

The second encode uses faster settings. --subme 2, --partitions none and no trellis. Either you used the wrong settings or there is a bug that causes fast first pass settings to be used on the second pass.

[rapscallion]

Thanks (I really didn't know what to look for). I haven't changed any settings so will try again and see if it wasn't just a fluke. (or maybe it is a bug in the update to ver 1032)

Edit :Tried again and it appears that something has changed in the way x264 handles the encode now, or Megui changed something with the update.

I have always selected x264-standalone avchd ,as the preset, and job1 (pass1) has created the *stats file with these parameters, and as you can see they are now duplicated for pass2 :

program --pass 2 --bitrate 8128 --stats ".stats" --level 4.1 --keyint 24 --min-keyint 2 --bframes 3 --b-adapt 2 --weightb --direct auto --subme 2 --partitions none --ipratio 1.1 --pbratio 1.1 --vbv-bufsize 16500 --vbv-maxrate 16500 --qcomp 0.5 --threads auto --thread-input --progress --no-psnr --no-ssim --output "output" "input" --mvrange 511 --nal-hrd --sar 1:1

Now, if I select "standalone blu-ray" the parameters for pass2 are what the former avchd were :

program --pass 2 --bitrate 8128 --stats ".stats" --level 4.1 --keyint 24 --min-keyint 2 --ref 3 --mixed-refs --bframes 3 --b-adapt 2 --weightb --direct auto --deblock -1:-1 --subme 7 --trellis 2 --partitions p8x8,b8x8,i4x4,i8x8 --8x8dct --ipratio 1.1 --pbratio 1.1 --vbv-bufsize 40000 --vbv-maxrate 40000 --qcomp 0.5 --me umh --threads auto --thread-input --progress --no-psnr --no-ssim --output "output" "input" --mvrange 511 --nal-hrd --sar 1:1

So, the question is which preset to use now, for creating a DVD9 AVCHD disc ?

Edit: Problem solved. Apparently the update (or something else) udated the preset/profile 2nd pass to the first pass parameters. All I had to do was re import the profiles and now avchd parameretrs are correct for both passes. Thanks again nurbs for pointing me in the right direction (this is all new to me)

[Sion]

This seems like probably a pretty easy question, but I couldn't find an answer, so I'm asking here...

When transcoding a file from x264 to Xvid, I usually use CBR and set the bitrate around 4000. I usually encode the video first with no audio, then mux in the audio afterwards from the original file. So, for the video-only portion of the process, I'd expect the final video bitrate to be what I set it for in meGUI. But it's usually significantly less. Why is this? For example, I transcoded a clip recently, using CBR, set the bitrate to an even 4000, used autoencode, told it to "use profile settings" (i.e. no target size). After the encoding is done, a mediainfo report shows the final bitrate for the video to be 3854, even though I set it to 4000. I'm not terribly concerned, it's not a big deal, just curious.

Thanks...

[Dark Shikari]

This seems like probably a pretty easy question, but I couldn't find an answer, so I'm asking here...

When transcoding a file from x264 to Xvid, I usually use CBR and set the bitrate around 4000. I usually encode the video first with no audio, then mux in the audio afterwards from the original file. So, for the video-only portion of the process, I'd expect the final video bitrate to be what I set it for in meGUI. But it's usually significantly less. Why is this? For example, I transcoded a clip recently, using CBR, set the bitrate to an even 4000, used autoencode, told it to "use profile settings" (i.e. no target size). After the encoding is done, a mediainfo report shows the final bitrate for the video to be 3854, even though I set it to 4000. I'm not terribly concerned, it's not a big deal, just curious.

Thanks...If you're actually using CBR, that means the encoder has to use the same bitrate everywhere--and if it's impossible to use the full 4 megabits in a given situation, it clearly can't compensate for that later by adding a few more bits, since the bitrate is constant.

[naugas]

When using 0.3.1.1032 and x264 1139, setting "Chroma QP Offset" always shows up two steps smaller when I check it with mediainfo. That is, I leave it at 0, it says -2, putting it at 2, it becomes 0 etc. Seems a little strange?

[Sion]

If you're actually using CBR, that means the encoder has to use the same bitrate everywhere--and if it's impossible to use the full 4 megabits in a given situation, it clearly can't compensate for that later by adding a few more bits, since the bitrate is constant.
Hmm... interesting. I'd not thought of it that way. Makes sense, thanks.

Now though, I'm curious, how/why would it be impossible to use the full amount of a certain bitrate for a given situation? I mean, even for a frame that is full-screen pure blue (for example) it could be defined with very few bits, but you *could* use as many bits as you want (though wasteful) right? Obviously based on your earlier comment this isn't right, but I'm curious how&why this isn't true.

Thanks!

[Dark Shikari]

When using 0.3.1.1032 and x264 1139, setting "Chroma QP Offset" always shows up two steps smaller when I check it with mediainfo. That is, I leave it at 0, it says -2, putting it at 2, it becomes 0 etc. Seems a little strange?x264 lowers it by 2 from the input value when using psy-RD.Hmm... interesting. I'd not thought of it that way. Makes sense, thanks.

Now though, I'm curious, how/why would it be impossible to use the full amount of a certain bitrate for a given situation? I mean, even for a frame that is full-screen pure blue (for example) it could be defined with very few bits, but you *could* use as many bits as you want (though wasteful) right? Obviously based on your earlier comment this isn't right, but I'm curious how&why this isn't true.On the frame level, Xvid doesn't work with a bit budget; it works with a given frame quantizer. The ratecontrol decides the quantizer in order to try to match the bit budget.

But what if you get to the minimum quantizer and still don't use up the entire bit budget? Since there's no point in going further, most encoders don't include code to handle this case. But there's a few things that could be done.

1. Xvid's default min QP is 2. You could lower this to 1 to allow it even more ability to waste bits (for no real visual gain).

2. The "lambda," that is, the "value" of bits, can be decreased internally, thus causing the encoder to choose decisions that increase quality but would normally cost too many bits to make such an increase worthwhile.

3. The encoder can pad the end of the frame with zeroes (used in cases where "hard CBR" is necessary).

[MacLover]

Hey, I know this will sound stupid but does meGUI run on Windows 7 Ultimate (32Bit) Beta? or should I just install XP (32Bit) instead?

[Sion]

Hey, I know this will sound stupid but does meGUI run on Windows 7 Ultimate (32Bit) Beta? or should I just install XP (32Bit) instead?
That's okay, your handle gives you a free pass for stupid questions. ;)

Stupid answer:
Why don't you just install it and try it out? Report your findings. I'm sure many people would be interested. :)

[Sharktooth]

it does...

[Forteen88]

Is it okey to put official x264 in megui\tools\x264-directory instead of using Skystrife's version? I wonder because Skystrife's version isn't updated that fast.

EDIT: OK, great, thanks. I thought those at:
http://x264.nl/
were the official ones.

[Kurtnoise]

sure...no problem but there isn't an official x264 build yet.

edit: keep in mind that some presets use some additional functions not available on every builds.

[-=:rkd:=-]

Hey guys..

I have been getting this error for the last 4 days while ripping a movie which is PAL interlaced...

After the rip is 99.5% complete it gives me an error ...Log file is like this..

-[Information] Log for job1 (video, Trial.avs -> )
--[Information] [4/26/2009 2:20:36 AM] Started handling job
--[Information] [4/26/2009 2:20:36 AM] Preprocessing
--[NoImage] Job commandline: "C:\Program Files\megui\tools\x264\x264.exe" --pass 1 --bitrate 1110
--stats "E:\B & B\Trial.stats" --bframes 3 --b-adapt 2 --b-pyramid --weightb --direct auto --deblock
-1:-1 --subme 2 --partitions none --me dia --threads auto --thread-input --sar 1:1 --cqmfile
"D:\Encoding\AvcMatrices\M4G-HighDetail-V3.1.cfg" --progress --no-psnr --no-ssim --output NUL "E:\B & B\Trial.avs"
--[Information] [4/26/2009 2:20:37 AM] Encoding started
--[NoImage] Standard output stream
--[NoImage] Standard error stream
---[NoImage] avis [info]: 720x320 @ 25.00 fps (4365 frames)
---[NoImage] x264 [info]: using SAR=1/1
---[NoImage] x264 [info]: using cpu capabilities: MMX2 SSE2 SSE3 Cache64
---[NoImage] x264 [info]: profile High, level 3.0
--[Information] [4/26/2009 2:27:10 AM] Job completed

And it says like X264 encountered a problem and needs to close...Tht irritating error reporting window comes..here is the Screenshot of the error..

http://i732.photobucket.com/albums/ww323/rajeev_cusat/1.jpg

Please help me....

[Kurtnoise]

hard to say...cleanup your avs plugins folder (there are maybe some conflicts) or try an other x264 build.

I thought those at:
http://x264.nl/
were the official ones.
no, there are not...

[-=:rkd:=-]

Hey guys..

I have been getting this error for the last 4 days while ripping a movie which is PAL interlaced...

After the rip is 99.5% complete it gives me an error ...Log file is like this..

-[Information] Log for job1 (video, Trial.avs -> )
--[Information] [4/26/2009 2:20:36 AM] Started handling job
--[Information] [4/26/2009 2:20:36 AM] Preprocessing
--[NoImage] Job commandline: "C:\Program Files\megui\tools\x264\x264.exe" --pass 1 --bitrate 1110
--stats "E:\B & B\Trial.stats" --bframes 3 --b-adapt 2 --b-pyramid --weightb --direct auto --deblock
-1:-1 --subme 2 --partitions none --me dia --threads auto --thread-input --sar 1:1 --cqmfile
"D:\Encoding\AvcMatrices\M4G-HighDetail-V3.1.cfg" --progress --no-psnr --no-ssim --output NUL "E:\B & B\Trial.avs"
--[Information] [4/26/2009 2:20:37 AM] Encoding started
--[NoImage] Standard output stream
--[NoImage] Standard error stream
---[NoImage] avis [info]: 720x320 @ 25.00 fps (4365 frames)
---[NoImage] x264 [info]: using SAR=1/1
---[NoImage] x264 [info]: using cpu capabilities: MMX2 SSE2 SSE3 Cache64
---[NoImage] x264 [info]: profile High, level 3.0
--[Information] [4/26/2009 2:27:10 AM] Job completed

And it says like X264 encountered a problem and needs to close...Tht irritating error reporting window comes..here is the Screenshot of the error..

http://i732.photobucket.com/albums/ww323/rajeev_cusat/1.jpg

Please help me....

Is there anyone who can help me trouble shoot this problem...???This error is driving me crazy

[Sharktooth]

have you tried cleaning up your avs plugins as kurtnoise suggested you?
also, this is not related to megui since your crash happens on x264.

[Rodger]

2 things possible from my point of view.

computer is overclocked
original stream is corrupt

[-=:rkd:=-]

Thnks to all of u guys for the prompt reply

@ kurtnoise

i cud not figure out tht u r addressing me...(I m really sorry for this) Will try it right now..

@ Sharktooth.

It happens wih Xvid and X264 both..I tried it with both the codecs...

@ Rodger

processor is not overclocked..I am sure...
Original stream seems to be corrupt??? i didnt get u..

First I will follow the kurtnoise method and will report it back in a moment..

Edit

After I opened my plugins folder I was confused which plugins may contradict why shud I remove this not tht..So as u guys are the one who write plugins for us so u people can understand the conflicts between them...I am posting a Snapshot of my plugin folder plz tell me the conflicting plugin...


http://i732.photobucket.com/albums/ww323/rajeev_cusat/1-2.jpg

Will this prob be removed if I dont keep all the plugins in my plugin folder and load it when required....

Thnks again guys

[Sharktooth]

remove everything (just move them in another folder) except DirectShowSource.dll.
then reinstall megui plugins thru the megui Update function (right click on the plugins and select force reinstall).
after it's done, try re-encoding and if it works then one or more of your plugins are either conflicting or corrupted.

[Poutnik]

I have read somewhere in the forum DXVA compatible H264
should not use more than 4 ref frames.

Your DXVA SD HQ MeGUI profile uses 8 ref frames.

Is the info above incorect ? Or is it conditional ?
I have not DXVA supporting card yet to check....

[saint-francis]

I have read somewhere in the forum DXVA compatible H264
should not use more than 4 ref frames.

Your DXVA SD HQ MeGUI profile uses 8 ref frames.

Is the info above incorect ? Or is it conditional ?
I have not DXVA supporting card yet to check....

Ref frame limit is dependent on your video card and the resolution of the material you are trying to play. For SD 8 refs will be fine.

[SeeChestlickRun]

Hey,

I cant seem to downmix AC3 4 channel to Vorbis 2 Channel.

They will always come out as 4 Channel... Why?

I have the Vorbis set at 'Downmix multichannel to Stereo' and Q=0.5 to make it about 128 bitrate (Not really because it's stuck in 4 channel)

Is it a bug?

Chestlick

[tebasuna51]

I cant seem to downmix AC3 4 channel to Vorbis 2 Channel.

They will always come out as 4 Channel... Why?

I think only the standard multichannel 5.1 is downmix to 2.0

To downmix other multichannel config you need write an avs file.

First you need know what kind of 4 channel is:
- 2/2.0 (FL,FR,SL,SR)
- 3/1.0 (FL,FR,FC,S)
- 3/0.1 (FL,FR,FC,LFE)
- 2/1.1 (FL,FR,LFE,S)

After you can select between the downmix method:
- Plain stereo
- Dolby ProLogic
- Dolby ProLogic II (only if 2/2.0)
and if you use the LFE channel (if present) to mix (Dolby recommend don't use the LFE channel for 2.0 downmix)

[SeeChestlickRun]

Oops, sorry, I don't know why I typed 4 channel, I think I was too tired last night.

This is what MediaInfo gave:

Audio
Format : AC-3
Format/Info : Audio Coding 3
Codec ID : A_AC3
Duration : 42mn 17s
Bit rate mode : Constant
Bit rate : 384 Kbps
Channel(s) : 6 channels
Channel positions : Front: L C R, Surround: L R, LFE
Sampling rate : 48.0 KHz

It's 6 channels, after all its from a DVD. (5.1 channel after all)

After encoding it, with this setting...

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

I get this.

Audio
Format : Vorbis
Format settings, Floor : 1
Duration : 42mn 17s
Bit rate : 344 Kbps
Channel(s) : 4 channels
Sampling rate : 48.0 KHz

Although, I'll look up at some avs script. Thanks.

[tebasuna51]

Oops, sorry, I don't know why I typed 4 channel, I think I was too tired last night.

It's 6 channels, after all its from a DVD. (5.1 channel after all)

Sorry, I can't reproduce your problem, works fine here with your settings.

[alexcel]

Hi:

I can't process mkv as input files, when I run dga creator, I get an error

"Can't fin libavcodec.dll in the dgavcindex folder".

The libavcodec is installed by megui in the avisynth 2.5.8 plugins folder, not in the dgavcindex folder so it can not be found.

I have downloaded another version of dgavcindex from neuron and installed it on a different folder, with all files in the same folder. Then I have changed the path to the new folder in megui settings

Then, If I launch dga creator the first error would not appear, but the indexing does not occur and no file is created, while it keeps saying "processing ..." for very long times until I abort operation.

My feeling is that this is a issue related to Vista 64 bits and how tools are installed

Any help is most appreciated.

Thanks!!

[nurbs]

According to the manual on neuron2.net dgavcindex can only index avc elementary streams (.264) and transport streams (.m2ts), not in an mkv container.

[alexcel]

According to the manual on neuron2.net dgavcindex can only index avc elementary streams (.264) and transport streams (.m2ts), not in an mkv container.

But I have read in this forum that processing mkv files as input files in megui is perfectly possible

Am I wrong?

[nurbs]

Never tried it, but they should be opened with directshowsource() if you add them in the main encoding tab. Maybe that works in the avs-creator as well. If you need the indexing you will have to demux the mkv first.

[daWsOn_s]

Can I add custom aspect ratios and filesize (in bitrate calculator) in some xml file without writing them everytime?

[Kurtnoise]

But I have read in this forum that processing mkv files as input files in megui is perfectly possible

Am I wrong?
only with the DGxxxNV tools...

Can I add custom aspect ratios and filesize (in bitrate calculator) in some xml file without writing them everytime?
nope...

[SacredCultivator]

Just curious, and sorry if not supposed to post here... For 64bit systems (testing it out), XP 64bit, as I'm still not too fond of Vista.

But anyway, for the 64bit, in regard to meGUI / filters/ etc. how would I go about it to switch to 64bit for that benefit. As I'm aware that there are still a few things that aren't 64bit compatible, and will still be under 32bit. And another thing would be since now there are 64bi x264 builds, I would assume I'd just grab those and replace the one in the meGUI installation (tools) folder, or does meGUI auto detect that?

Never really used 64bit so completely new to the idea.

---
EDIT:
I guess another quesiton is... in regard to encoding speed (if same settings are used comparing 32bit to 64bit, is the benefit that big?)

[nurbs]

I don't know if it is possible with megui, but your whole encoding chain (splitter, decoder, (avisynth), encoder) would have to be 64bit to be usable. Some people on the forum have managed to use avs2yuv to send frames from 32bit avisynth to 64bit x264, but that is not implemented in megui. IIRC the 64bit version of x264 is about 10% faster.

[SacredCultivator]

So it is fine to just have everything I currently under 32bit just changing the 64bit of x264 right?

[nurbs]

As I said, I don't know if that's possible in megui. AFAIK 64bit avisynth lacks a lot of plugins and the indexing programs are only 32bit, so it might be more trouble than it's worth.

[daWsOn_s]

Is there any change to cut video and audio files without re-encode the audio? For example if I want to cut commercials with AVS cutter and preserve the AC3 stream.
Do I have to pass through some other software before megui?

[nurbs]

For AC3 audio you can use "delaycut" (google it). Of course it doesn't integrate with the AVS cutter, so you'll have to enter the times at which you want to cut manually.

[Seraphic-]

Is anyone running MeGUI under Vista? I keep getting the same damn errors even though the path locations are correct.
Had this problem before and running MeGUI as Administrator fixed the issue, but now it isn't helping at all. :angry:
Do I somehow have the wrong path location or is something else the problem?

AVIFileSource: couldn't open file 'D:\Track1.wav'
(D:\WAV to 5.1.avs, line 1)


fl = WavSource("D:\Track1.wav")
fr = WavSource("D:\Track2.wav")
fc = WavSource("D:\Track5.wav")
lf = WavSource("D:\Track6.wav")
sl = WavSource("D:\Track3.wav")
sr = WavSource("D:\Track4.wav")
MergeChannels(fl, fr, fc, lf, sl, sr)

[Kurtnoise]

which avisynth version are you using ?

[Seraphic-]

which avisynth version are you using ?

AviSynth 2.5.8

[Kurtnoise]

works fine here on Vista...maybe try by changing your path. your Disk D is not protected ?

[Seraphic-]

works fine here on Vista...maybe try by changing your path. your Disk D is not protected ?

Don't think so. Also tried it from C drive and had same problem.
Think is has to do with the program in Vista.
Does your Vista ask you to v.i warning to allow or deny whenever you try and run MeGUI?
Even when I run as administrator it does that.

[Richardw322]

I have a general question. I have a set of MPEG2 files that I captured from TV. I want to convert them to XVID to save space, and view on my low power laptop. I am curious as to roughly how fay I can shrink the file size. They are about 2.5 gig now, and from what I have read I think I could take them down to around 500 meg or a little smaller and retain pretty good quality. I realize video quality is a subjective thing, and I don't want a hard fast rule. I just want to know if that would be a good starting point for testing. Oh, according to MPC HC they now have a bitrate of 9000kbps.
Thanks

[pihug12]

Trying server: http://megui.org/auto/stable/
Retrieving update file from server...
Error: Couldn't connect to server.
Trying server: http://megui.xvidvideo.ru/auto/stable/
Retrieving update file from server...
Error: Couldn't connect to server.
Error: Could not download XML file

I have this problem for three days (MeGUI 0.3.1.1032).
I try to uninstall/reinstall 0.3.1.1033 : same problem !

[Poopoo]

I have this problem for three days (MeGUI 0.3.1.1032).
I try to uninstall/reinstall 0.3.1.1033 : same problem !

Works fine here.

[b66pak]

how could i revert to an early mkvtoolnix version? the current one (2.7.0) has an very annoying bug...when split .mkvs in multiple parts the 2nd, 3rd etc sections can't be seek-ed (lock the player)...

thanks in advance...
_

[wolfbane5]

I've been using RipBot264 for all my mkv encodes for a while now. I thought I'd try out MeGUI since it has more options and whatnot. I was reading that the AVISynth Script creator can accept .m2ts and .ts inputs if you have FFDShow, Haali and DirectShowSource installed, otherwise you can create a D2V and use that. I have all of the above installed yet AVISynth Script creator basically says it can't open it and you need to index it first with DGIndex. Anyone know how to fix this?

I was also wondering if MeGUI can accept .dts audio inputs and simply copy the audio stream into the final mkv?

I am using the latest version of MeGUI and have updated all the components required for it to run.