So this has been nailing me since I updated to Lexington and is persisting in Manchester. I did not have these issues in Foxboro (which was the last version I had installed before updating to Lexington/Manchester) or earlier releases... like ever. Totally new issue.
 
The problem is that for some reason when I have my track input(s) routed exactly as they should be, echo/record enabled and all that other stuff set up as it should be and generally everything else needed to accept a live input set up as it should be... I don't get any input signal. On top of that I think today I got a signal on an old project I opened even though it was routed to an entirely different input (because I had been previously feeding that track from my board through a line in but today my guitar was hooked up to the multi ins on my interface... that was weird).
 
It's intermittent and the "solution" is to just screw around with the track Record Arm/Input Echo Status and/or switch to a different input and back again and/or close and reopen the project and/or open up my interface software (Scarlettmix)... etc.
 
Really it's just all about screwing around until I manage to shake the gremlins loose. That's best way to describe it.
 
I have of course recorded HUNDREDS if not thousands of live tracks into Sonar constantly for the past three years and although I've definitely sometimes not set things up properly before in the past that is NOT what this is. The input signal just isn't there until I futz about for a while doing all that stuff I described and eventually I get my signal.
 
Totally new thing, it's been affecting seemingly any and all projects, no other indications of what's causing it, etc.
 
Might be my rig but I'd like to know if this has been popping up for others so I can diagnose what's going on. I really hope my interface isn't dying.
 
Thanks.

Nobody has replied. But you are a vet round here so I believe you deserve at least lip service so you know someone cares so:
 
Nope beep, just you man.
 
Hope you get it sorted. - seems like a hardware problem to me right now.

bitman
Nobody has replied. But you are a vet round here so I believe you deserve at least lip service so you know someone cares so:
 
Nope beep, just you man.
 
Hope you get it sorted. - seems like a hardware problem to me right now.

Thanks, bitman. I still consider myself a n00b in many regards but this is definitely something I've done tons of and just noticed it recently.
 
I have however been messing around with Voicemeeter for my vids (since I guess late fall) and switching back and forth between that and the Focusrite drivers so that may be letting the gremlins creep in.
 
It really did seem to start happening after Lex though. I really need to come up with some scratch to get Jim to remote in and help me clean up this beast. lol
 
Cheers.

No problems here with inputs and Manchester on the DAW

Sounds like SONAR and your interface drivers are not in agreement about the state of the ports. Or some other process is interfering. I recommend you disable 'Share Drivers with Other Applications' if you haven't already. You might also experiment with other possibly related settings like Always Stream Audio Through FX, Allow Arming Changes During Playback and Recording, etc.
 
Next time it happens, see if toggling the audio engine or Input Echo off/on helps
 

@rsinger... Thanks for the extra data point. All helps.
 
@Brundle... Excellent. I'll take a poke at a bunch of that stuff and see what's up. Pretty sure I mucked about with a few of those settings when I was trying to make Sonar, Mirillis Action and eventually Voicemeeter to play nicely together. Thing is I did an entire session gig since I got all that setup... I think. Might have been before... AND maybe even if it was after I did all the crap it was the same project/folder the whole time so I may not have noticed it while on Foxboro.
 
This is generally happening with new projects or trying to connect to old projects and other such stuff. I've been trying to clean up some half finished work and get some new things on the go and that's where I'm noticing this. Once the "gremlins" are shook out the inputs seem to behave better.
 
Sorry it's very hard to describe and pin down. This is why I'm so paranoid about introducing new entities to my system but I got a little brave with the vid cap stuff because it was really necessary for some of my nefarious schemes. lol
 
Thanks, dood.

Can't help you Beep, all seems fine here.
 
You can however eliminate screensets as the source of your woes - input channels persist (as you would expect) when switching sets.
 
Keep us posted lad!