Jump to content


  • Content Count

  • Joined

  • Last visited

About austinpop

  • Rank
    Credo In Aures

Personal Information

  • Location
    Austin, TX

Recent Profile Visitors

23148 profile views
  1. Expanding my listening to another composer with whose music I'm not familiar...
  2. I’m just starting to get to know the Bruckner symphonies, but this album is just incredible.
  3. I have an i7-8700T, so 6 cores/12 threads. I settled on this a while back: 0-3 RoonServer 4-7 stylus 4-7 gstp 8-11 RoonServer and gstp are used when using Roon+StylusEP. Stylus and gstp are used when using Stylus. I will try giving gstp even more resources and see if that helps.
  4. You might be surprised. Exactly. Listen for yourself, and see which you prefer. This is why measuring the power of your particular use case is so useful.
  5. As I’ve reported before, a lower-capacity PSU may “work,” but a higher-capacity PSU can sound much better.
  6. While your meter cannot give you microbursts as @Nenon says, you can still get useful info. Since I don’t know what AC voltage your location has, these current values are hard to interpret. Try setting the meter to display watts, rather than current. Look at watts during - power on - system idle - music playback Assuming you’re in a 220v country, your data already shows something interesting: - EPS and ATX draw about equal amounts of power: 220x0.14 = 31W approx, and 220x0.17 = 37W approx. Validate this by remeasuring watts on your meter. Assuming these power measures are correct, I bet you would benefit from a much heftier PSU - of equal or better quality - to power both ATX and EPS: 6a, 10a or even higher. Remember - amps on your meter are AC amps at 220v, while the PSU current we’re talking about are DC at 19v or 12v.
  7. This stems from an optimization that has been around for some time now, where powering EPS via a separate 12V PSU, or at least a separate 12V rail, yielded dramatic SQ improvement.
  8. Good point, Alex. Low output impedance is a prerequisite for a PSU's ability to deliver instantaneous current bursts. Indeed, I wonder if a PSU's inability to respond instantly to current demand can introduce another flavor of induced jitter in the signal. Maybe @JohnSwenson's white paper addresses this aspect as well?
  9. Yes, please publish your findings here when you get them, along with build details and the exact workload (OS, music player, if HQP - what settings) you used. One useful piece of info that will be useful to others will be the relative consumption between ATX and EPS (CPU). Yes, again - this is not meant to be an exact science. Typically, your PSU should have a capacity several multiples of your observed consumption. But it will tell you, for example the relative weight of ATX and EPS, so you can decide how/where to allocate your resources into the capacity of each rail. Also be sure to observe other infrequent, but intensive workloads, like: library scanning, OS and software updates, for example. And finally, of course, a reminder to look at both peak and steady state.
  10. It's a good question, and one that needs a deep technical analysis. I suspect with the right instrumentation, it would be possible to observe the instantaneous current (and power) demand of a server over EPS and ATX. I just don't know if anyone - perhaps a server vendor - would be willing to publish their findings. I certainly have my suspicions, which I'll list below. Again, note: these are conjectures, not assertions: Current demand of the CPU is extremely peaky, driven both by the workload (software's) utilization of the CPU, the OS and BIOS CPU settings, and by the processor's own management of frequencies, C-States, P-States, and other energy management. A similar profile is likely for ATX as well, driven by the profile of memory accesses, disk, network, and audio (USB) I/O. This could be a contributing factor to why powering network, storage, and USB cards with independent PSUs can be so beneficial. We have been told by designers like Emile of SGM, that reducing latency of OS operations - more specifically, the variance of that latency - positively affects SQ. Well, this same reduction in variance could also be reducing variance in current demand on the PSU. Finally, we have observed the benefits of running the entire OS in memory (ramroot) and buffering tracks in memory before playback (Stylus). Here again, the effect is to reduce the variation in demand during playback, which in turn could be reducing the peaky demand on the PSU. So there is much we don't understand about the causal relationship between PSU size and quality with SQ. But all in all, the above conjectures make me unsurprised that PSUs that can handle extremely peaky current demand, and over-specification in general, have a positive impact on server SQ.
  11. Hi Mario, I don't use HQPlayer, as my DAC prefers native sample rates.
  12. Loving this thread, Brilliant stuff!
  13. First of all, as @bobfa rightly points out, these numbers are AC watts drawn by the PSU, not the DC watts being delivered to the server. I neglected to mention this measurement is only meant to serve as a rough guide. My point about difficulty was addressed at people who are trying to size a PSU for a system that they haven't built yet. Even if you assemble the system, you still need to find temporary PSUs to run ATX and EPS. I don't know - that seems pretty inconvenient to me.
  • Create New...