Subject: Re: [linux-audio-dev] file sizes and retrofits
From: Dave Phillips (dlphilp_AT_bright.net)
Date: su helmi 06 2000 - 11:20:57 EST
Greetings:
I will study the code more closely for more exact details. I can tell
you _what_ Ceres does, though I'm not at all sure how it reads a file
for the process: The load action is actually a "Load & Analyze" function
that (presumably) reads the entire file and performs an FFT on it, then
renders it to the graphic display. I assume it uses memory instead of
disk, restricting the possible file size to RAM. Am I correct in
assuming that this method is indeed restricting the acceptable size ?
I'll post more detail when I look closer at the current load routines.
== Dave Phillips
http://www.bright.net/~dlphilp/index.html
http://www.bright.net/~dlphilp/linuxsound/
Paul Barton-Davis wrote:
>
> > I have a question for you coders: If I want to make an app capable of
> >loading and processing large files, what do I look for and replace in
> >the current code ?
>
> dave - i don't think there are any general guidelines on this. there
> are so many ways that a program could access/load a file that there
> are a lot of different possibilities. if a program expects to be able
> to load the whole file into memory, for example, its never going to
> work unless you have enough swap space and don't mind the speed
> penalty of constantly paging to and from swap. by contrast, another
> program might only load 4K into memory at any one time, and even that
> might be implicit in its use of the stdio routines (fread/fwrite etc.)
> if you tell us more about what ceres does when it accesses a file,
> some more ideas might be forthcoming.
>
> --p
This archive was generated by hypermail 2b28 : pe maalis 10 2000 - 07:23:27 EST