Rob[at]Sound-Rehab
Max Output Level: -47 dBFS
- Total Posts : 2819
- Joined: 2011/02/03 04:31:35
- Location: Sound-Rehab, Austria
- Status: offline
Re: MOTU AVB series
2016/09/21 15:00:51
(permalink)
jbraner
Make sure you are actually running the old driver. I know it sounds dumb - but I had to uninstall / reinstall a couple of times before I was actually running the "old" driver. The beta ones never really get uninstalled.
The old one looks different if you look in Windows control panel, and it loads a different file if you check under device drivers.
When I'm back at my PC, I can give you the exact files if you need...
thanks, mate. i appreciate it. the first time around the driver definitely did not get uninstalled completely. the 2nd time I got a different audio preference GUI but no connection ... so there might have been some remnants left (especially as silly me installed the older driver before uninstalling the other one, expecting this thing to do it right by itself, not realizing this is a different installation package)
GOOD TUNES LAST FOREVER +++ Visit the Rehab +++ DAW: Platinum/X3e, win10 64 bit, i7-3930K (6x3.2GHz), Asus Sabertooth X79, 32 GB DDR3 1600MHz, ATI HD 5450, 120 GB SSD OCZ Agility3, 2x 1TB WD HDD SATA 600 Audio-Interface: 2x MOTU 1248 AVB, Focusrite OctoPre, (Roland Octa-Capture) Control-Surface: VS-700C VSTi: WAVES, NI K10u, FabFilter, IK, ... (too many really)
|
jbraner
Max Output Level: -57 dBFS
- Total Posts : 1830
- Joined: 2003/11/06 14:38:35
- Location: Edinburgh, Scotland
- Status: offline
Re: MOTU AVB series
2016/09/21 15:06:58
(permalink)
There are always remnants ;-)
Even when you "uninstall" in device manager - it doesn't really...
|
jbraner
Max Output Level: -57 dBFS
- Total Posts : 1830
- Joined: 2003/11/06 14:38:35
- Location: Edinburgh, Scotland
- Status: offline
Re: MOTU AVB series
2016/09/22 06:00:00
(permalink)
In Windows Device Manager: Here's what the "old" driver looks like  and this is what the beta driver looks like  You'll notice that the (beta driver) MOTUProAudio.sys never gets deleted - so make sure you're actually running the older driver.
|
Rob[at]Sound-Rehab
Max Output Level: -47 dBFS
- Total Posts : 2819
- Joined: 2011/02/03 04:31:35
- Location: Sound-Rehab, Austria
- Status: offline
Re: MOTU AVB series
2016/09/22 15:48:48
(permalink)
Thanks. I gave it another go and this time (why not before?) unstalling the AVB PRO driver and installing the USB AVB worked. So the device now seems to get recognized easier (well, it showed everytime I tested turning AVB or DAW off and on). However, I cannot access the routing matrix as the other MOTU apps still dont find the device (???); turning firewall off makes no difference. I could possibly access it from another PC connected via LAN, but then I can't use the AVB port to hook up a 2nd device ... Also, there is quite a penalty on the achievable lowest latency I can get as I need to use double size buffer which boost it from 4 ms RTL to >9 ms ... So for now, the PRO driver with its occasional quirks of not showing still wins
post edited by Rob[at]Sound-Rehab - 2016/09/22 16:10:45
GOOD TUNES LAST FOREVER +++ Visit the Rehab +++ DAW: Platinum/X3e, win10 64 bit, i7-3930K (6x3.2GHz), Asus Sabertooth X79, 32 GB DDR3 1600MHz, ATI HD 5450, 120 GB SSD OCZ Agility3, 2x 1TB WD HDD SATA 600 Audio-Interface: 2x MOTU 1248 AVB, Focusrite OctoPre, (Roland Octa-Capture) Control-Surface: VS-700C VSTi: WAVES, NI K10u, FabFilter, IK, ... (too many really)
|
jbraner
Max Output Level: -57 dBFS
- Total Posts : 1830
- Joined: 2003/11/06 14:38:35
- Location: Edinburgh, Scotland
- Status: offline
Re: MOTU AVB series
2016/09/22 16:02:28
(permalink)
Rob[atSound-Rehab]
Thanks. I gave it another go and this time (why not before?) unstalling the AVB PRO driver and installing the USB AVB worked. So the device now seems to get recognized easier (well, it showed everytime I tested turning AVB or DAW off and on). I just thought I'd mention it - since I had to "uninstall" a few times before it actually installed the right (older) driver. ;-)
However, I cannot access the routing matrix as the other MOTU apps still dont find the device (???); turning firewall off makes no difference. I could possibly access it from another PC connected via LAN, but then I can't use the AVB port to hook up a 2nd device ...
Hmmm, that works fine here. I'm even still loading that little system tray thing  I *do* use a fixed ip address on the Ultralite though. Maybe that helps?
Also, there is quite a penalty on the achievable lowest latency I can get as I need to use double size buffer which boost it from 4 ms RTL to >9 ms ...
That's also different from what I'm seeing. I get more or less the same latency settings (actually the exact same settings) on both.
So for now, the PRO driver with its occasional quirks of not showing still wins
Please keep us up to date on this OK? Also - let us know if a new beta driver comes out, and if you have any luck with the "losing connection to the MOTU device" problem 
post edited by jbraner - 2016/09/22 16:24:19
|
Rob[at]Sound-Rehab
Max Output Level: -47 dBFS
- Total Posts : 2819
- Joined: 2011/02/03 04:31:35
- Location: Sound-Rehab, Austria
- Status: offline
Re: MOTU AVB series
2016/09/23 02:42:56
(permalink)
jbraner
Please keep us up to date on this OK? Also - let us know if a new beta driver comes out, and if you have any luck with the "losing connection to the MOTU device" problem
Will do. I also contacted MOTU on this subject. We'll see if/how they respond ...
GOOD TUNES LAST FOREVER +++ Visit the Rehab +++ DAW: Platinum/X3e, win10 64 bit, i7-3930K (6x3.2GHz), Asus Sabertooth X79, 32 GB DDR3 1600MHz, ATI HD 5450, 120 GB SSD OCZ Agility3, 2x 1TB WD HDD SATA 600 Audio-Interface: 2x MOTU 1248 AVB, Focusrite OctoPre, (Roland Octa-Capture) Control-Surface: VS-700C VSTi: WAVES, NI K10u, FabFilter, IK, ... (too many really)
|
Rob[at]Sound-Rehab
Max Output Level: -47 dBFS
- Total Posts : 2819
- Joined: 2011/02/03 04:31:35
- Location: Sound-Rehab, Austria
- Status: offline
Re: MOTU AVB series
2016/09/24 03:11:49
(permalink)
jbraner
Rob[atSound-Rehab]
Also, there is quite a penalty on the achievable lowest latency I can get as I need to use double size buffer which boost it from 4 ms RTL to >9 ms ...
That's also different from what I'm seeing. I get more or less the same latency settings (actually the exact same settings) on both.
OK, I might have been unjust regarding latency. NI Kontakt 5.6 was also installed meanwhile and apparently K5.6 needs more resources than before for the same project. So the projects where I had to increase the buffer all use K5.6 (and of course this also applies to the AVB PRO driver now)
GOOD TUNES LAST FOREVER +++ Visit the Rehab +++ DAW: Platinum/X3e, win10 64 bit, i7-3930K (6x3.2GHz), Asus Sabertooth X79, 32 GB DDR3 1600MHz, ATI HD 5450, 120 GB SSD OCZ Agility3, 2x 1TB WD HDD SATA 600 Audio-Interface: 2x MOTU 1248 AVB, Focusrite OctoPre, (Roland Octa-Capture) Control-Surface: VS-700C VSTi: WAVES, NI K10u, FabFilter, IK, ... (too many really)
|
Rob[at]Sound-Rehab
Max Output Level: -47 dBFS
- Total Posts : 2819
- Joined: 2011/02/03 04:31:35
- Location: Sound-Rehab, Austria
- Status: offline
Re: MOTU AVB series
2016/10/02 05:28:06
(permalink)
jbraner
Please keep us up to date on this OK? Also - let us know if a new beta driver comes out, and if you have any luck with the "losing connection to the MOTU device" problem
quick update from my end regarding this situation: - no new driver update, but the "v4.0+71199 | Sep. 1, 2016" AVB drivers are now the official ones. the ones from March are gone from the download page ...
- I only see the connection issues rarely i.e. sometimes the device registers @ win10 (i.e. is seen by MOTU settings & routing app) but not by Sonar (maybe 1 out of 10 times). it usually does not happen if I boot studio devices including the MOTU before booting the DAW.
- Interestingly, I had one occasion where neither booting DAW nor MOTU gave me access to the ASIO drivers in Sonar. Simply unplugging & plugging the USB cable at the back of the MOTU solved that (which is a bit of a hassle as it is fully cabled in a large equipment rack) ... anyway, what's difference in win10 between a power cycle of the USB device and a cable unplug/plug action???
- I did email MOTU support about 10 days ago and did not even get an acknowledgement that they received my enquiry. This may just be due to being located in Europe and support via website is only for US (???). so pls anyone located in the US seeing this problem contact MOTU, we may have a bigger chance to get a reply from MOTU this way.
- Meanwhile I run 2 devices (2x 1248 networked via AVB) and while it took me about a week to set up the best routing from the zillion options you get, I am extremely impressed by how these 2 units act together as one gigantic audio device (clocking, direct monitor across devices, headphone mixes, etc). I managed to hook up all control room gear, outboard and live room connections to the input the MOTUs provide and can now simply operate by changing routing presets rather than fiddling with patch bays and fighting poorly labelled multicore output jacks.
post edited by Rob[at]Sound-Rehab - 2016/10/02 06:04:59
GOOD TUNES LAST FOREVER +++ Visit the Rehab +++ DAW: Platinum/X3e, win10 64 bit, i7-3930K (6x3.2GHz), Asus Sabertooth X79, 32 GB DDR3 1600MHz, ATI HD 5450, 120 GB SSD OCZ Agility3, 2x 1TB WD HDD SATA 600 Audio-Interface: 2x MOTU 1248 AVB, Focusrite OctoPre, (Roland Octa-Capture) Control-Surface: VS-700C VSTi: WAVES, NI K10u, FabFilter, IK, ... (too many really)
|
jbraner
Max Output Level: -57 dBFS
- Total Posts : 1830
- Joined: 2003/11/06 14:38:35
- Location: Edinburgh, Scotland
- Status: offline
Re: MOTU AVB series
2016/10/02 05:37:13
(permalink)
Thanks for th eupdate Rob.
I'll need to try the new drivers, and report back...
|
Rob[at]Sound-Rehab
Max Output Level: -47 dBFS
- Total Posts : 2819
- Joined: 2011/02/03 04:31:35
- Location: Sound-Rehab, Austria
- Status: offline
Re: MOTU AVB series
2016/10/03 18:03:53
(permalink)
jbraner
Thanks for th eupdate Rob.
I'll need to try the new drivers, and report back...
Have you had a chance to give the latest drivers a try? I just heard back from MOTU saying that this is not a "known" issue and I should check USB port, cable, etc ... yet I do remember having a similar issue on the backup DAW (?) and you guys see it, too (???) If you do get the connection problem again, pls check if unplugging the USB cable from the unit while powered does fix it (it seemed to work here twice which is odd as I don't understand this i.e. power cycle does not change it, but pulling the cables does, yet the USB plug sits very tight in that connection, so it can't be lose connection thing ...)
GOOD TUNES LAST FOREVER +++ Visit the Rehab +++ DAW: Platinum/X3e, win10 64 bit, i7-3930K (6x3.2GHz), Asus Sabertooth X79, 32 GB DDR3 1600MHz, ATI HD 5450, 120 GB SSD OCZ Agility3, 2x 1TB WD HDD SATA 600 Audio-Interface: 2x MOTU 1248 AVB, Focusrite OctoPre, (Roland Octa-Capture) Control-Surface: VS-700C VSTi: WAVES, NI K10u, FabFilter, IK, ... (too many really)
|
jbraner
Max Output Level: -57 dBFS
- Total Posts : 1830
- Joined: 2003/11/06 14:38:35
- Location: Edinburgh, Scotland
- Status: offline
Re: MOTU AVB series
2016/10/04 04:31:46
(permalink)
I haven't tried it yet. I'm not in a big rush, as the new driver seems to be the same as the last beta one
(MOTU Pro Audio Installer 4.0 (71199)) - and this is the one I had the most problems with.
I was thinking that it might work better if I install it over the old driver - rather than when I had the 3 betas installed over the top of each other - but I'm not overly confident.
I'll get around to it soon - but the old driver works great, so I'm reluctant to "rock the boat" ;-)
(don't worry, I always do though...)
|
jbraner
Max Output Level: -57 dBFS
- Total Posts : 1830
- Joined: 2003/11/06 14:38:35
- Location: Edinburgh, Scotland
- Status: offline
Re: MOTU AVB series
2016/10/06 11:02:31
(permalink)
OK - I tried the new driver, and it's just the same as the beta. I can't be bothered trying to get the interface connected every few times I boot up :-(
I was able to reconnect sometimes by power cycling the interface, but disconnecting the USB cable made no difference (well, I only tried it once). I also tried another USB port, and it came right up - disconnected (!)
Anyway - there's nothing wrong with my USB port because the older driver works fine.
I've gone back to the 1.6 driver - which works fine.
I'll go see if I can log a support incident on the MOTU site.
|
steveo42
Max Output Level: -89 dBFS
- Total Posts : 90
- Joined: 2015/11/14 18:18:04
- Status: offline
Re: MOTU AVB series
2016/10/06 11:08:23
(permalink)
I just had this happen again yesterday. Out of clear blue interface was seen by Windows etc but no sound. Powered down computer fully as well as MOTU and that didn't fix it. Unplugging and plugging USB cable was the fix. I've also discovered that after full power down, removing the line cord from the computer also fixes this problem.
One thing I noticed was that some of my USB ports somehow got the power management "Allow this computer to manage the power" turned back on. I know they were all off so I suspect the recent Anniversary Update reset them.
Other than that, I'm stumped.
|
Jim Roseberry
Max Output Level: 0 dBFS
- Total Posts : 9871
- Joined: 2004/03/23 11:34:51
- Location: Ohio
- Status: offline
Re: MOTU AVB series
2016/10/06 11:34:45
(permalink)
steveo42
I just had this happen again yesterday. Out of clear blue interface was seen by Windows etc but no sound. Powered down computer fully as well as MOTU and that didn't fix it. Unplugging and plugging USB cable was the fix. I've also discovered that after full power down, removing the line cord from the computer also fixes this problem.
One thing I noticed was that some of my USB ports somehow got the power management "Allow this computer to manage the power" turned back on. I know they were all off so I suspect the recent Anniversary Update reset them.
Other than that, I'm stumped.
FWIW, The Anniversary Update for Win10 does reenable some settings and background apps.
|
Rob[at]Sound-Rehab
Max Output Level: -47 dBFS
- Total Posts : 2819
- Joined: 2011/02/03 04:31:35
- Location: Sound-Rehab, Austria
- Status: offline
Re: MOTU AVB series
2016/10/06 13:30:38
(permalink)
jbraner
OK - I tried the new driver, and it's just the same as the beta. I can't be bothered trying to get the interface connected every few times I boot up :-(
I was able to reconnect sometimes by power cycling the interface, but disconnecting the USB cable made no difference (well, I only tried it once). I also tried another USB port, and it came right up - disconnected (!)
Anyway - there's nothing wrong with my USB port because the older driver works fine.
I've gone back to the 1.6 driver - which works fine.
I'll go see if I can log a support incident on the MOTU site.
steveo42
I just had this happen again yesterday. Out of clear blue interface was seen by Windows etc but no sound. Powered down computer fully as well as MOTU and that didn't fix it. Unplugging and plugging USB cable was the fix. I've also discovered that after full power down, removing the line cord from the computer also fixes this problem.
One thing I noticed was that some of my USB ports somehow got the power management "Allow this computer to manage the power" turned back on. I know they were all off so I suspect the recent Anniversary Update reset them.
Other than that, I'm stumped.
Could both of you please open a ticket with MOTU support ??? i.e. log in @ MOTU.com => MOTU Tech Links. They are very responsive on that official channel (compared to the email box that listed with the AVB driver download, which ended up in digital nirvana) ... it would be good for them to see that this is not just happening on my computer.
GOOD TUNES LAST FOREVER +++ Visit the Rehab +++ DAW: Platinum/X3e, win10 64 bit, i7-3930K (6x3.2GHz), Asus Sabertooth X79, 32 GB DDR3 1600MHz, ATI HD 5450, 120 GB SSD OCZ Agility3, 2x 1TB WD HDD SATA 600 Audio-Interface: 2x MOTU 1248 AVB, Focusrite OctoPre, (Roland Octa-Capture) Control-Surface: VS-700C VSTi: WAVES, NI K10u, FabFilter, IK, ... (too many really)
|
Jim Roseberry
Max Output Level: 0 dBFS
- Total Posts : 9871
- Joined: 2004/03/23 11:34:51
- Location: Ohio
- Status: offline
Re: MOTU AVB series
2016/10/06 16:22:43
(permalink)
Could you all check something?
What happens if you power down the AVB units (prior to starting your machine).
Then, once booted into Windows... turn on the AVB/s.
Does the problem persist?
Are you all on Win10 with the Anniversary Update applied?
|
jbraner
Max Output Level: -57 dBFS
- Total Posts : 1830
- Joined: 2003/11/06 14:38:35
- Location: Edinburgh, Scotland
- Status: offline
Re: MOTU AVB series
2016/10/06 16:47:31
(permalink)
Rob - I opened a ticket today ;-) Jim - that's not gonna fly for me, as I like to boot in to my "non music" partition - and then the music partition. Shutting everything down every time - just in case the MOTU driver is going to screw up - is a nuisance. Especially when the 1.6 driver is rock solid. Yep - I'm on Windows Anniversary update, but I think the beta drivers (and this new one is just the same as the last beta one from August) did the same thing before the Anniversary update. Also - the update didn't change any of my USB port power settings. UPDATE: I just got a fairly lame response from support, saying to try a new cable and a different PC. To me - the old driver wouldn't be rock solid if I had a bad cable...
post edited by jbraner - 2016/10/06 17:22:17
|
Jim Roseberry
Max Output Level: 0 dBFS
- Total Posts : 9871
- Joined: 2004/03/23 11:34:51
- Location: Ohio
- Status: offline
Re: MOTU AVB series
2016/10/06 17:18:26
(permalink)
Hi John, All I'm suggesting is to try booting into Windows (DAW install for you) with the AVB powered off. Once Windows is up/running, power up the AVB. It may or may not have an effect... but it's worth a quick test. I agree that the older driver is rock-solid. Round-trip latency wasn't particularly bad with this driver For those unfamiliar... 4.9ms at a 64-sample ASIO buffer size/44.1k
|
jbraner
Max Output Level: -57 dBFS
- Total Posts : 1830
- Joined: 2003/11/06 14:38:35
- Location: Edinburgh, Scotland
- Status: offline
Re: MOTU AVB series
2016/10/06 17:36:12
(permalink)
Hi Jim,
I'll install the new driver tomorrow again - and play around and try it.
I've had to change the cable for MOTU support and they want to see a video of what it looks like when it's "broken".
I've powered the MOTU off and on again - when it's"broken" - and sometimes it fixes it and some times it doesn't.
I'll play more tomorrow (but I'd rather work on some music)...
|
jbraner
Max Output Level: -57 dBFS
- Total Posts : 1830
- Joined: 2003/11/06 14:38:35
- Location: Edinburgh, Scotland
- Status: offline
Re: MOTU AVB series
2016/10/07 08:48:04
(permalink)
Jim Roseberry
Hi John,
All I'm suggesting is to try booting into Windows (DAW install for you) with the AVB powered off.
Once Windows is up/running, power up the AVB.
It may or may not have an effect... but it's worth a quick test.
Hi Jim, I think you're on to something here. Sorry, I was getting grouchy last night (I'm in the UK) as this is a PIA - but I did more testing today. When I first installed the new driver (I'd gone back to 1.6) it didn't work at all. I tried pulling out the USB cable a few times - and it worked sometimes and other times it didn't. Your method is the best workaround - this seems to work every time (so far, I'll let you know if it fails). Here's what I do when it's "broken": - Power everything off - boot up the PC (Ultralite AVB still off) - bring up the Ultralite AVB after the PC has booted. twice this seemed like it wasn't working - but the devices in control panel disappeared and re-appeared, and then it was working. So - so far, I've been able to get it working with this recipe - whenever it goes "bad". Sometimes it works fine - without doing anything special (I know this because I also tried to find a recipe for "breaking" it) I have a case open with MOTU, and have gone over all of this with their guy. I've sent screen shots etc etc - so we'll see. I can't believe that this is only a problem for me - and a few others here. I don't mind running on the old driver - but I feel it makes sense to try to figure out why the "new, improved" one doesn't work consistently.
post edited by jbraner - 2016/10/07 09:10:16
|
Rob[at]Sound-Rehab
Max Output Level: -47 dBFS
- Total Posts : 2819
- Joined: 2011/02/03 04:31:35
- Location: Sound-Rehab, Austria
- Status: offline
Re: MOTU AVB series
2016/10/07 13:10:15
(permalink)
Jim Roseberry
Could you all check something?
What happens if you power down the AVB units (prior to starting your machine).
Then, once booted into Windows... turn on the AVB/s.
Does the problem persist?
Are you all on Win10 with the Anniversary Update applied?
ok. I think now I can reproduce this thanks to Jim's suggestion ... - when coming from a cold boot it usually works fine (i.e. I can power up all studio gear and then boot the DAW, the AVB is recognized)
- when rebooting the DAW and leaving the AVB on, I do get the connection issue i.e.
- it shows as windows device and shows in MOTU web app when using "MOTU Pro Audio WebUI Setup", but
- it does not show up in the "MOTU Discovery" app
- windows sound will not work properly e.g. when playing a video file it stutters
- ASIO drivers will not show in Sonar
- interestingly: a power cycle of the AVB re-established connection
- when rebooting DAW while power cycling the AVB at the same time, it works and re-establishes the connection, even if the AVB is done rebooting before the DAW
so it looks there is something not properly initialized if the USB bus remains powered while rebooting (compared to a full power cut ) what I also get - and that is new since one of the recent win10 updates: @ boot I sometimes (not always) get the following error from the Microsoft Security Client: "An error has occurred in the program during initialization. If this problem continues, please contact your system administrator" Error code: 0x80070426 ... and when this happens, the "MOTU Discovery" app often remains unresponsive or does not find the AVB ... although the device itself works - very strange
post edited by Rob[at]Sound-Rehab - 2016/10/07 13:38:49
GOOD TUNES LAST FOREVER +++ Visit the Rehab +++ DAW: Platinum/X3e, win10 64 bit, i7-3930K (6x3.2GHz), Asus Sabertooth X79, 32 GB DDR3 1600MHz, ATI HD 5450, 120 GB SSD OCZ Agility3, 2x 1TB WD HDD SATA 600 Audio-Interface: 2x MOTU 1248 AVB, Focusrite OctoPre, (Roland Octa-Capture) Control-Surface: VS-700C VSTi: WAVES, NI K10u, FabFilter, IK, ... (too many really)
|
jbraner
Max Output Level: -57 dBFS
- Total Posts : 1830
- Joined: 2003/11/06 14:38:35
- Location: Edinburgh, Scotland
- Status: offline
Re: MOTU AVB series
2016/10/08 05:19:49
(permalink)
Rob, This is almost exactly what I see - except I can't reproduce anythign 100% of the time. The problem is definitely based on re-booting the PC (with AVB still up and running) interestingly: a power cycle of the AVB re-established connection This one only works for me sometimes. when rebooting DAW while power cycling the AVB at the same time, it works and re-establishes the connection, even if the AVB is done rebooting before the DAW Same with this one. This used to be the case in the earlier betas - but now it's a crap shoot whether it will work or not. Jim's method worked for me quite a few times (I'm sitting here like an idiot rebooting over and over to test these scenarios) but finally failed once last night. Also - my MOTU support ticket has gone quiet. He was supposed to get back to me first thing (East Coast USA time) yesterday, and I sent a full report with screen shots and full explanations - but I've heard nothing. Although it's a little bit of a pain, I wouldn't even mind if I had to power everything off when rebooting - but that only works 80% of the time or so. The real pain - is never really knowing if sound is going to come out (and pfaffing around if it's not working) Can you verify - that once it's up and running and working - everything is fine? The problem is only after a reboot - right?
|
Rob[at]Sound-Rehab
Max Output Level: -47 dBFS
- Total Posts : 2819
- Joined: 2011/02/03 04:31:35
- Location: Sound-Rehab, Austria
- Status: offline
Re: MOTU AVB series
2016/10/08 06:06:10
(permalink)
jbraner
This is almost exactly what I see - except I can't reproduce anythign 100% of the time.
same here. i had it working perfectly for 2 days (with several intentional reboots in between just to check on this), but yesterday I could then reproduce it a few times as described above jbraner
Also - my MOTU support ticket has gone quiet. He was supposed to get back to me first thing (East Coast USA time) yesterday, and I sent a full report with screen shots and full explanations - but I've heard nothing.
Yes, I've also added my most recent description to my ticket and haven't heard back yet. Maybe MOTU dev started looking into this themselves rather than having support give the usual troubleshooting guidelines ... they should have realized that these issues appear on decidated properly setup DAWs that worked fine before and work fine with other interfaces jbraner
Can you verify - that once it's up and running and working - everything is fine?
The problem is only after a reboot - right?
so far this is my observation. it usually shows and works, and keeps working solid and steady, no issues when changing buffers, routing, DSP mixing, etc. just as advertised ... only sometimes after booting the DAW it does not show up, then to fix it, it may be one power cycle, or cable unplug/plug, or totally shuting DAW, boot it first, then AVB ... BTW, I was actually thinking about testing this with a USB hub that has an on/off switch in between because I noticed a similar thing with the 2 MIDI intefaces (ESI M4U XT) but much less frequently (about once a month) that only 1 will show while the second does not) ... there a quick off/on flip of the hub fixes it within 2 seconds ...
post edited by Rob[at]Sound-Rehab - 2016/10/08 06:28:47
GOOD TUNES LAST FOREVER +++ Visit the Rehab +++ DAW: Platinum/X3e, win10 64 bit, i7-3930K (6x3.2GHz), Asus Sabertooth X79, 32 GB DDR3 1600MHz, ATI HD 5450, 120 GB SSD OCZ Agility3, 2x 1TB WD HDD SATA 600 Audio-Interface: 2x MOTU 1248 AVB, Focusrite OctoPre, (Roland Octa-Capture) Control-Surface: VS-700C VSTi: WAVES, NI K10u, FabFilter, IK, ... (too many really)
|
jbraner
Max Output Level: -57 dBFS
- Total Posts : 1830
- Joined: 2003/11/06 14:38:35
- Location: Edinburgh, Scotland
- Status: offline
Re: MOTU AVB series
2016/10/08 07:09:29
(permalink)
BTW, I was actually thinking about testing this with a USB hub I always assumed that hubs = one more level of things that can go wrong I'm glad you have a ticket open too - hopefully something will work out. Even if they officially say to use the old version for now
|
jbraner
Max Output Level: -57 dBFS
- Total Posts : 1830
- Joined: 2003/11/06 14:38:35
- Location: Edinburgh, Scotland
- Status: offline
Re: MOTU AVB series
2016/10/10 17:19:50
(permalink)
All quiet at MOTU - have you heard anything Rob?
|
Jim Roseberry
Max Output Level: 0 dBFS
- Total Posts : 9871
- Joined: 2004/03/23 11:34:51
- Location: Ohio
- Status: offline
Re: MOTU AVB series
2016/10/11 01:29:44
(permalink)
I had a feeling that powering down the MOTU while rebooting would eliminate the problem.
Obviously the issue should be fixed... but at least you have a workaround.
|
jbraner
Max Output Level: -57 dBFS
- Total Posts : 1830
- Joined: 2003/11/06 14:38:35
- Location: Edinburgh, Scotland
- Status: offline
Re: MOTU AVB series
2016/10/11 04:38:51
(permalink)
Jim Roseberry
I had a feeling that powering down the MOTU while rebooting would eliminate the problem.
Obviously the issue should be fixed... but at least you have a workaround.
The best workaround is really to go back to the older driver. I don't think anything is wrong with it - and I don't see any "improvement" in the new driver (I know it has Thunderbolt support - but for USB the old driver is great) except that the latency settings are more granular, and you can now bring them down lower than anything that will possibly work (like 8 samples with 8 sample safety buffer)
|
Rob[at]Sound-Rehab
Max Output Level: -47 dBFS
- Total Posts : 2819
- Joined: 2011/02/03 04:31:35
- Location: Sound-Rehab, Austria
- Status: offline
Re: MOTU AVB series
2016/10/11 13:50:16
(permalink)
jbraner
All quiet at MOTU - have you heard anything Rob?
no. all quiet here as well. jbraner
Jim Roseberry
I had a feeling that powering down the MOTU while rebooting would eliminate the problem.
Obviously the issue should be fixed... but at least you have a workaround.
The best workaround is really to go back to the older driver.
I don't think anything is wrong with it - and I don't see any "improvement" in the new driver (I know it has Thunderbolt support - but for USB the old driver is great) except that the latency settings are more granular, and you can now bring them down lower than anything that will possibly work (like 8 samples with 8 sample safety buffer)
This workaround - plus pulling the cable seems to get it working (I had a very stubborn one yesterday that didn't go away with DAW reboot and AVB reboot afterwards, so pulling the USB cable fixed it then) I will stick with the driver until MOTU releases newer ones. Once the device is up and running it works brilliantly. I enjoy the ultra low latency (now sample libraries can be triggered by e-drums like never before - I always had a slight latency feeling, even at RTL of 8ms, so having to ~4ms is really nice)
GOOD TUNES LAST FOREVER +++ Visit the Rehab +++ DAW: Platinum/X3e, win10 64 bit, i7-3930K (6x3.2GHz), Asus Sabertooth X79, 32 GB DDR3 1600MHz, ATI HD 5450, 120 GB SSD OCZ Agility3, 2x 1TB WD HDD SATA 600 Audio-Interface: 2x MOTU 1248 AVB, Focusrite OctoPre, (Roland Octa-Capture) Control-Surface: VS-700C VSTi: WAVES, NI K10u, FabFilter, IK, ... (too many really)
|
jbraner
Max Output Level: -57 dBFS
- Total Posts : 1830
- Joined: 2003/11/06 14:38:35
- Location: Edinburgh, Scotland
- Status: offline
Re: MOTU AVB series
2016/10/11 14:44:08
(permalink)
(I had a very stubborn one yesterday that didn't go away with DAW reboot and AVB reboot afterwards, so pulling the USB cable fixed it then) This is what really annoys me!  Sometimes it just stays "broken"!
I will stick with the driver until MOTU releases newer ones. Once the device is up and running it works brilliantly. I enjoy the ultra low latency (now sample libraries can be triggered by e-drums like never before - I always had a slight latency feeling, even at RTL of 8ms, so having to ~4ms is really nice) Do you get lower latencies with this driver - than with the previous one?
|
jbraner
Max Output Level: -57 dBFS
- Total Posts : 1830
- Joined: 2003/11/06 14:38:35
- Location: Edinburgh, Scotland
- Status: offline
Re: MOTU AVB series
2016/10/12 06:06:32
(permalink)
UPDATE:
MOTU support thinks that me and one other person (maybe you Rob?) are the only ones seeing this problem. I don't think anything is going to happen too quickly with this - esp if they can't reproduce the problem.
I wonder if it is down to different types of USB port? or USB controller?
I'm back on the old driver for now...
|