Hi! Ralph Glasstetter wrote:
>>>Just tried it with another file (2.4GB) ... and the progress bar stopped at >>>about 85%. >> >>While indexing or while exporting? > > It was while indexing, as with the 2 huge files I tried at first! That really looks like it bumped into the 2GB boundary. > That time I didn*t had a look at the progress bar but after it stopped I > could navigate in the video > (for only the first 50min, about 2GB?) and then the box had been frozen when > opening another file. > > >>>That's pretty near to 2GB again... does your lseek make problems? :-( >> >>That would be strange, because dvbcut has been using lseek() - the >>32-bit version on Windows - for positioning before. On the other hand, >>the Windows version works fine with 1 GB snippets (I had no bigger files >>for testing). > > > Yes, it has something to do with the combination of index&buffer... I guess I know where the problem comes from (to be verified later). There has always been a call to lseek(), even for the Windows port. But it probably was never used because with single files, all reading was done through mmap(). Therefore, the error didn't show up. The multi-file code, on the other hand, requires lseek() and read() because it can't mmap() a region that crosses a file boundary. I'm not sure why mmap() didn't fail on Windows as well, though. Michael. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ DVBCUT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dvbcut-user
