Since the 3.3 test was made after i did the 3.4 test i re-ran the 3.4 test in which it passed with 8 cpu and 100ms… Which has lead me to belive it might have been an unlycky coincidence where the scan of midi-devices occured at about track 249 the last time…
that’s exactly why i wanted to get one in the first place.
this CPU is totally bonkers in terms of single-threaded performance, especially since you can easily let it boost to 5.5-5.7Ghz for single core usage and take back the clock and voltage for heavy load (4+ threads).
perfect for renoise and realtime audio in general.
1 core: 97 RPTS
2 cores: 177 RTPS
3 cores: 256 RTPS
10: cores: all passed with peak of 55%
Indeed that Intel CPU has an impressive single core performance. But keep in mind that M1Pro is a mobile cpu, and the fan did not even seem to have kicked in. Maybe this is a sign that Renoise still could use the M1Pro even more efficiently. This performance is more than enough for me. I understand though that Apple is not attractive for a lot of people and always comes with annoying compromises. I wonder how your CPU would perform under macos/hackintosh, since after reading the numbers here, it seems to me that the macos Renoise actually can perform a bit better than the Windows version…?
The M1 ARM CPUs are indeed way more power efficient relative to the performance you can get out of the latest x86 offerings from Intel. I’m pretty sure that x86 will get in serious trouble throughout the next years, when Apple refines their CPUs and the architecture gets more widely natively supported by software.
i’m not sure how well hackintosh would perform with Intels Alder Lake platform, which utilizes Performance and Efficiency cores, since the OS’s thread scheduler needs to spread the loads correctly across those cores, in order to avoid workloads from running with pulled handbrake on E-Cores, when P-Cores would’ve been more adequate. I would have not migrated to Win11 if Win10 could have done that properly in all cases.
edit
a quick google revealed, that macOS will not differentiate between P- and E-Cores:
“XNU scheduler does not distinguish core types in macOS and will work no better than current Windows 10 in terms of core assignment.”
Well investigated, directly from the main opencore dev Indeed this does not look like a good option currently, but I am quite sure they will have patched everything within a year.
Decided to ditch modern Ryzen and go back to server classics of the past.
Think that i’ll keep that Xeon. Neat performance due to hi-core count and large cache.
Windows 7 x64 SP2+ ESU Intel Xeon E5-2696v4 22c/44t/64Gb RAM 2400/NVMe 980 Pro ESI Maya 44 eX PCIe
Renoise 3.4.2 Reg
ASIO/48Khz/~5ms
CPU overload protection: 98%
1CPU reached:
track:48
fx: 288
Cracks appeared at track 44
2CPU reached:
track:94
fx: >552
Cracks appeared at track 80
32CPU reached:
track:257 and without any problems reached [Ta! Amiga Rulez!!!]
fx: >~1500
No cracks at all
Max Load: 32%
44CPU reached:
track:257 and without any problems reached [Ta! Amiga Rulez!!!]
fx: >~1500
No cracks at all
Max Load: 28%
Nice, maybe also try to disable the recent microcode for the cpu without spectre fixes and so on. I don’t know how old your cpu is, but this can heavily increase the performance of older Intel cpus.
CPU: _____________ Intel i5-13600K | 6 P core, 8 E Core, 20 Threads OS: ______________ Pop_OS Linux Interface: _______ Jack Latency: _________ Not sure, probably 10ms or so
01 CPU: 121 RPTS 02 CPU: 237 RPTS 20 CPU: All Pass w/ 40% peak CPU load
Indeed this does not look like a good option currently, but I am quite sure they will have patched everything within a year.