MOTU Ultralite AVB In 1-24 meter pegging.

Since there are some MOTU AVB users here I figured I'd ask this question.
I'm having a weird problem with Windows 10 Professional and the MOTU AVB Ultralite both latest drivers and updates.
Nothing is plugged into the MOTU and the only outputs are the Mains.
 
The Windows Sound Control panel under the "Recording" Tab has the meter for In 1-24 pegged with nothing playing, fresh boot etc.
There is no other indication either in the MOTU Discovery App or the meters on the MOTU.
If I lower the volume the meter will move lower as well.
It seems like some kind of feedback loop. I have "Audio Interface" chosen in the MOTU app and it is default settings.
 
Now, here is the weird thing.
If I remove the drivers completely, do a fresh install it will not behave like this at least for a short while, and then it will return.
 
Any ideas?
 

Thanks for confiming you aren't seeing the same,  L Lyons.. I'm going to poke the MOTU support folks to see if they have any ideas. Seems like a really weird problem to me.
 

Rob[atSound-Rehab]

steveo42
The Windows Sound Control panel under the "Recording" Tab has the meter for In 1-24 pegged with nothing playing, fresh boot etc.
There is no other indication either in the MOTU Discovery App or the meters on the MOTU.
If I lower the volume the meter will move lower as well.
It seems like some kind of feedback loop. I have "Audio Interface" chosen in the MOTU app and it is default settings.
 
Now, here is the weird thing.
If I remove the drivers completely, do a fresh install it will not behave like this at least for a short while, and then it will return.

 
Hi Steve,
 
I'm afraid I don't fully understand the problem yet ... are you saying some win10 meter indicating an input signal that is not there? what are the implications you get when using it with DAW software?
 
if it doesn't register on the MOTU webUI, do you hear any of that if you e.g. route individual inputs (with nothing plugged into) to the MOTU headphone output in the MOTU routing matrix?
 
I will have a look at the later today (not in the studio right now), but cannot remeber seeing anything like that ... what I found interesting, though, when testing options trying to figure out my random record corrutions (see here) that I can completely disable all of MOTU (1-2 and 1-24) in the windows playback and recording device panels and it is still fully recognized and addressable in Sonar.

Hi Rob,
To answer your questions:
 
1. The Windows Sound Control panel (type sound in the start menu) on the recording tab shows the level meter for In 1-24 pegged green. Full signal. This is from a clean boot with nothing playing, I have System Sounds disabled BTW. I can turn it down with the volume slider but it still sits solid, no bouncing around.
 
It does not register on the MOTU itself or anywhere in the MOTU discovery app no matter what I route or where I route it.
I don't hear anything.
 
2. I disabled the In 1-24 device from the Windows Sound Control Panel just in case.
 
It's really weird.
 
 
 

I just had an odd one happen too.  It wasn't with MOTU, or windows sound control.  It was with a buss level meter, one I was using for metronome.  I stopped recording and the volume stopped at max and didn't change until I pressed play again.   I still haven't seen what you are seeing, yet.

jbraner
 
I'm not going to worry about it - and disabling the device is probably a good idea...

That's what I did a while ago when I realized 1-24 is of no use to windows. I have only 1-2 active for playback (disabled for recording) to be able to use media player with Sonar exports

Sorry for the delay in replying guys. Been up to my eyeballs in crap these days :)
 
So it appears this is indeed a bug. Just for grins and giggles, I switched the Ultralite to a different USB port and the problem went away.
Unfortunately it came back again and the only DAW related activity was opening Studio One and playing around with Reaper a bit.
After closing everything, doing a clean boot, the problem was still there until for some odd reason it disappeared again.
When it was failing, I did try playing around with the MOTU Discovery app, changing AVB settings, sample rates etc to see if I could fix it but no luck there.
 
I'm going to disable it in Windows because my fear is that something may be in a feedback loop sending high frequencies above my hearing range "somewhere", like my monitors, and ultimately toasting my tweeters or something else.
I agree this 1-24 thing in Windows is confusing and I'm not sure what programs would even use it?
Maybe some 5:1 systems?
I dunno.
I'll file a bug report with Motu as soon as I get a chance.
It would be good if others could do the same. 
Hopefully it gets fixed in the next driver.