Closed meta-meta closed 4 years ago
I've started implementing a customization of the OSC output format. I still need to implement the preset management. Although, custom output can be set using the GUI and will be saved between sessions. Just compile the latest code. No binaries yet.
It allows for using a quaternion array output, single ypr's or 3 member ypr array. The order of the arrays can be configured. Min and max values can be set as well.
Cheers, T.
I would like to have 2 independently headphones for mixing 360 with a partner. I can connect 2 trackers to 1 PC, load 2 instances of the OSC Bridge and see both trackers working simultaneously. There is no way to differentiate between the two instances in Reaper.
Being able to set an OSC port for each instance might allow me to create another OSC device in Reaper and I think in general is a desirable feature.
Another approach which is more flexible and perhaps more reliable (I'm not 100% sure that separate OSC devices in Reaper won't clash when using the same OSC address) would be to customize the OSC addresses for yaw pitch and roll.
Bonus points: This almost opens up the opportunity to bypass Reaper's OSC learn and use SPARTA AmbiBIN, though it looks like they also expect a 3 member array at
/ypr
: http://research.spa.aalto.fi/projects/sparta_vsts/plugins.html So being able to choose between separate messages for each coordinate or an array at 1 address would be another nice feature.