Re: [PD] zexy compilation issue with msys2
Try the attached patch. On Monday, March 21, 2016 10:43 AM, IOhannes m zmoelnigwrote: On 2016-03-21 15:38, Jonathan Wilkes via Pd-list wrote: > Yeah, I can do that. I'm not sure why it would fuzz, as the only changes are > inserting A_CANT. most likely because i'm trying to apply the patch onto another version of zexy than you. fgmasdr IOhannes ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list 0001-add-A_CANT-arg-to-dsp-methods.patch Description: Binary data ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] Edit Pd file to change coordinates. pdlua or other language?
Hi Fred, thanks, that looks promissing. But there is a problem, I'm on windows. Does the first line in the patch means that I have to find a unix computer to run it? Or can it be run from tcl? Best, Joao Hi João, It appeared to be a simple program in Tcl, which you should have, as it comes with Pd. The usage is: tclsh changeCoords.tcl patchName xcoord ycoord line1 ?line2? ... lineN arguments may be a number or a range, like 12-15. The patch is currently dumped to the console. Only minimal checking is done. If you remove the #'s for the puts "..." lines, you can see some interim results (which will ruin the patch format). Greetings, Fred Jan ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] [Bug]Dynamic Patching causes memory leak
OK... might be fixed now - thanks for flagging it. Miller On Thu, Dec 31, 2015 at 06:35:51AM +0100, Zack Lee wrote: > Hi, I found out that dynamic patching causes memory leak or overloading the > CPU usage. > > Which means, if you create and delete an object many times by dynamic > patching, at some point, the CPU usage will be overloaded and you will hear > the glitch in audio. > > I tried to find a way to fix this issue, but so far the only solution seem > to be to close and re-open the patch. > > I have tested this with both pd-0.46-7 and pd-extended 0.43.4 on Mac OS X > 10.10.3. > > I attached the test patch below so please check and see the problem I > mentioned. > The file name should be "test.pd", so please change the file name if it > changes to a different name once you download it. > > -Zack > ___ > 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] Edit Pd file to change coordinates. pdlua or other language?
Hi João, It appeared to be a simple program in Tcl, which you should have, as it comes with Pd. The usage is: tclsh changeCoords.tcl patchName xcoord ycoord line1 ?line2? ... lineN arguments may be a number or a range, like 12-15. The patch is currently dumped to the console. Only minimal checking is done. If you remove the #'s for the puts "..." lines, you can see some interim results (which will ruin the patch format). Greetings, Fred Jan #!/usr/bin/env tclsh # if {$argc < 4} { error "Usage: tclsh changeCoords.tcl patchName xcoord ycoord line1 ?line2? ..." } set patchName [lindex $argv 0] set xcoord[lindex $argv 1] set ycoord[lindex $argv 2] set lineArgCount $argc set lineList {} #puts "patchName $patchName; xcoord $xcoord; ycoord $ycoord lineArgCount; $lineArgCount" # line arguments may be numeric or a numeric range "nn-mm" (inclusive) for {set start 3} {$lineArgCount > $start} {incr start} { set arg [lindex $argv $start] #puts "$start: $arg" if [regexp {(\d+)-(\d+)} $arg lineRange startLine endLine] { if {$startLine < $endLine} { #puts "startLine $startLine; endLine $endLine;; $lineRange" for {set line $startLine} {$line <= $endLine} {incr line} { lappend lineList $line } } } else { #puts "line $arg" lappend lineList $arg } } puts "lines to patch: $lineList" set lineCount 1 set f [open $patchName] while {[gets $f patchLine] >= 0} { if [regexp {\#[ANX] } $patchLine] { if {[lsearch $lineList $lineCount] >= 0} { if [regexp {\#X obj (\d+) (\d+) (.+)} $patchLine allOfLine orgX orgY restOfLine] { #puts -nonewline "$lineCount: " puts "#X obj $xcoord $ycoord $restOfLine" } else { #puts -nonewline "$lineCount: " puts $patchLine } } else { #puts -nonewline "$lineCount: " puts $patchLine } incr lineCount } else { puts $patchLine } } close $f ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] zexy compilation issue with msys2
Yeah, I can do that. I'm not sure why it would fuzz, as the only changes are inserting A_CANT. -Jonathan On Monday, March 21, 2016 5:58 AM, IOhannes m zmoelnigwrote: On 2016-03-21 10:50, IOhannes m zmoelnig wrote: > is there any specific reason to not use v2.2.6? also: would it be possible to send the patch in a format that `git am` recognizes? $ git am /tmp/acant.patch Patch format detection failed $ git --version git version 2.7.0 fgmasdr IOhannes ___ 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] zexy compilation issue with msys2
On 2016-03-21 15:38, Jonathan Wilkes via Pd-list wrote: > Yeah, I can do that. I'm not sure why it would fuzz, as the only changes are > inserting A_CANT. most likely because i'm trying to apply the patch onto another version of zexy than you. fgmasdr IOhannes signature.asc Description: OpenPGP digital signature ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] ASIO SDK
On Sun, 2016-03-20 at 23:42 +, Jonathan Wilkes wrote: > That's a good reason for doing a physical release of the GUI port on > CD ROM. I know you are joking. Still, let me put it this way: They want you to show their ASIO logo everywhere you provide your software, on the physical package or on the download page. Roman signature.asc Description: This is a digitally signed message part ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] Tests -- Pd 0.46-7 Microsoft Windows (installer)
On Sun, 2016-03-20 at 22:27 +, Lucas Cordiviola wrote: > Tests -- Pd 0.46-7 Microsoft Windows (installer) [...] Thanks for the detailed report. I didn't have a chance to test on Windows 8.1 yet. I'm glad to hear that there are no major obstacles. I might be able to test on Windows 10 soon, too. Roman signature.asc Description: This is a digitally signed message part ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] zexy compilation issue with msys2
On 2016-03-21 00:10, Jonathan Wilkes via Pd-list wrote: > Before I pin to a newer version, here's the only revision I could find from > Pd-l2ork that needs to be merged upsteam. It just adds an A_CANT arg to the > "dsp" method of signal objects for the off-chance that a user sends a > "dsp" message manually. thanks for the patch. however: against which version of zexy is it supposed to apply? i tried both git-HEAD, the v2.2.6 release and the last master branch in the svn (before i dumped it) and the patch fails on all of these. i also tried it on v2.2.5, where i at least succeeded to apply it, but still with some fuzz. is there any specific reason to not use v2.2.6? fgm,asdr IOhannes signature.asc Description: OpenPGP digital signature ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list