moin again,
On 2011-01-30 17:07:44, Mathieu Bouchard ma...@artengine.ca appears to
have written:
On Sat, 29 Jan 2011, Bryan Jurish wrote:
In this scenario, we're blatantly re-casting the array's (t_float*)
into a (char*) and reading/writing raw bytes.
Ok, I thought you were going to write
On Sat, 29 Jan 2011, Bryan Jurish wrote:
Yup, all freely stipulated. My issue was not so much with the use of
floats qua floats to store size data, rather the necessity of storing
size data *in addition to* the size reported by the array itself.
In this scenario, we're blatantly re-casting the
On Fri, 28 Jan 2011, Bryan Jurish wrote:
iirc, Miller has indicated in the past that he feels this sort of thing
should be done using arrays.
But a feeling is but a feeling. Now, how about a justification ?
But that's not the sort of thing one gets from Miller often.
(B) you must scale all
moin Mathieu, moin all,
On 2011-01-29 17:12:02, Mathieu Bouchard ma...@artengine.ca appears to
have written:
On Fri, 28 Jan 2011, Bryan Jurish wrote:
iirc, Miller has indicated in the past that he feels this sort of
thing should be done using arrays.
But a feeling is but a feeling. Now,
On Wed, 2011-01-26 at 22:54 +0100, João Pais wrote:
For converting, I like moocow/any2bytes and moocow/bytes2any.
I think I had a look at it as well. do you have any comparative reason for
that one instead of the other? or it was just the first one to get to you?
One important thing to
moin all,
fwiw, I'll add my vote in favor of getting Martin's [str] / blob patch
into pd vanilla. iirc, Miller has indicated in the past that he feels
this sort of thing should be done using arrays. There are a couple of
proof-of-concept objects (not compiled by default) in pdstring
Hi,
I was curious to know what is the standard encoding of pd files in each
operating system. According to Notepad+, in XP is ANSI.
Or a followup question, which format is better for pd to read a string of
characters and convert it to floats? ANSI seems the be most reliable here
where
Hi Jo?o,
The reason I'm asking is because I'm working with converting ascii
characters to their float value.
If anyone wants, I can send a small test patch to try out.
I convert ascii characters to float with PHP.
If you have a patch to convert text inside pd (vanilla) can you send me?
I convert ascii characters to float with PHP.
If you have a patch to convert text inside pd (vanilla) can you send me?
what you mean, convert ascii to float? there are several objects for that,
for now I'm using [mrpeach/str to_list] or [mrpeach/str to_symbol]
, João Pais wrote:
Hi,
I was curious to know what is the standard encoding of pd files in
each operating system. According to Notepad+, in XP is ANSI.
Or a followup question, which format is better for pd to read a
string of characters and convert it to floats? ANSI seems the be
most
will both be fully ANSI if only the
standard ASCII chars are used, i.e. no ü, ã, é, etc.
For converting, I like moocow/any2bytes and moocow/bytes2any.
.hc
On Jan 26, 2011, at 5:17 AM, João Pais wrote:
Hi,
I was curious to know what is the standard encoding of pd files in
each operating
Pd 0.43 is probably something like ISO-8859-1 or perhaps UTF-8, Pd
0.43 is UTF-8. UTF-8 or ISO-8859-1 will both be fully ANSI if only the
standard ASCII chars are used, i.e. no ü, ã, é, etc.
hmm, for my case I'm needing the 256 values in the chart. I'm noticing
that there are differences
@João: ... for converting strings (lists of bytes, represented as pd
floats) to floats (as in pd floats, a la C strtof() friends) you can
do some sick bad ugly and wrong things using [bytes2any] in conjunction
with [locale] (e.g. by dynamically re-setting LC_NUMERIC) ... but maybe
that wasn't
On Wed, 26 Jan 2011, Hans-Christoph Steiner wrote:
Pd 0.43 is probably something like ISO-8859-1 or perhaps UTF-8
Pd Extended 0.42 and 0.41 are system-dependent on this : ISO_8859-1 on
OSX, ISO_8859-1 in Linux's pd server, and UTF-8 in Linux's pd client.
This explains why accents in OSX
14 matches
Mail list logo
