Hi all,
I’ve verified that the spat.oper doesn’t compute delay times following the source distance from listener.
To be more clear: two copies of the same source, one placed near and the other at a very great distances reach the listener at the same time.
I’m wondering if in the Spat environment is there a way or an auxiliary objet to calculate that.
Thank you
Hi Lorenzo,
Indeed this is a severe bug: the source delay is only applied if Doppler Effect is ON.
I dont know when this bug was introduced… I’m investigating.
Anyway, it will be fixed in the next release.
In the meanwhile it’s pretty easy to use other objects to do that.
Attached a simple example patch.
T.
----------begin_max5_patcher----------
1254.3oc0YssaaiCD8Y6uBAg8oEoY0M6HuO086HnvfVhVlsxjBjzotMH8ae4
MoHJKYyHeANOTqzgTjGdlKblQuNch+JxdHy26e8d1axjWmNYhRjTvDy+eh+V
v9rR.SMMeL7mjUe2+A8Pb3dtRbkWFYa0NNbYNhwA3LX8Tp.7rMHbwRJLiq2o
nvfGCdvKZt5QXvB0Cwudey7RqIXNFrEpV6+ih.k0KGJWISfguDtnVHd2VDtD
xUPLr0ZvP+VsFgghsnYtjc7tSVKh+qJnFh99MXQc.fTCmXHEwxiJgu.oLDA2
Zgl3CppZIdRqWQxjemnVn4OzHBg0hBaDQgufpe+EMRATAMxEb3NplV1mN2WO
3aSq27Vb7LIo9jhgmmndjjF7NEKzyEkjre.U7YPsPREDivUTHCh4.tAEMCmC
WC1UxW1O2ZO9ZPFbvWtWk6D+BJJmfkfv5Mkhq2tm8BMlMsOLpYfAU87xByQ9
N1J.UxpqJUKRT8fbBozdnFEovO.fQaAbHGoAaTPyhh1VQQXt0FAw.wZrgkQI
kkVKkdjW5YjbgtNC9STNeiZsZSkhoippUA9MbTNp.x31x3fBlsDKG61Fgscv
sjeLGcamclvk3wLBVXmyENFslRON6gyzpqX0izft95G2euqO+h1x6ys+Ht98
39mzZjCBAvH6nx3XxCLD7CgSs7uU+yB7LvKv7kBzINyKAbNEsRDHj0hiaQxR
NhJNoBhao1rPo2aF+soS69WB26qjNrSr5SnBEl+pXJyNOU37AUgQWbUXiB6S
jRaKjw.Evd0ZYkP.8AOJTxzdgdgsmUIBCyH6zQkhNtJ0xoTeKQzn0nQKtrpz
vipR891swCoj.xWAvE9NwjZeiYyOOei3fKa7sixjpC2shMUwaL1secKIG5UG
d0oaOzlngIKNO9MJ8xxuwNE74SRfGEW3l9PmPoNGS4uVmv1on+zf783c+aMr
nnisPrIYnKHUn2VGuV7oENRFtY7YSFAefS66oCKuJXfr+TGD438SCFuRMYWG
Rxy9LIRMkivMUG7762BzYhaP441YiqSfkIsjysLkOpR6ih4dfx.XN89AyoNh
442MP9SHKKCH4DlueLlm6HhCuTrrIkf5tJbpard8BU6+o6svGnf3dAwQ17g1
zhRxJPooEPMuaO0cO8cRT8qVy6RG0pip2skZZCAQR94vRvu7PXusLX1wZqlt
eZIQlbkz2NE+gaqVcAZ9qoEqr5JwYznsZosasjE1iz4UndDX9oA3q1spt8Li
fgGpmkTXEDma32vS2vxDc2KRGa+Jmcc6W4HXl0kDw56vIWaSMKXjm7j22hdR
m8rYkngXEw4Cvk4fap04DFg5NQmDDXaDd4L4f6qnd+05Pu+VVwXvid+iWbR7
imVADuPS8gi01K9ty1a.JR2XJoK4e79p..Ya.XLrj4hC5Lc+LBOrLbGYoH+q
msHCUfk6Z6usfiWsNbQfWoabL8ETcoibeYm9ZmX88Mg5.4i3Zmvq40Nm2EHt
FlzvAiMLY5cRTxKryLoBRUtxZ6Km7jMclzjDyH7jOeG43AC20suNWX2X0xZW
BuVEzsxAih3vhbZWHvPUKXUfygUJbXUBGXQ3LbV3.dRucvYlKzSzsCOItfmY
2N7D6BdRtY3I0E3DOR3n8057M6kHoy2puy2o+vuQ+Peedw971z+mYizDX
-----------end_max5_patcher-----------
Hi again,
Second thoughts: it turns out it’s not a bug, but rather a (historical) design choice.
We’ll communicate later on that.
For now, if you need to delay the source signal according to the distance, either turn Doppler ON, or use a patch similar to what I sent.
Sorry for the inconvenience,
T.
Hi T.
I’m in London now and we made the delays with the mixing desk, of course only for the fixed sources.
It would be fine if the delays will be computed by the system, because with that you can realize transparent amplification when you place the musicians with the spat in the hall or otherwise realize some fine spatial effects with movements in the space.
It can become a new attribute, isn’t it? Just like Doppler: something like “compute delays with distance”
I’ve not tested the panning type dbap (I had no time here, but I will test it as soon as I’ll work again in another big hall like this one).
Thank you for the quick replies !
L
Hi T.
interested in knowing if my proposals for a “compute delays with distance” attribute could be considered for future releases.
Keep me informed
ciao and Thanks for your replies
Hi Lorenzo,
Yes, something similar might come out in the next releases.
T.
Thanks Thibaut,
It will be very useful for my projects.
cheers
L