Da mein Englisch nicht so gut ist, habe ich 2 Fragen bezüglich iCore Prozessoren und Serato...

1. Läuft das TTM 57 auf einem solchen System? Da es ja keinen USB 2 Port hat...

2. Wie würde ich es sonst zum laufen kriegen :D

Du meinste einen imac mit i3, i5 oder gar i7 Prozessor?

Das Ding hat 4 USB 2.0 Ports, also warum sollte es nicht gehen???

Gruß

MG

Hey hoo.. Ja genau... nur scheinbar gibt es da gewisse probleme mit SL1 und TTM 57 bez. USB 1.1 oder 1.0...

MGness, es geht nicht darum wie viele USB 2.0 ports der Rechner hat, sondern darum das es Probleme gab mit Rechnern die icore chips intus haben und USB 1.0 devices (SL1 und TTM 57). Serato hat herausgefunden, wo das Problem lag und mit Apple eine Lösung gefunden. Serato sagt mit der 2.1 Version sollte das Problem gelöst sein, aber erstmal nur für die icore Macs. Hier ein post vom Serato Moderator aus dem enttsprechenden thread im engl. Forum:

Hi thebuttonfreak,

We've had no negative reports regarding the change we made in 2.1 for the i-series Macs, it works.

Depending on how much patience you have left after all of this, you might want to hold off just a little longer on switching to a Mac (unless you've been wanting to switch for a while already) - there's still every reason to believe that the problem can be fixed on Windows just like on the Mac computers with the same issue.

To clarify:

The change that went into 2.1 for the i-series equipped Macs isn't a "fix" to our software, it's what is called a workaround. We switched to an alternative (slightly less "high-performance") way of asking the OS X operating system to handle our USB because the part of OS X we were using before (since the beginning in fact) just to get things going again while we wait for Apple to fix things properly to work with the second-rate USB1.1 support in the new Intel Core 'i' Macs.

The Windows machines that have the problem have the exact same chipset, and the solution to the problem isn't likely to be any more difficult, the only issue is that the "Windows API" for USB (the bit we call out to when we want to send audio from the computer to the Rane box) doesn't allow to tweak things to get it all working again (unless Microsoft get back to us with something hidden that we don't know about) so the change has to be made "under the hood" in the Windows OS.

If the machine with the problem isn't your only Scratch Live computer, then it might pay to hang in there until we hear back from Microsoft with an answer. I can say for now that we are in communication with them and so it shouldn't be too much longer before we find out whether this problem is fixable or not...