Re: [PD] consolidate backward- and MaxMSP compatibility in Cyclone (was: Purpose of Cyclone)

I find Fred Jan's maintenance reasonable because sticking with current behavior means 0% of patches in the wild will be negatively affected.  There's the possibility that his maintenance hinders Max compatibility for future patches, but this isn't something we can quantify. We can _estimate_

Re: [PD] consolidate backward- and MaxMSP compatibility in Cyclone (was: Purpose of Cyclone)

On Tue, Dec 22, 2015 at 9:41 PM, Alexandre Torres Porres wrote: > If we're discussing [average~], how about my idea of having a second right > signal outlet as default? I think it's an easy and simple solution. Help > file would explain how the left control outlet is for

Re: [PD] consolidate backward- and MaxMSP compatibility in Cyclone (was: Purpose of Cyclone)

2015-12-22 17:58 GMT-02:00 Jonathan Wilkes : > I find Fred Jan's maintenance reasonable because sticking with current > behavior means 0% of patches in > the wild will be negatively affected. There's the possibility that his > maintenance hinders Max compatibility for future

Re: [PD] consolidate backward- and MaxMSP compatibility in Cyclone (was: Purpose of Cyclone)

If I may make a suggestion - when I find that an object isn't terribly well designed (for example my own qlist :) I make another one, with another name, that does the job better (text). cheers Miller On Tue, Dec 22, 2015 at 08:51:03PM -0200, Alexandre Torres Porres wrote: > Well, newer patches

Re: [PD] consolidate backward- and MaxMSP compatibility in Cyclone (was: Purpose of Cyclone)

2015-12-22 15:25 GMT-02:00 Jonathan Wilkes via Pd-list : > Hi anyone encouraging backward breakage, > Please make a collection of as many patches as possible, from as many > public > sources as possible. > > Then mine this data to get a sense of what percentage of patches

Re: [PD] consolidate backward- and MaxMSP compatibility in Cyclone (was: Purpose of Cyclone)

Well, newer patches with newer functionalities not working in older versions is how things go anyway, right? Vanilla 0-46 patches don't run in 0.45 and so on... there's no way around that I guess. > the dual outlet layout with message left and > signal right is rather unusual. But I think it's

Re: [PD] consolidate backward- and MaxMSP compatibility in Cyclone (was: Purpose of Cyclone)

What about versioning? If people *have* to have older compatibility, then why can’t they just run an older version of cyclone? Newer development can take place on the current version and you can clearly note api changes/updates in a CHANGELOG. Say tag cyclone right now as version 1.0.0 and all

Re: [PD] consolidate backward- and MaxMSP compatibility in Cyclone

seems the thread has forked, hadn't seen this. 2015-12-22 18:52 GMT-02:00 Fred Jan Kraan : > Sorry for all the confusion I have apparently created. > I feel quite responsible, so apologies as well > It seems that more words just means more misunderstanding. So here I >

Re: [PD] consolidate backward- and MaxMSP compatibility in Cyclone (was: Purpose of Cyclone)

Actually one of the problems with extended was that it loaded *everything* by default, so people aren’t used to specifying required libs. Imagine if [declare] or [import] could also specify lib versions ... Dan Wilcox @danomatika danomatika.com

Re: [PD] consolidate backward- and MaxMSP compatibility in Cyclone (was: Purpose of Cyclone)

2015-12-23 1:44 GMT-02:00 Dan Wilcox : > What about versioning? If people *have* to have older compatibility, then > why can’t they just run an older version of cyclone? > We're not really even at a real discussion where people would *have* and *need* to stay with an older

Re: [PD] JACKerror: Cannot use real-time scheduling (RR/0)(22: Invalid argument) JACKerror: JackClient::AcquireSelfRealTime error

however, no sound problem, no bad messages on qjackctl. On Wed, Dec 23, 2015 at 1:54 AM, Jonghyun Kim wrote: > hi list, > > JACKerror: Cannot use real-time scheduling (RR/0)(22: Invalid argument) > JACKerror: JackClient::AcquireSelfRealTime error > > this errors occurs

Re: [PD] consolidate backward- and MaxMSP compatibility in Cyclone (was: Purpose of Cyclone)

Pd is a programming language and I cannot think of any long-lived language where things did not become deprecated and/or required older code authors to make minor changes to ensure it works on newer versions of the same language. I think cyclone would do well to follow this mantra and by doing so

[PD] JACKerror: Cannot use real-time scheduling (RR/0)(22: Invalid argument) JACKerror: JackClient::AcquireSelfRealTime error

hi list, JACKerror: Cannot use real-time scheduling (RR/0)(22: Invalid argument) JACKerror: JackClient::AcquireSelfRealTime error this errors occurs every pd variants on my system: pd-vanliia 0.46-7, 0.45-4, pd-extended 0.43-4, but no errors with pd-l2ork 20151219(based on pd 0.42? i guess?).

[PD] consolidate backward- and MaxMSP compatibility in Cyclone (was: Purpose of Cyclone)

Hello Alexandre, Fred Jan, pd list, It makes me sad to see your earlier productive collaboration on Cyclone stagnating with this dispute about the purpose. Between 2005 - 2015 the purpose of Cyclone has been determined more by what it was than by what it should be, by lack of human resources [1].

Re: [PD] JACKerror: Cannot use real-time scheduling (RR/0)(22: Invalid argument) JACKerror: JackClient::AcquireSelfRealTime error

added this lines to the end of /etc/security/limits.conf === @audio – rtprio 99 @audio – memlockunlimited @audio – nice -10 === sudo usermod -a -G audio MY_USER_ID On Wed, Dec 23, 2015 at 2:01 AM, Jonghyun Kim wrote: > however, no sound problem, no

Re: [PD] consolidate backward- and MaxMSP compatibility in Cyclone (was: Purpose of Cyclone)

2015-12-22 21:46 GMT-02:00 Miller Puckette : > when I find that an object isn't terribly well designed (...) I make > another one, with another name, that does the job better. > Sounds great, too bad the darn thing about cyclone is that we need to stick to deal with cloning the

Re: [PD] [PD-announce] ANN: pd-l2ork version 20151219 now available

OK, I think I narrowed it down to my Skylake/Haswell TSX improvement in respect to pthreads. I forgot to update the variable on trylock. Now, everything works as it should. I will reupload a new build with this important fix shortly. In the meantime, you can pull the latest git and build only core