Joining Avi Files

[Mahneb]

How's It |Done...Please!!!

[Nocturnus]

Run VirtualDub, open first file in it.
Mark Direct Stream Copy in Video configuration dialog, then Append Avi Segment in File options and open second file.
Save final avi.
Simple, isn't it.

[Mahneb]

I'll let you know. Thanks for the swift answer.

:)

[Amerzone]

And, obviously, if you have more than two segments to join, just keep appending them to the first part and press F7 only once at the end to save the final avi...

[Executioner]

Isn't there a 2 gig limit on avi's? The reason I ask is I was joining 2 avi files for a combined movie length of 2 hours and 25 minutes. In my first attempt, VirtualDub created 2 files - one at 2 gigs and the other with the remaining time left on the movie.

In my second attempt, I selected a different codec and was able to compress the movie to almost 2 gig avi. Is there a way around this 2 gig limit? I have a NTFS drive where all my encoding takes place, so it's not a OS problem.

[lamer_de]

In my second attempt, I selected a different codec and was able to compress the movie to almost 2 gig avi.

Huh? I always used it to make 1 clip out of two, so obviously the big one will have the exact size as the 2 smaller ones.

If you want to re-encode, you can do so, of course. I suggest you use GKnot/Nandub or XVID, you can specify the size of the final encode very precisely. AFAIK there's no way to bypass this limit, it's a flaw of the format. Maybe OGG can handle bigger files, I'm not sure about that.

But why do you need 2GB avi files? They won't fit on CDR-s :p

EDIT: I found this in the forum:
http://forum.doom9.org/showthread.php?s=&threadid=35260

CU,
lamer_de

[Zhnujm]

@Executioner: make sure you are using "save avi" and not "save old format avi", it restricts the filesize to 2gb.

[Executioner]

I was joining the 2 avi's to make a SVCD to be played on my DvD player using DVD2SVCD program. I wanted DVD2SVCD to make the cuts and I needed one large file.

I did use the xvid codec and it was almost 2 gig's in size. Since I was joining and saving 2 avi files into one, I selected the option "save segmented avi". This is where it will as for a size, and I think it was between 50 to 2000 megs. I typed in 2048, but if I typed in another value, it would not accept it.

[Zhnujm]

i am not exactly sure what you want to do but if you just want to join 2 already compressed avi files, just load the first file, append the second file , set audio + video to "direct stream copy" and select "save avi".
dont use "save segmented avi" and dont recompress the files. that would be a waste of time and quality. ;)

[Executioner]

Thanks Zhnujm, I'll keep that in mind the next time I have to combine 2 or more AVI's.

[HuMpH]

While on the subject of joining .avi files....what if the files are from xvid source.I just tried to join them in vdub but get msg saying "could'nt locate decompressor for format xvid" when i try to load the first file, am i missing something here?

[lamer_de]

That eroor message lets me conclude that you only have the direct show filters installed, not the xvid codec. Strange enough, vdub can't join xvid files for me either. I use aviutil which does the job just fine. Dunno if this is some sort of bug, it's not implemented into vdub yet or just bad luck

CU,
lamer_de

[HuMpH]

thnx m8 will go get aviutil :)

Hmm aviutil wont open it niether says "wrong format"
even tried to use the nimo lite pack to see if it installed different codecs but that says "cant open codec" when i hit the .exe :confused:
what exactly is the correct codec needed for xvid i dont understand why it plays fine but wont let anything else open it to join into 1 file.

[?¿öM¿?]

Try posting in the Xvid forum. Should get a answer there. :)

[lancer]

Zhnujm


doesn't win98 still have a 2gb file size whether I select save avi instead of old format avi anyway?

[hakko504]

@ lancer

FAT-32 always has a filesize limit of 4GB. Do remember that a lot of apps have problems with 2GB+ AVI's whether they are OpenDML or not.

[Karl Beem]

The joining works - as long as the files were not captured with AVI_IO. If they were, Vdub gives the error message: "Cannot append segment. The video streams have different data format." Even when the two files are obtained by capture,end capture,capture... IOW, they should be identical in format. Very curious.

[Zhnujm]

have a close look at the file information in vdub, the smallest difference in the sample rate or frames per second and vdub doesnt append these files anymore. :(

[hubereevez]

Exactly same fps, resolution and when trying to append :
"different data format" : argh
.....and I searched the forum (fps answer)

thanks

hubhub

[hubereevez]

Hi,
I used some other tool (avi joiner)
both file status : 608*256 ; 25,00fps : ok
wonder why virtualdub(mod) is so hard with me
'll trying some other settings

[alexnoe]

what about AVI-Mux GUI?

[hubereevez]

yep already done :)
jsut wondering why vdub, vdubmod have such a behaviour
hubhub

[MinosK]

Hello.. I tried to join 2 avi files with VBR audio and when i try to open the 2ed one i got the message "Cannot apend segment: The audio streams heave different sampling rates (15998.00000 vs. 16000.00000)"
Can anyone help me? I used Nandub and VirtualDubMod but the same...

[alexnoe]

look 2 messages above

[mangis]

Just wondering when I split a movie to fit on 2 cds and then rejoin those files the result is always a file that is 2-3MBs larger than the original movie. Is this normal ?, I thought that I should end up with a file exactly the same.

[Rober2D2]

About latest virtualdubmod version (1.5.1.1a), I find almost impossible to make to xvid AVI files that can be appended, even when I use the same source, same resolution and same codec settings. I even tried making a 2 pass xvid avi using 2 jobs, shutdown virtualdubmod and repeated jobs again to make an identical file (I was unable to append them. This didn't happen in 1.4.x versions.

The curious thing is that if I convert AVIs into OGM files, virtualdubmod can append them with no problems.

[Suiryc]

Originally posted by Rober2D2
About latest virtualdubmod version (1.5.1.1a), I find almost impossible to make to xvid AVI files that can be appended, even when I use the same source, same resolution and same codec settings. I even tried making a 2 pass xvid avi using 2 jobs, shutdown virtualdubmod and repeated jobs again to make an identical file (I was unable to append them. This didn't happen in 1.4.x versions.

The curious thing is that if I convert AVIs into OGM files, virtualdubmod can append them with no problems.
This is (was) a problem caused by both the XviD codec and VirtualDub(Mod).
Here is what happened :
when initializing output in VirtualDub(Mod), the XviD codec ask for a header of 108 bytes (don't ask me why, I dunno). But it only initialize a header of 40 bytes (corresponding to the BITMAPINFOHEADER structure, which is the standard video header).
This is the first problem. The second one was introduced in VirtualDub 1.5.0 (I think this wouldn't happen with previous versions) and so in VirtualDubMod 1.5.1.1a. The problem is that VirtualDub(Mod) reserve space for those 108 bytes asked by XviD, but doesn't initialize it to a 0x00 value.
Since neither XviD nor VirtualDub(Mod) initializes the 108-40 bytes that follow the BITMAPINFOHEADER info, you get unknown data in this part.
Of course when you try to append 2 files VirtualDub(Mod) compare the 2 headers and if they differ then it rejects the appending.

Now the reject would happen more often (almost always actually) in VirtualDubMod because we make some extra initialization (the Script editor things etc) that fill some memory space with text strings, and VirtualDub core may reuse those memory addresses later when reserving space for the headers. Since reserved memory hadn't been reseted you still have some strings in those reused adresses, and of course the strings you have here are never the same (so 2 XviD files would have 2 different header).

This problem only happened with XviD, the DivX codec ask for 40 bytes when being initialized.

I found this problem today (thanks to sysKin for providing some sample files to see what was the problem :)) and fixed it in our CVS.
In the meantime I also realized that Avery made the same fix since VirtualDub 1.5.2 (but his fix was actually in answer to a similar problem with the HuffYUV codec :p).