Joining 2 Xvid files

[maormini]

I have searched the forum up and down and didn't find a full answer to this question!
I have 2 xvid encoded files which the only difference between them is the bitrate used. All other settings are the same.
When I load the files in vdub or vdub mod I get an error when trying to append the 2 segements that says not same stream or something like that.
I saw somewhere that there could be a solution if I will use a program called aviutil to join the files but I can't find the program anywhere!
So, if antyone can help me with my little problem it will be highly appreceated.

By the way when loading the xvid files in vdub or vdub mod the first frame gives me some sort of error about the b-fram lag or something. Does anyone know something about that?

[Nic]

"says not same stream or something like that." ?!?!
Your kidding me right? You want help and thats the kind of bug report your giving?

Looking through Doom9's Download section would have found AviUtl also a google search would have found it.

"gives me some sort of error about the b-fram lag or something"
Be more accurate next time...anyway don't worry about it, its caused by the vfw interface which can't handle B-Frames, it won't show up when using the DShow filter for decoding.

Thats all the help your going to get, next time try alot harder first if you want help.

Thread Closed.

-Nic

[Nic]

It seems I was mistaken, this is a problem with XviD. I thought it to be one of the standard AVI joining problems (invalid bits in avi header etc).

sysKin, will be along shortly to describe the current avi joining problem with XviD.

My apologies for being too quick to close the thread. It's one of the reasons why when bug reporting you have to give as much information as possible, otherwise moderators and users will disregard the thread.

-Nic

[sysKin]

@maormini: Nic was right to yell at you, you really shouldn't have posted a question like this.

Now, about the problem: it was xvid's fault. The bug (in vfw code) was spotted only a few weeks ago by Cyrius of virtualdubmod team. It's fixed now, but I can't confirm if newest Koepi's build is new enough.

How to join them: remux both files to ogm using any tool you want (virtualdubmod for example). Then, join them using virtualdubmod and save again (to avi, if you want to). Perhaps you can also use matroska for the intermediate file, I don't know.

This problem has been around for a long time, all xvid files have it

Radek

[DaveQB]

thanx maormini for bring this up.

i havent had this problem but perhaps coz i use AVISynth alot and that might be getting around this problem.

i'll be careful with this and when i am editing...

(i use Matroska alot too )

[rossy_boy69]

i had same problem got round it by running each part of the movie through avimux-gui then join them in the normal way through nandub hope this helps

[DaveQB]

hmmm so AVIMux has something the other editors dont? ?(ie VDubMod)

i cant get the english language file to work with AVImux

[alexnoe]

AVI-Mux GUI does not compare all header data, but only 'important' things like codec, resolution and fps. If those match, it accepts the files and joins them.
Also, not all parts of the headers are read and used. The BufferSize members for example are ignored and rebuilt when muxing a file.

That's why it can repair some errors in source files.

i cant get the english language file to work with AVImux

What's happening?

[DaveQB]

hahah oops!!
i was thinking of AVIutl

i followed ya link in sig,
looks good!!

cheers!!

[vass-iliskus]

Originally posted by sysKin
Now, about the problem: it was xvid's fault. The bug (in vfw code) was spotted only a few weeks ago by Cyrius of virtualdubmod team. It's fixed now, but I can't confirm if newest Koepi's build is new enough.

I recently came across the similar problem, so I guess maybe this bug is not completely fixed, or it has a twin

In short: when appending one fragment to another, encoded with exactly the same xvid settings, the mentioned above error message (Cannot append segment: The video streams have different data formats.) appears.

The only real difference between these two fragments is that one was encoded from YV12 source, while the other from YUY2.

I was thinking XviD uses YV12 color space, so the origin is not affecting the fragments after they're encoded, am I wrong ?

P.S. Using Koepi's 24062003-1 build, VDubMod 1.5.4.1 and AviSynth 1.5.2, saving to avi.

[sysKin]

Originally posted by vass-iliskus
The only real difference between these two fragments is that one was encoded from YV12 source, while the other from YUY2.

I was thinking XviD uses YV12 color space, so the origin is not affecting the fragments after they're encoded, am I wrong ?

It's not that simple
First of all, XviD streams do not have to be compatible at all - one can use qpel, the other not, etc etc etc - but you will still be able to join them, because it's not the content of the AVI that has to be joinable.
In order to join avi files, avi header must match. Now comes the funny part - colourspace *used to create* the avi is written in the header. If you used YU12 for the first and YUV2 for the second, avi headers are different and you can't join.

Stupid but true...

I don't really have any good idea which could help you...

Regards,
Radek

[vass-iliskus]

Thanks for you answer, it is very interesting... To my particular
problem I found the answer even before I was writing the post: it
appeared when I was playing with credits encoded in huffyuv to save
some time on heavy filtering, so I just wrapped huffyuv-encoded avi
into artificial .avs with converttoyv12() before feeding it to xvid.

Last time when I was receiving the same error was trying to follow
your advice on settings for credits (5 b-frames, threshold 5000,
something like that). That time I forced VDub to do the merge using
the debugger, now it seems to work without human itervention
I was wandering since then - what happens to decoder when it
encounters such junction ? In VDub one sees the famous "B-frame
decoder lag" message, but, technically, what happens during the
playback ? Will the video stream be delayed at that moment, some kind
of 'hiccup' ?

Regarding the header: I was thinking it is up to the developer of
each codec to decide what he puts there, is that really so ?
How could one know which properties of a stream are 'vital' for the
compatibility with another one (assuming they're made using the same
codec of course) ?

[Rice_Boy]

hey there, sory i did a seacrh and couldnt find my question,

can i join 2 XviD files that have different resolutions?, im trying to combine the Xtras with the main movie. but they have different aspect ratios.

How do i acually join the 2 files in Vdub? ive searched for this also but no one acually mentions how to do it, they just say that you can.

Thank you

[DaveQB]

i am no expert, but i do know the best way to over come errors in joining strems in VD(mod) is to use AVIMux GUI instead.

I dont know the technical side, but it joins differently, more in a raw way if you will, and has a better success rate.

i hope this helps

[Tommy Carrot]

Originally posted by Rice_Boy
hey there, sory i did a seacrh and couldnt find my question,

can i join 2 XviD files that have different resolutions?, im trying to combine the Xtras with the main movie. but they have different aspect ratios.

How do i acually join the 2 files in Vdub? ive searched for this also but no one acually mentions how to do it, they just say that you can.

Thank you

You'll have to open the first part, then the 'append avi segment' option in the file menu will do the rest.