Hi Ivica,
Thanks for the patch. I will try to apply them to the new repository at
github: https://github.com/electrickery/pd-cyclone and do some testing.
Just the opportunity to try the branch feature of git :-).
> Fred Jan,
>
> Attached are diffs between l2ork coll.c (threaded option and anothe
Fred Jan,
Attached are diffs between l2ork coll.c (threaded option and another
feature that is currently missing in Pd implementation but is present in
Max) and another small bug-fix inside curve.c. There are more changes to
Scope.c and comment.c but given these are gui based they are not goin
On 10/17/2015 03:16 PM, Fred Jan Kraan wrote:
On 2015-10-17 05:57 PM, Jonathan Wilkes wrote:
Fred Jan,
Now that's interesting. Thanks for testing it.
What happens with larger data sets? One thousand, ten thousand, etc.
Same result for 10.000 items; first the bang, then the result from the
du
Fred Jan,Let's say you've got a [cycle~] at frequency A. What happens if you
send it a message to change to
frequency B, read a big file with [coll], then change the frequency back to A,
all in zero logical time? (I.e.,
each event is a child of the same [trigger]. Do you hear the change to
Wow, that behavior is incredibly confusing.
I just had a zany idea:
1) an object (or a creator for [readsf~]) to "play" the bytes of an arbitrary
file as a signal2) an object that takes in a signal and builds a list until it
hits a specified value, then outputs the list and starts again. optiona
On 2015-10-17 05:57 PM, Jonathan Wilkes wrote:
> Fred Jan,
> Now that's interesting. Thanks for testing it.
>
> What happens with larger data sets? One thousand, ten thousand, etc.
Same result for 10.000 items; first the bang, then the result from the
dump. No interruption of the sound.
>
> A
Fred Jan,Now that's interesting. Thanks for testing it.
What happens with larger data sets? One thousand, ten thousand, etc.
And a question for Ivica,When you were using Max, did you mess with any global
settings? I remember reading docs about
a setting that could affect this (but I can't remem
Threaded coll does the same because IIRC it enqueues events it cannot
execute until the file is loaded, except, this makes it fall out of sync
with the rest of the system in that case, but then again that is why coll
has "done loading bang" outlet.
Also, I think what will test Max's threaded natur
Hi Jonathan,
> Hi Fred Jan,
> I suppose what I am asking is if the read/write bang outlet happens
> depth-first
> in Max, or not.
The test patch in Max 5 looked more or less like this:
[bang(
|
[t b b]
|\
|[read test.coll(
| |
[dump( |
\ /
[coll]
| |
[print]
[coll] and
Hi Fred Jan,I suppose what I am asking is if the read/write bang outlet happens
depth-first
in Max, or not.
If it does not, then it means Max _is_ sacrificing predictability for
performance
in that case. As long as we can predict that it will not crash, I think at
least having that option wou
On 2015-10-17 06:38 AM, Jonathan Wilkes via Pd-list wrote:
>
> Hi Ivica,
>
> When we discussed the threading feature before, I advocated against it
> since
> it breaks determinism.
There is an other reason for not adding threading to the coll object. In
the past I did some testing and found it
11 matches
Mail list logo
