Great to see bob~ already out.
since I was already working on it for 0.47
BTW, when is 0.47 planned to come out? Is it the next scheduled release? I suppose it is unless some fast and important bug fix needs to be made, right?
I have one easy fix for it that you can work on, we're still missing a help file for the [vnsapshot~] object, it'd be nice to have one in the next release, whenever and which ever that is.
I'd also like to remind you about the paf~ external that we were discussing here a while ago, you were saying you could bring it back now that the patent is over, let me remind you that the F13 example still mentions the existence of this object, this also seems like an easy fix for the next release.
Moreover, I got a few suggestions that you may consider for 0.47, let me give you the full list including the 2 above:
Easy fixes:
help file of [vsnapshot~]
[paf~] external
Suggestions for 0.47:
[env~] could have a second outlet for peak amplitude.
be able to set [lrshift~] by messages besides argument.
[bang~] doesn't work for block sizes smaller than 64, it could ideally
work for block sizes down to 1 sample (we were discussing this earlier in the list).
Thanks for the update cheers
2015-03-22 19:32 GMT-03:00 Peter P. peterparker@fastmail.com:
- Miller Puckette msp@ucsd.edu [2015-03-22 16:30]:
Oops - that's the second time I made this mistake - I was unwittingly committing to a branch in the git repo. Try it again (I hope it's fixed now).
Perfect, works great! btw, in my case a make install inside bob~s source directory created a folder /usr/local/lib/pd/extra/bob~ that had no read nor execute permissions set for other (all) users. Is this expected and standard behavior?
Thanks, Peter
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list