Hmmm,... strange... since I just indexed sucessfully a 7.7GB and 10GB recording from german Kabel1 and had no Problem at all! :D
The first one is already processed/cutted... and also NO Problem in writing the output (but that was much smaller than 4GB, because the large files contain several episodes.... anyhow the output disk is a FAT32 one... so I can't test what happens when writing more than 4GB... ;-)). Was that working for me because I read the recordings directly from my Sat receivers disk by mounting it with Svens TFFS? I don't think so,... I assume that problem has to do with WRITING more then 4GB (which I never did),.... right? ciao Ralph Am Dienstag, 17. Oktober 2006 23:01 schrieb Michael Riepe: > Last week, I wrote: > > That might be a problem with the file's size - more than 4GB sometimes > > causes strange effects. I couldn't figure out why yet. > > I ran some tests and noticed that several operations overflow when an > index is generated for a file that is larger than 4GB. This will also > happen with a 64-bit version because some variables simply are too > small. It will take quite a while to clean up that mess - and this time > I really mean "quite a while". Don't expect a fix within 24 hours. ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ DVBCUT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dvbcut-user
