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 support@vsl.co.at, 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,

PS: VSL's software engineers are on stand-by already, waiting for your reproduction steps.

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

@inthefold said:

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

Nice!

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 Dietz,

every time when MIR is starting up there is now a reminder, that an update is available, if the latest update is not installed. There is only a choice between "Remind me later" and "Install". Especially now it's too easy to click the wrong button and install an unwanted update as long as a known bug is under development. Wouldn't it be a good idea, to give the user the option, to switch this automatic update search off in the MIR preferences?

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

PS: the bug also applies to multi-channel output tracks.

Hi Antonio!

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

@Another User said:

the bug also applies to multi-channel output tracks

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

Hi Konrad,

Thank you so much for the detailed response, I now understand the inherent limitations you were referring to. I wasn't aware that MIR Pro 3D didn't downmix raw ambisonics like it does the other surround/immersive formats.

All the best, António