Jump to content

TheAttorney

Members
  • Content Count

    134
  • Joined

  • Last visited

1 Follower

About TheAttorney

  • Rank
    Sophomore Member

Personal Information

  • Location
    UK

Recent Profile Visitors

1273 profile views
  1. I've found a link (not the original one I had in mind) to a thread about silver/gold resistivity: here It's on the audiotruth site, which is enough said for many if us. But it does claim that resistivity is not linear to the % gold added. But apart from that, this Mundorf wire is likely to be top of my list for the next time I decide to make another DC cable 🙂
  2. I'm a fan of "silver with a bit of gold" cables, based on past experience of Siltech phono cable and Toxic headphone cables. But one thing puzzles me regarding use as a DC cable: Adding say 1% gold to a silver cable is known to increase its resistance by a proportionally much larger amount. I can't track down the exact values at the moment, but I remember that it increases resistance to significantly higher than copper. A while back, some "sound scientists" were giving the Toxic designer a hard time on this topic. And for DC power supplies it's understood that lower resistance is better (all else being equal). So if this silver gold DC cable sounds so good, then there must be something else going on that trumps the negative aspects of increased resistance?
  3. For the last 2 or 3 updates, I've not come out of ramroot in order to do the update, and I've not noticed any issues in updating this way: I can see new updates when they're available, I can do the updates, and everything still works after any subsequent reboot, all without ever leaving ramroot. As a precaution, I do a "Save FS to Disc" after each update. I'm not sure if even that is necessary, but it's easy to do, so I may as well do it. EDIT: It's not necessary to "check for software updates" because an update tab automatically appears in Settings screen when an update is available. If you don't get this then something is wrong, but I don't think it's necessarily to do with ramroot.
  4. I recently tried both the above and 0 gstp 1-2 stylus 3 with my standalone, no DSP, Stylus on my 4 core NUC7i7DN, but I still went back to my long term 0-1 stylus 2 gstp 3, which sounded more natural and focused (one man's "airy" is another man's "bright"). However, the differences were quite subtle to my ears. The original reason for choosing my long term setting was because, when looking at the CPU load/temp display, Stylus took up the least CPU load, then gstp, with "everything else" taking up the most. Therefore it made sense to allocate more cores to the thing that took the biggest load. But with so many variables, it's no surprise that others get different results.
  5. When in queue buffer mode, I have no issues with clicking on a different track - it plays immediately. But I do have the much smaller redbook FLAC files. I also don't hear much sonic advantages in queue buffering vs single track buffering. For those that do hear a difference, please elaborate what that is and does it only apply to the first few seconds of each track? There appears to have been an improvement to the single track buffering as well: Previously, the next track only loaded at the point I skipped to it, and very occasionally I would not hear the first split-second of that track. Now it looks as if the next rack is always pre-loaded and it's the track-after-next that is buffered when the next track starts. So it's always one step ahead and that seems to work well - so far I've never missed the first split-second of the next track.
  6. 20200124 - Clarified use of HQPlayer Ccontrol API by StylusEP both in Euphony app and in Signal path display in Roon client - Fixed StylusEP playback of DSD files converted to PCM by Roon via HQPlayer Control API - Fixed UI hangup when clicking albumartist in Album info dialog - Fixed NAA endpoint device selection in HQPlayer settings - Fixed initial volume when using StylusEP through HQPlayer Control API - Fixed Artist view list display (sometimes, when songs without artist tag were found in library, nothing was displayed in the list) - Fixed Summus playback mode when using StylusEP through HQPlayer Control API - Fixed Summus playback mode indication when used as endpoint (refresh page if necessary to see current status of Summus playback mode) Looks like a new bug has been introduced with this latest release: "Now Playing" screen doesn't appear when I hit bottom left album icon - there's just a background displayed. This is on both Edge and Firefox browsers.
  7. Question: How many audiophiles does it take to change a light bulb? Answer: 3 (1 to change the bulb, and 2 to argue about how much better the old one was)
  8. I have Stylus running on 7i7DN in the small, fanless, Porcoolpine case. The CPU speed makes a huge difference to the CPU temperature. At full throttle (Turbo and Hyperthreading on), the temp hovered around 70C. At my current setting (1.1 Ghz, hyperthreading off) temp is around 36C, and total server AC power consumption is a miserly 8W. Any speed up to the base 1.9Ghz makes only a small difference to temp - it's the Turbo boost that greatly impacts temp. When I had hyperhthreading on, the faster CPU speeds sounded better, as is current consensus around here. With hyperthreading off, I heard little difference between the CPU speeds - and actually slightly preferred current setting to Turbo. This could have been wishful thinking because the peace of mind of low temp (and helping save the planet) makes me feel so much more relaxed that it makes my system sound better too 🙂
  9. I think it is normal to have these partitions - mine are the same. From memory, the two 3.4GB partitions are for the Current and Last Saved versions, used so it's easy to roll back to the Last Saved version for any reason - something I've never needed to do.
  10. Yes, I've since edited my post in the meantime with more info. Anyway, I'm pleasantly surprised that this feature works at all, considering I'm using ramroot and queue buffering with only 4 GB RAM (not doing any DSP probably helps).
  11. Where is this option located? I can't find it anywhere, but I seem to have it set anyway because there is now no buffering when skipping to next track, and most of my queued items are marked blue. I say "most" because I currently have over 100 tracks in my play queue and only 4GB RAM, which is shown to be over 80% used (and marked red, implying a limit is being reached). Despite this low memory, Stylus keeps playing and adjusting what's marked Blue, so I imagine it's dynamically adjusting what's buffered when it gets to RAM limits. EDIT: I've found it now, at the top of the queue. It displayes that 100 tracks are buffered, out of 117 currently in queue. But there is still a small bit of disc activity when skipping tracks. One small enhancement (that I had requested), that's not listed in the change log, is that the current track playing is now always in display whenever you get back to the play queue. Previously, returning to the play queue always went to the start of the queue, so you then had to scroll down to find the track playing - significant when there's a long queue spread over several pages. This now works well. Click on artist name opens artist's page on LastFM I'm a bit confused about this one. I had asked for the ability to see all other albums by an artist when you are on the Now Playing screen of that artist (a roon-like feature). This has been implemented when you click on the artist name on the Now Playing page. In practice, this has been done by a filtered search, but you then have to go to library view to see that result. I'd rather you were taken directly to that result if that's possible. Not sure how that relates to the above change log entry, or if that is a different feature that I haven't spotted yet.
  12. Yes, my system is: NUC7i7DN + Euphony Stylus > Lush2 > IsoRegen > Lush2 > HMS > DAVE > HEK SE headphones. NUC, IR and HMS powered by 3-rail PH SR7. And I tried the previously stated A, B, C, D configuraions, with D (both ends TANF) sounded best to me. It still puzzles me why, if I have TANF downstream of IR, it still matters so much whether or not I have TANF upstream.
  13. I've finished my re-evaluation of above A-D comparisons. The first 3 were done in quick succession, but I then did long term comparisons of C and D to try to get a handle on the differences. I short, I fully agree with FileMakerDev's findings, and D (TANF on both) was still best for me - and by a considerable margin. Because of the recent love for the Default setting, I tried hard to like it, but in the end I just couldn't. In all cases there were no jumpers, which may have skewed the results, but I didn't want to faff around with jumpers again. But lets put aside personal preference for now, and try to objectively look at the differences between Default and TANF - becuase one of these must be technically more correct than the other, in terms of accurately passing through the signal and in filtering noise: I don't think there's any doubt that TANF gives more of everything: More detail, clarity, dynamics, focus, image separation, depth, etc. Images pop out more from the mix to create a more vivid and immersive presentation. It is more transparent in that it more readily shows up the differences between recordings, even differences between tracks on the same recording. I don't think it is tonally brighter, just more presence, air and sparkle when it's there on the recording. Which doesn't mean that I always like what I hear - because it shows up the bad as well as the good. In comparison, Default smooths everything out, which makes it kinder to bright recordings, but also drains some of the life out of all recordings (even the bright ones), which is ultimately less satisfying for me. A bit like going from an analogue Master Tape to a 2nd or 3rd generation copy - everything is toned down a bit to be duller and flatter. So which is more techically correct? Is TANF's hyper detail a by-product of, for example, letting in too much RFI? Or is it transparently showing up limitations in the rest of my system? My usual analogy at this point is "the more I clean my windows, the more I notice the rubbish in my back yard". I don't really know the answer to this, but from what I've heard, I'm sticking with the Transparency theory and looking to route out the remaining weaker parts of my system to get to my ultimate balanced sound.
  14. Rather spookily, I've been evaluating exactly the same 4 variations for much the same reasons. But first I pitched JSSG Cubed against TANF because it was so easy to change a single pin. And for me, TANF won easily. Yes JSSG Cubed was warm and pleasant, and yes it had more bass. But that pleasantness seemed to lose some of the life and soul of the music, at least compared to TANF. And for me, "more bass" meant "bloated bass" compared to TANF's tighter bass presentation. I'll report back on Default vs TANF in a couple of days, but one thing I can say right now that a seeminlgy small change to the rest of the system can skew the relative merits of these two configurations. Which further reinforces the YMMV mantra.
  15. See what happens when you speak too soon. This is just the beginning! At first, I was unsure about Ray's new notation style of replacing letters with numbers, but I'm warming to it now. It will become more pertinent as we get to 6... 8... 10 shields. Would that be too far fetched? Not with the kind of crazy guys we have around here 🙃
×
×
  • Create New...