why do you need the textfile?
there might be a better option than that.
Hi Gilberto:
the two main things that cause audio dropouts in PD besides CPU overload are:
Writing to visible tables/arrays
Hard drive access
These problems have to do with the graphics engine and threading protocol of (Miller's) PD, and there's not much you can do to your computer to improve them, I'm afraid. Some other community-developed versions of PD have tried to correct these shortcomings (search for "threaded sound filer" for example), but I'm not sure how far any of them got.
The solution for 1) is to hide your table/array in a subpatch.
The solution for 2) is to find a way to write your data to RAM rather than directly to the HD.
Some people on this list have suggested RAMdisks for storing samples and arrays so they can be read/written without disk access. You might check the archive for some of those mails.
good luck, d.
gilberto bernardes wrote:
Dear list
I'm recording arround 2-5 seconds of sound in real time and drawing it into a table. During this procedure I'm also making a textfile with all the points of the array. During this procedure the audio drops for a brief moment.
Can someone tell me all the procedures I can do to try to avoid them. Maybe can I try to puch the performance of my computer to some extreme to try to have better results?
Another completly different question, can someone tell me if it's possible to add some kind of flag to a struct object in a data structures patch to not be able to select an object in the drawing window?
(also could someone give an example of how to incorporate those flags in the struct object, or drawing object)
Thanks in advance, Gilberto Bernardes
Transfira JÁ a última versão do Windows Live Messenger! Clique aqui! http://g.msn.com/8HMBBRPT/2746??PS=47575
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On Fri, 2007-11-16 at 14:29 +0100, Derek Holzer wrote:
Hi Gilberto:
the two main things that cause audio dropouts in PD besides CPU overload are:
- Writing to visible tables/arrays
i cannot confirm this on my ubuntu box. what i notice is, that display isn't updated when the content of the array changes too quickly (< 30ms). however, it _is_ a good idea to hide the array in a [table] or in a subpatch in order to save cpu.
roman
___________________________________________________________ Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de