Havent had a problem with Ultralite with previous tie ups with PC and MAC(Intel Desktop, HP, MACbook Pro). meaning, Ultralite is probably not the suspect. i already posted this with someone's other thread. but just want to make this an official query.
i tried the Ultralite with my Dell 1525 laptop with specs 2gb c2d 7200 rpm after installation. . .
using Belkin 5/4 FW 800 PCI-e after disabling Wifi, Lan and other possible interference. .
AUDIO "FREEZES". as in literally FREEZES. . . . i really don't know what the Dell 1525 doesnt understand. arghhh.
effects found since:
1. Audio Freezes
2. SX doesnt accepts the change in MOTU Audio in the Devices Menu. then hangs. . .
3. still counting. . .
poor dell. tried calling Dell with no help.
Configuring Dell 1525 laptop with Ultralite
-
- KVRAF
- 6323 posts since 30 Dec, 2004 from London uk
Some Dell laptops just dont work well for audio. Strip all unecessary software off like virus checkers etc. Firewire is notorious for trouble unless u have a T.I chipet.
-
- KVRian
- 1176 posts since 25 Dec, 2003 from Kentucky y'all
HI,
Dell wont work nor will most new laptops anymore
2 options
1) Buy an USB interface
2) buy a known works for pro audio laptop
Scott
ADK
Dell wont work nor will most new laptops anymore
2 options
1) Buy an USB interface
2) buy a known works for pro audio laptop
Scott
ADK
-
- KVRer
- Topic Starter
- 13 posts since 1 Aug, 2007
peace jcs. happy to see you also here in KVR. i was suppose to get ADK also last '06.
update:
update:
after installing KB885222. it immediately created a folder having a name 256849dc. . . after opening it had a file 1394b windows update.
then, i tried the regular intial setup with MOTU Ultralite. it finally worked. SX recognized the change in device setup.
although i still have to test recording, in order to finally test if it has no pops and clicks. hopefully this week.
ill continue to update you guys.id like to thank the MOTU tech guys for their great replies...
by the way. i'll post their reply here so that when people again use the search button. hopefully they'll find this post.
update:
update:
after installing KB885222. it immediately created a folder having a name 256849dc. . . after opening it had a file 1394b windows update.
then, i tried the regular intial setup with MOTU Ultralite. it finally worked. SX recognized the change in device setup.
although i still have to test recording, in order to finally test if it has no pops and clicks. hopefully this week.
ill continue to update you guys.id like to thank the MOTU tech guys for their great replies...
by the way. i'll post their reply here so that when people again use the search button. hopefully they'll find this post.
-
- KVRer
- Topic Starter
- 13 posts since 1 Aug, 2007
This is the reply of MOTU tech.
Hello,
After installing the hot fix, I recommend backing up your system registry. There is a link on the included support page that outlines this procedure in detail. Once backed up, please try performing the following procedure to ensure that your Firewire controller is operating at the proper bus speed. Also, is this a PC that your built? What type of motherboard are you using?
1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI\1394_hc_hw_id\1394_instance_id\Device Parameters
3. If the SidSpeed value does not exist in the right pane after you click the Device Parameters subkey in step 2, create it. To do this, point to New on the Edit menu, click DWORD Value, type SidSpeed, and then press ENTER.
4. Right-click SidSpeed, and then click Modify.
5. In the Value data box, type one of the values that are shown in the following table, and then click OK.
Value Speed
0 S100 speed
1 S200 speed
2 S400 speed (default value)
3 S400/S800 speed (Windows XP Service Pack 1 [SP1] value)
Note: If you try to use a value that is larger than 3, SidSpeed will use a value of 0 (S100 speed).
6. Quit Registry Editor.
To locate the FireWire controller information, follow these steps:
1. Open Device Manager. To do this, right-click My Computer on the Start menu, click Manage, and then click Device Manager under System Tools. You can also click Properties under My Computer, and then click Device Manager on the Hardware tab.
2. Locate your FireWire controller in the IEEE 1934 Bus host controllers section.
3. Right-click the FireWire controller entry, click Properties, and then click the Details tab.
4. Click Device Instance Id. You see a string of letters and numbers that is similar to the following:
PCI\VEN_104C&DEV_8020&SUBSYS_00D81028&REV_00\4&19FD8D60&0&60F0
The information between the two slash marks (\) is the "1394_hc_hw_id". "VEN_104C&DEV_8020&SUBSYS_00D81028&REV_00" is the hardware ID in this example.
The information that follows the second slash mark (\) is the "1394_instance_id". "4&19FD8D60&0&60F0" is the instance ID in this example.