Would love to see some mono versions of the new post effects in an upcoming update. As it is, the unit doesn’t sum to mono even if only the left out is connected, so you end up losing out on things like stereo delays, reverbs and even the doubler.
People have come up with quick fixes like 2xTRS to XLR adaptors but it would be nice to just have mono versions of these effects to avoid possible phase issues and the like.
Wow… didn’t realize of this until I read this post.
That makes almost useless the option of going to a cab (no IR) with one output and to FOH (with IR) with the other output. At least if using stereo effects.
You can also see and hear it demonstrated in this video around 16:55. This was just before the most recent update but they didn’t mention anything about this being corrected so I believe it’s still the case.
The ideal solution would be auto-summing ( with level-matching with mono ) when there is no jack present at right output.
So, I guess it will show as a firmware update in the future.
And, if both L and R outs are connected, it should give you the option to make it stereo or mono, in order to output the same signal thorough both outputs if needed (to use real cab and FRFR simultaneously, since it already has the option to mute IRs in whatever output).
Actually, it’s weird that they implemented the independent IR muting per output while not implementing the mono option. They should do it urgently.
I asked support for this subject. This is what they replied (very quick, they work great), regarding mono sum even when muting one output IR:
“It’s important to note that stereo effects are not automatically summed to dual mono. This means that if you have a stereo effect in your signal chain, the left and right channels will carry separate signals, and each will be sent to its respective output. Therefore, one side of the effect will go to the left output (1L) and the other side to the right output (2R). If you plan to use this method, we recommend using mono effects only.
If you’re asking about summing the stereo signal from both outputs into dual mono signals, this functionality is not currently supported in the Nano Cortex.”.
They said that they’ll pass the feedback to dev team.
IMO this is a pretty big oversight that really needs to be addressed ASAP in order for this to be truly usable live. It’s not uncommon to only have access to one input at a gig or jam session, so to be unable to use most of the cool post effects kinda sucks.
Well, regardless of support told me, I’m making tests and I DO THINK that bypassing IR in one output actually SUMS TO MONO.
I’m trying an analog stereo delay, which has a ping pong button. If I use the stereo headphone output into a stereo input of my speaker, it obviously sounds with all repeats of the ping pong. If the ping pong button is not active, it seems to me that the delay acts as mono.
Now, if I plug just the left out to the speaker (not bypassing IRs at all), only half the ping pong repeats sound. To this point, all is as expected. And, if ping pong is off, all the repeats sound, which kind of confirms to me that the delay is mono unless you activate the ping pong button.
Now… I bypass left output IR… and then all the repeats of the ping pong sound.
It doesn’t make any difference wether the reverbs are on or off.
To confirm, I also tried a doubler effect. Without any IR bypass, the doubling does not sound. But when left IR is bypassed, the doubling effect sound.
Conclusion: bypassing IR actually makes a difference. It kind of sums to mono. I don’t know if it’s a total sum or not. I’d swear it does. I don’t feel losses.
And this is what support team replies to my observations:
“Hi Ángel,
Yes, we just tested this, and your observations appear to be correct. Bypassing the IR on one output does seem to sum the signal to mono. Previously, we had only tested with IRs active, so that was an oversight on our part. This behavior aligns with how the developers likely intended it, though we cannot confirm whether it is a true mono sum.
Your feedback has been extremely helpful, and we’ve learned a lot from your detailed testing. We will make sure to pass your notes along to the development team and stay more closely aligned with these details in the future. With every major software update, there’s always a learning curve for us as well.
Nice work! I don’t have time at the moment to replicate but I do wonder if the behavior is the same for both the 1/L as it is for the 2/R ports.
Kind of sounds like NDSP has a bug that is possibly a feature but still mostly a bug.
My initial assumption was 1/L sums to mono unless 2/R is detected then split to stereo. If IR bypass enabled on one but not both sum both to mono.
I’m sure someone somewhere will say they want stereo out with only one IR bypassed output and that would need an explicit setting if everything else is implied by 1 or 2 outputs detected and IR global setting.
So…. I admit I always assumed the manual’s hookup diagram implied 1L by itself is mono for integration into a greater pedal board.
But upon closer look it seems the wording implies using both 1L/2R for stereo output.
I guess this turns into a feature request for mono summing like there is now an IR global bypass?
To me, I think this makes the same sense as a user would then leverage the stereo when able but otherwise sum to mono like we can set global IR bypass on one or both outputs. This may also be much more straightforward than mono and stereo versions of an effect and TRS detection isn’t viable because independent global IR bypass means you may still want dual mono out.
When I look at this topic, It seems to me as if it would be a more elegant solution to implement “Auto-Sum-To-Mono” instead of mono versions of all effects ( of course with output level compensation ) . If NC can not sense if 1L or both outs are plugged, the choice ( stereo, dual mono etc.. ) could be inside system settings.
Pros:
A lot less development effort for mono versions of each stereo effect
It is automatic ( sensing which outs are used and deciding )
I would also love to just see some straight up Mono versions of the effects. They are in the Quad Cortex, so it really shouldn’t been an issues to port them over to the nano. I’ve noticed really odd glitches with the stereo delays even when the width is set to 0%. On a gig last night I was using the Analog delay and the repeats were just garbled and not actually repeating normally.