OK. So I finished re-installing Project5 2.5 on my DAW today. I had left it off when I migrated to Windows 10 x64 and Platinum x64 last July. Wanted to avoid the 32-bit world for a while, if possible.
So really, no point in nit-picking this thing that's over 10 years old, and will still run on Windows 10. No point trying to load this up like a full blown DAW either. But for a musical scratchpad, or a groove machine, it still works
I have $1000+ worth of other software that did not make the trip over at all (stuff that ran OK on Win XP & Win 7).
Taking it for what it is, and not expecting it to be something it's not, it's really a fast, light, synth workstation. The matrix view and clip browser is very well integrated. The workspace is still clean and uncluttered, and doesn't seem outdated at all. I can also load up many of my 3rd party instruments (that didn't exist 10 years ago).
It runs with a fairly low latency on my ASIO drivers, between 5.8 and 11.6 ms (256-512 samples), depending on how I load it with instruments. With 6 or more instruments stacked, I need to bump it up to 512, but that is still usable.
The main thing I observed is that this is a single threaded application, so the internal CPU meter is reflecting the single thread, not the computer total. Probably got to watch out that you don't hit the ceiling, but so far I haven't been able to. No memory issues here either, but I run more synths than samplers, so my memory footprint is usually low.
I tested it with the sample content project,
"You Are That Man (Grandpa Mojo)". This project is scattered over 20 tracks (4 MIDI and 16 audio). The CPU never went above 11% during playback. Project5 is showing RAM use of about 400MB with this project loaded. That song sure brings back some old memories of the first time I installed P5 back in the day
It still is what it was. But it actually runs better on today's hardware. And that ain't bad at all!!!