[BUG] App crashing before UI loading - new hints of the root cause

[CoffeeList1278]

Before you make a new bug report:

• Have you searched the Issues to see if your problem has already been reported? If it has, please follow that Issue instead of opening a duplicate!
• Have you checked the Rough edges for help?

Description

The NAM standalone app crashes instantly on startup with exception code 0xc0000409 (STATUS_STACK_BUFFER_OVERRUN) before the GUI comes up.

To reproduce

Steps to reproduce the behavior:

1. Encounter the problem as described in README.md (I don't really understand the root cause)
2. Try running the Gateway_x64.exe
3. Open EventViewer -> Windows Logs -> Application
4. See an Application error from Gateway_x64.exe

Expected behavior

I expected the Gateway v1.0.1 to open and work flawlessly as did the NAM v0.7.13 I used previously.

The fix

I investigated changes between the configurations and found out that there is a difference from the old version config. I copied over the whole config from the NAM v0.7.13 settings.ini into the settings.ini of the v1.0.1 and the Gateway started working. I didn't even attempt to do the fix described in the readme as the issue no longer comes up.

After further investigation, the issue is solved by changing the default value for driver=0 to driver=1 as is used in my older version.

When I manually select the first driver option and my interface in the GUI, the app instantly crashes. The device names for the ASIO config seem to be different too. It looks like the root cause might be in trying to access non-existent driver-device pairing.

##Screenshots

The left config is the functioning one, the right one is the malfunctioning stock one. The left config is the functioning one, the right one is after manually replicating the error. The left config is the functioning one, the right one is after manually replicating the error with the stock device option.

Computer & other info

• OS Windows 10
• Onboard graphics & version GTX 1070ti
• Plugin version 1.0.1
• Standalone
• Audio interface M-Audio M-Track Duo
• Sample rate 44.1 kHz/48kHz (makes no difference, I tested it)
• Buffer size 128/512 (makes no difference, I tested it)
• Does the bug not happen under some other conditions? Changing the config driver setting as described above.

[CoffeeList1278]

I also tried to run it with the functional config with the driver changed to 0. Once it came up but made strange noise instead of the correct sound output, but usually it crashed instantly.

The left config is the functioning one with driver value swapped to 0 before running Gateway, the right one is the version that Gateway saved after the GUI edit. The difference from the stock config seems to only be in in2=1 in the new one, suggesting that the missing second input in the driver 0 device is the root cause of the whole issue.