Simply click the “ OK” button to continue. Plug in your Mbox and wait until the “ Found New Hardware” box pops up. Note If you have purchased a Command|8 control surface, check the Command|8 & Drivers boxĬlick the “ install” button. Only “ Pro Tools LE 8.0“, “ Application Files“, “ DigiRack Plug-ins” & “ Pro Tools Creative Collection“ should be Checked. The installer does this part for you, just click “ next” Open the unzipped “ Pro_Tools_LE_v8_56243” folder & go into the “ Pro Tools LE Installer” folder, then click on the first “ setup.exe” icon to open the installer.
Note: If you downloaded Pro Tools 8, you will need to right click on the downloaded file ( Pro_Tools_LE_v8_56243.zip) and choose “ extract” or “ extract all“Once the file is extracted you will have a new folder called “ Pro_Tools_LE_v8_56243“.
Insert the Pro Tools LE disk, or open Pro Tools 8 Installer you’ve downloaded. If you’ve plugged it in already, go ahead and unplug it now. Choose your OS below:Īt this point, your mbox should still be unplugged. To make this process go smoothly, I encourage everyone to optimize their computer fist. Setting Up the Mbox 2 ( Windows ) First Things Firstīefore we start plugging things in, we first need to install the Pro Tools software. There is definitely a way to get it to run though (because I’m still currently using the M2 as my audio interface).If you’re new to Pro Tools, have just purchased an Mbox 2, Mbox 2 Mini, or Mbox 2 Micro – or just need help setting everything up, this article is for you. I remember the error you’re mentioning, and getting very frustrated that it was losing connection during the updater. Jeeze, this is me remember 2 years back now and I wish I remembered more clearly what I had to do for you. Since the M2 takes a while to turn on, and sort of “boot up” i think i did something along those lines to give it time to be restart fully before continuing in the process. I want to say I did something odd like the SECOND the Mbox restarts I used the VirtualBox pause command to pause it, and then hopped in the VM’s settings and reminded the VM that the Mbox was connected. I want to say it’s something like the updater restarts the Mbox, and by restarting it, VirtualBox loses connection with it for a moment, and then the Mbox updater fails to continue the update process. 
Oh this sounds really familiar! I think i may have had to do something odd to get around it.
0 kommentar(er)
