"Rob" wrote in message
b.com...
On 09/04/2012 13:54, Arny Krueger wrote:
"Jim wrote in message


Are you aware of the architecture of that new and highly popular class of
machine called the "Tablet"? ;-)

Most can be interfaced to home equipment for AV, both audio and video.
Some
of the interfaces are pure digital for highest quality.

So much for machines with low inherent noise being niche machines!

Good point, but not enough storage, slowish processors and I'm not sure
how Android would cope with serving 1TB of data.

Android appears to be a dialect of Linux which supports large volumes.

Android currently supports an updated version of the FAT32 file system
called YAFFS2 and is to be or was recently upgraded to a new file system
called EXT4.

FAT32 has long been capable of supporting volumes up to 2 TB.

http://support.microsoft.com/kb/154997

Moving on to EXT4:

http://en.wikipedia.org/wiki/Ext4

"The ext4 filesystem can support volumes with sizes up to 1 exbibyte (EiB)
and files with sizes up to 16 tebibytes (TiB).[9]"

In article , Arny
Krueger
wrote:

"Rob" wrote in message
b.com...

Android appears to be a dialect of Linux which supports large volumes.

Android currently supports an updated version of the FAT32 file system
called YAFFS2 and is to be or was recently upgraded to a new file system
called EXT4.

Moving on to EXT4:

http://en.wikipedia.org/wiki/Ext4

"The ext4 filesystem can support volumes with sizes up to 1 exbibyte
(EiB) and files with sizes up to 16 tebibytes (TiB).[9]"

A word of caution, though. It is one thing for the spec of the filing
system to be such as to have such limits. But what you get with a specific
commercial device may depend on how the programmers of the device and its
firmware, etc, impliment using the filing system.

e.g. 1. I've found programs which use a *signed* 32 bit long (int) for
pointer offset into a file. Thus halving the max file size the program can
handle wrt using an unsigned long.

e.g. 2. The Tascam recorder I use works nicely. But its implimentation of
the FAT filer falls over at 8GB despite it cheerfully formatting, say 16GB
memory as being 16GB and showing free space in accord.

So you may find a given device or program has limits that are less than
you'd expect when seeing what something like ext4 or fat can do - *if*
fully and correctly handled!

Slainte,

Jim

--
Please use the address on the audiomisc page if you wish to email me.
Electronics http://www.st-and.ac.uk/~www_pa/Scot...o/electron.htm
Armstrong Audio http://www.audiomisc.co.uk/Armstrong/armstrong.html
Audio Misc http://www.audiomisc.co.uk/index.html

"Jim Lesurf" wrote in message
...
In article , Arny
Krueger
wrote:

"Rob" wrote in message
b.com...

Android appears to be a dialect of Linux which supports large volumes.

Android currently supports an updated version of the FAT32 file system
called YAFFS2 and is to be or was recently upgraded to a new file system
called EXT4.

Moving on to EXT4:

http://en.wikipedia.org/wiki/Ext4

"The ext4 filesystem can support volumes with sizes up to 1 exbibyte
(EiB) and files with sizes up to 16 tebibytes (TiB).[9]"

A word of caution, though. It is one thing for the spec of the filing
system to be such as to have such limits. But what you get with a specific
commercial device may depend on how the programmers of the device and its
firmware, etc, impliment using the filing system.

Right. For example YAFFS2 is a FAT32-based system with a theoretical 2 GB
volume limit, Android implementations of it in consumer hands seem to stop
at 16 GB.

e.g. 1. I've found programs which use a *signed* 32 bit long (int) for
pointer offset into a file. Thus halving the max file size the program can
handle wrt using an unsigned long.

e.g. 2. The Tascam recorder I use works nicely. But its implimentation of
the FAT filer falls over at 8GB despite it cheerfully formatting, say 16GB
memory as being 16GB and showing free space in accord.

So you may find a given device or program has limits that are less than
you'd expect when seeing what something like ext4 or fat can do - *if*
fully and correctly handled!

I've seen all of the above nasty things happen with various devices, mostly
cameras.

In the final analysis - if it works then it works but it might not! ;-)

The most irritating of these seem to be devices that get sticky and nasty
and unreliable when faced with too-fast flash.