Jump to content


  • Content Count

  • Joined

  • Last visited

1 Follower

About sdolezalek

  • Rank
    Intellectually Curious Member

Personal Information

  • Location
    Bay Area, CA

Recent Profile Visitors

9726 profile views
  1. The fronts are 20.1s and they are 5 feet from the front wall.
  2. Although I swear by the Magnepan "Tri-Center" approach in my 7.1 application, I have returned to using on L+R for stereo listening (and that is with a system where the distance between speakers is far greater than from the speakers to the listener). I believe one advantage is the dipolar nature of the Magnepans and the need to move them far away from the back wall (5ft in my case). But there are three things that really got rid of "any hole in the middle:" 1) a perfectly symetrical room for reflection purposes; 2) making sure that the speaker distance to each ear was correct down to an inch; and 3) using REW to make sure the L+R frequency + phase response curves were as identical as possible. With those fine tuned I can sit 15 feet away from speakers that are 25 feet apart and you would swear there is a center channel playing because of the holographic sounds that emanate from across the full sound stage. When I watch movies, however, the tri-center becomes very important. Because movies are recorded with dialog being center focused, most single center speakers make those voices sound like they are coming from a hole in the wall in the center of the room (all from exactly the same place). What the tri-center does is to provide a better mix of direct and reflected sound that gives voices the sense of floating in space, part of which is very carefully timing both the lag and the volume balance between the center channel and the two center channel wing speakers. The idea is to have the center channel sound arrive at your ears a fraction of a moment ahead of that coming from the "wings." That may not be ideal from an "audiophile accuracy" perspective, but is great in creating the illusion of the voices being "in the room."
  3. Chris: I believe you are missing one final piece of the package that makes the other three even better -- HQ Player. Using the Sonore products as network appliances, Roon as the user interface, Qobuz to feed content, and HQ Player to fine tune it is I believe the best available combination today (it does require some computing power ;-) )
  4. Yes, switching to -2s and ext2 variants did the trick so that I can now access both 16/44 and 24/192 content without dropouts. Thank you! I guess my processor (which was the fastest I could buy two years ago) just isn't fast enough -- And I thought the Intel power wars were done ;-)
  5. Miska: Actually, I misidentified my CUDA card, I recently replaced the M4000 card with the P4000 Pascal-based card. Nonetheless, if I switch from a check to a grayout on the CUDA offload, it fixes the dropouts on 16/44 files, but makes it much worse on 24/192 material. Does that trigger any further thoughts? Thanks.
  6. Yes, although what I tried today was to direct connect the SMSL M500 DAC to the processing PC that has both Roon and HQ Player on it to see if I would still get dropouts (now taking the Rendu out of the equation). I do. That makes me think it may not be a network problem. It still happens at the same level regardless of whether I'm playing content stored on my NAS, from Tidal/Qobuz, 16/44 or 24/384 or DSD files. It does not occur converting to DSD128 but does at DSD256. I took some more pictures of the CPU, GPU and Network loads to see whether anything occurred during a dropout and I can't see any spikes that correlate to when I'm hearing a dropout. So now I'm even more confused.
  7. Jussi: Thank you for the response. I enabled power/cable length detection and hardware flow control throughout the network, but I still get the same dropouts. If I run DSD 128 it works fine. If you or anyone else has further ideas they would be greatly appreciated.
  8. Computers and the Internet: They were supposed to give us access to unlimited learning and knowledge. Those, in turn, were supposed to resolve disputes about facts and knowledge and leave us with little uncertainty. Instead, the exact opposite has happened. The volume of available information has far surpassed our feeble brains abilities to distill it to useful/reliable knowledge. The resulting confusion, not clarity, has led us to retreat to tribal systems of belief, where we turn to reinforcement from members of our tribe to give us comfort that our belief is the correct one. These days it is hard to find any area in which there is a true consensus, never mind universal agreement. Instead, we have vehement disagreement about almost everything, with the very uncertainty that led us to a tribal view emotionally leading us to defend that view with even more force than if it were one we safely had in hand. My only safe solution: Sit back and listen to the music...
  9. I have been trying without success to identify the problem that causes my upsampling and conversion to DSD 256 through HQPlayer 4 (but still using Roon as the music player) to cause audible dropouts (moments of silence) in the middle of playback. The problem does not occur if I simply use Roon's own upsampler to convert to DSD256 (leaving HQP out). Interestingly, the problem is consistent across all file types, from 16/44 material played from Qobuz/Tidal through HQP/Roon to DSD256 files on my Roon drive to PCM 24/352 files on my hard-drive. I don't believe it is either a CPU problem (i7-6700K CPU with 32GM RAM), a GPU problem (NVIDIA QUADRO P4000) or a broadband capacity problem (250Mbps connection). My network configuration is as follows: Arris Surfboard SVG2482AC cable modem >> TP Link TL-R600VPN Router >> CISCO SG200-24FP Switch >> SYNOLOGY DiskStation 415+ >> PERSONAL COMPUTER >> Sonicorbiter SE functioning as NAA >> MicroRendu >> SMSL M500 DAC (all network connections are showing gigabit throughput). One possible issue is that when I do a latency ping between the computer and the Sonicorbiter I get results that swing between 18ms and 75ms. The one behavior I am seeing is that Roon and HQ Player alternate in their use of CPU power and that, as a result, content is streamed through the network in bursts, with my guess being that these bursts are causing some kind of bottleneck. When Roon does the upsampling itself, it retains full access to the CPU and it streams in a much smoother fashion eliminating the spikiness I see in network usage. See images below and attached (HQ Player Settings, Roon Stream and Network and CPU usage). Any advice as to what might be causing the problem would be hugely appreciated.
  10. What does this do that you cannot accomplish using Thierry's software and implementing those corrections in HQPlayer/Roon?
  11. As long as you don't ask whether we know how to use it...
  12. Looks good, but in a minimum order quantity of 25 units it definitely isn't cheap. Know anyplace to get just one?
  13. sdolezalek

    HQ Player

    Jussi: After a multitude of threads discussing the digital to analog conversion, I still don't think that most visitors to this site understand the three simple principles you have laid out above: 1) If you ears are highly sensitive to time domain response -- choose [these] filters; 2) if your ears are frequency response sensitive -- choose [these] filters; and 3) if your computing or DAC system allows for conversions to occur far outside the audible band you can have the best of both worlds, but should still pay attention to which modulator you are using, so use [these] filters...(filling in the [these] designations in HQPlayer would also be helpful ) It also provides a great rationale for why many of prefer using HQPlayer for these conversions -- because we can make the choices that best suit our ears, not those of our DAC designer.
  14. That I've stopped listening to live music, other people's systems, audio shows, or any other source of fake audio quality...
  15. You don't say why you think you can/should "do better." I assume that you chose the Yggy, Pass, Martin Logan combos because you liked their sound signatures. If so, there is no reason to change any of those. It would be very helpful if you said something about where you thought your current listening was falling short. Or is it that you just want to know where an additional $3k would give you the most bang for the buck? If that is it, then the Aurender solution is not a bad one, particularly if you don't want to have to learn about noise, specifications, configurations, etc. in computers, software, upsampling, DSP, power supplies, NAA's, etc. But I might pay particular attention to what other Yggy owners here use as a front end that matches well with their Yggy as you want to make sure that your streamer outputs matches what your DAC does best with.
  • Create New...