Re: [PD] expr "copysign" function doesn't seem to work

Hey, i've been meaning to ask you about plans to make [fexpr~] available for Max. I've been recently teaching peopl about max as well, and I use [fexpr~] a lot. I always assumed max had the same objects, but was surprised to learn it doesn't have an [expr~] object, just an [expr] which seems to ba

Re: [PD] expr "copysign" function doesn't seem to work

Hello, great to hear from you. Yes, I got that fix, but I never compiled it and was just hoping someday it'd show up as an update, and I'm just worried it never came to be. Sorry to put you on the spot. I'm still learning about the bug reports work and get dealt with in Pd, people in the list were

Re: [PD] expr "copysign" function doesn't seem to work

> Thanks for your investigations and bug reports - that is important work. I'm more than glab to be able to help this way, unfortuntely I can't do more and fix the code myself. Not yet at least :) cheers 2015-06-07 23:07 GMT-03:00 Chris McCormick : > Hi Alexandre, > > Thanks for your investig

Re: [PD] expr "copysign" function doesn't seem to work

Hi Alexandre, This seems to be a bug. I am not sure why I missed the 'n' on the name either. As it seems that this function has never worked, we should fix the name as well. The solution is simple as follows: extra/expr~/vexp_fun.c 188c188 < {"copysign",ex_copysign,2}, --- >

Re: [PD] expr "copysign" function doesn't seem to work

Hi Alexandre, Thanks for your investigations and bug reports - that is important work. On 08/06/15 05:40, Alexandre Torres Porres wrote: > But I'd still like to know if anyone can fix this. I'm not sure how the > authorship works in this particular example. I know it's an "extra" > feature in van

Re: [PD] some repo house cleaning

Hi Jonathan, Whoops, looks like more words were needed after all, heh. :) On 07/06/15 23:51, Jonathan Wilkes via Pd-list wrote: > I'm using github for the nw.js port atm, too. But I see way less > potential for future shenanigans from a non-commercial host > with a long track record. I don't th

Re: [PD] slide~ (msp) in pd

* Alexandre Torres Porres [2015-06-07 18:36]: > well, if you want efficiency, why not just use the [slide~] object for Pd > in cyclone? I guess I was just curious. Thank you for your vanilla port of it Alexandre. ___ Pd-list@lists.iem.at mailing list UN

Re: [PD] expr "copysign" function doesn't seem to work

I can't get imodf($f1) to load into expr either, and it's one of the listed functions in the website, it doesn't seem to be the same problem with "copysig". It's on my list to report soon, but if anyone finds a way to load it please let me know. cheers 2015-06-07 19:46 GMT-03:00 Alexandre Torres P

Re: [PD] Problems with maintaining Pd-extended (was Mess and redundancy...)

> On Jun 7, 2015, at 7:03 PM, Dan Wilcox wrote: > >> On Jun 7, 2015, at 6:44 PM, Alexandre Torres Porres > > wrote: >> >> such as why would it have to be concentrated in "one person”? > > Because that’s how the existing extended setup was originally built and > maintai

Re: [PD] Problems with maintaining Pd-extended (was Mess and redundancy...)

> On Jun 7, 2015, at 6:44 PM, Alexandre Torres Porres > wrote: > > such as why would it have to be concentrated in "one person”? Because that’s how the existing extended setup was originally built and maintained. > Why the build farm is gone and how hard would it be to

Re: [PD] Problems with maintaining Pd-extended (was Mess and redundancy...)

> On Jun 7, 2015, at 6:44 PM, Alexandre Torres Porres wrote: > > such as why would it have to be concentrated in "one person”? Because that’s how the existing extended setup was originally built and maintained. > Why the build farm is gone and how hard would it be to put it all back and > run

Re: [PD] expr "copysign" function doesn't seem to work

I got nothing against the bug tracker, and I'll report it soon, let me just test all the functions carefully. thanks for the info cheers 2015-06-07 19:38 GMT-03:00 Dan Wilcox : > If you don’t want to use the bug tracker, it makes sense to write up a > list of expr bugs you’ve found and move the

Re: [PD] Problems with maintaining Pd-extended (was Mess and redundancy...)

hmm, looks like the "vanilla route" idea is taking place, awesome ;) but ok, lets not to force the cat out of the bag, we'll hold on for that... one way or another, I'd still like to know more about why and how things are complicated with the current extended scenario in more details. such as why

Re: [PD] slide~ (msp) in pd

well, if you want efficiency, why not just use the [slide~] object for Pd in cyclone? 2015-06-07 13:45 GMT-03:00 Alexandre Torres Porres : > no, but it's obviously more inefficient :) > > it could be simpler if you were to use [change~], that was the tricky part > for me > > 2015-06-07 12:20 GMT-

Re: [PD] expr "copysign" function doesn't seem to work

If you don’t want to use the bug tracker, it makes sense to write up a list of expr bugs you’ve found and move the discussion to pd-dev. I think everyone can agree that finding and fixing said bugs is a good thing we would all want to see happen. Nutshell: yes, we can fix it and update it. This

Re: [PD] expr "copysign" function doesn't seem to work

one issue that stands out in the case of expr is that its official manual and code distribution is hosted in sharok's website, so I guess he needs to be involved. 2015-06-07 18:40 GMT-03:00 Alexandre Torres Porres : > Great, I'll try to remember all bugs I found and test the object for even > mor

Re: [PD] expr "copysign" function doesn't seem to work

Great, I'll try to remember all bugs I found and test the object for even more issues that there may be and then report them. But I'd still like to know if anyone can fix this. I'm not sure how the authorship works in this particular example. I know it's an "extra" feature in vanilla, not maintain

Re: [PD] expr "copysign" function doesn't seem to work

On 06/07/2015 11:17 PM, Alexandre Torres Porres wrote: > So, what could we do? in any case make a bug-report at sourceforge, so the information can be collected in a central place. usually, this makes it to not miss an issue (e.g. a bug report is only closed once it is resolved; not because i 'ac

Re: [PD] expr "copysign" function doesn't seem to work

Well, I'm worried about the bugs in expr and that they get fixed actually, there are more bugs I found by the way. Now Shahrokh doesn't seem to be working on it and making updates anymore. I remember I complained about something in 2009 to him and it never got fixed. I could list them all as well,

Re: [PD] expr "copysign" function doesn't seem to work

You can substitute the copysign function with this ugly thing: [expr $f1*if($f2==0, 1, $f2/abs($f2))] cheers, jan On 06/07/2015 10:39 PM, Jan Baumgart wrote: It's spelled "copysig" in expr. But I couldn't get it to work. copysig in expr only takes one argument, whereas the c math function tak

Re: [PD] Cycle~ difference with Max5. Was: Update cyclone maintenance

> The offset can be set as argument and it works I can't seem to make it work, how do you do it? can you send me a patch? It seems [cycle~] will only work with tables that are 512 in size. It can be of any size in max now, but the help of Max 7 says: "This wavetable may be of any size, *but hist

Re: [PD] expr "copysign" function doesn't seem to work

It's spelled "copysig" in expr. But I couldn't get it to work. copysig in expr only takes one argument, whereas the c math function takes two arguments: float copysignf(float x, float y); It returns the absolute value of x with the sign of y. Smells like a bug to me... cheers, Jan On 06/07/

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 :)

Re: [PD] [sgn~] bug report

On 06/07/2015 10:14 PM, Alexandre Torres Porres wrote: >> pd-extended already comes with a menu-entry >> for "report a bug" that links to that page > > Yeah, it does, but I've never really used it much so I'm not used to it. > Moreover, I have to say I was insecure this was working, really, with a

Re: [PD] [sgn~] bug report

> pd-extended already comes with a menu-entry > for "report a bug" that links to that page Yeah, it does, but I've never really used it much so I'm not used to it. Moreover, I have to say I was insecure this was working, really, with all the discussion that extended is not being actively maintaine

[PD] Cycle~ difference with Max5. Was: Update cyclone maintenance

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

Re: [PD] expr "copysign" function doesn't seem to work

I'm assuming this copysign function is like the [sgn~] object in zexy, right? If not, what would it be? cheers 2015-06-07 16:57 GMT-03:00 Alexandre Torres Porres : > hi there, I was checking the source of expr (find it attached) and saw > this "copysign" function that I needed for a formula, but

[PD] expr "copysign" function doesn't seem to work

hi there, I was checking the source of expr (find it attached) and saw this "copysign" function that I needed for a formula, but I can't get it to work/load. I'm trying something like [expr copysign($f1)] and it's not happening. The expr manual page in http://yadegari.org/expr/expr.html tells abou

Re: [PD] [sgn~] bug report

On 06/07/2015 09:27 PM, Alexandre Torres Porres wrote: > Hi, there's a bug in [sgn~] when the block size is equal to 1! I have an > attached patch to show this. thanks for the report. > > Not sure if the list is the best channel to report bugs, I assume there had > to be a better channel to repo

Re: [PD] olimex board

On 06/04/2015 02:57 PM, Julian Brooks wrote: > JUst double-checked to be sure and > sudo apt-get install pd-iemlib > definitely working here. pd-iemlib has only been added in Debian/jessie. btw, pd-iemtab has only been added *now*. fmdsar IOhannes signature.asc Description: OpenPGP digital si

Re: [PD] olimex board

On 06/04/2015 10:24 PM, katja wrote: > There's also a way to build Jessie's Pd on Wheezy, described by > IOhannes on pd list. > btw, that way also works to build any external that is packaged for Debian (and many are, thanks to hans) fgmadsr IOhannes signature.asc Description: OpenPGP digit

[PD] [sgn~] bug report

Hi, there's a bug in [sgn~] when the block size is equal to 1! I have an attached patch to show this. Not sure if the list is the best channel to report bugs, I assume there had to be a better channel to report, if such one exists, please tell me. cheers sgn-bug.pd Description: Binary data

Re: [PD] Patch acting weird with Pd 0.46.6

On 06/05/2015 04:24 AM, Jonathan Wilkes via Pd-list wrote: > > For example, looking at a patch... *2 seconds of eyeballs doing their > thing*... oh, there is the fanout. > > vs... > > Oh, _everything's_ a trigger. Thinking... *2-2000 seconds of > thought*... oh, there is the dogmatic trigger.

Re: [PD] Patch acting weird with Pd 0.46.6

On 06/05/2015 04:55 AM, Jonathan Wilkes via Pd-list wrote: > It sounds like Pierre was thinking that trigger would fire > "breadth-first" before starting the next iteration of the loop. ah yes. i think i should mention "depth-first" in my scripture answers. thanks. gfmdsr IOhannes signature.a

Re: [PD] Patch acting weird with Pd 0.46.6

On 06/05/2015 04:24 AM, Jonathan Wilkes via Pd-list wrote: > > If I have a choice to debug a recursive (control) object chain using > my toolkit vs. your toolkit, I'll choose mine. totally. i very much prefer your toolkit as well, as it allows me to blindly answer the question "why is my patch b

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

Re: [PD] slide~ (msp) in pd

no, but it's obviously more inefficient :) it could be simpler if you were to use [change~], that was the tricky part for me 2015-06-07 12:20 GMT-03:00 Peter P. : > * Alexandre Torres Porres [2015-06-06 17:17]: > > the other day I implemented, just for fun, the [cyclone/slide~] object > with >

Re: [PD] some repo house cleaning

On 06/07/2015 11:07 AM, Chris McCormick wrote: On 07/06/15 09:52, Jonathan Wilkes via Pd-list wrote: an alternative plan that'd be great. I think it was Socrates said something about "code > words": I'm using github for the nw.js port atm, too. But I see way less potential for future shenani

Re: [PD] some repo house cleaning

On Sat, Jun 6, 2015 at 9:52 PM, Jonathan Wilkes via Pd-list < pd-list@lists.iem.at> wrote: > Hi list, > tldr; Sourceforge has bundled malware with older Windows binaries for Gimp > and apparently moved an old Sourceforge repo for nmap to a mirror where the > nmap author does not have access. (Sou

Re: [PD] slide~ (msp) in pd

* Alexandre Torres Porres [2015-06-06 17:17]: > the other day I implemented, just for fun, the [cyclone/slide~] object with > [fexpr~], it's 100% compatible to vanilla. find it attached. cheers Great! Did you have a chance to compare cpu useage between the two? ___

Re: [PD] Problems with maintaining Pd-extended (was Mess and redundancy...)

On 07/06/15 20:38, Roman Haefeli wrote: > On Sam, 2015-06-06 at 12:37 -0400, Dan Wilcox wrote: >> To save extra discussion energy and *possibly* let the “cat out of the >> bag” let me say this: just wait a bit, something good is in the works >> to offer a solution to many of these problems. > > I

Re: [PD] some repo house cleaning

On 07/06/15 09:52, Jonathan Wilkes via Pd-list wrote: > an alternative plan that'd be great. I think it was Socrates said something about "code > words": https://github.com/pure-data/deken Cheers, Chris. -- http://mccormick.cx/ ___ Pd-list@lists.ie

Re: [PD] pow with negative numbers

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi claude, thank you for the enlightenment. m. On 2015년 06월 07일 09:57, Claude Heiland-Allen wrote: > On 07/06/15 01:38, Chris McCormick wrote: >> So the "**" operator behaves differently from "pow(x, 2)". > > It's more likely that: > > - x ** 2 > >

Re: [PD] Nettles. Was: cyclone/maxmode functionality usage

yeah, I can't load these objects for some reason, I wonder why is that, I'm on mac os and extended 42, any idea? I didn't know they were in cyclone... But I remember we discussed about them, not all of them are part of zexy actually. Zexy's only got 3 out of these, whixh are: <~, >~ and ==~ It do

Re: [PD] Problems with maintaining Pd-extended (was Mess and redundancy...)

On Sam, 2015-06-06 at 12:37 -0400, Dan Wilcox wrote: > To save extra discussion energy and *possibly* let the “cat out of the > bag” let me say this: just wait a bit, something good is in the works > to offer a solution to many of these problems. I'm looking forward! Roman ___

[PD] Nettles. Was: cyclone/maxmode functionality usage

Hi Alexandre, The nettles are the cyclone bin-ops objects we discussed before: !-, !/, ==~, !=~, <~, <=~, >~, >=~, !-~, !/~, %~, +=~ They are part of the cyclone library object, which may or may not be part of your distribution. The source code is in externals/miXed/cyclone/shadow/nettles.c, hence

Re: [PD] haversine formula in Pd

some people were saying expr does internal double precision calculation, is it true? i dont think so... 2015-06-07 3:10 GMT-03:00 Cyrille Henry : > > > Le 07/06/2015 04:48, Max a écrit : > >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Merci Cyrille, >> >> in the formula the intermedia

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 alre

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 gen