@jamesh Well since both the Mk I and Mk II exhibit the same behaviour and swapping the inputs to the power amp doesn’t affect the R channel issue I can’t imagine it can be anything else but the Jeff Rowland itself somehow being sensitive to DSD ultrasonic noise just on one channel. Whether that indicates a circuit about to fail or not I have no idea.
Certainly a concern though, but converting DSD to PCM in Roon gets rid of the noise, it’s a shame I can’t play SACD’s via the PST but I don’t have may of those anyway.
Thanks, Elk. I guess you can attach a PDF but regular users can’t. The ‘upload’ button only supports photo files (PDF is not an option). Or did I miss something?
I rolled my MK2 back to firmware 173 and 2.3.0 for various reasons and was wondering if the the ground lift and shell lift features should be accessible and usable with those early beta firmware versions. I wasn’t planning on staying on these beta versions, but couldn’t remember when exactly those features were introduced and if I should still be seeing them available in the menu with this firmware installed. Maybe they were always there and I’m just forgetting, but for some reason I thought they were introduce later on.
@tedsmith any news on the next release that fixes I believe 2.5.0 is what I have and held off on the 2.5.1 since it had a bug. That is still the latest right?
I’m not privy to the day to day scheduling issues at PS Audio, but they should have started the next set of work items for the UI code. As always, day to day fire drills play havoc with accurate predictions.
@tedsmith Any ETA on the successor to 208-antero that keeps SQ but mitigates loud pops, ticks and white noise? I still running 198 since I experience those issues with 208.
Normally I feel that I’m the young whippersnapper around here, but I’ve been in the IT space for a sufficient number of decades to point out that GUI and CLI are extremely different things but both are UI. The MkII has a bitmapped display, yes, but it uses it almost exclusively for text and the input method has absolutely nothing to do with on-screen coordinates. That’s a text-based UI. Contrast with the MkI which includes pictures and virtual controls like sliders on a screen which allows an input method based on what’s on the screen in the location that you touch. That’s a Graphical UI.
My point is to disagree with your statement that “GUI and UI are the same thing”. UI is the superclass, GUI and text-based interfaces are subclasses. kzk was correct in saying “UI, not GUI” because the MkII interface is not graphical.
