[PD-dev] Tabread/write on array bigger than 16777216 points

[IOhannes m zmoelnig]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2011-07-13 19:31, katja wrote:
> On Wed, Jul 13, 2011 at 3:51 PM, IOhannes m zmoelnig <zmoelnig at iem.at>wrote:
> 
>>> the idea is to make "double" the standard for Pd in the future.
>>> if nobody spents time for that it will never happen.
> 
> I'd like to help with this if I can (with only fragmentary knowledge of Pd
> core code I must say). I recall looking at the options to compile Pd with
> type double, but running into union tabfudge and UNITBIT32 which are used by
> rather central Pd objects like [osc~] and [phasor~]. I did not fully grasp
> the working of this clever type punning hack, but assumed it cannot be
> translated to type double rightaway. Is it true that this trick is crucial
> for computational speed of [osc~] & co, and must an equivalent routine still
> be developed (if possible at all)? Or are there other, more important
> bottlenecks to solve?
> 

i think this is the main showstopper right now.
the type punning tricks used to be crucial (i assume), but nowadays the
speed gain should be rather low (at least according to some tests we did).

i would suggest to come up with a generic implementatin of those
objects, do benchmarking and if needed (and possible) provide an
alternative optimized solution (in addition to the generic one)

fgmadsr
IOhannes
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk4d2AgACgkQkX2Xpv6ydvQxMQCfWS9vWrq9VFBAPOD7a92A0SYO
fu0AoNbMEpEs1EGdQC9RmBBeNyHSJDqf
=5vXD
-----END PGP SIGNATURE-----

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3636 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.puredata.info/pipermail/pd-dev/attachments/20110713/2ba20d33/attachment.bin>