[PD-dev] [ pure-data-Bugs-3599983 ] vbap 1.0.3.2 fails when sent longer "define_loudspeakers" me

[SourceForge.net]

Bugs item #3599983, was opened at 2013-01-08 11:42
Message generated for change (Tracker Item Submitted) made by nobody
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=3599983&group_id=55736

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: externals
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: vbap 1.0.3.2 fails when sent longer "define_loudspeakers" me

Initial Comment:


Using Pd-0.42.5-extended.app, Pd-0.43-3.app, and Pd-0.43.4-extended-20121101
on OSX 10.6x and 10.7x,

vbap 1.0.3.2 crashes when sent longer "define_loudspeakers" messages


the PD console displays: vbap: Loudspeaker setup configured! pd: getbytes() failed -- out of memory vbap: Configure loudspeakers first!
and the program crashes.


(It appears to be failing in the "vbap_matrix" method.  But, perhaps, the data sent to that message is already bad).



Following HCS's suggestion, 

I tried doubling both MAX_LS_AMOUNT as well as MAX_LS_SETS.  Now the program does not crash, vbap fails each time:  when sent the define_loudspeakers,   the PD console displays: 


"vbap loudspeaker-matrices: param 475 is not a float."   (from vbap_matrix method)


Things I have noticed:

--The above param number in the error message will be different each time pd is relaunched and a new attempt is made. 
--increasing MAX_LS_AMOUNT and MAX_LS_SETS 10 times introduces intermittency:    Some times the same error message above will be displayed,  sometimes it the define_loudspeakers message will succeed, and VBAP will function correctly.
-- occasionally,  a different error message in the pd console will result:
"Dimension can be only 2 or 3" (from vbap_matrix method)

--And of course, the problem does not manifest when smaller configurations are used (i.e.  shorter define_loudspeakers messages).



I wrestled with the problem for a long time without getting any further.  Maybe you, or someone out there, will have some greater insight into this problem.  Any assistance or additional suggestions would be greatly appreciated, since the problem above comes with the latest pd-extended.  


Below is the the vbap message that provokes the problem:


define_loudspeakers 3 0 90 -7.5 55 52.5 55 112.5 55 172.5
55 -127.5 55 -67.5 55 7.5 20 37.5 20 67.5 20 97.5 20 127.5 20 157.5
20 -172.5 20 -142.5 20 -112.5 20 -82.5 20 -52.5 20 -22.5 20 7.5 -15
37.5 -15 67.5 -15 97.5 -15 127.5 -15 157.5 -15 -172.5 -15 -142.5 -15
-112.5 -15 -82.5 -15 -52.5 -15 -22.5 -15



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=3599983&group_id=55736