Standalone can only use interface's input 1 for mono input

[rakeshcoresoft]

I have Focusrite Scarlett Solo 3rd Gen as my audio interface. It uses Input channel 2 as Instrument input. It is not possible to select input channel 2 in NAM Standalone GUI. Please add this feature.

[danielbeutner]

I do have the same problem with the arturia minifuse 2. Only channel 1 works for NAM standalone and channel 2's volume seems too low.

[seve54]

I do have the same problem with audio ìnterface Terratec Phase 22

[jonlinnarson]

Same here. Even if I select inputs 3&4 in the preferences of NAM, I'm still hearing the signal from inputs 1&2 (RME Babyface Pro).
The strange thing is that everything has worked fine with v0.5.0 and v0.7.0, so this is a new problem that appeared in v0.7.1.

[DungeonDev78]

Same problem here :( Input device is just Scarlet Solo USB without input 1 or 2.

[karymus]

Same with M AUDUO SOLO.

[sdatkinson]

This should be fixed with #166 and will be available in v0.7.3.

[sdatkinson]

Bad news I'm afraid: the fix breaks support for folks with single-input interfaces.

It's a tough call, but I've reverted the fix for this. I'll have to ask folks to continue to sit tight on this one while we work on getting the right fix in.

[nmontua]

Would it be too messy to have two builds for the time being?

[sdatkinson]

Would it be too messy to have two builds for the time being?

I've strongly considered it.

The reason that tipped me to the "no" side is that it'd open me up to potentially a whole other source of bugs to have to field, and it might be especially hard to get folks to provide the needed information (which version they're using). I just don't think I could handle it.

[nmontua]

Would it be too messy to have two builds for the time being?

I've strongly considered it.

The reason that tipped me to the "no" side is that it'd open me up to potentially a whole other source of bugs to have to field, and it might be especially hard to get folks to provide the needed information (which version they're using). I just don't think I could handle it.

Fair enough, that makes sense to me. I just thought I'd ask.

[RocklandSally]

I should have come here first .. lol.. yep.. same problem with ONLY the standalone version of NAM... within Reaper you can specify input #2 ... thanks for everything @sdatkinson

[twynfeyr]

I can see you've identified the problem and a solution is incoming, but I'll add my interface to the list in case it matters in some way. Steinburg UR12.

[olilarkin]

this is an iPlug2 bug, please add the iplug2 label!

[jonlinnarson]

this is an iPlug2 bug, please add the iplug2 label!

Does that mean that Steven can't really do anything about this issue?

[sdatkinson]

@jonlinnarson kind of.

Technically, I could fix the problem in iPlug2. On one hand, I'm not an expert in the framework; on the other hand, I can reproduce this Issue myself, which makes a huge difference in how hard it is to figure out what to do about it! 🙂

[splisp]

Yes, that's really unfortunate. I have a Yamaha AG03 which has an hi-Z instrument input on channel 2 and it cannot be selected. I have also entered another issue on iplug2's preferences dialog a few minutes ago.

[olilarkin]

FYI: I'm working on fixing the standalone app I/O here: https://github.com/iPlug2/iPlug2/tree/app/flexible-io

[Gimmee99]

+1 on getting a fix from me. I have the Tascam 16x8 interface and port 1 in an XLR input. 1/4" inputs don't start until 9.

[fatgonzo]

Having the same issue with Steinberg UR22, ideally would like to use input 2 for both channels.

[Gimmee99]

@sdatkinson Do you know if there is a specific bug for this in the iplug project? I see above where someone says they are "working on this" with a link, but I think for me that just links to the general project and not a specific issue. I have some experience with software engineering and might be able to either help with this or find some people to help me with it if nobody else is going to ever get this fixed?

[olilarkin]

Hi @Gimmee99

I am chronically busy so didn't manage to fix this in iPlug2 yet, since the whole app wrapper needs a bigger overhaul for multichannel support. What I suggest - if someone wants to work on a fix specific for NAM, which shouldn't be too hard, is for @sdatkinson to merge #556, then whoever wants to can just fix the nam specific app wrapper code, without worrying about upstreaming it to iPlug2.