I have a patch that is reading a text file (converted from gpx), and parsing it out in order to drive sound synthesis.
I'm using both snapshot and a tabwrite to visualize the two different synth chains (one driven by latitude + altitude, the other by longitude + altitude), and can see that the numbers are ranging a lot - from 0 to 120 or so... which is expected, and no problem.
The problem is that writesf~ is only seeming to take the values when they exist between 0 and 1, so only a small portion of my patch is actually recording. At least, this seems to be the issue, as far as I can tell. Can anyone confirm this behaviour ? Is there a way to edit it?
I've tried to put both a clip~ and tanh~ on my signal chain before writesf~, but they both seem to just ignore and values over the argument, and not actually compress/remap the values. Again, am I reading this behaviour correctly?
I can of course decrease the signal, but as I have several different files in my patch, and they all give different values, it is difficult to come up with an absolute value that wont unnecessarily make some of the tracks/processes sound too quiet...
None of this is a problem as far as actual playback is concerned, so in the end I might just record the output with Wiretap or some screencapture software, and just rip the audio, but I had never used writesf~ before, so thought I'd give it a try.
I might also be interested in trying soundfiler, but I am currently writing to 3 different arrays, and it doesn't seem possible to combine multiple arrays into one soundfiler write thread... but please, let me know if you have experience otherwise.
thanks for any feedback...