[SPARTA Panner] if real source channel index exceeds some number, Reaper crashes.

[mtmccrea]

When loading a loudspeaker configuration, it appears that there is an upper limit to the channel ID of a non-imaginary speaker ("Channel" in the JSON file), beyond which Reaper crashes.

This doesn't seem to be a problem if the speaker is imaginary (i.e. "IsImaginary": true in the JSON file).

Example: I have a 76-channel array. 38 are real, 38 imaginary. If the real channels are in the first half of the configuration (channels 1-38), it loads fine. If the real channels are in the second half (channels 38-76), reaper crashes when the config file is loaded.

Narrowing down a bit, I took the breaking case (channels 38-76 are real) and trimmed channels until reaper didn't crash. Real channels up to Channel ID 69 are OK, but breaks at 70. Changing Channel 70 to be imaginary and it works again.

The 4 attached config files illustrate the above cases (GItHub required them to be .txt so should be converted back to .json). ls_config_VBAP_38real_70okIfImaginary.txt ls_config_VBAP_76ch_secondHalfReal_BREAKS.txt ls_config_VBAP_76ch_firstHalfReal_OK.txt ls_config_VBAP_38real_69ok.txt

I'd say the max Channel ID of a real loudspeaker is 69, but that number may just be 'magic', in that it could be somehow related to the total number of channels, number of specified track channels (I'm using 38 or 40), or something specific to this configuration and how the triangulation/inversion is performed in by SAF.

Panner version 1.5.8 Reaper version 6.26

[mtmccrea]

It also seems that it's sensitive to the order that the Channel IDs are listed in the .json file.

I regenerated my loudspeaker configuration such that the real channels are always in the first half of the Channel IDs to remedy the problem originally listed. When Channel IDs are listed in order (real channels 1-38 precede virtual channels 39-76 in the json file), the config loads fine. When virtual channels are listed first (virtual channels 39-76 precede real channels 1-38 in the json file), reaper crashes when trying to load the config.

In both cases, the corresponding entries ("Elements") are identical, it's just the order of the entries in the json file that differs.

Test files attached. ls_config_VBAP_ls_76ch_firstHalfChanIDsReal_realListedFirst_OK.txt ls_config_VBAP_ls_76ch_firstHalfChanIDsReal_virtualListedFirst_Breaks.txt

[leomccormack]

I'll give them a go :)