Oh well, I guess I should find a decent old Sony Vaio Pent IV machine for cheap. When I donated my old Pent IV machine to a young student I didn’t realize I’d lose access to SX. It’s a shame (rip-off) the powers that be felt no obligation to create and offer up “some” form of a fix to “grand-father” it into the next generation of hardware, especially seeing as how Win 10 doesn’t seem to have a problem with. I realize it’s “old” software, but I liked it, and it perfromed well. Generally, Cubase SX leaned more toward the “high-end” of software, which makes me wonder exactly why it was so readily abandoned. Of course, it had slipped my mind that SX was designed around the Pentium IV, and how was I to know exactly how “exclusive” and “rigid” this design apparently is? I keep my system updated, but apparently MS isn’t going to create/release a new Microsoft C + + 2018 Redistributable (圆4) xxxxxxxxxxx that will enable compatibility with the new Intel Core machines, assuming that’s even possible. I remember some very nice latency values of 13ms, 26ms, etc. I was always quite happy with my simple 1.3GHz Pentium IV/MOTU 828 (FireWire) setup. I did this hoping to use Cubase SX again. Nevertheless, I went ahead and bought/installed a Texas Instruments 1394 OHCI Compliant Host Controller for the Intel Core i7-6700 CPU 3.40GHz machine I purchased a couple of yrs ago, and it works fine with Win 10. Yes, I realize that Thunderbolt, USB 3.0, & USB-C have all sped past FireWire. I never used this Sync IN connection with my old Sony Vaio Pent IV because I had no use for an ADAT machine. Win 10 likes it well enough to allow the install, IEEE 1394 and all.
The 828 I have is the very first version they made–what MOTU now refers to as the “Original”, & yes I do have the latest drivers. Thanks for your quick reply, MrSoundman.“Absolutely, …via it’s ADAT ports.”- Are you speaking of ADAT “ports” found within the software?,–because the rear panel of my 828 has only the 9-pin ADAT Sync IN connection.
0 kommentar(er)
