AVI seeking 2Gb limit?

[Slider2k]

It seems that SMS can't seek on >2Gb avi files. If i try ff/rewind SMS just drops me out of video. If i try seeking through 'SELECT' it just hangs. Note: playing over network by RadHostClient.

[dlanor]

It seems that SMS can't seek on >2Gb avi files. If i try ff/rewind SMS just drops me out of video. If i try seeking through 'SELECT' it just hangs. Note: playing over network by RadHostClient.

That is probably due to a limitation of the HOST protocol. if a 'signed' 32-bit word is used for the offset within a file, then that offset will be seen as negative when it reaches the 2GB limit (2G == 2**31 which sets the sign bit).

Unfortunately the lseek function only uses 32 bits for the file offset, and the 'lseek64' function was never implemented.

While it would be possible to reimplement/expand the protocol to include lseek64, this in itself would have no effect until both server and client programs are recompiled accordingly.

For the time being you'll just have to live with this limitation, just as you have to accept the filesize limits of DVD-Video discs and FAT32 USB devices.

You might have better luck if networking SMS with Samba instead of HOST, since that is unlikely to have the same limitation (unless SMS is bugged in that regard). I've never tried that myself as I don't have so large video files.

Best regards: dlanor

[KnoWei]

@Slider2k:
SMS will scan on *.avi > 2GB for at least certain SMS set-ups. Most of my *.avi are over that size as I encode for full TV size resolution and high data rate (usually around 3Kbps).

When encoding I use OpenDML option in Mencoder which allows encoding beyond the 2GB restriction imposed by the orginal *.avi standard. I stream to my SMS from a NAS that supports SMB so I'm not using RadHostClient and cannot speak to this variable in your setup.

You may already be aware of this but you can inspect your *.avi files with something like GSpot to see how it was encoded.

Hope this helps.

~KnoWei