Their new Quad Core Mobile CPU is interesting.
I’m waiting for a fast desktop quad with Vega GPUs.

But please take my place as the Guinnea Pig.
I luckily have a son I can give anything that won’t work.
Even though the i7 7700k worked the x64 Portaudio.dll had to be tweaked by the Plogue Bidule developer.

I’m not buying anything until 2018, and the DIMMs for DRAM have to be perpendicular for use in a 1U.
Intel is dumping everything they got into the market.
8700k is actually 6 x i5 7000 Series Cores.
Their chipsets keep changing driving everyone nuts, and this keeps motherboard manufacturers too busy trying to be the first guys, rather than making AMD Boards for Racks and ITX Boxes.

ThreadRipper seems to have several issues. The first of which is the fact that it's multiple slabs of silicon in a single 'package'. This means that for memory access and the like the chips act similarly to my dual CPU machines, and require NUMA support for 'ideal' multithreaded access. There's always the 'gaming' mode that drops all of the virtual cores and improves things for games, but even with this setting...

Well, there's a lot of problems for audio users being reported so far. In Gearslutz there are a few builds, and even with RME drivers people seem to not be able to go BELOW 7ms/64samples without major problems (and sometimes not ABOVE 256samples/15ms), and it's not as simple to solve as a DPC issue from GPU drivers or LAN etc. I honestly haven't paid full attention to dig in and see what the specific issue is, but I highly recommend sourcing known working builds for low latency audio if you choose to go with ThreadRipper.

I really hate to spend hours, days, weeks or sometimes even months to try to make a computer just working correctly. I guess this technology is not yet mature. Let's wait for industry to have it usable without too much issue.

Keep in mind those numbers are hearsay, as they are taken from the Gearslutz posts and not my system (I have no TR system here). Latencies differ depending on OS (OSX has extra safety buffers), internal buffers for the A/DA in the soundcard and it's mixer, and so on.......and...I have no idea what's going on with those systems, sorry

valis wrote:Keep in mind those numbers are hearsay, as they are taken from the Gearslutz posts and not my system (I have no TR system here). Latencies differ depending on OS (OSX has extra safety buffers), internal buffers for the A/DA in the soundcard and it's mixer, and so on.......and...I have no idea what's going on with those systems, sorry

I don´t blame you since you mentioned Gearslutz in your post above.

But I remembered those numbers (quoted from Sweetwater) in my post above from using RME cards and drivers as well and they were very close if not identical.

So, when those guys over @Gearslutz use today´s RME cards and drivers, they babble BS because those values mentioned cannot be real at all, regardless if the processor is an Intel or AMD.

And yes, round tip latency differs depending on system, application, drivers and s##t,- but that wasn´t the point.
Buffer sizes are fixed count of samples and fixed relation in time, the calculation based on the sample rate in use.

The new Scope 7 driver, perhaps, works correctly with bad for Scope 5.1 chipset...?

It would be nice from Holger to give us some info about which chipset amongst new ones he would recommend for Xite & PCI. I don't know if he has the oportunity to test Xite with some of new chipsets... I hope he tried with, at least, one new MB, though.

The dream would be that it comes from time to time to discuss all this here... I know that if he does that, it will be a tusnami of questions... That's maybe why he avoids to come on Z... But for technical issues, he is the one who knows the best !