But if that is installed and you don't need it I would uninstall it, sometimes 3rd party software include ASIO4ALL without making it super obvious. And this is why to double check what interface Pro Tools is actually using as the playback engine, which you did so it's not using ASIO4ALL. And when you mention things like large latency that can be a sign that is happening. It's easy for Pro Tools to seemingly start up with the wrong interface and if you have ASIO4All installed Pro Tools can access devices via their WDM (not ASIO) driver. The question is were you actually using that ASIO driver for that interface. However, I believe it's quite an old interface nowadays. Doesn't that sound like a cable issue to you? It worked for a moment at the beginning, now it doesn't. I have a strange feeling my USB cables are crap. If all looks good, you can try starting Pro Tools while holding the N key.Īlso, make sure you have a good USB cable before doing any of this. If there is, you will need to find the issue. If it does, make sure there is no red X next to it. Once the system is back up, try plugging in the R16 and seeing if it shows up in device manager. Restart your system, go back into device manager and make sure it is gone.įrom there, I would install the R16 driver and reboot. When the uninstall device dialog is shown, make sure you check the box next to Attempt to remove the driver and click the Ok button. If you do, right click on the entry and select Uninstall Device. Expand the Sound, video and game controllers section and hopefully you will see an entry for the R16. Go into Windows Device Manager and under the View menu, click the option to Show Hidden Devices. You can try disconnecting the R16 from your computer. If it is not showing up in device manager, then there is no way Pro Tools is going to find it. I purchased a Pro Tools Studio perpetual licenses about 4 months ago - What is the oldest ProTools version I'm entitled to use? Perhaps I could try connecting this interface with an even older version?Īre there any alternative drivers for ProTools? Am I able to somehow route the 8 channels of my r16 into VoiceMeeterBanana and then into pro tools, using VM as the ProTools interface? I'm struggling! Could it be a compatibility thing with this driver (which I belive as I say might be a bit old) and the latest version of ProTools? I have done all of this, manually re-installed, restarted, etc. Never let Window plug and pray do anything. Run the installer again, reboot and reconnect the device and see if it works. reconnect the device, make sure it's not found. reboot (even if the uninstaller does not ask for it). Like disconnect the device, run the driver uninstaller. You sometime might need to kick stuff in the guts to make sure a driver really uninstalls and installs OK. Downgrading to a legacy version of ProToolsĪnother note: I was getting an AWFUL lot of latency when I did get it working when I plugged it all in the first time (before it broke) GPU (of some sort, I don't remember which one) Here are some images of the various error messages when I plug the interface back in: However, I then restarted my system, logged in, and now all of the sudden windows won't recognise my audio interface? I have the Zoom R16 setup in audio interface mode, installed the correct audio interface drivers for windows, and was off! I was able to record in ProTools. I have a Zoom R16 (8-channel audio interface) and a perpetual Pro Tools Studio license on a laptop, I'm trying to connect them together to record some drums (timbales).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |