MOTU with Bootcamp - anybody?

[JPeters86]

Hi folks,

Is anybody succesfully using a MOTU device while running Windows XP via Bootcamp? I've tried before with my 8pre but I never got it to work. I'm considering a switch from Logic to Reaper but don't have the dough to buy a new PC now, so I want to use my MBP instead.

Any comments greatly appreciated.

Best!

[JPeters86]

Nobody?

[MonkeyAdam]

Why don't you use the Mac version of Reaper? Wasn't there a stable (non-beta) version?

[JPeters86]

Originally Posted by MonkeyAdam

Why don't you use the Mac version of Reaper? Wasn't there a stable (non-beta) version?

Yes there is, but I'm eager to try out some Windows VST only plugins, like that new tape emulator. I thought I might give it a try just as well. Well I'll just try if I get it to work this time and report back.

Thanks!

[andsonic]

I'm using a PCIe 424 with a 24 i/o, 1296, and 2408. No problems on our MacPro with bootcamped XP pro.

[JPeters86]

Good to hear, thanks!

[JPeters86]

Just giving this a little bump.

I can't seem to get it working after all. I get a BSOD every time Windows 7 boots on my MBP (mid 2007). Installing the MOTU drivers in Windows works OK, but I can't get the audio working. Very strange!

[andsonic]

Originally Posted by JPeters86

Just giving this a little bump.

I can't seem to get it working after all. I get a BSOD every time Windows 7 boots on my MBP (mid 2007). Installing the MOTU drivers in Windows works OK, but I can't get the audio working. Very strange!

...just wanted to add that whilst the PCI 424 is working fine, I've had no luck with firewire audio interfaces. My Mackie Control is working just fine over USB & I can mount firewire hard drives. I just can't get any firewire audio interfaces to work.

[JPeters86]

Originally Posted by andsonic

...just wanted to add that whilst the PCI 424 is working fine, I've had no luck with firewire audio interfaces. My Mackie Control is working just fine over USB & I can mount firewire hard drives. I just can't get any firewire audio interfaces to work.

Thanks for sharing.

I eventually got it working but I still keep getting BSODs. Also the audio output gets f'd up pretty bad on some moments, also when just playing an mp3 trough media player. It definitely has something to do with the firewire device, without it everything works totally fine. Very strange...

[helm's deep]

just wanted to add that I as well have had very bad luck with firewire stuff on a pc. for some reason it just hates it. I used to use the motu 896, and even the firepod, and i would get BSOD all the time as well. I'm going pcie, you should consider that as well.
best wishes!

[wags3d]

Hi All,

I just bought a Mac-Mini Core 2 Duo and I was trying to get my MOTU 896 firewire interface to work with Win XP Pro SP3 running under bootcamp and Snow Leopard 10.6.7. I loaded the MOTU drivers and got the computer to recognize the 896 but I was getting no audio through it.

After much searching and gnashing of teeth I found this fix and it worked. I wanted to share this for anyone in the future trying to fix a similar problem. The solution seems complex but it actually was fairly easy. Be sure to back up your registry first! Just google how to back it up then follow these directions. This worked for me, what a relief since I bought the mini specifically to do this.

Solution:

There is a setting in the Windows registry that controls the data rate between the FireWire adapter and connected devices. Adjusting this setting might resolve the problem you're experiencing. Please follow these steps to adjust this value in the Windows registry. Make sure to power off your Traveler before hand.

1. In the Start menu, choose Control Panel > System > Hardware. Click the Device Manager button.

2. In the Device Manager, expand the section titled IEEE 1394 Bus Host Controllers. Right-click on the FireWire adapter device to which the audio interface is connected, and choose Properties.

3. In the Properties window, select the Details tab. In the Property dropdown menu, select Device Instance ID.

4. In the Value field, you will see a string of letters and numbers that is similar to the following:

PCI\VEN104C&DEV_8020&SUBSYS_00D81028&REV00\4&19FD8D60&0&60F0

The second and third parts of this string are significant. The portion of the string between the two backslashes (\) is the hardware ID for the FireWire adapter. The portion of the string following the final backslash is the instance ID. Keep the Properties window open or save these values.

5. In the Start menu, choose Run. Type regedit at the command prompt. Press return to launch the Registry Editor.

6. In the Registry Editor, navigate to this registry subkey using the folder hierarchy at the left side of the window:

HKEYLOCAL_MACHINESYSTEMCurrentControlSetEnumPCIhardware_IDinstanceID

The hardware_ID and instance_ID are the values from step 4 (Device Manager > FireWire adapter properties > Details > Device Instance ID).

7. When you have reached this subkey, select Device Parameters. In the right side of the window, you may see one or more defined values. If you see a value named SidSpeed, continue to step 8. If the SidSpeed value does not exist in the right pane after you click the Device Parameters subkey, you will need to create it. To do this, open the Edit menu and choose New > DWORD Value. Type SidSpeed for the value's name, and then press return.

8. Right-click on SidSpeed, and select Modify. In the value data field, enter 3, and then click OK.

9. Close the Registry Editor program, and then restart the computer. After the computer has restarted, log in to Windows and test the problem again.

[CinningBao]

Very interesting - I've not had much luck with my 828mk2 and XPpro on bootcamp, BSOD way too often, and this is doing things I've not tried before.. I'll test this out when I get back to the studio.

Thanks!

[erdwandler]

wags3d you made my day!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
helped me with my MOTU Ultralike mk3