[®om]

Sur IRC tout à l'heure:

[19:44] rom1v: "--engage allow_avc_in_vfw_mode" >>> is it the same when muxing x264-avi when this option is enabled THAN a native mkv x264?
[19:46] unmei: no, i don't think so
[19:46] unmei: it simply _allows_ you to mux avc in vfw mode (like it was done before)
[19:47] rom1v: but what's better when you mux a native mkv x264?
[19:47] unmei: don't encode to avi if you want native avc mode in matroska
[19:47] rom1v: (i always use native mkv x264, but I would like to know the difference)
[19:47] unmei: don't ask me, but i assume one point is frames in coding order
[19:48] unmei: in vfw mode the avi-b-frame-hack is simply copied over
[19:56] bond: there is no avc vfw avi b-frame hack
[19:56] bond: it just stores the avc stream in mkv as it was stored in avi
[19:56] rom1v: and?
[19:56] rom1v: what's the diff
[19:56] bond: which means it doesnt store the avc stream in mkv as the mkv specs define to store an avc stream in mkv
[19:57] bond: i guess the timestamps arent set?
[19:57] bond: interoperability isnt there
[20:01] unmei: bond, i tend to call the work around the one-in-one out in vfw a hack
[20:01] unmei: even if that is not proper terminology
[20:02] unmei: err one-in, one-out
[20:03] bond: well its not really a hack, its how vfw works
[20:03] alexnoe:
[20:03] bond: yeah its crap and so is its brother avi ;P
[20:04] rom1v: even if virtualdub mod saves as MKV?
[20:04] bond: vdm doesnt write native mkv, but vfw mkv
[20:04] rom1v: oki
[20:05] alexnoe: the vfw bitstream contains more crap
[20:05] alexnoe: than the natively muxed one
[20:06] bond: like avi
[20:06] alexnoe: for a 2h movie iirc it was 800 kb for packed bitstream and 300 kb for nonpacked bitstream that got striped away when transmuxing to native
[20:07] bond: you get the video delayed when playing vfw mkv with b-frames too i guess?