Core i processors and USB 1.1 audio interfaces - Experiences

As you all may (or not) have read in the last weeks and moths there are more often threads with issues that could not be solved because of the combination of Intel Core i processors and "older" USB 1.1 audio interfaces.
In fact it is something like roulette at the moment: It can work, but it does not have to! I know more than five different machines from i5 to i7, Windows to Mac with which it works and does not!
Sandy Bridge (the new generation processors [correct me if I am wrong]) processors do not work with the U46MKII (USB 1.1) but with an USB 2.0 audio interface like the Hercules DJ Trim 4&6. An Core i7 quad in a Macbook has problems with the U46MKII (USB 1.1) but with an Native Instruments Audio 6 (USB 2.0) it works flawlessly.
My machine (Intel Core i5 460M) has no problem with the U46MKII and the build in audio interface of the U-Mix Control Pro (both USB 1.1). But the latency has to be increased a lot. At the moment (July 2011, Cross 1.6.0) I can only run it with a latency of 10ms in timecode mode. With the Hercules DJ Trim 4&6 (USB 2.0) I can mix in timecode mode with 4ms @ 44.1kHz and 4ms @48kHz without a drop out or anything else. I can still decrease it!!!
One of my best friends bought a comparable machine to mine (same vendor, same processor, same RAM, same HDD but a NVIDIA graphic card instead of an ATI). We could not get Cross and the U46MKII (USB 1.1) nor Cross and the Stanton Scratch Amp (Version 1.5, firewire) to work. Absolutely no chance!
From my experience (THIS IS NO OFFICIAL MIXVIBES STATEMENT) you will get problems if you use Cross with an Intel Core i processor and a USB 1.1 audio interface. If you have this problem and solved it by using a USB 2.0 audio interface please reply to this thread to support my theory. Even if you have found another solution please reply to this thread! Thank you!
This thread will be marked as sticky because I think that it is totally important to have this in mind while buying a new machine! Additionally we should build some kind of blacklist (and maybe whitelist) with machines in that are tested and do not work - what do you think?
Thanks for reading!!!
Cheers,
Steve
In fact it is something like roulette at the moment: It can work, but it does not have to! I know more than five different machines from i5 to i7, Windows to Mac with which it works and does not!
Sandy Bridge (the new generation processors [correct me if I am wrong]) processors do not work with the U46MKII (USB 1.1) but with an USB 2.0 audio interface like the Hercules DJ Trim 4&6. An Core i7 quad in a Macbook has problems with the U46MKII (USB 1.1) but with an Native Instruments Audio 6 (USB 2.0) it works flawlessly.
My machine (Intel Core i5 460M) has no problem with the U46MKII and the build in audio interface of the U-Mix Control Pro (both USB 1.1). But the latency has to be increased a lot. At the moment (July 2011, Cross 1.6.0) I can only run it with a latency of 10ms in timecode mode. With the Hercules DJ Trim 4&6 (USB 2.0) I can mix in timecode mode with 4ms @ 44.1kHz and 4ms @48kHz without a drop out or anything else. I can still decrease it!!!
One of my best friends bought a comparable machine to mine (same vendor, same processor, same RAM, same HDD but a NVIDIA graphic card instead of an ATI). We could not get Cross and the U46MKII (USB 1.1) nor Cross and the Stanton Scratch Amp (Version 1.5, firewire) to work. Absolutely no chance!
From my experience (THIS IS NO OFFICIAL MIXVIBES STATEMENT) you will get problems if you use Cross with an Intel Core i processor and a USB 1.1 audio interface. If you have this problem and solved it by using a USB 2.0 audio interface please reply to this thread to support my theory. Even if you have found another solution please reply to this thread! Thank you!
This thread will be marked as sticky because I think that it is totally important to have this in mind while buying a new machine! Additionally we should build some kind of blacklist (and maybe whitelist) with machines in that are tested and do not work - what do you think?
Thanks for reading!!!
Cheers,
Steve