|
Post by winetree on Sept 9, 2016 1:16:27 GMT -6
Wiz, It'll probably be Early next week, I'll have to go to a friends house to SKYPE. HAVE A GOOD GIG ROBERT
|
|
|
Post by wiz on Sept 9, 2016 4:15:24 GMT -6
Wiz, It'll probably be Early next week, I'll have to go to a friends house to SKYPE. HAVE A GOOD GIG ROBERT no problems I can call your home or cell
|
|
|
Post by sam on Sept 13, 2016 9:04:07 GMT -6
I've had a 16A for about a year and a half now, and I love it. I never think twice about anything in my signal flow anymore. TB to the iMac is great, and straight IO instead of pres or anything in the way is nice. I almost never use the DSP or open the MOTU mixer, I just have it set up so I can run everything in PT, and the 16A is just my method of transport.
|
|
|
Post by hardtoe on Sept 15, 2016 22:13:23 GMT -6
Do people still sweat the big Ben? I haven't heard any mention of it in years I'm clocking the Motu 1248 off a Big Ben (at 44.1)- Coming from an Apogee Ensemble, the Big Ben made the 1248 feel a bit more like the sound I was used to from the Ensemble (but with greater clarity and depth). Without the Big Ben, the 1248 sounds a little soft in the midrange image on my setup, but the external clocking gave me a monitoring sound I could work with - tighter and more pokey - I also clock the Ensemble and a Audient Mico off the BB as well. Bought the Big Ben 192 used for $700 in mint condition - I also tried the Black Lion Micro Clock MKII, but I didn't like how it sounded - seemed to fuzzy thing up harmonically like feathered hair - the opposite of making things tighter like the Big Ben did...
|
|
|
Post by indiehouse on Oct 18, 2017 15:05:09 GMT -6
Are people still digging the 16a? I've got a chance to pick one up cheap. Had a go with one a couple years ago and was having driver issues with my Mac mini. Tech support couldn't figure it out and blamed my computer. I sold it and got a BF Apollo 16 which has been rock solid. Also, the Motu matrix was very non-intuitive to understand.
I was thinking I could pick up the Motu, ditch the Apollo and pocket a grand. Not sure if it's worth the trouble? Also, not sure of the conversion quality difference?
|
|
|
Post by guitfiddler on Oct 18, 2017 16:04:59 GMT -6
Still wondering myself...
|
|
|
Post by wiz on Oct 18, 2017 16:10:12 GMT -6
I still dig mine.
Check the music videos in my signature every one is using the 16a.
Also note that every single track,has been through at least 4 trips of conversion! 3 here 1 at the mastering house!
i don't even think about the quality of conversion anymore.
Cheers
Wiz
|
|
|
Post by EmRR on Oct 18, 2017 18:24:00 GMT -6
No problems with the sound here.
|
|
|
Post by indiehouse on Oct 18, 2017 18:29:40 GMT -6
No problems with the sound here. How's stability for you? Routing? Latency? Those are more important than sound, as I'm pretty confident the Motu sounds great. The giant Motu troubleshooting thread on GS is concerning, on top of the stability problems I had. I was buried in projects at the time and needed something that just worked. I didn't have time to mess around with a system that was unstable, so I ditched it. Also, I hear that latency is an issue if your trying to track to a session that already has some processing. Is latency an issue if I'm going to overdub on a session that's heavily mixed and has a fair amount of plugs and outboard?
|
|
|
Post by wiz on Oct 18, 2017 18:45:53 GMT -6
No problems with the sound here. How's stability for you? Routing? Latency? Those are more important than sound, as I'm pretty confident the Motu sounds great. The giant Motu troubleshooting thread on GS is concerning, on top of the stability problems I had. I was buried in projects at the time and needed something that just worked. I didn't have time to mess around with a system that was unstable, so I ditched it. Also, I hear that latency is an issue if your trying to track to a session that already has some processing. Is latency an issue if I'm going to overdub on a session that's heavily mixed and has a fair amount of plugs and outboard? I have not experienced anything of the above... on Mac , using Logic cheers Wiz
|
|
|
Post by subspace on Oct 18, 2017 18:52:10 GMT -6
I haven't had any driver issues running Thunderbolt on a MacBook Pro since 2015. I've seen lots of "interesting" posts from Windows users about MOTU drivers since they came out with them, not my circus, not my monkeys. Sound quality is high, latency is low. Latency with a high CPU load works exactly like any other interface I've had, if the project runs at a particular buffer setting with one interface, it will run at that setting with the MOTU, the latency will just be lower by comparison. The routing matrix is a patch bay between the internal digital mixer, your software, and the 16A's physical outputs, so starting with the presets is easiest.
|
|
|
Post by EmRR on Oct 18, 2017 19:23:33 GMT -6
All my previous comments on system stability still stand. Every new driver release is a chance to hold my breath, and, driver updates are confoundingly impossible with normal system connections in place, the whole thing has to be torn down and re-patched one box at a time to do updates: exactly the opposite of what a distributed AVB system in a large facility should require. Mac here, TB connection to Mac, AVB between M8 and 16A. Lose the TB connection and hardwire AVB directly to the Mac for updates! Then do the next box! Now do that from master control down at the old sports arena! Then put it all back together! I don't have latency issues, because I use the AVB mixer(s). I guess all the people with latency issues are trying to avoid it, which is impossible, or what you get. Routing is comprehensive. But. No talkback path; I still need a dedicated stereo input TB box so I can talk to 3 separate HP mixes at once with control room monitor dimmed. With 16A and Monitor 8 I have 4 AVB browser windows open, on top of the DAW window. One AVB mixer is playback monitoring for overdubs, one is live input monitoring, one cascades into the other. Both AVB mixers are maxed out. It's kind of a fucking nightmare, but the only way to make it all work. All this modern crap is designed for people tracking one thing at a time, with no professional concessions for traditional multi-input/musician live tracking and overdubs. If I had patchbay multing inputs to both converter and console B mix, with DAW playback into main channel inputs, I could avoid AVB mixing completely. Or MOTU could bother to write the code so inputs would auto route to outputs as all their previous products did. But, in 3 years of people asking, they haven't, so forget it. But it sounds fine! I have no idea what people discover on other modern converter interface systems, better or worse. Rant over!(?)
|
|
|
Post by dandeurloo on Oct 18, 2017 20:15:56 GMT -6
Mine has been rock solid for a few years. I haven't updated in over a year. So, I have no idea if any updates cause issues.
I have a 16a and 24Ao connected to each other via AVB and the main interface connected to my mac through TB. Doing it this way I have really low latency. I don't use the MOTU mixer much. I actually try and avoid it as much as possible.
I do clock mine off of the BLA Micro Clock III XB. It helps.
My 2 cents
|
|
ericn
Temp
Balance Engineer
Posts: 14,939
Member is Online
|
Post by ericn on Oct 18, 2017 21:03:38 GMT -6
Ah, i see. For consideration: Even if your interface is lower latency, this does not mean you do not have to think about latency at all. It heavily depends on your digital signal chain. There is no problem for us to record with 5.6 ms latency setting (or in this ballpark) for recording with inbox cue. If i add specific plugins, say an Acustica nebula-based effect, Klanghelm compressor in HQ mode etc., adding live softsynths, multichannel samplers etc, the audio engine can become unstable with low latency, getting dropouts, while beeing totally OK at higher latency. It must not even depend on the horsepower of your computer alone. Surely, more speed and RAM can minimize issues, but often enough this is in no relation to the problem. Even after optimizing your OS for low latency, let's have a single part of the DAW software or used plugins have a problem, and bang, you can only get away with higher latency setting. There is no such thing like "zero" latency at all in digital world. It's marketing bogus. It simply does not exist. Each and every audio stream needs a buffer and it needs a buffer that is considerably higher than a "realtime" double byte value that the cpu can process in a single instruction clocked in GHz land. Magnetudes higher. And this will not change to become a non-issue you don't have to think about, anytime soon, because no way processing power/speed will increase several magnitudes in forseeable future. Right now, it is actually stuck around 4-5 GHz and parallelization of processing is used to overcome the issue in most applications. So ultralow latency is not unproblematic only because your interface has no problem with it. Whenever an audio buffer is underrun or overflown, things get nasty. No matter, where this happens along the road. A spike in a computer thread due to anything happening in your DAW, non-even balance of the cores, each and every problem that can appear can make latency an issue if one of the audio buffers runs empty or could not take any more samples (buffer overflow) when the following processing can't keep up with it. The lower the latency setting, the worse. Independent of the interface minimum latency. That's what i wanted to express with my remark, that the DAW processing, if fairly heavily used, easily has more to do with the need of higher latency settings, than the interface itself. I consider below 10ms a non-issue, as long as i don't monitor over headphone, and have some oldschool "live-feeling" experience, even as a bass player. Drummers may or may not have already problems with it. EASIEST way ever to never care about latency again is *analog cue*. In fact it's the only one. No (perceivable) latency in the monitoring for the recorded artist at all. At least a magnitude below perceivability i guess, no matter how heavily you send the analog signal thru long runs and (analog) processing. I actually see no real alternative for that at all, if you don't want to think about latency. It solves so many problems at once and is so easy to achieve. Split recorded signal and use analog cue on a mixer, done. Sure, leave it to you to get all deep and technical 😎! Since grabbing the RADAR V I haven't noticed latency, it's like being back on TDM or HD!
|
|
|
Post by terryrocks on Oct 18, 2017 22:26:39 GMT -6
I’ve had a 16a for 2-3 years and it works great. Actually contemplating a second unit for more i/o so I can hardwire units like zod and kemper.
|
|
|
Post by indiehouse on Oct 19, 2017 9:04:36 GMT -6
All my previous comments on system stability still stand. Every new driver release is a chance to hold my breath, and, driver updates are confoundingly impossible with normal system connections in place, the whole thing has to be torn down and re-patched one box at a time to do updates: exactly the opposite of what a distributed AVB system in a large facility should require. Mac here, TB connection to Mac, AVB between M8 and 16A. Lose the TB connection and hardwire AVB directly to the Mac for updates! Then do the next box! Now do that from master control down at the old sports arena! Then put it all back together! I don't have latency issues, because I use the AVB mixer(s). I guess all the people with latency issues are trying to avoid it, which is impossible, or what you get. Routing is comprehensive. But. No talkback path; I still need a dedicated stereo input TB box so I can talk to 3 separate HP mixes at once with control room monitor dimmed. With 16A and Monitor 8 I have 4 AVB browser windows open, on top of the DAW window. One AVB mixer is playback monitoring for overdubs, one is live input monitoring, one cascades into the other. Both AVB mixers are maxed out. It's kind of a fucking nightmare, but the only way to make it all work. All this modern crap is designed for people tracking one thing at a time, with no professional concessions for traditional multi-input/musician live tracking and overdubs. If I had patchbay multing inputs to both converter and console B mix, with DAW playback into main channel inputs, I could avoid AVB mixing completely. Or MOTU could bother to write the code so inputs would auto route to outputs as all their previous products did. But, in 3 years of people asking, they haven't, so forget it. But it sounds fine! I have no idea what people discover on other modern converter interface systems, better or worse. Rant over!(?) I remember racking my head trying to figure out the AVB mixer and the routing matrix. It made me really appreciate UAD's console and it was actually a relief to go back to that when I picked up the BF Apollo 16. True, the routing options may be more limited than Motu's, but UAD Console is just so intuitive to use.
|
|
|
Post by adamjbrass on Oct 19, 2017 9:08:02 GMT -6
Do people still sweat the big Ben? I haven't heard any mention of it in years its a good box, but there are certainly better, more accurate clocks in some new AD converters. but the best External Clock I have tried is the Grimm CC1/CC2,
|
|
|
Post by dandeurloo on Oct 19, 2017 19:30:37 GMT -6
All my previous comments on system stability still stand. Every new driver release is a chance to hold my breath, and, driver updates are confoundingly impossible with normal system connections in place, the whole thing has to be torn down and re-patched one box at a time to do updates: exactly the opposite of what a distributed AVB system in a large facility should require. Mac here, TB connection to Mac, AVB between M8 and 16A. Lose the TB connection and hardwire AVB directly to the Mac for updates! Then do the next box! Now do that from master control down at the old sports arena! Then put it all back together! I don't have latency issues, because I use the AVB mixer(s). I guess all the people with latency issues are trying to avoid it, which is impossible, or what you get. Routing is comprehensive. But. No talkback path; I still need a dedicated stereo input TB box so I can talk to 3 separate HP mixes at once with control room monitor dimmed. With 16A and Monitor 8 I have 4 AVB browser windows open, on top of the DAW window. One AVB mixer is playback monitoring for overdubs, one is live input monitoring, one cascades into the other. Both AVB mixers are maxed out. It's kind of a fucking nightmare, but the only way to make it all work. All this modern crap is designed for people tracking one thing at a time, with no professional concessions for traditional multi-input/musician live tracking and overdubs. If I had patchbay multing inputs to both converter and console B mix, with DAW playback into main channel inputs, I could avoid AVB mixing completely. Or MOTU could bother to write the code so inputs would auto route to outputs as all their previous products did. But, in 3 years of people asking, they haven't, so forget it. But it sounds fine! I have no idea what people discover on other modern converter interface systems, better or worse. Rant over!(?) I remember racking my head trying to figure out the AVB mixer and the routing matrix. It made me really appreciate UAD's console and it was actually a relief to go back to that when I picked up the BF Apollo 16. True, the routing options may be more limited than Motu's, but UAD Console is just so intuitive to use. I agree, it is easy to get lost in. But I will say Motu tech support has been very very helpful. I have been shocked at how good they are to their clients. That is a major plus IMO.
|
|
|
Post by kcatthedog on Oct 19, 2017 19:49:46 GMT -6
@dander didn't you mod yours a fair bit ?
|
|
|
Post by porkyman on Oct 19, 2017 21:53:44 GMT -6
I had driver issues and got sick of trying to figure out the routing every time I wanted to change something. It's just really bad. I don't understand how intelligent ppl created it.
|
|
|
Post by dandeurloo on Oct 19, 2017 22:14:36 GMT -6
@dander didn't you mod yours a fair bit ? Yeah, a lot!
|
|