I guess I can help you with teeth~, it's really supposed to be darn simple as hell. The filter formulas is not a problem for me. I guess I could help and just try and do it.

"The objects you mentioned, apparantly happened to be part of cyclone, in the 'cyclone sub-library', but I cannot find them anymore in the code"

I had the idea they were around and vanished.

"Some of the objects exist in zexy, but not all"

But with some other name, right? Cause I tried to instantiate these objects and they just didn't show up. I'd like to know which ones are in zexy and how to call them up.

I could try to implement them in code

Me too, maybe I could collaborate. I've been meaning to start coding objects for a long while now.

cheers

2015-02-22 11:26 GMT-03:00 Fred Jan Kraan fjkraan@xs4all.nl:

Hi Alexandre,

The primary goal with cyclone maintenance was fixing the known bugs, maybe add missing functionality for existing objects and improve the help-patches. This is now more or less completed, apart from providing compiled versions for 'compile-unfriendly' platforms.

Adding new objects was not the primary goal, but could be next. I looked at the teeth~ object you suggested, but it will take more time to understand the transition from formula to code. Filter code, certainly optimized, is not simple to understand!

The objects you mentioned, apparantly happened to be part of cyclone, in the 'cyclone sub-library', but I cannot find them anymore in the code. I will try to find out why. Some of the objects exist in zexy, but not all, so it is the question where best to add new ones.

As a first step creating them as abstractions might be a good idea, and if some of them turn out to be expensive, I could try to implement them in code. In which library they should be placed could be an other discussion. For now, I only do cyclone...

Greetings,

Fred Jan

...

Other suggestions for objects, these are quite simple to make, maybe too silly to bother as well;

[!-] & [!-~] [!/] & [!/~]

and also the signal versions of comparatives such as

[>~], [>=~], [<~], [<=~], [!=~] & [==~]

by the way, this could all be done with simple abstractions made out of [epxr] and [expr~]. I could do them like that if you want it.

cheers

2015-01-23 14:25 GMT-02:00 Fred Jan Kraan <fjkraan@xs4all.nl mailto:fjkraan@xs4all.nl>:

Hi All,

At
http://fjkraan.home.xs4all.nl/__digaud/puredata/cyclone/index.__html
<http://fjkraan.home.xs4all.nl/digaud/puredata/cyclone/index.html> a
new set of revised help-patches for the cyclone library are
available. Most previous remarks are applied.

There are now previews of the Windows binaries and MacOSX. The
latter is build on MacOSX 10.5 with XCode 3.14, so should have
executables for PPC, i386 and i386_64. I confirmed the last two are
working (10.5 and 10.8).

It remains in progress, in the task list are the fixed and remaining
issues.

Fred Jan

_________________________________________________
Pd-list@lists.iem.at <mailto:Pd-list@lists.iem.at> mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/__listinfo/pd-list
<http://lists.puredata.info/listinfo/pd-list>

&&~, ||~, <~, >~, ==~

none of these are created in extended 0.42-5, were they added only in the latest version?

cheers

2015-02-23 5:50 GMT-03:00 IOhannes m zmoelnig zmoelnig@iem.at:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256

On 2015-02-23 02:54, Alexandre Torres Porres wrote:

...

But with some other name, right? Cause I tried to instantiate these objects and they just didn't show up. I'd like to know which ones are in zexy and how to call them up.

&&~, ||~, <~, >~, ==~

fdms IOhannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v1

iQIcBAEBCAAGBQJU6unuAAoJELZQGcR/ejb4qH4QAIbu1L7XYeBtKza8Hg5BgVEx TfIdxLWpbs8KK6ErEj3rtRX+RMrr/q7j+AJCZGUwnqhrpkgVudyruzIRDOcfNpMb /VBOub1Hc1oiyHwFSxyjaI1QutmHR52MfwVTYtL2/2pTSuj+ndYkP/rfMB0GUa1x ABFnFOzmUsaP51ZSZy+6zcAsShuoxgMNn0lqR/0wukhrYCjLTo4o26py57LTADSn bY23TUm41NihZLomDhIIMqIQnazG6uVtfGndiW0v9+DOnM6WaPrjcyBu552MFFdF zJkpy6F3dw6eZXENNDHyfHRN2Pu1LJY9Xm0prb1YIdMttMwTD11L0mi9uKE6RIDW mm5SnlperKCVVj+u2GotbkUWQiiEftumGJzLVwS8Ksx2IefYS8HhFkCKx2Asy+3B IdHUR00Tfo+LPXPmN1V0z04Z4VFg5At+15J3nlzq8b9gw5/FMXrm67eT23c7O0Iq v2tTWZz2Xkqe71UA5TIypkxfTDzsZ2Mb/9XHKqCZd0sF9e1Zji+wAfgAEQtyvLsZ 0haSeP7qnI1ZZ/0eJKNCI4vxU/ejXknNVZHHit/Radf8Z+5ehQHBDjn7Y0WgXau6 h6oGGM+oV28w0hs6Ue/wo8tvKb6brLLViEy93DAQmqCMI0fogaAv7q93x7+w2Jcj eyGWA0cjZ3acreKGE9Pv =TgO6 -----END PGP SIGNATURE-----

---

Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list

try loading the "hexloader" before accessing these objects, it might help.

Yep, now it loads them all, thanks.

So hmm, seems weird that it doesn't load on its own, but maybe I just wont bother to follow up with all the tech issues. But anyway, I'd like to know if there are any plans to get to a point where we could create these objects without this workaround... is it?

So, getting back to the objects. From the 10 objects I pointed out (here below)

[!-], [!-~], [!/], [!/~], [>~], [>=~], [<~], [<=~], [!=~] and [==~]

We do have in fact only 3 in zexy (<~, >~, ==~), but their behaviour wouldn't count as proper max cloning, cause when you put a number argument in it, it only takes number data into the second inlet, while in Max it still allows an audio signal to come through.

I think it's important to avoid redundancies, but I guess you can't avoid it if one is doing exact max clones of these 3 and the other 7 objects.

I made one abstraction here for [>=~], find it attached. It works fine here in my computer even though it contains "weird and problematic" characters in its name.

It doesn't work exactly like the max version though, cause that one works with a number argument that is ignored whenever there's a signal coming through (even if it is "0"). In order to do it like that, I guess you have to compile it as an object. For that matter, I started another thread, please check.

thanks

PS: 0.42.5? wasn't that released 5 years ago, and superceded 2 years ago by 0.43.4?

PS response: Yeah, but I never adapted to 0.43.4, I felt it was buggy in a few ways. By the way, one of the issues was that many of my patches didn't work because of the [poltocar~] and [cartopol~] bug/problem I pointed out in this thread about maintaining cyclone. Moreover, I have a quite dense tutorial with over 200 examples now, and many of them used [cartopol~]... other patches wouldn't work for other reasons.

I was expecting newer releases to fix this and other issues, but the development stopped and died completely... so...

it seems that Pd has a revolutionary fast development cycle

yeah, I beg to differ :)

2015-02-24 12:11 GMT-03:00 IOhannes m zmoelnig zmoelnig@iem.at:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256

On 2015-02-24 15:50, Alexandre Torres Porres wrote:

...

...

&&~, ||~, <~, >~, ==~

none of these are created in extended 0.42-5, were they added only in the latest version?

no. zexy ships these objects for about 10 years or so (maybe longer).

there has been endless discussion about

• • object names containing special characters (like '|')
• • splitting multi-object libraries (like zexy) into single-object

binaries

both are most likely related to your problems. please check the archives on those issues (and let's not repeat themover).

try loading the "hexloader" before accessing these objects, it might help.

fgmasdr IOhannes

PS: 0.42.5? wasn't that released 5 years ago, and superceded 2 years ago by 0.43.4? finally, it seems that Pd has a revolutionary fast development cycle - at least compared to inertia of its users :-) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1

iQIcBAEBCAAGBQJU7JS6AAoJELZQGcR/ejb46ycP/j8hb/ak6TAAL2K/jXMFE/rW gSq8PiQqW7yo4+M1aUK9+sb/hnPBoC80OVjRBOlPou9ktH2z1/ioT+DCM+UQzXeb IvhF2ykmWU5s6morwEbZ2FtURNiB8KUSL919noKZGpZpxjFWo5GVch5h6YFTl7zm 8Xzia/7Gq5mR9XMVHwooPySY5qaGSUDCnXEWKmeBmnH3Pj77lovdzWOAN9jt8cUa SoPJEQuJyTF/nPlO/j6sA9DN0xU6crHK3wQL62cnwKKeviAW4b5toOWmMdJf6xXg i9059mhA/z1vD2IUcsbYJOokoNYxVI9S7P15NaY6Wf20wSPkyAkqOt7Cb8VMkVv/ G36SmSN00KL8Mdtu6a/68EhuHRk0fwwEc/alk3zTb1/hlXidmBiuHFzR+P+DklA3 Z0uhgGeSl2EL986ES/TQLKxibkVs3nTOpQ5R2shyXHoN7jS/wYdhcQaCdjx84s6U LHjxtpCpo8MHeKRMo6xq2Pduf6rmZNiKCzohqqtcZ1AY5bVAd1eZGY2CpQr7X1/C J8pkWXjNb38/J416Ix7Jo6M17NUaLoGlDogKx+BRFvTh3k8+M0zjBYAv8iW8ptGK GQ/JhPdBPZ+HBcUq+zxMdibUogf39Pxp5xhXpKJWfR/S3ZLIR+QeGEkYD535XaTj Lq7wpExpmCa5DnEnTumj =+wzf -----END PGP SIGNATURE-----

---

Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list

"*I made one abstraction here for [>=~], find it attached. It works fine here in my computer **even though it contains "weird and problematic" characters in its name.*"

Ha, it doesn't work at all with [!/], but it does with [!-]

2015-02-24 15:43 GMT-03:00 Alexandre Torres Porres porres@gmail.com:

Another option is that we could just keep this somewhat different behaviour that's also in the zexy objects, and just add the other 7. Those extra 7 could be in cyclone or maybe even in zexy, but that's up to the maintainers.

I would really like to collaborate though. I've been meaning to start coding objects for a while, and this seems like a good motivation to start doing it.

cheers

2015-02-24 14:35 GMT-03:00 Alexandre Torres Porres porres@gmail.com:

...

try loading the "hexloader" before accessing these objects, it might help.

Yep, now it loads them all, thanks.

So hmm, seems weird that it doesn't load on its own, but maybe I just wont bother to follow up with all the tech issues. But anyway, I'd like to know if there are any plans to get to a point where we could create these objects without this workaround... is it?

So, getting back to the objects. From the 10 objects I pointed out (here below)

[!-], [!-~], [!/], [!/~], [>~], [>=~], [<~], [<=~], [!=~] and [==~]

We do have in fact only 3 in zexy (<~, >~, ==~), but their behaviour wouldn't count as proper max cloning, cause when you put a number argument in it, it only takes number data into the second inlet, while in Max it still allows an audio signal to come through.

I think it's important to avoid redundancies, but I guess you can't avoid it if one is doing exact max clones of these 3 and the other 7 objects.

I made one abstraction here for [>=~], find it attached. It works fine here in my computer even though it contains "weird and problematic" characters in its name.

It doesn't work exactly like the max version though, cause that one works with a number argument that is ignored whenever there's a signal coming through (even if it is "0"). In order to do it like that, I guess you have to compile it as an object. For that matter, I started another thread, please check.

thanks

...

PS: 0.42.5? wasn't that released 5 years ago, and superceded 2 years ago by 0.43.4?

PS response: Yeah, but I never adapted to 0.43.4, I felt it was buggy in a few ways. By the way, one of the issues was that many of my patches didn't work because of the [poltocar~] and [cartopol~] bug/problem I pointed out in this thread about maintaining cyclone. Moreover, I have a quite dense tutorial with over 200 examples now, and many of them used [cartopol~]... other patches wouldn't work for other reasons.

I was expecting newer releases to fix this and other issues, but the development stopped and died completely... so...

...

it seems that Pd has a revolutionary fast development cycle

yeah, I beg to differ :)

2015-02-24 12:11 GMT-03:00 IOhannes m zmoelnig zmoelnig@iem.at:

-----BEGIN PGP SIGNED MESSAGE-----

...

Hash: SHA256

On 2015-02-24 15:50, Alexandre Torres Porres wrote:

...

...

&&~, ||~, <~, >~, ==~

none of these are created in extended 0.42-5, were they added only in the latest version?

no. zexy ships these objects for about 10 years or so (maybe longer).

there has been endless discussion about

• • object names containing special characters (like '|')
• • splitting multi-object libraries (like zexy) into single-object

binaries

both are most likely related to your problems. please check the archives on those issues (and let's not repeat themover).

try loading the "hexloader" before accessing these objects, it might help.

fgmasdr IOhannes

PS: 0.42.5? wasn't that released 5 years ago, and superceded 2 years ago by 0.43.4? finally, it seems that Pd has a revolutionary fast development cycle - at least compared to inertia of its users :-) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1

iQIcBAEBCAAGBQJU7JS6AAoJELZQGcR/ejb46ycP/j8hb/ak6TAAL2K/jXMFE/rW gSq8PiQqW7yo4+M1aUK9+sb/hnPBoC80OVjRBOlPou9ktH2z1/ioT+DCM+UQzXeb IvhF2ykmWU5s6morwEbZ2FtURNiB8KUSL919noKZGpZpxjFWo5GVch5h6YFTl7zm 8Xzia/7Gq5mR9XMVHwooPySY5qaGSUDCnXEWKmeBmnH3Pj77lovdzWOAN9jt8cUa SoPJEQuJyTF/nPlO/j6sA9DN0xU6crHK3wQL62cnwKKeviAW4b5toOWmMdJf6xXg i9059mhA/z1vD2IUcsbYJOokoNYxVI9S7P15NaY6Wf20wSPkyAkqOt7Cb8VMkVv/ G36SmSN00KL8Mdtu6a/68EhuHRk0fwwEc/alk3zTb1/hlXidmBiuHFzR+P+DklA3 Z0uhgGeSl2EL986ES/TQLKxibkVs3nTOpQ5R2shyXHoN7jS/wYdhcQaCdjx84s6U LHjxtpCpo8MHeKRMo6xq2Pduf6rmZNiKCzohqqtcZ1AY5bVAd1eZGY2CpQr7X1/C J8pkWXjNb38/J416Ix7Jo6M17NUaLoGlDogKx+BRFvTh3k8+M0zjBYAv8iW8ptGK GQ/JhPdBPZ+HBcUq+zxMdibUogf39Pxp5xhXpKJWfR/S3ZLIR+QeGEkYD535XaTj Lq7wpExpmCa5DnEnTumj =+wzf -----END PGP SIGNATURE-----

---

Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list

I did some of those in Pd-extended as I had the same trouble with weird characters in object names; try mrpeach/op~

Martin

On Tue, Feb 24, 2015 at 1:51 PM, Alexandre Torres Porres porres@gmail.com wrote:

"*I made one abstraction here for [>=~], find it attached. It works fine here in my computer **even though it contains "weird and problematic" characters in its name.*"

Ha, it doesn't work at all with [!/], but it does with [!-]

2015-02-24 15:43 GMT-03:00 Alexandre Torres Porres porres@gmail.com:

Another option is that we could just keep this somewhat different

...

behaviour that's also in the zexy objects, and just add the other 7. Those extra 7 could be in cyclone or maybe even in zexy, but that's up to the maintainers.

I would really like to collaborate though. I've been meaning to start coding objects for a while, and this seems like a good motivation to start doing it.

cheers

2015-02-24 14:35 GMT-03:00 Alexandre Torres Porres porres@gmail.com:

...

try loading the "hexloader" before accessing these objects, it might help.

Yep, now it loads them all, thanks.

So hmm, seems weird that it doesn't load on its own, but maybe I just wont bother to follow up with all the tech issues. But anyway, I'd like to know if there are any plans to get to a point where we could create these objects without this workaround... is it?

So, getting back to the objects. From the 10 objects I pointed out (here below)

[!-], [!-~], [!/], [!/~], [>~], [>=~], [<~], [<=~], [!=~] and [==~]

We do have in fact only 3 in zexy (<~, >~, ==~), but their behaviour wouldn't count as proper max cloning, cause when you put a number argument in it, it only takes number data into the second inlet, while in Max it still allows an audio signal to come through.

I think it's important to avoid redundancies, but I guess you can't avoid it if one is doing exact max clones of these 3 and the other 7 objects.

I made one abstraction here for [>=~], find it attached. It works fine here in my computer even though it contains "weird and problematic" characters in its name.

It doesn't work exactly like the max version though, cause that one works with a number argument that is ignored whenever there's a signal coming through (even if it is "0"). In order to do it like that, I guess you have to compile it as an object. For that matter, I started another thread, please check.

thanks

...

PS: 0.42.5? wasn't that released 5 years ago, and superceded 2 years ago by 0.43.4?

PS response: Yeah, but I never adapted to 0.43.4, I felt it was buggy in a few ways. By the way, one of the issues was that many of my patches didn't work because of the [poltocar~] and [cartopol~] bug/problem I pointed out in this thread about maintaining cyclone. Moreover, I have a quite dense tutorial with over 200 examples now, and many of them used [cartopol~]... other patches wouldn't work for other reasons.

I was expecting newer releases to fix this and other issues, but the development stopped and died completely... so...

...

it seems that Pd has a revolutionary fast development cycle

yeah, I beg to differ :)

2015-02-24 12:11 GMT-03:00 IOhannes m zmoelnig zmoelnig@iem.at:

-----BEGIN PGP SIGNED MESSAGE-----

...

Hash: SHA256

On 2015-02-24 15:50, Alexandre Torres Porres wrote:

...

...

&&~, ||~, <~, >~, ==~

none of these are created in extended 0.42-5, were they added only in the latest version?

no. zexy ships these objects for about 10 years or so (maybe longer).

there has been endless discussion about

• • object names containing special characters (like '|')
• • splitting multi-object libraries (like zexy) into single-object

binaries

both are most likely related to your problems. please check the archives on those issues (and let's not repeat themover).

try loading the "hexloader" before accessing these objects, it might help.

fgmasdr IOhannes

PS: 0.42.5? wasn't that released 5 years ago, and superceded 2 years ago by 0.43.4? finally, it seems that Pd has a revolutionary fast development cycle - at least compared to inertia of its users :-) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1

iQIcBAEBCAAGBQJU7JS6AAoJELZQGcR/ejb46ycP/j8hb/ak6TAAL2K/jXMFE/rW gSq8PiQqW7yo4+M1aUK9+sb/hnPBoC80OVjRBOlPou9ktH2z1/ioT+DCM+UQzXeb IvhF2ykmWU5s6morwEbZ2FtURNiB8KUSL919noKZGpZpxjFWo5GVch5h6YFTl7zm 8Xzia/7Gq5mR9XMVHwooPySY5qaGSUDCnXEWKmeBmnH3Pj77lovdzWOAN9jt8cUa SoPJEQuJyTF/nPlO/j6sA9DN0xU6crHK3wQL62cnwKKeviAW4b5toOWmMdJf6xXg i9059mhA/z1vD2IUcsbYJOokoNYxVI9S7P15NaY6Wf20wSPkyAkqOt7Cb8VMkVv/ G36SmSN00KL8Mdtu6a/68EhuHRk0fwwEc/alk3zTb1/hlXidmBiuHFzR+P+DklA3 Z0uhgGeSl2EL986ES/TQLKxibkVs3nTOpQ5R2shyXHoN7jS/wYdhcQaCdjx84s6U LHjxtpCpo8MHeKRMo6xq2Pduf6rmZNiKCzohqqtcZ1AY5bVAd1eZGY2CpQr7X1/C J8pkWXjNb38/J416Ix7Jo6M17NUaLoGlDogKx+BRFvTh3k8+M0zjBYAv8iW8ptGK GQ/JhPdBPZ+HBcUq+zxMdibUogf39Pxp5xhXpKJWfR/S3ZLIR+QeGEkYD535XaTj Lq7wpExpmCa5DnEnTumj =+wzf -----END PGP SIGNATURE-----

---

Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list

---

Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list

Hi, I have a question about upper case letters in the begining of some objects like [Uzi] and [Scope~] in cyclone. Why is that? In Pd it does make a difference by the way, not in Max.

Anyway, if one would change that, old patches would need to be updated as well, which is a bummer, but even so I think it's preferable not to deal with knowing which objects need the upper case or not, and for no apparent particular reason. One way or another, I wonder why it happened, anyone?

cheers

2015-02-24 16:41 GMT-03:00 Alexandre Torres Porres porres@gmail.com:

Cool.

One way or another, I just use expr~ whener I need these things anyway. But it might be convenient to have these objects, and I just feel like start coding somewhere, and this seems like an easy task. So the idea of having these exact proper clones of the max objects felt good to me. But it I confess it might be just too silly for anyone to really bother, and it's more related to my will to start coding.

The thing is that this characters issue might just ruin or everything in the end... or make it more complicated than I thought, so... bummer...

By the way, my abstractions wouldn't be exact clones of the max objects, cause they don't even take arguments (like yours don't also).

I can at least work on getting a code version of teeth~

cheers

2015-02-24 16:16 GMT-03:00 Martin Peach chakekatzil@gmail.com:

I did some of those in Pd-extended as I had the same trouble with weird

...

characters in object names; try mrpeach/op~

Martin

On Tue, Feb 24, 2015 at 1:51 PM, Alexandre Torres Porres < porres@gmail.com> wrote:

...

"*I made one abstraction here for [>=~], find it attached. It works fine here in my computer **even though it contains "weird and problematic" characters in its name.*"

Ha, it doesn't work at all with [!/], but it does with [!-]

2015-02-24 15:43 GMT-03:00 Alexandre Torres Porres porres@gmail.com:

Another option is that we could just keep this somewhat different

...

behaviour that's also in the zexy objects, and just add the other 7. Those extra 7 could be in cyclone or maybe even in zexy, but that's up to the maintainers.

I would really like to collaborate though. I've been meaning to start coding objects for a while, and this seems like a good motivation to start doing it.

cheers

2015-02-24 14:35 GMT-03:00 Alexandre Torres Porres porres@gmail.com:

...

try loading the "hexloader" before accessing these objects, it might help.

Yep, now it loads them all, thanks.

So hmm, seems weird that it doesn't load on its own, but maybe I just wont bother to follow up with all the tech issues. But anyway, I'd like to know if there are any plans to get to a point where we could create these objects without this workaround... is it?

So, getting back to the objects. From the 10 objects I pointed out (here below)

[!-], [!-~], [!/], [!/~], [>~], [>=~], [<~], [<=~], [!=~] and [==~]

We do have in fact only 3 in zexy (<~, >~, ==~), but their behaviour wouldn't count as proper max cloning, cause when you put a number argument in it, it only takes number data into the second inlet, while in Max it still allows an audio signal to come through.

I think it's important to avoid redundancies, but I guess you can't avoid it if one is doing exact max clones of these 3 and the other 7 objects.

I made one abstraction here for [>=~], find it attached. It works fine here in my computer even though it contains "weird and problematic" characters in its name.

It doesn't work exactly like the max version though, cause that one works with a number argument that is ignored whenever there's a signal coming through (even if it is "0"). In order to do it like that, I guess you have to compile it as an object. For that matter, I started another thread, please check.

thanks

...

PS: 0.42.5? wasn't that released 5 years ago, and superceded 2 years ago by 0.43.4?

PS response: Yeah, but I never adapted to 0.43.4, I felt it was buggy in a few ways. By the way, one of the issues was that many of my patches didn't work because of the [poltocar~] and [cartopol~] bug/problem I pointed out in this thread about maintaining cyclone. Moreover, I have a quite dense tutorial with over 200 examples now, and many of them used [cartopol~]... other patches wouldn't work for other reasons.

I was expecting newer releases to fix this and other issues, but the development stopped and died completely... so...

...

it seems that Pd has a revolutionary fast development cycle

yeah, I beg to differ :)

2015-02-24 12:11 GMT-03:00 IOhannes m zmoelnig zmoelnig@iem.at:

-----BEGIN PGP SIGNED MESSAGE-----

...

Hash: SHA256

On 2015-02-24 15:50, Alexandre Torres Porres wrote: >> &&~, ||~, <~, >~, ==~ > > none of these are created in extended 0.42-5, were they added only > in the latest version?

no. zexy ships these objects for about 10 years or so (maybe longer).

there has been endless discussion about

• • object names containing special characters (like '|')
• • splitting multi-object libraries (like zexy) into single-object

binaries

both are most likely related to your problems. please check the archives on those issues (and let's not repeat themover).

try loading the "hexloader" before accessing these objects, it might help.

fgmasdr IOhannes

PS: 0.42.5? wasn't that released 5 years ago, and superceded 2 years ago by 0.43.4? finally, it seems that Pd has a revolutionary fast development cycle - at least compared to inertia of its users :-) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1

iQIcBAEBCAAGBQJU7JS6AAoJELZQGcR/ejb46ycP/j8hb/ak6TAAL2K/jXMFE/rW gSq8PiQqW7yo4+M1aUK9+sb/hnPBoC80OVjRBOlPou9ktH2z1/ioT+DCM+UQzXeb IvhF2ykmWU5s6morwEbZ2FtURNiB8KUSL919noKZGpZpxjFWo5GVch5h6YFTl7zm 8Xzia/7Gq5mR9XMVHwooPySY5qaGSUDCnXEWKmeBmnH3Pj77lovdzWOAN9jt8cUa SoPJEQuJyTF/nPlO/j6sA9DN0xU6crHK3wQL62cnwKKeviAW4b5toOWmMdJf6xXg i9059mhA/z1vD2IUcsbYJOokoNYxVI9S7P15NaY6Wf20wSPkyAkqOt7Cb8VMkVv/ G36SmSN00KL8Mdtu6a/68EhuHRk0fwwEc/alk3zTb1/hlXidmBiuHFzR+P+DklA3 Z0uhgGeSl2EL986ES/TQLKxibkVs3nTOpQ5R2shyXHoN7jS/wYdhcQaCdjx84s6U LHjxtpCpo8MHeKRMo6xq2Pduf6rmZNiKCzohqqtcZ1AY5bVAd1eZGY2CpQr7X1/C J8pkWXjNb38/J416Ix7Jo6M17NUaLoGlDogKx+BRFvTh3k8+M0zjBYAv8iW8ptGK GQ/JhPdBPZ+HBcUq+zxMdibUogf39Pxp5xhXpKJWfR/S3ZLIR+QeGEkYD535XaTj Lq7wpExpmCa5DnEnTumj =+wzf -----END PGP SIGNATURE-----

---

Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list

---

Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list

It was this thread at the PD-dev list:

[PD-dev] cyclone and uppercase http://lists.puredata.info/pipermail/pd-dev/2009-03/013146.html

Fred Jan

On 2015-03-05 06:18 PM, Alexandre Torres Porres wrote:

Hi, I have a question about upper case letters in the begining of some objects like [Uzi] and [Scope~] in cyclone. Why is that? In Pd it does make a difference by the way, not in Max.

Anyway, if one would change that, old patches would need to be updated as well, which is a bummer, but even so I think it's preferable not to deal with knowing which objects need the upper case or not, and for no apparent particular reason. One way or another, I wonder why it happened, anyone?

cheers

Hi Alexandre, pd-list,

These are the objects: Append, Borax, Bucket, Clip, Decode, Histo, MouseState, Peak, Table, TogEdge, Through, Uzi, Clip~, Line~, Scope~, Snapshot~.

It appears Hans already implemented lowercase object names for all but Table, and a lowercase version with "cyclone/" prefixed for most (append and Table being the exception).

Fred Jan

On 2015-03-05 08:46 PM, Alexandre Torres Porres wrote:

Hey, yeah, didn't think of adding aliases , that solves the issue and maintains backwards compatibility with old patches. I hope it gets done.

cheers

2015-03-05 15:38 GMT-03:00 Fred Jan Kraan <fjkraan@xs4all.nl mailto:fjkraan@xs4all.nl>:

It was this thread at the PD-dev list:

[PD-dev] cyclone and uppercase
http://lists.puredata.info/pipermail/pd-dev/2009-03/013146.html

Fred Jan

On 2015-03-05 06:18 PM, Alexandre Torres Porres wrote:
> Hi, I have a question about upper case letters in the begining of some
> objects like [Uzi] and [Scope~] in cyclone. Why is that? In Pd it does
> make a difference by the way, not in Max.
>
> Anyway, if one would change that, old patches would need to be updated
> as well, which is a bummer, but even so I think it's preferable not to
> deal with knowing which objects need the upper case or not, and for no
> apparent particular reason. One way or another, I wonder why it
> happened, anyone?
>
> cheers

Ok, downloaded Pd Extended 0.43 and now I see that [uzi] loads the cyclone version of Uzi and etc...

"*It was this thread at the PD-dev list:*

*[PD-dev] cyclone and uppercasehttp://lists.puredata.info/pipermail/pd-dev/2009-03/013146.html http://lists.puredata.info/pipermail/pd-dev/2009-03/013146.html *"

Nice, I followed the thread and agree with hans, it makes sense that it loads that way, but I do add my point where it's a bit of a hassle to remember which objects have uppercase or not.

cheers

2015-03-05 18:20 GMT-03:00 Alexandre Torres Porres porres@gmail.com:

Does it mean we're supposed to be able to load objects as lower case names somehow? Cause I don't seem to be able to do it anyhow. Hints please?

thanks

2015-03-05 17:34 GMT-03:00 Fred Jan Kraan fjkraan@xs4all.nl:

Hi Alexandre, pd-list,

...

These are the objects: Append, Borax, Bucket, Clip, Decode, Histo, MouseState, Peak, Table, TogEdge, Through, Uzi, Clip~, Line~, Scope~, Snapshot~.

It appears Hans already implemented lowercase object names for all but Table, and a lowercase version with "cyclone/" prefixed for most (append and Table being the exception).

Fred Jan

On 2015-03-05 08:46 PM, Alexandre Torres Porres wrote:

...

Hey, yeah, didn't think of adding aliases , that solves the issue and maintains backwards compatibility with old patches. I hope it gets done.

cheers

2015-03-05 15:38 GMT-03:00 Fred Jan Kraan <fjkraan@xs4all.nl mailto:fjkraan@xs4all.nl>:

It was this thread at the PD-dev list:

[PD-dev] cyclone and uppercase
http://lists.puredata.info/pipermail/pd-dev/2009-03/013146.html

Fred Jan

On 2015-03-05 06:18 PM, Alexandre Torres Porres wrote:
> Hi, I have a question about upper case letters in the begining of

some

...

> objects like [Uzi] and [Scope~] in cyclone. Why is that? In Pd it

does

...

> make a difference by the way, not in Max.
>
> Anyway, if one would change that, old patches would need to be

updated

...

> as well, which is a bummer, but even so I think it's preferable

not to

...

> deal with knowing which objects need the upper case or not, and

for no

...

> apparent particular reason. One way or another, I wonder why it
> happened, anyone?
>
> cheers

for instance, it says "Symbol argument sets name of table to play from. Additional int argument after that sets sample offset into the table (default 0)"

well, I put an int argument after that, and it doesn't really work at all!

2015-05-24 23:05 GMT-03:00 Alexandre Torres Porres porres@gmail.com:

hi fred, how's it going? I was checking [cycle~] and it seems it's not behaving much closely like in max, have you checked that? I'm saying more about its behaviour as a wavetable, where it can offsett the table and everything.

I can't find that list of bugs you were working on, where is it? How is it anyway?

thanks cheers

2015-01-23 14:25 GMT-02:00 Fred Jan Kraan fjkraan@xs4all.nl:

Hi All,

...

At http://fjkraan.home.xs4all.nl/digaud/puredata/cyclone/index.html a new set of revised help-patches for the cyclone library are available. Most previous remarks are applied.

There are now previews of the Windows binaries and MacOSX. The latter is build on MacOSX 10.5 with XCode 3.14, so should have executables for PPC, i386 and i386_64. I confirmed the last two are working (10.5 and 10.8).

It remains in progress, in the task list are the fixed and remaining issues.

Fred Jan

---

Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list

please do not consider my previous message, I clearly had no idea what I was talking about and was just really confused :) sorry

2015-05-26 18:12 GMT-03:00 Alexandre Torres Porres porres@gmail.com:

By the way, [sah~] in Pd has the inlets switched. In max, the left one is supposed to trigger the sample and hold, unlike [samphold~] in Pd. But [sah~] is just like [samphold~]. In order for it to be a proper clone of max, that'd need to be corrected, not sure if it happened already.

2015-05-24 23:18 GMT-03:00 Alexandre Torres Porres porres@gmail.com:

...

for instance, it says "Symbol argument sets name of table to play from. Additional int argument after that sets sample offset into the table (default 0)"

well, I put an int argument after that, and it doesn't really work at all!

2015-05-24 23:05 GMT-03:00 Alexandre Torres Porres porres@gmail.com:

hi fred, how's it going? I was checking [cycle~] and it seems it's not

...

behaving much closely like in max, have you checked that? I'm saying more about its behaviour as a wavetable, where it can offsett the table and everything.

I can't find that list of bugs you were working on, where is it? How is it anyway?

thanks cheers

2015-01-23 14:25 GMT-02:00 Fred Jan Kraan fjkraan@xs4all.nl:

Hi All,

...

At http://fjkraan.home.xs4all.nl/digaud/puredata/cyclone/index.html a new set of revised help-patches for the cyclone library are available. Most previous remarks are applied.

There are now previews of the Windows binaries and MacOSX. The latter is build on MacOSX 10.5 with XCode 3.14, so should have executables for PPC, i386 and i386_64. I confirmed the last two are working (10.5 and 10.8).

It remains in progress, in the task list are the fixed and remaining issues.

Fred Jan

---

Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list

The concept of hot and cold inlets appears to apply to messages, not signals

Surely, it's not that what confused me. Actually Max did confuse me I guess, I thought I found a different behavior in [sah~] over there. But I actually hadn't understood how it worked. Sorry... it all makes sense now and [sah~] is indeed working in the same way!

Anyway, like I asked before, I can't find that list of bugs you were working on, where is it?

Did you see what I mentioned about [cycle~]?

Now, since the maintenance of Extended seems to be dead, I guess the point of updating cyclone is to make it available for download. I've always had the idea it was available for download somewhere, but it isn't. There's the download version from the package that was out in 0.42 extended in puredata.info and that's it.

So, where's that page with the bug list that you were working on? I'd like to check it out.

And when do you think we could have it for download in the puredata.info site (or somewhere else as well)?

Can I get the package as it is now and test it?

thanks

2015-06-05 3:29 GMT-03:00 Fred Jan Kraan fjkraan@xs4all.nl:

Hi Alexandre,

Sorry, I had missed your message, most active Pd-time had gone into helping to improve the build system for cyclone and pd-externals in general.

The concept of hot and cold inlets appears to apply to messages, not signals. Sah~ appears to work as described in the Max5 documentation. I'll improve the help-patch.

Consider it a good thing Pd can confuse you. It would get boring if it didn't :-).

Greetings,

Fred Jan

On 2015-06-05 03:42 AM, Alexandre Torres Porres wrote:

...

please do not consider my previous message, I clearly had no idea what I was talking about and was just really confused :) sorry

2015-05-26 18:12 GMT-03:00 Alexandre Torres Porres <porres@gmail.com mailto:porres@gmail.com>:

By the way, [sah~] in Pd has the inlets switched. In max, the left
one is supposed to trigger the sample and hold, unlike [samphold~]
in Pd. But [sah~] is just like [samphold~]. In order for it to be a
proper clone of max, that'd need to be corrected, not sure if it
happened already.

2015-05-24 23:18 GMT-03:00 Alexandre Torres Porres <porres@gmail.com
<mailto:porres@gmail.com>>:

    for instance, it says "Symbol argument sets name of table to
    play from. Additional int argument after that sets sample offset
    into the table (default 0)"

    well, I put an int argument after that, and it doesn't really
    work at all!

    2015-05-24 23:05 GMT-03:00 Alexandre Torres Porres
    <porres@gmail.com <mailto:porres@gmail.com>>:

        hi fred, how's it going? I was checking [cycle~] and it
        seems it's not behaving much closely like in max, have you
        checked that? I'm saying more about its behaviour as a
        wavetable, where it can offsett the table and everything.

        I can't find that list of bugs you were working on, where is
        it? How is it anyway?

        thanks
        cheers

        2015-01-23 14:25 GMT-02:00 Fred Jan Kraan <fjkraan@xs4all.nl
        <mailto:fjkraan@xs4all.nl>>:

            Hi All,

            At

http://fjkraan.home.xs4all.nl/digaud/puredata/cyclone/index.html

...

            a new set of revised help-patches for the cyclone
            library are available. Most previous remarks are applied.

            There are now previews of the Windows binaries and
            MacOSX. The latter is build on MacOSX 10.5 with XCode
            3.14, so should have executables for PPC, i386 and
            i386_64. I confirmed the last two are working (10.5 and
            10.8).

            It remains in progress, in the task list are the fixed
            and remaining issues.

            Fred Jan

            _______________________________________________
            Pd-list@lists.iem.at <mailto:Pd-list@lists.iem.at>
            mailing list
            UNSUBSCRIBE and account-management ->
            http://lists.puredata.info/listinfo/pd-list

On Fre, 2015-06-05 at 17:34 -0300, Alexandre Torres Porres wrote:

I'm voting for a new [scale] and [scale~] object in cyclone, the second is missing completely in extended, the first is around, but in different versions, like [maxlib/scale], which has a log option, and is actually buggy, and the [expr_scale], which is just an expr abstraction. Seems like very simple externals to make and I could go ahead and code them. I think they'd be really useful.

Why do you need them as externals? Those are simply less portable (at least they need recompiling when switching platforms) and they require only very few vanilla objects as abstractions. I don't think this is an example where you gain much performance when implemented as an external. Why not build yourself abstractions?

For example, [scale~] would be essential to adjust the amplitude range from LFOs to control your patches. the [scale] would be good for adjusting MIDI input.

This was exactly the use case I had in mind when writing [rh_scalelog~] and [rh_scalelin~]. Assuming that sources (i.e. LFOs, ADSRs, oscillators,...) are using a standardized range (0-1), I didn't see a need for input scaling.

Roman

Hi Alexandre,

I checked the cycle~ behaviour against the Max5 doc, and it appears to work as described. Only clicking to view the current buffer contents is not implemented (yet). The offset can be set as argument and it works. The second inlet controls the phase, which amounts to more or less the same.

Can you indicate what the differences are?

Greetings,

Fred Jan

On 2015-05-25 04:05 AM, Alexandre Torres Porres wrote:

hi fred, how's it going? I was checking [cycle~] and it seems it's not behaving much closely like in max, have you checked that? I'm saying more about its behaviour as a wavetable, where it can offsett the table and everything.

I can't find that list of bugs you were working on, where is it? How is it anyway?

thanks cheers

2015-01-23 14:25 GMT-02:00 Fred Jan Kraan <fjkraan@xs4all.nl mailto:fjkraan@xs4all.nl>:

Hi All,

At http://fjkraan.home.xs4all.nl/digaud/puredata/cyclone/index.html
a new set of revised help-patches for the cyclone library are
available. Most previous remarks are applied.

There are now previews of the Windows binaries and MacOSX. The
latter is build on MacOSX 10.5 with XCode 3.14, so should have
executables for PPC, i386 and i386_64. I confirmed the last two are
working (10.5 and 10.8).

It remains in progress, in the task list are the fixed and remaining
issues.

Fred Jan

_______________________________________________
Pd-list@lists.iem.at <mailto:Pd-list@lists.iem.at> mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list

Hi Alexandre,

...

The offset can be set as argument and it works

I can't seem to make it work, how do you do it? can you send me a patch?

Here two patches. cycle~-test1.pd demonstrates the phase control using the internal buffer. I do not quite understand if and how the offset relates to the phase, but mixing two signals with a variable phase displays addition and elimination. cycle~-test2.pd should demonstrate the same with an external buffer~, but not having that I used an array. This doesn't do what I expect. I will do some more investigation on what it does.

It seems [cycle~] will only work with tables that are 512 in size. It can be of any size in max now, but the help of Max 7 says: "This wavetable may be of any size, _/*but historically was limited to 512 samples*/_." So maybe when [cyclone/cycle~] was made it was limited to 512... anyway, this size limitation was something I also raised here.

To keep maintenance to cyclone reasonable, I try to limit it to the functionality of Max 5. The documentation for Max 5 is conveniently online and I have a installation available for comparison. So Max 7 functionality is out of scope for me.

More details, in max you can set [cycle~] with other messages to control the buffer size and offset, check attached image.

The buffer_sizeinsamps and buffer_offset attributes appear to be newer than Max 5. The sample-offset argument should work however.

cheers

Greetings,

Fred Jan

2015-06-07 17:08 GMT-03:00 Fred Jan Kraan <fjkraan@xs4all.nl mailto:fjkraan@xs4all.nl>:

Hi Alexandre,

I checked the cycle~ behaviour against the Max5 doc, and it appears to
work as described. Only clicking to view the current buffer contents is
not implemented (yet). The offset can be set as argument and it works.
The second inlet controls the phase, which amounts to more or less
the same.

Can you indicate what the differences are?

Greetings,

Fred Jan

On 2015-05-25 04:05 AM, Alexandre Torres Porres wrote:
> hi fred, how's it going? I was checking [cycle~] and it seems it's not
> behaving much closely like in max, have you checked that? I'm saying
> more about its behaviour as a wavetable, where it can offsett the
table
> and everything.
>
> I can't find that list of bugs you were working on, where is it?
How is
> it anyway?
>
> thanks
> cheers
>
> 2015-01-23 14:25 GMT-02:00 Fred Jan Kraan <fjkraan@xs4all.nl
<mailto:fjkraan@xs4all.nl>
> <mailto:fjkraan@xs4all.nl <mailto:fjkraan@xs4all.nl>>>:
>
>     Hi All,
>
>     At
http://fjkraan.home.xs4all.nl/digaud/puredata/cyclone/index.html
>     a new set of revised help-patches for the cyclone library are
>     available. Most previous remarks are applied.
>
>     There are now previews of the Windows binaries and MacOSX. The
>     latter is build on MacOSX 10.5 with XCode 3.14, so should have
>     executables for PPC, i386 and i386_64. I confirmed the last
two are
>     working (10.5 and 10.8).
>
>     It remains in progress, in the task list are the fixed and
remaining
>     issues.
>
>     Fred Jan
>
>     _______________________________________________
>     Pd-list@lists.iem.at <mailto:Pd-list@lists.iem.at>
<mailto:Pd-list@lists.iem.at <mailto:Pd-list@lists.iem.at>> mailing list
>     UNSUBSCRIBE and account-management ->
>     http://lists.puredata.info/listinfo/pd-list
>
>

Hi Alexandre,

Since sending the patches, I looked in the code and found a problem that need fixing too (the issue affects funbuff~, peek~ and poke~ too). The offset argument indeed only works with the external buffer.

It seems to be working, apart from the offset. This needs some special handling if you try to read past the external buffer size. This is possible with small buffers or large offsets. But back to the patches: There are three different situations:

• internal cosine table, no offset possible,
• external buffer without offset,
• external buffer with offset.

In all situations the phase can be controlled with the right inlet.

About the sample-offset, I have some problem understanding how it works, and have to change it anyhow to fix the issue (garray_getarraywords related on 64-bit systems). So I try to make it work as I understand it should.

If you have Max, you might try to see what happens in these two situations:

• read from a buffer smaller than 512 bytes,
• read from a 512 byte buffer but with an offset.

Max probably fills the remainder with zeros, or wraps around. The documentation (https://docs.cycling74.com/max5/refpages/msp-ref/cycle~.html or https://docs.cycling74.com/max7/maxobject/cycle~) doesn't say.

Greetings,

Fred Jan

hi there, not sure what you meant, but your patches demonstrate how the offset argument is not working. It's clear to me they're not affecting the object at all in test 1, cause they should cancel out and they don't. And according to the help file of max, the offset argument only works if you give it a buffer name (so I understand it doesn't work for the internal cosine function). And it seems it's supposed to be an int value, meaning the sample/index offset in the table, but it doesn't seem to work as well with given table names.

Are you with me?

cheers

2015-06-08 5:10 GMT-03:00 Fred Jan Kraan <fjkraan@xs4all.nl mailto:fjkraan@xs4all.nl>:

Hi Alexandre,

>> The offset can be set as argument and it works
>
> I can't seem to make it work, how do you do it? can you send me a patch?

Here two patches. cycle~-test1.pd demonstrates the phase control using
the internal buffer. I do not quite understand if and how the offset
relates to the phase, but mixing two signals with a variable phase
displays addition and elimination. cycle~-test2.pd should demonstrate
the same with an external buffer~, but not having that I used an array.
This doesn't do what I expect. I will do some more investigation on what
it does.
>
> It seems [cycle~] will only work with tables that are 512 in size. It
> can be of any size in max now, but  the help of Max 7 says: "This
> wavetable may be of any size, _/*but historically was limited to 512
> samples*/_." So maybe when [cyclone/cycle~] was made it was limited to
> 512... anyway, this size limitation was something I also raised here.

To keep maintenance to cyclone reasonable, I try to limit it to the
functionality of Max 5. The documentation for Max 5 is conveniently
online and I have a  installation available for comparison. So Max 7
functionality is out of scope for me.
>
> More details, in max you can set [cycle~] with other messages to control
> the buffer size and offset, check attached image.

The buffer_sizeinsamps and buffer_offset attributes appear to be newer
than Max 5. The sample-offset argument should work however.
>
> cheers
>
Greetings,

Fred Jan
>
>
>
> 2015-06-07 17:08 GMT-03:00 Fred Jan Kraan <fjkraan@xs4all.nl <mailto:fjkraan@xs4all.nl>
> <mailto:fjkraan@xs4all.nl <mailto:fjkraan@xs4all.nl>>>:
>
>     Hi Alexandre,
>
>     I checked the cycle~ behaviour against the Max5 doc, and it appears to
>     work as described. Only clicking to view the current buffer contents is
>     not implemented (yet). The offset can be set as argument and it works.
>     The second inlet controls the phase, which amounts to more or less
>     the same.
>
>     Can you indicate what the differences are?
>
>     Greetings,
>
>     Fred Jan
>
>     On 2015-05-25 04:05 AM, Alexandre Torres Porres wrote:
>     > hi fred, how's it going? I was checking [cycle~] and it seems it's not
>     > behaving much closely like in max, have you checked that? I'm saying
>     > more about its behaviour as a wavetable, where it can offsett the
>     table
>     > and everything.
>     >
>     > I can't find that list of bugs you were working on, where is it?
>     How is
>     > it anyway?
>     >
>     > thanks
>     > cheers
>     >
>     > 2015-01-23 14:25 GMT-02:00 Fred Jan Kraan <fjkraan@xs4all.nl <mailto:fjkraan@xs4all.nl>
>     <mailto:fjkraan@xs4all.nl <mailto:fjkraan@xs4all.nl>>
>     > <mailto:fjkraan@xs4all.nl <mailto:fjkraan@xs4all.nl>
<mailto:fjkraan@xs4all.nl <mailto:fjkraan@xs4all.nl>>>>:
>     >
>     >     Hi All,
>     >
>     >     At
>     http://fjkraan.home.xs4all.nl/digaud/puredata/cyclone/index.html
>     >     a new set of revised help-patches for the cyclone library are
>     >     available. Most previous remarks are applied.
>     >
>     >     There are now previews of the Windows binaries and MacOSX. The
>     >     latter is build on MacOSX 10.5 with XCode 3.14, so should have
>     >     executables for PPC, i386 and i386_64. I confirmed the last
>     two are
>     >     working (10.5 and 10.8).
>     >
>     >     It remains in progress, in the task list are the fixed and
>     remaining
>     >     issues.
>     >
>     >     Fred Jan
>     >
>     >     _______________________________________________
>     >     Pd-list@lists.iem.at <mailto:Pd-list@lists.iem.at>
<mailto:Pd-list@lists.iem.at <mailto:Pd-list@lists.iem.at>>
>     <mailto:Pd-list@lists.iem.at <mailto:Pd-list@lists.iem.at>
<mailto:Pd-list@lists.iem.at <mailto:Pd-list@lists.iem.at>>> mailing
list
>     >     UNSUBSCRIBE and account-management ->
>     >     http://lists.puredata.info/listinfo/pd-list
>     >
>     >
>
>

If you have Max, you might try to see what happens in these two situations:

• read from a buffer smaller than 512 bytes,
• read from a 512 byte buffer but with an offset.

it's not "bytes", it's just points, really. So, I tested the second thing. About the first, I guess the idea is that it'll fill the rest with zeros. But my test showed that it'll try to do that but it'll generate some "noise", check the attached picture.

About setting the cycle object to change the table name, I see in Max 5 documentation that you can also specify in this message the sample offset.

From what I tried in Pd, this is not working at all, it'll not read from

the table at all.

check the bit in the documentation about it:

*"The word **set, followed by the name of a buffer~ https://docs.cycling74.com/max5/refpages/msp-ref/buffer~.html object, changes the wavetable used by cycle~. The name can optionally be followed by an int specifying the sample offset into the named buffer~ https://docs.cycling74.com/max5/refpages/msp-ref/buffer~.html object's sample memory."*

2015-06-08 18:21 GMT-03:00 Alexandre Torres Porres porres@gmail.com:

by the way, this table was a 256 point table containing the first half cycle of a cosine.

2015-06-08 18:20 GMT-03:00 Alexandre Torres Porres porres@gmail.com:

...

...

If you have Max, you might try to see what happens in these two situations:

• read from a buffer smaller than 512 bytes,
• read from a 512 byte buffer but with an offset.

it's not "bytes", it's just points, really. So, I tested the second thing. About the first, I guess the idea is that it'll fill the rest with zeros. But my test showed that it'll try to do that but it'll generate some "noise", check the attached picture.

Hi Alexandre,

Currently cycle~ works just as you described, with scrolling through a buffer and zeroing the remainder. I also adapted the help patch by including part of your patch.

The fact that I have Max5 doesn't mean I can use it very well. Using arrays/tables/buffers and writing to them is sufficiently different, so I completely fail to see how to do it :-(. Could take ages, which I prefer to use for fixing more issues.

For now I try to fix the other objects affected by the garray_getarraywords issue and then make new zips available. Unless someone reports new bugs :-)

Greetings,

Fred Jan

On 2015-06-09 06:46 AM, Alexandre Torres Porres wrote:

If you have Max, you might try to see what happens in these two
situations:
- read from a buffer smaller than 512 bytes,
- read from a 512 byte buffer but with an offset.
Max probably fills the remainder with zeros, or wraps around.

I had tried the second one, but didn't the first one, and yeah, it zero out the remainder. I did try this one directly with Max 5, btw.

And I also ejoyed Max 5 to try the idea of testing a buffer that's longer than 512 samples but scrolling through the table with the buffer offset message. It works! And I guess it only makes sense to use this in this way. Check attached picture. It's a table with 1024 points being offset by 256 points.

cheers

another report for [rand~], by the way, maybe you should get involved here and mark them as fixed

http://sourceforge.net/p/pure-data/bugs/1177/

2015-06-09 10:12 GMT-03:00 Alexandre Torres Porres porres@gmail.com:

About the sample-offset, I have some problem understanding how it works,

...

and have to change it anyhow to fix the issue (garray_getarraywords related on 64-bit systems).

seems there was a bug report about this :) http://sourceforge.net/p/pure-data/bugs/1180/

So, hey Fred, would you be able to get into sourceforge and close all the bug reports that have already been taken care of?

I'm not sure how to get in it and do it. I guess I should do that to cause I'm aware of a few things that are going on, so if anyone could tell me how to do it, I'd like to try and collaborate.

Moreover, still about [cycle~], I just wanted to make sure it behaves exactly like it says in Max 5 documentation. They descibre how it needs a table with 513 points, and that the 513 needs to be the same as the 1st because of the interpolation (I assume it does a simple linear interpolation then, right?). In the case of a table with 512 points, [cycle~] will add a 513th point that's a copy of the first. Anyway, this is what it says in the documentation and I'd like to check with you if it's working exactly like that as well. Perhaps you could mention that too in the help file.

cheers

2015-06-09 10:46 GMT-03:00 Alexandre Torres Porres porres@gmail.com:

collected all bug reports related to cyclone. It'd be good to commitor close/mark as fixed.

http://sourceforge.net/p/pure-data/bugs/991/

http://sourceforge.net/p/pure-data/bugs/950/

http://sourceforge.net/p/pure-data/bugs/652/

http://sourceforge.net/p/pure-data/bugs/647/

http://sourceforge.net/p/pure-data/bugs/215/

http://sourceforge.net/p/pure-data/bugs/163/

http://sourceforge.net/p/pure-data/bugs/78/

http://sourceforge.net/p/pure-data/bugs/1188/

http://sourceforge.net/p/pure-data/bugs/1186/

http://sourceforge.net/p/pure-data/bugs/1128/ (that was me actually, haha)

2015-06-09 10:15 GMT-03:00 Alexandre Torres Porres porres@gmail.com:

...

another report for [rand~], by the way, maybe you should get involved here and mark them as fixed

http://sourceforge.net/p/pure-data/bugs/1177/

2015-06-09 10:12 GMT-03:00 Alexandre Torres Porres porres@gmail.com:

...

About the sample-offset, I have some problem understanding how it works,

...

and have to change it anyhow to fix the issue (garray_getarraywords related on 64-bit systems).

seems there was a bug report about this :) http://sourceforge.net/p/pure-data/bugs/1180/

---

Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list

"*I do not completely understand the Description of the Max5 cycle~: when*

*should I make the 513th sample the same as the 512th and when should I**use the first? The latest implementation always uses the first.*"

you should never make the 513th the same as the 512th.

The idea is that it operates with a 512 size table, but internally it needs 513 points, where the 513th is for interpolation and needs to be the same as the 1st point.

So, when a user specify a 512 size table, the cycle~ documentation in Max5 says it'll create a 513 points table where the 513th point is the same as the 1st.

This happens cause it is a simple linear interpolation. In Pd we have a 4 point interpolation in objects such as tabread4, so you need the first point to be the same as the last, and also need two extra last points to be the same as the first two points (so you need 3 extra points). The sinesum command for tables will generate these extra points automatically, and tabosc4~ will read these wavetables also in the correct way.

Back to max 5 documentation and cycle~... It also says that if someone is specifying a 513 size table, that they should make sure that the 513th sample is the same as the 1st. Because in this case the object won't do anything and will just get the specified table.

So creating a copy of the 1st sample to be the 513th sample is a behaviour in cycle~ only for given tables that are 512 in size. This is what I was asking you, if it really behaved that way. What do you say?

This makes me believe that when you specify a bigger table, like 1024, and start offsetting it, that it won't do anything to make this interpolation perfect, but it'll consider the "extra" 513th point in the table to be the same as the first. This is not a real problem in the real world, you can't really perceive it...

cheers

2015-06-11 4:09 GMT-03:00 Fred Jan Kraan fjkraan@xs4all.nl:

Hi Alexandre,

...

So, hey Fred, would you be able to get into sourceforge and close all the bug reports that have already been taken care of?

I'm not sure how to get in it and do it. I guess I should do that to cause I'm aware of a few things that are going on, so if anyone could tell me how to do it, I'd like to try and collaborate.

IOhannes changed the policy, so any registered developer can close issues. I already started closing some of which I was reasonable sure they were fixed. Some others, I want to check first.

...

Moreover, still about [cycle~], I just wanted to make sure it behaves exactly like it says in Max 5 documentation. They descibre how it needs a table with 513 points, and that the 513 needs to be the same as the 1st because of the interpolation (I assume it does a simple linear interpolation then, right?). In the case of a table with 512 points, [cycle~] will add a 513th point that's a copy of the first. Anyway, this is what it says in the documentation and I'd like to check with you if it's working exactly like that as well. Perhaps you could mention that too in the help file.

Yesterday, I updated the cyclone binary distributions at http://puredata.info/Members/fjkraan. The simplest way to install the correct one is using the deken-plugin: https://github.com/pure-data/deken. If you use Pd-extended, you have to rename or remove the original cyclone directory, to prevent having two cyclones.

Indeed, simple interpolation is used. From the cycle_perform: *out++ = f1 + frac * (f2 - f1);

I replaced the core of the cycle_gettable, and in case of an external array, the 513th sample is copied from the first.

I do not completely understand the Description of the Max5 cycle~: when should I make the 513th sample the same as the 512th and when should I use the first? The latest implementation always uses the first.

...

cheers

Fred Jan

...

2015-06-09 10:46 GMT-03:00 Alexandre Torres Porres <porres@gmail.com mailto:porres@gmail.com>:

collected all bug reports related to cyclone. It'd be good to
commitor close/mark as fixed.

http://sourceforge.net/p/pure-data/bugs/991/

http://sourceforge.net/p/pure-data/bugs/950/

http://sourceforge.net/p/pure-data/bugs/652/

http://sourceforge.net/p/pure-data/bugs/647/

http://sourceforge.net/p/pure-data/bugs/215/

http://sourceforge.net/p/pure-data/bugs/163/

http://sourceforge.net/p/pure-data/bugs/78/

http://sourceforge.net/p/pure-data/bugs/1188/

http://sourceforge.net/p/pure-data/bugs/1186/

http://sourceforge.net/p/pure-data/bugs/1128/ (that was me actually,
haha)

2015-06-09 10:15 GMT-03:00 Alexandre Torres Porres <porres@gmail.com
<mailto:porres@gmail.com>>:

    another report for [rand~], by the way, maybe you should get
    involved here and mark them as fixed

    http://sourceforge.net/p/pure-data/bugs/1177/



    2015-06-09 10:12 GMT-03:00 Alexandre Torres Porres
    <porres@gmail.com <mailto:porres@gmail.com>>:

            About the sample-offset, I have some problem
            understanding how it works,
            and have to change it anyhow to fix the issue
            (garray_getarraywords
            related on 64-bit systems).


        seems there was a bug report about this :)
        http://sourceforge.net/p/pure-data/bugs/1180/





_______________________________________________
Pd-list@lists.iem.at <mailto:Pd-list@lists.iem.at> mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list

about the help file, you have in your new versions, regarding the phase input, the message: "- drive by phase only (frequency is 0)"

This is wrong. Maybe you copied from the max documentation example where in fact phase was driven by phasor and it had a frequency of zero, but in practice, you can alter the phase any way you want with any frequency input, just like the test examples you sent me!

So I'd just specify that the second inlet is for "phase input".

maybe you could insert an example for phase modulation. Because one advantage of cycle~ is enabling easy access to phase for phase modulation. See my attaches patch.

cheers

2015-06-08 18:35 GMT-03:00 Alexandre Torres Porres porres@gmail.com:

...

To keep maintenance to cyclone reasonable, I try to limit it to the functionality of Max 5. The documentation for Max 5 is conveniently online and I have a installation available for comparison. So Max 7 functionality is out of scope for me.

Oh, so you do have Max 5 to test it. Can you see if it works, or if it has a problem like Max 6 and 7?

I can check the differences between the objects in Max 5 and Max 6/7. It may be boring and tiring work, but it could be good to see the differences from current Max distribution. My guess is that most objects will behave exactly the same. Maybe just cycle~ and a couple of others may have something different. Then we could see what would it take to make the objects compatible to the current Max 7 distribution.

One other thing I'd like to talk to you about is the help file of cycle, but I'll do this on another message.

cheers