|
Post by ninworks on Jun 15, 2021 19:23:38 GMT -5
I ran into a latency problem the other day while recording guitars on my buddy's album project. I was able to make it acceptable by lowering the buffer size and putting the Pro Tools into Low Latency Mode. This Pro Tools session didn't have many tracks so I got away with reducing the buffer size all the way but, that got me thinking. What if I had a full-blown, high track count, session running and couldn't get away with reducing the buffer size that much? The latency could be problematic. I have had similar problems in the past.
I came up with a solution that would completely, 100%, make the monitoring of the record-enabled track, latency free and wouldn't use ANY computer resources. I won't bore everyone with the rather lengthy explanation but it will involve me having to take one of my old 8 channel Mogami snake cables I removed from one of my previous recording system racks and fitting it with TRS jacks so I can use balanced signal lines for the connections.
I have to stop thinking about this stuff so much. Every time I do I create a lot of work for myself. The good part of that is that every time I redo something the setup is that much better and easier to use. Maybe someday I won't have to modify anything anymore. Then the formats will change again and I'll have to start all over. Computers don't last forever and when mine breaks my only option will probably be to upgrade if I want to keep doing this. Then the reconstruction begins.
As a kid I started out with all this nonsense because I wanted to be just a guitar player. WHAT HAPPENED??
|
|
|
Post by Auf Kiltre on Jun 15, 2021 20:35:56 GMT -5
Latency drives me crazy, especially when tracking vocals. Today my wife took off to DC for a few days on business and I decided to try retracking a vocal take in her walk in closet. Clothes, clothes everywhere. I didn't want to drag in my Eleven Rack so I dug out my old Mbox Mini and the latency was giving me fits. It all seems so random at times. I've tried all the usual things like low latency monitoring, decreased buffer sizes, but I've not found a consistent solution yet.
|
|
|
Post by ninworks on Jun 15, 2021 21:55:24 GMT -5
It may not help but the first thing I would do is to see if there's a driver update for it. Those things are pretty outdated by now and it's probably been a long time since you looked to see if there are any updates. You never know what will happen.
|
|
|
Post by Auf Kiltre on Jun 16, 2021 8:00:04 GMT -5
Yeah, my only concern is taking this Win7 box back on line. The other really weird thing is how the Mbox reconnected to Pro Tools. I got the usual notification that the device was not the same as the last session. At this point I usually go to I/O, make sure the right device is selected and click "default" on in and out. I could not get "mic" to work when selected for the track. I could see signal hitting the mbox but Pro Tools wasn't mapping the audio under that selection. I had to select "guitar in" and there was my signal. Everything worked as it should under that mapping (gain, phantom power, etc.).
I have some video editing software on this box that introduced an unwanted element in the P/T device section, I'm thinking it probably corrupted something in the mbox drivers.
Bahhh, I want my old portastudio back🤣
|
|
|
Post by ninworks on Jun 16, 2021 11:35:14 GMT -5
I swap back and forth between interfaces all the time. The I/O settings are crucial to making everything work correctly.
The first thing to do is to go to your Settings menu and select the Playback Engine. Make sure the M-box is listed as the current interface. If it's not, go to the dropdown box next to playback engine on that screen and select it then click on OK. If it's already there then close that window and go to the I/O Settings menu. Mine always opens up to the Output tab. Highlight all the devices in the list and click on Delete. After that click on the Default button. Then click on OK. That should make the list show all the current Outputs for the resident interface.
Nest click on the Input tab and do the same thing you did with the Output section. Click on OK and everything for the M-box should be active.
This probably won't help with the latency but it will make all the I/O stuff work as it should.
When you hook back up to the Eleven Rack go through the previous steps with it as well to get everything working again.
I have a Windows 7 laptop out in my shed that I use for looking up stuff online all the time while I'm out there working on stuff. It still works just fine. What you might want to do to play it safe before going online with it would be to disable Automatic Updates in the Control Panel. That way nothing unexpected will happen. I keep all my computer set to that so the updates will only happen when I want them to. If I do an update and it jacks something up I know it was the update and can reverse it. If the updates happen automatically something could go haywire and I'd have no idea what caused it and end up chasing my tail until I found the problem and remedied it. That can take me days sometimes.
|
|
|
Post by ninworks on Jun 16, 2021 11:36:36 GMT -5
Bahhh, I want my old portastudio back🤣 No you don't!
|
|