Group Admins

  • Profile picture of warusfel
  • Profile picture of T.

Spat

Public Group active 1 week, 2 days ago

User group for Spat, panoramix, ToscA , and ADMix

spat.spat~ set listener message bug

Author 2 Subscribed Users |
Profile photo of polyrhythmic
polyrhythmic

Hello,

I’m 99% sure this is a bug. I’m trying to set the listener position and when I send a message to spat.spat~ such as

“listener rpy 30. 30. 30.” or “listener pitch 30.” or “listener roll 30.” I receive these errors:

“invalid message: listener rpy 30. 30. 30.”
“unknown coordinate type”

I have no issues with setting the xyz and yaw values independently.

The documents seem to show that setting rpy, pitch, and roll should be possible.

Are pitch and roll just not supported at the moment?

August 23, 2016 at 03:19 #18851
Profile photo of T.
T.

Hello,

Let’s see it another way:
In spat~, the only situation where moving/rotating the listener would be meaningful is headphone-based rendering (binaural), assuming you have some head-tracking device.

Yet, for the spat.oper and spat.spat~ objects, the listener MUST remain in the central location (0,0,0).
Indeed you can notice that it’s not possible to move the listener in the spat.oper interface.
So, the only proper way to simulate listener’s translation/rotation is to convert the sound scene from the (0,0,0) perspective.
The easiest way to achieve that is to use the spat.abs2rel object.
The attached patch illustrates that: The spat.viewer window represents the sound scene in an absolute perspective; in this perspective, you can freely translate/rotate the listener. Then everything is converted (and rendered) to a (0,0,0)-relative point of view.

In this patch, roll, pitch and yaw messages are supported.
Please note however that only the “yaw” angle is visually depicted in the GUI.

— Pasted Max Patch, click to expand. —
August 23, 2016 at 12:07 #18859

You must be logged in to reply to this topic.

Log in now