shouldn't Matroska support files >2GB ??

[theReal]

I have encoded a 4-CD Divx recently (video plus two AC3 audio streams) and tried to save it to one big file first. Of course it wouldn't work with .avi, so I thought I'd try the Matroska container (which was pretty easy coz I'm using VDubMod anyways).

However, I still had the same problems as with avi: I was able to save to 700MB pieces without any problems, but when I tried to save one big file, VdubMod would just save and save and save... but never stop. Am I doing something wrong, or does Matroska not support files >2GB neither, just like avi (at least when using AC3 audio)??

[ChristianHJW]

How much RAM do you have, and how big is your virtual memory ? This sounds more like a memory leak to me, because we were making 80 GB MKV files already, and without any problems. What version of VirtualdubMod are you using ? Can you have a look at your memory usage in task manager when the muxing goes slower and slower ?

[theReal]

How much RAM do you have, and how big is your virtual memory ? I have 512MB RAM, WinXP, Virtual Memory 768MB min.- 1536MB max.

I think I was using VdubMod 1.5.4.1 but I'm not 100% sure (maybe it was an older version, but not much older)

btw. I have been saving avi files up to 20GB without any problems on capture - the only difference was they had PCM audio and not dual AC3 audio streams...

[Hiro2k]

Have you tired muxing it in mkvtoolinux instead of VdubMod? The problem could be in VdubMod and not in matroska itself.

[Atamido]

From the Matroska specs page:Modern computers have difficulties dealing with data coded on more than 64 bits, so for the moment we won't specify more as we will hardly ever encounter an element bigger than 2^56 octets, i.e. 7x10^16 octets or 72000 terabytes. So, no, there is not a limit that you would hit in the design of Matroska. And the limit that is there is artificial because of computers having issues.

First, I would recommend updating to the latest VDMod. There were a lot of changes that went on in the core that may have fixed this bug. MKVMerge or AVI-Mux GUI should both work also.

Also, you are using NTFS instead of FAT32, correct?

[alexnoe]

Of course it wouldn't work with .aviLOOOOOOOOOOOOOL
AVI files can be half as large as Matroska files: The index uses 64 bit signed integers, while matroska uses unsigned, i.e. 36000 Terabyte should work. Check the links in my signature.

If large files work neither on AVI nor on Matroska, it is time to reinstall windows: The limit of FAT32 is 4 GB, not 2 GB, so the error is most likely not there.

[theReal]

I'm not using FAT32, I'm using NTFS, WinXP Pro SP1

As I said before, I'm constantly dealing with avi files between 5 and 20 Gig when I capture stuff (MJPEG or DV). But somehow it seems a bit different when the audio is 2 tracks of AC3.

From earlier discussions I remember that there was mentioned some kind of limit with avi files over 2GB (that had nothing to do with the Windows filesystem). So I always considered myself lucky that I never had any problems with big avis.

I'm going to try one of the other matroska programs and the newest VdubMod, we'll see :)
(going to take a few days 'coz I'm at my parents' house right now and can't check it)

*EDIT*: I just read some info on the avi format and saw that all these 2 and 4GB limitations only apply to avi 1.0 that uses 32bit indices.

[MetaHiro]

Upgrade your VDMod. This was a bug in the build you are using.

[mikeX]

i get a similar problem with the latest vdubmod releases (1.5.10.1-2389/2407) both on 700 MB and 1400 MB files:

after a while i get a 0.0 fps rendering rate (with idle priority)

a 'workaround' i came up with recently is messing around with the priority when the above mentioned problem occures (e.g. set it to higher and then to normal) and/or turn lacing off

i don't really use matroska yet (i use ogm instead) so i haven't tested enough :(

i was muxing avi video streams (sometimes mkv) with vorbis audio (1) and srt subtitles (1 or 2), so i couldn't test with AVIMux GUI either because i hadn't checked for a new version in a while and didn't have vorbis support

i think (but i'm not that sure really) that the problem occured while muxing into ogm once or twice), if that's the case it's definately a vdubmod bug :(

anyways i'm on linux right now :D, and probably will be for a while so i don't know when i'm gonna be able to test with the new AVIMux GUI

[theReal]

It was a VDubMod Problem. I tried the newest version 1.5.10 and it worked for both avi and matroska!!!! :cool:

[boombastic]

I had this problem:i tried to mux a 240 MB ogg file with a 1,8 GB avi file with MKVtoolnik 0.8.0 and there is a gradual loss of sync. between auido and video which after 2 hours of movie is unacceptable.This never happened with small file.Someone experienced this?

[alexnoe]

Does it happen with other muxers, too? If it does, then one of your source files is likely to be b0rked :p

[Mosu]

Originally posted by boombastic
I had this problem:i tried to mux a 240 MB ogg file with a 1,8 GB avi file with MKVtoolnik 0.8.0 and there is a gradual loss of sync. between auido and video which after 2 hours of movie is unacceptable.This never happened with small file.Someone experienced this?

A very simple check: check the length of the Ogg and the AVI. They will probably differ.