View Full Version : Need help with MeGUI x264 settings.
jellysandwich
16th August 2005, 21:21
I think my settings are wrong, so here's
a picture:
http://jellysandwich.info/js/megui.JPG
When I mux the raw 264 file into an mp4
file via YAMB/Mp4Box, Media Player Classic
gives the "could not render some of the pins
in the graph" error. If I try to use convert
that mp4 file into an mkv file via Mkvmerge
GUI, I get some trashy video file, which you
can download here:
http://jellysandwich.info/js/Collaterall.mkv
What am I doing wrong?
js
Doom9
16th August 2005, 21:57
well.. if it were your settings (at first glance I don't spot anything but it's getting late), then if you used default settings instead it would work and you can work your way backwards until you can put your finger on an option to cause the problem.
And why not use megui for mp4 muxing?
jellysandwich
17th August 2005, 00:29
Ok, default settings worked, so I'll try
changing various settings one at a time
and see what happens.
I didn't want to risk using MP4/MKV output
because of the bug mentioned in Sharktooth's
thread. But
Also, I seem to be unable to open them (the
ones that work) in Vdub. These are the errors:
[!] MKV: A frame of stream 1 (at 834 ms) had only a forward reference (maybe
broken file).
[!] MKV: A frame of stream 1 (at 3336 ms) had only a forward reference (maybe
broken file).
[!] MKV: A frame of stream 1 (at 5839 ms) had only a forward reference (maybe
broken file).
[!] MKV: A frame of stream 1 (at 8341 ms) had only a forward reference (maybe
broken file).
[!] MKV: A frame of stream 1 (at 10844 ms) had only a forward reference (maybe
broken file).
[!] MKV: A frame of stream 1 (at 13346 ms) had only a forward reference (maybe
broken file).
[!] MKV: A frame of stream 1 (at 15849 ms) had only a forward reference (maybe
broken file).
[!] MKV: A frame of stream 1 (at 18351 ms) had only a forward reference (maybe
broken file).
[!] MKV: A frame of stream 1 (at 20854 ms) had only a forward reference (maybe
broken file).
[!] MKV: A frame of stream 1 (at 23356 ms) had only a forward reference (maybe
broken file).
[!] MKV: A frame of stream 1 (at 25859 ms) had only a forward reference (maybe
broken file).
[!] MKV: A frame of stream 1 (at 28361 ms) had only a forward reference (maybe
broken file).
[!] MKV: A frame of stream 1 (at 30864 ms) had only a forward reference (maybe
broken file).
[!] MKV: A frame of stream 1 (at 33366 ms) had only a forward reference (maybe
broken file).
[!] MKV: A frame of stream 1 (at 35869 ms) had only a forward reference (maybe
broken file).
[!] MKV: A frame of stream 1 (at 38371 ms) had only a forward reference (maybe
broken file).
[!] MKV: A frame of stream 1 (at 40874 ms) had only a forward reference (maybe
broken file).
[!] MKV: A frame of stream 1 (at 43376 ms) had only a forward reference (maybe
broken file).
[!] MKV: A frame of stream 1 (at 45879 ms) had only a forward reference (maybe
broken file).
[!] MKV: A frame of stream 1 (at 48381 ms) had only a forward reference (maybe
broken file).
[!] MKV: A frame of stream 1 (at 50884 ms) had only a forward reference (maybe
broken file).
[!] MKV: A frame of stream 1 (at 53386 ms) had only a forward reference (maybe
broken file).
[!] MKV: A frame of stream 1 (at 55889 ms) had only a forward reference (maybe
broken file).
[!] MKV: A frame of stream 1 (at 58391 ms) had only a forward reference (maybe
broken file).
[!] MKV: A frame of stream 1 (at 60894 ms) had only a forward reference (maybe
broken file).
[!] MKV: A frame of stream 1 (at 63396 ms) had only a forward reference (maybe
broken file).
[!] MKV: A frame of stream 1 (at 67567 ms) had only a forward reference (maybe
broken file).
[!] MKV: A frame of stream 1 (at 75075 ms) had only a forward reference (maybe
broken file).
[!] MKV: A frame of stream 1 (at 77577 ms) had only a forward reference (maybe
broken file).
[!] MKV: A frame of stream 1 (at 80080 ms) had only a forward reference (maybe
broken file).
[!] MKV: A frame of stream 1 (at 82582 ms) had only a forward reference (maybe
broken file).
[!] MKV: A frame of stream 1 (at 85085 ms) had only a forward reference (maybe
broken file).
[!] MKV: A frame of stream 1 (at 87587 ms) had only a forward reference (maybe
broken file).
[!] MKV: A frame of stream 1 (at 90090 ms) had only a forward reference (maybe
broken file).
[!] MKV: A frame of stream 1 (at 92592 ms) had only a forward reference (maybe
broken file).
[!] MKV: A frame of stream 1 (at 95095 ms) had only a forward reference (maybe
broken file).
[!] MKV: A frame of stream 1 (at 97597 ms) had only a forward reference (maybe
broken file).
[!] MKV: A frame of stream 1 (at 100100 ms) had only a forward reference
(maybe broken file).
[!] MKV: A frame of stream 1 (at 102602 ms) had only a forward reference
(maybe broken file).
[!] MKV: A frame of stream 1 (at 105105 ms) had only a forward reference
(maybe broken file).
[!] MKV: A frame of stream 1 (at 107607 ms) had only a forward reference
(maybe broken file).
[!] MKV: A frame of stream 1 (at 110110 ms) had only a forward reference
(maybe broken file).
[!] MKV: A frame of stream 1 (at 112612 ms) had only a forward reference
(maybe broken file).
[!] MKV: A frame of stream 1 (at 115115 ms) had only a forward reference
(maybe broken file).
[!] MKV: A frame of stream 1 (at 124290 ms) had only a forward reference
(maybe broken file).
[!] MKV: A frame of stream 1 (at 127627 ms) had only a forward reference
(maybe broken file).
[!] MKV: A frame of stream 1 (at 129295 ms) had only a forward reference
(maybe broken file).
[!] MKV: A frame of stream 1 (at 130964 ms) had only a forward reference
(maybe broken file).
[!] Couldn't locate decompressor for format 'ÿÿÿÿ' (unknown).
VirtualDub requires a Video for Windows (VFW) compatible codec to
decompress video. DirectShow codecs, such as those used by Windows Media
Player, are not suitable. Only 'Direct stream copy' is available for this
video.
I find the last one particularly odd. Then,
I noticed that the fourCC's available were
x264, avc1, and VSSH. Do I need to do
something special to have Vdub recognize
those?
I didn't realize CLI would be this hard. :(
js
jellysandwich
17th August 2005, 02:06
Ok, everything is starting to work now
that I'm using newer versions of Yamb
and Mp4box. I can successfully create
working mp4 and mkv files.
I still have problems opening them up in
Vdub though - I get this error:
[!] Couldn't locate decompressor for format 'ÿÿÿÿ' (unknown).
VirtualDub requires a Video for Windows (VFW) compatible codec to
decompress video. DirectShow codecs, such as those used by Windows Media
Player, are not suitable. Only 'Direct stream copy' is available for this
video.
It's not a big deal, but if anyone knows
anything about it, feel free to enlighten
me.
Off to encode...
js
Doom9
17th August 2005, 08:13
I noticed that the fourCC's available were x264, avc1, and VSSH. Do I need to do something special to have Vdub recognize those?
after installing ffdshow, go into vdub, access the ffdshow configuration, go to the decoder tab and make sure avc/x264 decoding is enabled (it's disabled by default).
However, because we're dealing with native MPEG-4 storage here when you either create a direct mkv file or mux an mp4 into mkv, VDubMod will not be able to properly handle this (an experienced Matroska user correct me please if I'm wrong), because at the time when VDubMod was created, native storage wasn't known. If you absolutely need VDubMod editability, mux your AVI into MKV directly.. that'll make use of the VfW compatibility mode and VDubMod should be able to handle that, but the native mode is to be prefered, especially for AVC (and now also for ASP, but as I said, it breaks compatibility with a lot of older apps).
Last but not least, does somebody force you to wrap lines after 10 cm? Why not let the board software take care of that instead so that users with every resolution will have their full screen width put to use?
Doom9
17th August 2005, 08:39
by the way, does anybody feel like creating a 16x16 and 32x32 icon? a "minimize to system tray" functionality would kinda need a 16x16 icon (which is then also used in the upper left corner of the app), and the 32x32 version would be used for shortcuts on your desktop.
jellysandwich
17th August 2005, 12:56
after installing ffdshow, go into vdub, access the ffdshow configuration, go to the decoder tab and make sure avc/x264 decoding is enabled (it's disabled by default).
However, because we're dealing with native MPEG-4 storage here when you either create a direct mkv file or mux an mp4 into mkv, VDubMod will not be able to properly handle this (an experienced Matroska user correct me please if I'm wrong), because at the time when VDubMod was created, native storage wasn't known. If you absolutely need VDubMod editability, mux your AVI into MKV directly.. that'll make use of the VfW compatibility mode and VDubMod should be able to handle that, but the native mode is to be prefered, especially for AVC (and now also for ASP, but as I said, it breaks compatibility with a lot of older apps).
When you say "mux your AVI into MKV
directly," are you talking about the vfw
version? Because I have no problems
with that... But I understand everything
else in that paragraph. Thanks for explaining.
Last but not least, does somebody force you to wrap lines after 10 cm? Why not let the board software take care of that instead so that users with every resolution will have their full screen width put to use?
Sorry, sorry. I do that whenever I post
anywhere; it's my style. If it really bothers
anyone, I wouldn't mind posting normally, just
tell me.
js
Doom9
17th August 2005, 13:08
When you say "mux your AVI into MKV
directly," are you talking about the vfw
version? Because I have no problems
with that... But I understand everything
else in that paragraph. Thanks for explaining.No, I mean using mkvmerge with an AVC-in-AVI input rather than AVC-in-MP4.
Sorry, sorry. I do that whenever I post
anywhere; it's my style. If it really bothers
anyone, I wouldn't mind posting normally, just
tell me. My display resolution is 1920x1020 so yes, it bothers me a lot.
jellysandwich
17th August 2005, 20:12
No, I mean using mkvmerge with an AVC-in-AVI input rather than AVC-in-MP4.
Hmm, how would I get an AVC-in-AVI input? The only way I know how is via vfw, since MeGUI doesn't give that option...
My display resolution is 1920x1020 so yes, it bothers me a lot.
Ok, I'll post normally from now on.
js
Doom9
17th August 2005, 20:14
since MeGUI doesn't give that option...Not correct.. using mencoder as x264 encoder you can create AVC in AVI. Download a recent mencoder build, then go into the megui settings and change the x264 encoder to mencoder.
jellysandwich
17th August 2005, 23:38
Not correct.. using mencoder as x264 encoder you can create AVC in AVI. Download a recent mencoder build, then go into the megui settings and change the x264 encoder to mencoder.
Woops, I meant MeGUI x264. OK, I'll try out the regular MeGUI then, thanks.
js
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.