[FIXED] "MOTU Has Been Disconnected or Turned Off"??

[sjoens]

I've owned 3 different MOTU 1/2 rack interfaces and they've all had issues of one sort or another.  The mk3 has worked fine until a couple of Windows updates.  Now I get this issue after it's been on for several hours.  So maybe I need to reboot the system every 2 hours to avoid it?  Silliness.

Their newer stuff isn't half-rackable with older stuff, if at all.  More silliness.

Small town local markets for almost anything seems to have dried up recently and online sales is tough due to shipping hikes.  Sold a $600 mixer in original box for $300, a 1/4 of which was shipping.    Common items either go to a transfer site or recycle center after 2 years with no bites on craigslist.

[sjoens]

Seems I got the wrong drivers from the wrong page.  Trying the right ones now but something still weird.  Cakewalk sees the right IN/OUT names but in Windows settings the different INs/OUTs have no names. . .  just blank.

[Bass Guitar]

Interesting enough I’ve done absolutely nothing and there is still no new driver but I thought I would try the Motu again and it seems to now work fine?? Possibly a Windows update fixed what it originally broke?? 
Anyway it’s great to have it working again. 
Cross my fingers 

[sjoens]

Mine isn't.  Still the same issues.  Trying the un/re-install one more time.  I've crossed posted in the MOTU forum but doubtful it'll ever get resolved.

Could be a Windows 10 thing.  Yeah it's deprecated but I signed up for extended support. . . whatever that means. 

I'll be checking it on a Win7 and Win11 system to narrow it down.  Otherwise it's bound to be repurposed as an overpriced hockey puck.

Edited yesterday at 07:05 AM by sjoens

[David Baay]

15 hours ago, sjoens said:

Cakewalk sees the right IN/OUT names but in Windows settings the different INs/OUTs have no names.

Sonar's using ASIO while Windows will be using WASAPI; it's not uncommon for the different driver modes to present I/O ports differently.

FWIW, I bought a used Ultralite mk3 a year or so ago. It was cosmetically in mint condition but I had to return it because the USB port (or its connection to the board)  was mechanically flaky and would disconnect whenever the cable moved.

 

[Bass Guitar]

Because it became a PITA I put it on consignment at the local music store.  
I bought a SSL 2. After 6 months of using the SSL2 I was missing the M4. It never sold so I took it back. 
I just returned to rebooting before I would start recording anything. But other things would randomly go wrong especially if stupid Studio 1 was used. It switches to 44.1 if you open a midi file. I’d force 48 and carry on but now other apps won’t play. 

So back it went on the shelf and I was then using the Zoom L8. 
I love the L8 but I kept staring at the M4 and just a week ago I plugged it back in. 
It has been working perfectly fine since. It was on all day and I recorded something 12 hours later just to test. 
 

But for sure my original problem was that I needed USB C ports on my PC. Motu is a very Mac oriented device. 
 

[sjoens]

1 hour ago, David Baay said:

it's not uncommon for the different driver modes to present I/O ports differently.

This is the 1st time it reports them blank tho.

Fortunately I can enter my own names but I have no idea which one is which w/o some trial & error.

1 hour ago, David Baay said:

the USB port (or its connection to the board)  was mechanically flaky and would disconnect whenever the cable moved.

Nice.  One more thing to look at.

[mettelus]

14 hours ago, sjoens said:

I'll be checking it on a Win7 and Win11 system to narrow it down.  Otherwise it's bound to be repurposed as an overpriced hockey puck.

I upgraded to Win11 last week and in dealing with all of the nuances of the update, I noticed today that the system had essentially purged all sound devices not actively connected to the machine during that update. At first I thought it wasn't displaying disabled/disconnected hardware, but they were being shown, just not there. It also enabled everything I had disabled on Win10, so if you have done an O/S change that is something to check, maybe even go as far as uninstalling/re-installing drivers to be sure. Upgrading to Win10 didn't do this (just to clarify), so it may be a TPM artifact of Win11, but is worth noting in case you have shifted O/S to do another run-through of drivers/settings to be sure things are still what they were prior.

[sjoens]

The only change on this system is Windows 10 updates.  My Win 7 & WIn11 laptops are all on original OS's.

[sjoens]

Both Win7 & WIn11 work without incident.  After more un/re-installs and running the sound troubleshooter in Win10, it seems to be working without incident also.

Been running a project for a few hours and so far no disconnect warnings.

Thank you all for your tips.