Hi all --
I'm not sure it's done right, but my intention in s_audio_pa.c is to use 'float' when talking to the portaudio API and t_sample to talk to the rest of Pd -- so t_sample could be made double without affecting portaudio.
The only situation I can imagine in which t_sample might want to differ from t_float is to do ficed-point audio... but I think nowadays that's almost never needed.
cheers Miller
On Wed, Jul 27, 2011 at 05:56:01PM -0400, Hans-Christoph Steiner wrote:
On Jul 27, 2011, at 5:47 PM, IOhannes m zmölnig wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 07/27/2011 11:11 PM, Hans-Christoph Steiner wrote:
like you've covered that already. As for 64-bit floats to output, a quick hack to get things working is to just hammer samples down to 32-bits...
i don't think that's such a great idea. loads of problems (mainly with granular synthesis or other applications where you want to access large tables sample accurately in the signal(!) flow) can simply be fixed by making signals be 64bit too.
and then, quite some infrastructure code makes no clear separations between t_float and t_sample, so it might be simpler to make Pd use doubles throughout and not just for one type of numbers.
I'm saying only as the final output stage to portaudio as a temporary hack to get things working. Its not a good idea otherwise.
.hc
“We must become the change we want to see. - Mahatma Gandhi
Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev