Hi António,

sorry to hear that you're facing problems. I was testing the raw Ambisonics Output Formats extensively, so there must a specific reason for these crashes on your system.

Please get in contact with , with reference to this thread. Include as many details as possible (ideally you let the Vienna Assistent create a report), and please also include an exemplary project (preferably Nuendo) that exhibits the issue. I'm sure VSL's developers will sort out the problem quickly, :-)

TIA,

Hi Dietz,

VSL's support staff was able to reproduce the bug that I reported. We'll see what comes out of it.

All the best, António

Thank you very much for the report!

Could it be that you are trying to set an ambisonics configuration (minimum channel count would be 4) to a channel with stereo configuration? This would explain why it missed our attention. This configuration doesn't make sense.

I am adding safeties for existing sessions with this wrong config and will make it impossible to choose an ambisonics configuration if the host channel's channel count is not enough.

In the meantime if you need to use raw ambisonics, please make sure to add the mir plug-in to a channel strip with enough output channels.

Best,

Konrad

Hi Konrad,

I don't understand your proposed solution to it at all. I can do what I reported with every other surround/immersive preset, and I could do it in all previous versions of MIR Pro 3D. The only surround/immersive preset that doesn't work that way now is raw ambisonics.

As a side note, it seems entirely arbitrary to say that the minimum is 4 channels, especially given that it worked in every version before.

All the best, António

Hi Antonio!

Sorry for the confusion. Allow me to clarify and be more specific:

Originally Posted by: inthefold

I can do what I reported with every other surround/immersive preset, and I could do it in all previous versions of MIR Pro 3D.

There is a fundamental difference between raw ambisonics output and the classical formats.

For the latter, MIR takes over all of the processing and decoding into different capsule formats, microphone positions and so forth. What you also get is a submixer that allows you to up/down mix into your actual channel configuration. This submixer can be found in on the right side of the Channel Configuration Editor. Especially if you have more capsules than available channels, this step is absolutely necessary. And also makes perfect sense in a lot of circumstances.

Now the Raw Ambisonics Output is different:

Here, the user has to do all of the ambisonics processing on her own. You don't get any decoding into say classical stereo or immersive formats. This is why you absolutely need to set up MIR's output channel count so it has at least:

- 4 channels for 1st order ambisonics

- 9 channels for 2nd order ambisonics

- 16 channels for 3rd order ambisonics

Those channels have to be available, because you as a user have to have a proper ambisonics decoder plug-in after MIR. And this plug-in needs all of the channels of the respective Ambisonics order to make sense of the signal. So adding any form of down mixing in MIR's own processing chain would not work (in case of Raw Ambisonics output)

You are right that this wouldn't make any sense and seems very confusing. But I have to admit that part of the Raw Ambisonics processing chain was broken in previous versions of MIR: The part that handles the dry signal processing. It is for example responsible for handling instrument or microphone rotation. It was broken for previous versions so your dry signal would not be processed at all. It wouldn't crash however ... but ... it also wouldn't work correctly.

I would expect the following for the current version: For an immersive format (say: 5.1.4) with a high enough channel count, order 1 and order 2 would not crash (because there, MIR can output 10 channels and it only needs 4/9). But third order (which requires 16) would crash. However, I would recommend to add MIR to a channel with the proper ambisonics configuration.

I hope this background info is useful and not too confusing :) 

All the best and thank you again for pointing me to this bug!

Konrad