Hi all,

I'm having a strange problem with arrays. I'm using [tabread] to read from an array, and every read from an odd-numbered index is returning 0. It's a bit like the array data is "double-spaced", i.e. I have to double the index to get the index I actually want.

For example, if I store {1, 2, 3, 4, 5, 6, 7}, I get back {1, 0, 2, 0, 3, 0, 4}. The array graph looks normal, and examining the array as a list looks fine as well.

On saving and reloading the patch, however, the array graph changes, showing every second value as 0 and the array contents are spread out. The list view also has a 0 at all the odd-numbered indexes. What's worse, [tabread]ing the array contents reveals that it's now quadruple-spaced, i.e. {1, 0, 0, 0, 2, 0, 0}!

I used Pd recently on Windows XP and Mac OS X and don't remember arrays behaving like this. I'm using Pd 0.40.2, compiled from source, on Gentoo GNU/Linux, kernel 2.6.19-gentoo-r5 for AMD64. I was using 0.39 when I first noticed the problem and grabbed the latest source. Could it perhaps be a 64-bit thing?

Thanks for any help you can offer,
screwtop

I had a look around the code, and I think it is a 64-bit issue. Reading the comments in src/m_pd.h, there seem to be some assumptions made about storage sizes, e.g. long is the size of a pointer, float is at most the same size.

I guess using double instead of float would satisfy that constraint (64-bit long is the same size as a 64-bit pointer), right? I don't like the chances of that being a simple clean change to make, though...surely someone else must have seen this if it really is a problem on AMD64...so is it just me?

Cheers,
screwtop

Ah-ha:
https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1532439&group_id=55736

Downloaded the patch, applied to 0.40-2 without any problems, arrays now work as advertised.

Sorry for the noise - hope this might help others.

screwtop

Nope, spoke too soon: arrays work within the patch, but when saved and reloaded it is corrupted again.

However, that SourceForge page now contains a note that this seems to be fixed in version 0.41.