Re: [PD] Update cyclone maintenance
Hi Alexandre, Since you are interested in doing some maintenance in the cyclone library, I would like to report a possible bug found by an user in the forum and then confirmed by me. Apparently there are some problems with the object [delay~] and I am not sure they are present in Max 5 (I can check at my school if you want to). The problem is actually two bugs: first, the argument is completely ignored (so no delay is applied when I try [delay 44100]). The second problem is about the range of the values accepted by [delay~] via its rightmost inlet: it clips any input into values between 0 and 44100, so it's not possible to have a delay longer than 1 second. Here is the forum thread where this was reported: http://forum.pdpatchrepo.info/topic/9371/what-does-delay-do/2 Cheers, Gilberto ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Update cyclone maintenance
About maintaining cyclone, I think a reorg would be great, and further maintenance as well. If you want to do whatever you want with it, then just make a fork and work on it as a new name. If you want to stick to cyclone's central goal of Max/MSP compatibility, then keep working on it as cyclone. But please do not work on cyclone and break the Max/MSP compatibility. .hc Alexandre Torres Porres: About the [rampsmooth~], I see the new object is corrected, great! One thing though, I just realized how it has no audio signal inlets for the arguments!!! It was supposed to have them, just like [slide~] does. cheers 2015-06-07 7:28 GMT-03:00 Fred Jan Kraan fjkr...@xs4all.nl: Hi Jan, Thanks for pointing this out. I had seen the logic juggling with RAMPSMOOTH_GEOMETRIC and RAMPSMOOTH_LINEAR, but hadn't came to the conclusion the default behaviour was incorrect. I changed the code for now, but could make the change possible at run-time, as it was intended. But as we already have [slide~] for this, it is not very needed. Greetings, Fred Jan On 2015-06-07 11:33 AM, Jan Baumgart wrote: Actually, the linear version is already in cyclone's code. You can choose at compile time by not setting #define RAMPSMOOTH_GEOMETRIC cheers, jan On 06/06/2015 10:26 PM, Alexandre Torres Porres wrote: I have another bug to report, now in [rampsmooth~]. According to its help file, it should generate a linear ramp, but it doesn't. Instead, it generates a logarithmic curve just like [slide~]. I have attached a picture that shows how both are operating in the same way, where they shouldn't. In MAX, [rampsmooth~] does in fact generate a perfectly linear ramp, unlike [slide~]. I was actually able to implement [slide~] only with [fexpr~], making it 100% compatible to vanilla. If there's a filter formula tht generates perfectly linear ramps I can implement it I guess, but it should be fairly easy to change it in the object. I'll see what I can do to help. cheers 2015-06-05 18:08 GMT-03:00 Dan Wilcox danomat...@gmail.com mailto:danomat...@gmail.com: [m_scale] is an abstraction ... Dan Wilcox @danomatika https://twitter.com/danomatika danomatika.com http://danomatika.com robotcowboy.com http://robotcowboy.com On Jun 5, 2015, at 5:05 PM, Alexandre Torres Porres por...@gmail.com mailto:por...@gmail.com wrote: Yeah, I already built it with expr, so I don't really need to download etxernals for that. I was just wondering if extended already had such a thing, and it doesn't, so I think it's a nice addon to cyclone. An addon to cyclone would implicate and addon to extended, but then, it's not clear it'll ever be maintained again. Last time anyone talked about it in this list was 6 months ago... one way or another, seems like a nice addon to cyclone. Maybe it could be just an abstraction and it doesn't have to be a compiled object, I see the point. But I'd like to try and code it as an external into the cyclone library if possible. cheers 2015-06-05 17:50 GMT-03:00 Dan Wilcox danomat...@gmail.com mailto:danomat...@gmail.com: See [m_scale] in rjlib: https://github.com/rjdj/rjlib/tree/master/rj Dan Wilcox @danomatika https://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/ On Jun 5, 2015, at 4:35 PM, pd-list-requ...@lists.iem.at mailto:pd-list-requ...@lists.iem.at wrote: *From:*Alexandre Torres Porres por...@gmail.com mailto:por...@gmail.com *Subject:**Re: [PD] Update cyclone maintenance* *Date:*June 5, 2015 at 4:34:55 PM EDT *To:*Fred Jan Kraan fjkr...@xs4all.nl mailto:fjkr...@xs4all.nl *Cc:*pd-list@lists.iem.at mailto:pd-list@lists.iem.at pd-list@lists.iem.at mailto:pd-list@lists.iem.at 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. 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. cheers ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list N�n�r)em�h�yhiם�w^�� ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management - http
Re: [PD] Update cyclone maintenance
About the [rampsmooth~], I see the new object is corrected, great! One thing though, I just realized how it has no audio signal inlets for the arguments!!! It was supposed to have them, just like [slide~] does. cheers 2015-06-07 7:28 GMT-03:00 Fred Jan Kraan fjkr...@xs4all.nl: Hi Jan, Thanks for pointing this out. I had seen the logic juggling with RAMPSMOOTH_GEOMETRIC and RAMPSMOOTH_LINEAR, but hadn't came to the conclusion the default behaviour was incorrect. I changed the code for now, but could make the change possible at run-time, as it was intended. But as we already have [slide~] for this, it is not very needed. Greetings, Fred Jan On 2015-06-07 11:33 AM, Jan Baumgart wrote: Actually, the linear version is already in cyclone's code. You can choose at compile time by not setting #define RAMPSMOOTH_GEOMETRIC cheers, jan On 06/06/2015 10:26 PM, Alexandre Torres Porres wrote: I have another bug to report, now in [rampsmooth~]. According to its help file, it should generate a linear ramp, but it doesn't. Instead, it generates a logarithmic curve just like [slide~]. I have attached a picture that shows how both are operating in the same way, where they shouldn't. In MAX, [rampsmooth~] does in fact generate a perfectly linear ramp, unlike [slide~]. I was actually able to implement [slide~] only with [fexpr~], making it 100% compatible to vanilla. If there's a filter formula tht generates perfectly linear ramps I can implement it I guess, but it should be fairly easy to change it in the object. I'll see what I can do to help. cheers 2015-06-05 18:08 GMT-03:00 Dan Wilcox danomat...@gmail.com mailto:danomat...@gmail.com: [m_scale] is an abstraction ... Dan Wilcox @danomatika https://twitter.com/danomatika danomatika.com http://danomatika.com robotcowboy.com http://robotcowboy.com On Jun 5, 2015, at 5:05 PM, Alexandre Torres Porres por...@gmail.com mailto:por...@gmail.com wrote: Yeah, I already built it with expr, so I don't really need to download etxernals for that. I was just wondering if extended already had such a thing, and it doesn't, so I think it's a nice addon to cyclone. An addon to cyclone would implicate and addon to extended, but then, it's not clear it'll ever be maintained again. Last time anyone talked about it in this list was 6 months ago... one way or another, seems like a nice addon to cyclone. Maybe it could be just an abstraction and it doesn't have to be a compiled object, I see the point. But I'd like to try and code it as an external into the cyclone library if possible. cheers 2015-06-05 17:50 GMT-03:00 Dan Wilcox danomat...@gmail.com mailto:danomat...@gmail.com: See [m_scale] in rjlib: https://github.com/rjdj/rjlib/tree/master/rj Dan Wilcox @danomatika https://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/ On Jun 5, 2015, at 4:35 PM, pd-list-requ...@lists.iem.at mailto:pd-list-requ...@lists.iem.at wrote: *From:*Alexandre Torres Porres por...@gmail.com mailto:por...@gmail.com *Subject:**Re: [PD] Update cyclone maintenance* *Date:*June 5, 2015 at 4:34:55 PM EDT *To:*Fred Jan Kraan fjkr...@xs4all.nl mailto:fjkr...@xs4all.nl *Cc:*pd-list@lists.iem.at mailto:pd-list@lists.iem.at pd-list@lists.iem.at mailto:pd-list@lists.iem.at 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. 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. cheers ___ 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
Re: [PD] Update cyclone maintenance
yeah, we have slide~ for logarithmic ramps and rampsmooth~ in max is inteded to be only a linear ramp smoother, so I find it weird that there's this option in the code, I guess it shouldn't be there if the idea is to make them compatible. Anyway, I was trying to make it in a patch and I did it :) - find it attached if you care. cheers 2015-06-07 7:28 GMT-03:00 Fred Jan Kraan fjkr...@xs4all.nl: Hi Jan, Thanks for pointing this out. I had seen the logic juggling with RAMPSMOOTH_GEOMETRIC and RAMPSMOOTH_LINEAR, but hadn't came to the conclusion the default behaviour was incorrect. I changed the code for now, but could make the change possible at run-time, as it was intended. But as we already have [slide~] for this, it is not very needed. Greetings, Fred Jan On 2015-06-07 11:33 AM, Jan Baumgart wrote: Actually, the linear version is already in cyclone's code. You can choose at compile time by not setting #define RAMPSMOOTH_GEOMETRIC cheers, jan On 06/06/2015 10:26 PM, Alexandre Torres Porres wrote: I have another bug to report, now in [rampsmooth~]. According to its help file, it should generate a linear ramp, but it doesn't. Instead, it generates a logarithmic curve just like [slide~]. I have attached a picture that shows how both are operating in the same way, where they shouldn't. In MAX, [rampsmooth~] does in fact generate a perfectly linear ramp, unlike [slide~]. I was actually able to implement [slide~] only with [fexpr~], making it 100% compatible to vanilla. If there's a filter formula tht generates perfectly linear ramps I can implement it I guess, but it should be fairly easy to change it in the object. I'll see what I can do to help. cheers 2015-06-05 18:08 GMT-03:00 Dan Wilcox danomat...@gmail.com mailto:danomat...@gmail.com: [m_scale] is an abstraction ... Dan Wilcox @danomatika https://twitter.com/danomatika danomatika.com http://danomatika.com robotcowboy.com http://robotcowboy.com On Jun 5, 2015, at 5:05 PM, Alexandre Torres Porres por...@gmail.com mailto:por...@gmail.com wrote: Yeah, I already built it with expr, so I don't really need to download etxernals for that. I was just wondering if extended already had such a thing, and it doesn't, so I think it's a nice addon to cyclone. An addon to cyclone would implicate and addon to extended, but then, it's not clear it'll ever be maintained again. Last time anyone talked about it in this list was 6 months ago... one way or another, seems like a nice addon to cyclone. Maybe it could be just an abstraction and it doesn't have to be a compiled object, I see the point. But I'd like to try and code it as an external into the cyclone library if possible. cheers 2015-06-05 17:50 GMT-03:00 Dan Wilcox danomat...@gmail.com mailto:danomat...@gmail.com: See [m_scale] in rjlib: https://github.com/rjdj/rjlib/tree/master/rj Dan Wilcox @danomatika https://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/ On Jun 5, 2015, at 4:35 PM, pd-list-requ...@lists.iem.at mailto:pd-list-requ...@lists.iem.at wrote: *From:*Alexandre Torres Porres por...@gmail.com mailto:por...@gmail.com *Subject:**Re: [PD] Update cyclone maintenance* *Date:*June 5, 2015 at 4:34:55 PM EDT *To:*Fred Jan Kraan fjkr...@xs4all.nl mailto:fjkr...@xs4all.nl *Cc:*pd-list@lists.iem.at mailto:pd-list@lists.iem.at pd-list@lists.iem.at mailto:pd-list@lists.iem.at 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. 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. cheers ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list rampsmooth.pd Description: Binary data ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Update cyclone maintenance
Hi Alexandre, another bug, now in [slide~], it needs a ramp up value that is small, so the ramp down works. On the other hand, ramp down value can be zero and ramp up will still work. Check attached file. Fixed this one too. I will try to fix cycle~ too before updating all binary packages. I was able to implement slide~ with vanilla objects only and with [fexpr~], it works fine without this bug, but I found that the formula needs to have at least a value of 1 to work, so [max~ 1] does the job. but when it receives a 0, the audio will actually become constant, so it's not related to the bug in the slide~ object, where the ramp just doesn't happen. The slide~ object will effectively use 1 for up and down values smaller than 1. Which is sensible as it represents the number of samples of the slide. cheers Thank you greetings, Fred Jan 2015-06-06 17:26 GMT-03:00 Alexandre Torres Porres por...@gmail.com mailto:por...@gmail.com: I have another bug to report, now in [rampsmooth~]. According to its help file, it should generate a linear ramp, but it doesn't. Instead, it generates a logarithmic curve just like [slide~]. I have attached a picture that shows how both are operating in the same way, where they shouldn't. In MAX, [rampsmooth~] does in fact generate a perfectly linear ramp, unlike [slide~]. I was actually able to implement [slide~] only with [fexpr~], making it 100% compatible to vanilla. If there's a filter formula tht generates perfectly linear ramps I can implement it I guess, but it should be fairly easy to change it in the object. I'll see what I can do to help. cheers 2015-06-05 18:08 GMT-03:00 Dan Wilcox danomat...@gmail.com mailto:danomat...@gmail.com: [m_scale] is an abstraction ... Dan Wilcox @danomatika https://twitter.com/danomatika danomatika.com http://danomatika.com robotcowboy.com http://robotcowboy.com On Jun 5, 2015, at 5:05 PM, Alexandre Torres Porres por...@gmail.com mailto:por...@gmail.com wrote: Yeah, I already built it with expr, so I don't really need to download etxernals for that. I was just wondering if extended already had such a thing, and it doesn't, so I think it's a nice addon to cyclone. An addon to cyclone would implicate and addon to extended, but then, it's not clear it'll ever be maintained again. Last time anyone talked about it in this list was 6 months ago... one way or another, seems like a nice addon to cyclone. Maybe it could be just an abstraction and it doesn't have to be a compiled object, I see the point. But I'd like to try and code it as an external into the cyclone library if possible. cheers 2015-06-05 17:50 GMT-03:00 Dan Wilcox danomat...@gmail.com mailto:danomat...@gmail.com: See [m_scale] in rjlib: https://github.com/rjdj/rjlib/tree/master/rj Dan Wilcox @danomatika https://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/ On Jun 5, 2015, at 4:35 PM, pd-list-requ...@lists.iem.at mailto:pd-list-requ...@lists.iem.at wrote: *From: *Alexandre Torres Porres por...@gmail.com mailto:por...@gmail.com *Subject: **Re: [PD] Update cyclone maintenance* *Date: *June 5, 2015 at 4:34:55 PM EDT *To: *Fred Jan Kraan fjkr...@xs4all.nl mailto:fjkr...@xs4all.nl *Cc: *pd-list@lists.iem.at mailto:pd-list@lists.iem.at pd-list@lists.iem.at mailto:pd-list@lists.iem.at 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. 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. cheers ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Update cyclone maintenance
Hi Jan, Thanks for pointing this out. I had seen the logic juggling with RAMPSMOOTH_GEOMETRIC and RAMPSMOOTH_LINEAR, but hadn't came to the conclusion the default behaviour was incorrect. I changed the code for now, but could make the change possible at run-time, as it was intended. But as we already have [slide~] for this, it is not very needed. Greetings, Fred Jan On 2015-06-07 11:33 AM, Jan Baumgart wrote: Actually, the linear version is already in cyclone's code. You can choose at compile time by not setting #define RAMPSMOOTH_GEOMETRIC cheers, jan On 06/06/2015 10:26 PM, Alexandre Torres Porres wrote: I have another bug to report, now in [rampsmooth~]. According to its help file, it should generate a linear ramp, but it doesn't. Instead, it generates a logarithmic curve just like [slide~]. I have attached a picture that shows how both are operating in the same way, where they shouldn't. In MAX, [rampsmooth~] does in fact generate a perfectly linear ramp, unlike [slide~]. I was actually able to implement [slide~] only with [fexpr~], making it 100% compatible to vanilla. If there's a filter formula tht generates perfectly linear ramps I can implement it I guess, but it should be fairly easy to change it in the object. I'll see what I can do to help. cheers 2015-06-05 18:08 GMT-03:00 Dan Wilcox danomat...@gmail.com mailto:danomat...@gmail.com: [m_scale] is an abstraction ... Dan Wilcox @danomatika https://twitter.com/danomatika danomatika.com http://danomatika.com robotcowboy.com http://robotcowboy.com On Jun 5, 2015, at 5:05 PM, Alexandre Torres Porres por...@gmail.com mailto:por...@gmail.com wrote: Yeah, I already built it with expr, so I don't really need to download etxernals for that. I was just wondering if extended already had such a thing, and it doesn't, so I think it's a nice addon to cyclone. An addon to cyclone would implicate and addon to extended, but then, it's not clear it'll ever be maintained again. Last time anyone talked about it in this list was 6 months ago... one way or another, seems like a nice addon to cyclone. Maybe it could be just an abstraction and it doesn't have to be a compiled object, I see the point. But I'd like to try and code it as an external into the cyclone library if possible. cheers 2015-06-05 17:50 GMT-03:00 Dan Wilcox danomat...@gmail.com mailto:danomat...@gmail.com: See [m_scale] in rjlib: https://github.com/rjdj/rjlib/tree/master/rj Dan Wilcox @danomatika https://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/ On Jun 5, 2015, at 4:35 PM, pd-list-requ...@lists.iem.at mailto:pd-list-requ...@lists.iem.at wrote: *From:*Alexandre Torres Porres por...@gmail.com mailto:por...@gmail.com *Subject:**Re: [PD] Update cyclone maintenance* *Date:*June 5, 2015 at 4:34:55 PM EDT *To:*Fred Jan Kraan fjkr...@xs4all.nl mailto:fjkr...@xs4all.nl *Cc:*pd-list@lists.iem.at mailto:pd-list@lists.iem.at pd-list@lists.iem.at mailto:pd-list@lists.iem.at 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. 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. cheers ___ 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
Re: [PD] Update cyclone maintenance
Actually, the linear version is already in cyclone's code. You can choose at compile time by not setting #define RAMPSMOOTH_GEOMETRIC cheers, jan On 06/06/2015 10:26 PM, Alexandre Torres Porres wrote: I have another bug to report, now in [rampsmooth~]. According to its help file, it should generate a linear ramp, but it doesn't. Instead, it generates a logarithmic curve just like [slide~]. I have attached a picture that shows how both are operating in the same way, where they shouldn't. In MAX, [rampsmooth~] does in fact generate a perfectly linear ramp, unlike [slide~]. I was actually able to implement [slide~] only with [fexpr~], making it 100% compatible to vanilla. If there's a filter formula tht generates perfectly linear ramps I can implement it I guess, but it should be fairly easy to change it in the object. I'll see what I can do to help. cheers 2015-06-05 18:08 GMT-03:00 Dan Wilcox danomat...@gmail.com mailto:danomat...@gmail.com: [m_scale] is an abstraction ... Dan Wilcox @danomatika https://twitter.com/danomatika danomatika.com http://danomatika.com robotcowboy.com http://robotcowboy.com On Jun 5, 2015, at 5:05 PM, Alexandre Torres Porres por...@gmail.com mailto:por...@gmail.com wrote: Yeah, I already built it with expr, so I don't really need to download etxernals for that. I was just wondering if extended already had such a thing, and it doesn't, so I think it's a nice addon to cyclone. An addon to cyclone would implicate and addon to extended, but then, it's not clear it'll ever be maintained again. Last time anyone talked about it in this list was 6 months ago... one way or another, seems like a nice addon to cyclone. Maybe it could be just an abstraction and it doesn't have to be a compiled object, I see the point. But I'd like to try and code it as an external into the cyclone library if possible. cheers 2015-06-05 17:50 GMT-03:00 Dan Wilcox danomat...@gmail.com mailto:danomat...@gmail.com: See [m_scale] in rjlib: https://github.com/rjdj/rjlib/tree/master/rj Dan Wilcox @danomatika https://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/ On Jun 5, 2015, at 4:35 PM, pd-list-requ...@lists.iem.at mailto:pd-list-requ...@lists.iem.at wrote: *From:*Alexandre Torres Porres por...@gmail.com mailto:por...@gmail.com *Subject:**Re: [PD] Update cyclone maintenance* *Date:*June 5, 2015 at 4:34:55 PM EDT *To:*Fred Jan Kraan fjkr...@xs4all.nl mailto:fjkr...@xs4all.nl *Cc:*pd-list@lists.iem.at mailto:pd-list@lists.iem.at pd-list@lists.iem.at mailto:pd-list@lists.iem.at 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. 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. cheers ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list -- Jan Baumgart Technischer Mitarbeiter Hochschule für Musik und Darstellende Kunst Eschersheimer Landstr. 29-39 60322 Frankfurt am Main ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Update cyclone maintenance
I have another bug to report, now in [rampsmooth~]. According to its help file, it should generate a linear ramp, but it doesn't. Instead, it generates a logarithmic curve just like [slide~]. I have attached a picture that shows how both are operating in the same way, where they shouldn't. In MAX, [rampsmooth~] does in fact generate a perfectly linear ramp, unlike [slide~]. I was actually able to implement [slide~] only with [fexpr~], making it 100% compatible to vanilla. If there's a filter formula tht generates perfectly linear ramps I can implement it I guess, but it should be fairly easy to change it in the object. I'll see what I can do to help. cheers 2015-06-05 18:08 GMT-03:00 Dan Wilcox danomat...@gmail.com: [m_scale] is an abstraction ... Dan Wilcox @danomatika https://twitter.com/danomatika danomatika.com robotcowboy.com On Jun 5, 2015, at 5:05 PM, Alexandre Torres Porres por...@gmail.com wrote: Yeah, I already built it with expr, so I don't really need to download etxernals for that. I was just wondering if extended already had such a thing, and it doesn't, so I think it's a nice addon to cyclone. An addon to cyclone would implicate and addon to extended, but then, it's not clear it'll ever be maintained again. Last time anyone talked about it in this list was 6 months ago... one way or another, seems like a nice addon to cyclone. Maybe it could be just an abstraction and it doesn't have to be a compiled object, I see the point. But I'd like to try and code it as an external into the cyclone library if possible. cheers 2015-06-05 17:50 GMT-03:00 Dan Wilcox danomat...@gmail.com: See [m_scale] in rjlib: https://github.com/rjdj/rjlib/tree/master/rj Dan Wilcox @danomatika https://twitter.com/danomatika danomatika.com robotcowboy.com On Jun 5, 2015, at 4:35 PM, pd-list-requ...@lists.iem.at wrote: *From: *Alexandre Torres Porres por...@gmail.com *Subject: **Re: [PD] Update cyclone maintenance* *Date: *June 5, 2015 at 4:34:55 PM EDT *To: *Fred Jan Kraan fjkr...@xs4all.nl *Cc: *pd-list@lists.iem.at pd-list@lists.iem.at 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. 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. cheers ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Update cyclone maintenance
another bug, now in [slide~], it needs a ramp up value that is small, so the ramp down works. On the other hand, ramp down value can be zero and ramp up will still work. Check attached file. I was able to implement slide~ with vanilla objects only and with [fexpr~], it works fine without this bug, but I found that the formula needs to have at least a value of 1 to work, so [max~ 1] does the job. but when it receives a 0, the audio will actually become constant, so it's not related to the bug in the slide~ object, where the ramp just doesn't happen. cheers 2015-06-06 17:26 GMT-03:00 Alexandre Torres Porres por...@gmail.com: I have another bug to report, now in [rampsmooth~]. According to its help file, it should generate a linear ramp, but it doesn't. Instead, it generates a logarithmic curve just like [slide~]. I have attached a picture that shows how both are operating in the same way, where they shouldn't. In MAX, [rampsmooth~] does in fact generate a perfectly linear ramp, unlike [slide~]. I was actually able to implement [slide~] only with [fexpr~], making it 100% compatible to vanilla. If there's a filter formula tht generates perfectly linear ramps I can implement it I guess, but it should be fairly easy to change it in the object. I'll see what I can do to help. cheers 2015-06-05 18:08 GMT-03:00 Dan Wilcox danomat...@gmail.com: [m_scale] is an abstraction ... Dan Wilcox @danomatika https://twitter.com/danomatika danomatika.com robotcowboy.com On Jun 5, 2015, at 5:05 PM, Alexandre Torres Porres por...@gmail.com wrote: Yeah, I already built it with expr, so I don't really need to download etxernals for that. I was just wondering if extended already had such a thing, and it doesn't, so I think it's a nice addon to cyclone. An addon to cyclone would implicate and addon to extended, but then, it's not clear it'll ever be maintained again. Last time anyone talked about it in this list was 6 months ago... one way or another, seems like a nice addon to cyclone. Maybe it could be just an abstraction and it doesn't have to be a compiled object, I see the point. But I'd like to try and code it as an external into the cyclone library if possible. cheers 2015-06-05 17:50 GMT-03:00 Dan Wilcox danomat...@gmail.com: See [m_scale] in rjlib: https://github.com/rjdj/rjlib/tree/master/rj Dan Wilcox @danomatika https://twitter.com/danomatika danomatika.com robotcowboy.com On Jun 5, 2015, at 4:35 PM, pd-list-requ...@lists.iem.at wrote: *From: *Alexandre Torres Porres por...@gmail.com *Subject: **Re: [PD] Update cyclone maintenance* *Date: *June 5, 2015 at 4:34:55 PM EDT *To: *Fred Jan Kraan fjkr...@xs4all.nl *Cc: *pd-list@lists.iem.at pd-list@lists.iem.at 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. 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. cheers slide-bug.pd Description: Binary data ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Update cyclone maintenance
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 por...@gmail.com mailto:por...@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 por...@gmail.com mailto:por...@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 por...@gmail.com mailto:por...@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 fjkr...@xs4all.nl mailto:fjkr...@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 ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Update cyclone maintenance
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 fjkr...@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 por...@gmail.com mailto:por...@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 por...@gmail.com mailto:por...@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 por...@gmail.com mailto:por...@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 fjkr...@xs4all.nl mailto:fjkr...@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 ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Update cyclone maintenance
Hi Alexandre, On 2015-06-05 09:21 PM, Alexandre Torres Porres wrote: 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? The list and the object states is here: http://fjkraan.home.xs4all.nl/digaud/puredata/cyclone/cycloneToDo.html. Did you see what I mentioned about [cycle~]? No, but I will try to dig up your post about it. 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 http://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 http://puredata.info site (or somewhere else as well)? Can I get the package as it is now and test it? For now, you can find a zip of the cyclone directory here: http://fjkraan.home.xs4all.nl/digaud/puredata/cyclone/index.html. Being just zips, it is not very convenient. But a better solution for distributing externals is in the works. thanks Greetings, Fred Jan ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Update cyclone maintenance
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 ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Update cyclone maintenance
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. 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. cheers 2015-06-05 16:21 GMT-03:00 Alexandre Torres Porres por...@gmail.com: 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 fjkr...@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 por...@gmail.com mailto:por...@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 por...@gmail.com mailto:por...@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 por...@gmail.com mailto:por...@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 fjkr...@xs4all.nl mailto:fjkr...@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 ___ Pd-list@lists.iem.at mailing list
Re: [PD] Update cyclone maintenance
See [m_scale] in rjlib: https://github.com/rjdj/rjlib/tree/master/rj https://github.com/rjdj/rjlib/tree/master/rj Dan Wilcox @danomatika https://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/ On Jun 5, 2015, at 4:35 PM, pd-list-requ...@lists.iem.at wrote: From: Alexandre Torres Porres por...@gmail.com mailto:por...@gmail.com Subject: Re: [PD] Update cyclone maintenance Date: June 5, 2015 at 4:34:55 PM EDT To: Fred Jan Kraan fjkr...@xs4all.nl mailto:fjkr...@xs4all.nl Cc: pd-list@lists.iem.at mailto:pd-list@lists.iem.at pd-list@lists.iem.at mailto:pd-list@lists.iem.at 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. 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. cheers ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Update cyclone maintenance
Yeah, I already built it with expr, so I don't really need to download etxernals for that. I was just wondering if extended already had such a thing, and it doesn't, so I think it's a nice addon to cyclone. An addon to cyclone would implicate and addon to extended, but then, it's not clear it'll ever be maintained again. Last time anyone talked about it in this list was 6 months ago... one way or another, seems like a nice addon to cyclone. Maybe it could be just an abstraction and it doesn't have to be a compiled object, I see the point. But I'd like to try and code it as an external into the cyclone library if possible. cheers 2015-06-05 17:50 GMT-03:00 Dan Wilcox danomat...@gmail.com: See [m_scale] in rjlib: https://github.com/rjdj/rjlib/tree/master/rj Dan Wilcox @danomatika https://twitter.com/danomatika danomatika.com robotcowboy.com On Jun 5, 2015, at 4:35 PM, pd-list-requ...@lists.iem.at wrote: *From: *Alexandre Torres Porres por...@gmail.com *Subject: **Re: [PD] Update cyclone maintenance* *Date: *June 5, 2015 at 4:34:55 PM EDT *To: *Fred Jan Kraan fjkr...@xs4all.nl *Cc: *pd-list@lists.iem.at pd-list@lists.iem.at 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. 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. cheers ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Update cyclone maintenance
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 por...@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 por...@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 por...@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 fjkr...@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 ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Update cyclone maintenance
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 por...@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 fjkr...@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 ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Update cyclone maintenance
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 por...@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 fjkr...@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 fjkr...@xs4all.nl mailto:fjkr...@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 ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Update cyclone maintenance
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 fjkr...@xs4all.nl mailto:fjkr...@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 ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Update cyclone maintenance
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 fjkr...@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 ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Update cyclone maintenance
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 fjkr...@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 fjkr...@xs4all.nl mailto:fjkr...@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 ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Update cyclone maintenance
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 por...@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 chakekat...@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 por...@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 por...@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 por...@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 zmoel...@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
Re: [PD] Update cyclone maintenance
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 ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Update cyclone maintenance
Hi Alexandre, 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? Originally, the objects in Max/MSP had capitals, but that changed a long time ago. Some time back (can't find it now) there was a discussion on this at the list and the conclusion was that the objects should also be available in lower case. Apparently this never happened. When I find the discussion again, and the reasoning is still sound, I could try to implement it. Fred Jan cheers ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Update cyclone maintenance
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 chakekat...@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 por...@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 por...@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 por...@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 zmoel...@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
Re: [PD] Update cyclone maintenance
-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
Re: [PD] Update cyclone maintenance
~, ||~, ~, ~, ==~ 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 zmoel...@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 ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Update cyclone maintenance
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 por...@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 zmoel...@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
Re: [PD] Update cyclone maintenance
*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 por...@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 por...@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 zmoel...@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
Re: [PD] Update cyclone maintenance
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 zmoel...@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 =~-help.pd Description: Binary data =~.pd Description: Binary data ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Update cyclone maintenance
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 por...@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 por...@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 por...@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 zmoel...@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- ___
Re: [PD] Update cyclone maintenance
-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
Re: [PD] Update cyclone maintenance
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 fjkr...@xs4all.nl mailto:fjkr...@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 ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Update cyclone maintenance
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 fjkr...@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 fjkr...@xs4all.nl mailto:fjkr...@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 ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Update cyclone maintenance
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 fjkr...@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 ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
