< Back to IRCAM Forum

Direct sound doesn't work with parallel 1 attribute

Hi,

I noticed a problem setting the spat.spat~ in parallel 1 mode in 4.9.1.
If parallel attribute is set to 1 and you turn off the reverb of Spat, nothing comes out of the spat.spat~.
Is it a known bug or it’s like that only for me?

the bug is showed in the pasted patch. Could you verify it?

Max 7.3.1 (running 32bit or 64bit)
Spat 4.9.1 (Build May 18 2016) (32 bits float)
OSX 10.11.6 (El Capitan)

  
----------begin_max5_patcher----------  
1414.3oc6a0zjahCD8r8uBUT6gjpl3BIAF64T1beus0dY1TSICZrUFrvkPLe  
jTI+1WgDfwdvdDLwZ9XmCAajTDu90s5903jeLdj2hr6n4dfyAW.FM5GiGMRO  
T4.iptej2Zxcwojb8x7hyVulxkdmYlSRuSpGOeCQNIaCUbN3enhbVFGDLY9D  
H3Ceofkl.9Kx8.3L.xGN8ifOfQfELYN3pzLh7i+qnd6XI5MKaw29Tvr5A4Eq  
Y7TpTC.X0fpGW7JFe4kBZrzX.A3oS7OCD.8K+.MSeGb1DevW2tSYEx5sxuZz  
b48oT8y0qbfeNdb4kyrjPVSyyIKoOfPtwvBcYYS6zxPG1xvgZSBZ9HPaXH+C  
ZX0bjYH48anlswyq4uvSyloeOgD+qtLsfdaZQZaBO2XZg0WOo9rCED6OA72E  
BNPE7RJRXY0K3pLtLm8c8CDFLwuCCG12nUbfwmZtVFlp7onmICmmIo.4JJ3y  
aHBRZJME.ADoTvVTHahsSYbZbVAW11md.tYQwhEozMYLyp86jz781Y04rDZ6  
s1VpLxDCAmAmD1bJILpEWZ1+1aiKY2fI.Y1xkoTcfEOAjc0UZ1VPUYIVbNf0  
9V.KGn7G.RrjcC8rxYDTyffbE6mnbL5kqv+lBoZy.5jukW9UmtJr0gw3o8ML  
Nzjz03APUTO9YJLFqH5pyuxUJFaMUJxFRzaaJIp20gLrfgRlYRuM6YhQPOZn  
mDbal357mJKE1WVBFzhkpNy9rQSvSQfSPuKI393FSvQGUxQndmI.YbkFq.ET  
e8QDoTVvQQ2TwkTNoJIs+gDvnql70SptMQV15xhe5ruf+.1E2f6qJmZtox2N  
+4V.GmdqxPdfsWppSY6H.FDzkc2cDcviZ23o6nxw+DGTmp7bSVRX7lxg2PDb  
UT1dydA7q0KHeU1s0qnFDaDzbUxBhTIiusMAiL05v5ZclJdsEt0lwZRKFuhv  
4zzcHrdxhHiFYj44GdXshQG4nUSnkfUaaGMhKmsjSR8N6w9V4ezcyU9kTVdq  
yoworMW1jqrlvI2PStrQh41ukW4Xq7rk9tzBZ1U0CWOdayKMiu7n92cVsxWK  
jcr7tVaMS32wbqUdux49TTi518lmniRm14rLNSxTbmllachXmEUnVTyYg.y7  
5CC0e7aKc+zApx40R59CjwSWnWcH1uKNIpuo4q4DSZ9vYCMM+BBe4I1vUGJi  
utqV3QyFXj.xupS9gZ0UISNs181Vk.eVgKUCUhXZNHvb2FJ4ZpPe61Fg6hjl  
OvJgHro3wLzCXoREkMYk9SgJ2.3KYoIdcRhgO470cQy6jaVYmJzejDycdTd3  
4lNlCq7EKdT+UG9Hr+.UvVEHiPvmlOBePUbU0Ke44CNX8AXz.6u6+AsC.C6a  
chZt40c6.PXeSBVY2UsCLO5EU2.CnU.sYr8xg5B.5+6nKfJxqpK.XT36cAXU  
W.u2Bfco3mOrWW0a3F.5s9e7qe4+SGVTvaJw+cI3efk5p06il9td+Srde3.U  
n9FTtu9Ao+cK16eaGZVnb7c8KFVtBtU0B.aogDZtjwaTIbQS1wVqYEKIgxam  
LOgkWBwjFL9f3CaQSjEnYpyPyTKPCxYnIvF3.cFbJa59wYm4NCOHahjKeK8t  
DOPavCzc3AYCdPtCOXavC1M3Y1Kr3YaxEtGnOo3wprgtqTwdGkO.dBbKdf1f  
Gn6vCxF7fbGdv1fGGcdGaQ7ydE4No3AYS7L1c3wF0F9NENPafCzYvAYCbPNC  
NXafiaNaAso1EzcZwfgunjNCsQ5Lzw3AZCdftCOHavCxc3AaCdbzwqSXeolW  
n.Yyl5+WMTBkRf3sl7sLQyO2f2ZF2bq9sg3In2vxa+iK3QDwqXRZrrPXdCH2  
My7JG8VmkPE7BldsiKex+b7+AgFvzTA  
-----------end_max5_patcher-----------  

Hi Lorenzo,

Yes, something is broken in parallel mode in v4.9.1.
(I think this was already reported here).
This is fixed in the internal release (v4.9.2 – which should become public someday soon).

T.

PS : anyway, dont bother with @parallel if you have only 4 sources.
If you have, say, less than 30 sources, @parallel will probably not be very effective. (if not counterproductive)