Support for files larger than 4GB in 6.x?

[litkaj]

I'm currently running 5.04 but this has been a problem for me for quite some time. I've got a few XviD files that are larger than 4 GB and when played through Sage, they tend to flake out if you do anything but let them play, uninterrupted, from beginning to end.

The problem seems to manifest itself as an inability to determine the movie length. For example, last night I watched a movie that's ~2:25 and Sage told me it was only 50 minutes long. Any attempts to fast forward or rewind past half the claimed length cause the movie to skip around to where ever it feels like.

This same video file plays just fine in Media Player.

[fidget]

Originally Posted by litkaj

I'm currently running 5.04 but this has been a problem for me for quite some time. I've got a few XviD files that are larger than 4 GB and when played through Sage, they tend to flake out if you do anything but let them play, uninterrupted, from beginning to end.

The problem seems to manifest itself as an inability to determine the movie length. For example, last night I watched a movie that's ~2:25 and Sage told me it was only 50 minutes long. Any attempts to fast forward or rewind past half the claimed length cause the movie to skip around to where ever it feels like.

This same video file plays just fine in Media Player.

How do you have your hard drive formatted? FAT32 has a file size limitation. I have all of mine formatted for NTFS (64KB blocks) and have repeatedly recorded and played back 9+GB files without any problems.

[Goodspike]

Originally Posted by fidget

How do you have your hard drive formatted? FAT32 has a file size limitation. I have all of mine formatted for NTFS (64KB blocks) and have repeatedly recorded and played back 9+GB files without any problems.

I suspect these are files created by some other application, perhaps on a machine without NTFS, or just one that limted the size.

Sage does have issues playing back some files created by other applications, especially if the file has been broken up. I have that problem with about 1/3rd of the files created by my MyHD card, and probably 100% if the program gets stopped in the middle for some reason.

[nielm]

AVI's greater than 2GB can sometimes cause problems in certain media players depending on which app generated them due to the AVI file format's 1GB chunk limit... Some versions of FFMPEG are know to create files with this problem...

[ke6guj]

Originally Posted by litkaj

The problem seems to manifest itself as an inability to determine the movie length. For example, last night I watched a movie that's ~2:25 and Sage told me it was only 50 minutes long. Any attempts to fast forward or rewind past half the claimed length cause the movie to skip around to where ever it feels like.

Ignoring the 4gb+ filesize for a moment, that problem sounds like Sage scanned the file during creation or during a move. Try to rename the file so Sage rescans it and it may fix your problem.

If that fixes it then the permanent solution is to not let Sage san a file during its creation in a folder that Sage scans. Options include, turning off automatic import folder scanning (available in SageV6), or to do all file creation or moves accross HD's and network, into a tempory folder that Sage doesn't scan. Then, once the file is complete, you can do a same-HD move between folders. Then, it will complete the move before Sage can scan it during its incomplete period.

[litkaj]

Originally Posted by fidget

How do you have your hard drive formatted? FAT32 has a file size limitation. I have all of mine formatted for NTFS (64KB blocks) and have repeatedly recorded and played back 9+GB files without any problems.

The local drive is formatted with NTFS but the files are pulled from a network share. That array is formatted as ext3 and is residing on a box running the x86-64 version of Openfiler.

Originally Posted by Goodspike

I suspect these are files created by some other application, perhaps on a machine without NTFS, or just one that limted the size.

Sage does have issues playing back some files created by other applications, especially if the file has been broken up. I have that problem with about 1/3rd of the files created by my MyHD card, and probably 100% if the program gets stopped in the middle for some reason.

All files were created from DVD source on my desktop (Windows XP Pro, all drives are NTFS). The application used to create the media files was AutoGK.

Originally Posted by ke6guj

Ignoring the 4gb+ filesize for a moment, that problem sounds like Sage scanned the file during creation or during a move. Try to rename the file so Sage rescans it and it may fix your problem.

If that fixes it then the permanent solution is to not let Sage san a file during its creation in a folder that Sage scans. Options include, turning off automatic import folder scanning (available in SageV6), or to do all file creation or moves accross HD's and network, into a tempory folder that Sage doesn't scan. Then, once the file is complete, you can do a same-HD move between folders. Then, it will complete the move before Sage can scan it during its incomplete period.

I tried renaming one of the files and it didn't do any good. It should be noted that I have quite a few files that are in the 3.8-3.9GB range and all of those are fine. It's only files that are over 4GB that have the problem.

All:
I'm running Sage as a service under a login account with admin privileges. Is there some better way of doing it when you have files on the network?