XXHighEnd - The Ultra HighEnd Audio Player
August 08, 2020, 08:40:12 am *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: August 6, 2017 : Phasure Webshop open ! Go to the Shop
Search current board structure only !!  
   Home   Help Search Login Register  
Pages: [1] 2 3 4 5 6 7 8 9 10
 on: August 07, 2020, 10:36:45 am 
Started by briefremarks - Last post by PeterSt

Any other thoughts?

Haha, that your reporting about this possibly is not consistent. I mean, I recall that you could solve the issue (for more than one time).

The only real help could be my mentioning that it can happen that the lot is in error and stays in error until a reboot of the PC. Over here we can run into that too. When this happens, it was always encouraged for by disconnecting/connecting the main USB cable (we test all USB cables on this same (my main) system).

Because you seem to inconsistently report (read : encounter) these errors, I'd surely consider even more than you already do, external influences (like the example of your Led lights, what this ever back started with).

I propably already mentioned the combinations of the middle (grounding) switch on your NOS1 and the PE switch on the back of the Mach III (4 combinations there). I may not have mentioned the trialling you could do with Yes/No PE grounding of each of the elements you have in the chain (in your case minimally Speaker, DAC, PC).
Do notice the relation USB has to PE. Not that I ever solved USB errors with it, but it connects (the PC does that) so if you have the PC in PE I would remove that as a first (make a special cable, or easier - an extension block).


 on: August 06, 2020, 06:18:43 am 
Started by briefremarks - Last post by briefremarks
I've had a chance to do some reasonable testing. 
- With standard connection (Lush^2 + standard short USB cable) I get USB Stream and FIFO errors.  However, some times after reconnecting error rate is higher.  After a few trials, I usually get to an error level where I can "live" with it, although the glitches these errors cause in SQ is distracting;
- Replacing Lush^2 with Lush.  Error rate goes up;
- Lush^2 + other short shielded USB cables; not much change;
- Lush in place of Lush^2, and Lush^2 in place of short USB cable--maybe slight reduction in errors.

I have not tried different configurations on Lush^2 used in place of the short USB cable.  Used the standard configuration.

Peter: I'd be glad to order another Lush^2 and experiment a bit more. Should I do standard 40 cm?  The Lush^2 is hard to squeeze in there, especially with the Blaxius^2.

Any other thoughts?  I'm thinking of doing another extreme organizing of cables and re-arranging components. 

 on: July 13, 2020, 07:56:29 pm 
Started by briefremarks - Last post by briefremarks

Thanks for responding.  Just amazing the level of support you provide! I do have a Lush^1, and will try what you suggest.  If it works then I'd like to order a shorter Lush^2 so I can have it for both cables.

Will let you know soon.


 on: July 13, 2020, 01:29:54 pm 
Started by briefremarks - Last post by PeterSt
Hi Ramesh,

I did not try using the short Clarixa cable, as the last time I tried that, it affected SQ badly.

That is at least the same as our experience, with assembling the "good cable" also inside for its 15-20cm piece or whatever is required.

I now may wonder what happens when you'd put the Lush^2 in that position. Of course it is not a "short cable" any more in that case, but this isn't necessarily bad at all. Now I forgot whether you also have a Lush^1 but if you do, try the Lush^1 where you normally use the Lush^2 and put the Lush^2 in the "short cable" position.

I offer this option because that short cable could be highly sensitive to radiation and the isolation chips is also ...
And this is how the Lush^2 could explicitly be of help here (all the shields).


 on: July 13, 2020, 05:24:47 am 
Started by briefremarks - Last post by briefremarks
Reviving this thread with an experience update.  Recently reconnected the small USB cable connected to the Phisolator and started to get the USB Stream/FIFO errors again, and no buffer settings would resolve the errors. After much fiddling around connecting and reconnecting the small USB cable, after about the 10th try doing this, the errors mostly went away.  Now I get occasional FIFO errors, no USB Stream errors.

In my system, something is very sensitive to how the small USB cable is connected.  Wondering if this might just be the cable, and what everyone else's experience is.  When I was fiddling around I tried other USB cables, but they did not make a difference.  I did not try using the short Clarixa cable, as the last time I tried that, it affected SQ badly. 

I'm afraid to touch anything now!!  This one issue continues has restricted my ability to really comment on 2.11, which I hope to do. 

Just sharing with others.  Of course many have commented on this in the past.

Hoping everyone is well,


 on: June 22, 2020, 06:52:51 pm 
Started by Scroobius - Last post by Scroobius
Tidal was off for a couple of days but is now back up and running.



 on: June 22, 2020, 07:40:55 am 
Started by Scroobius - Last post by briefremarks

I had the same problem as Paul a few days ago, and was going to comment on it, but got caught up in other stuff.  Just tried again, and all is working well.  Assuming it has something to do with the offline mode features of Tidal that are now back.


 on: June 20, 2020, 02:28:23 pm 
Started by Scroobius - Last post by arvind
Hi guys,

Yes Tidal is working here too. Probably something wrong at Tidal end briefly.

Best regards,


 on: June 20, 2020, 11:35:42 am 
Started by Scroobius - Last post by Nick
Hey Guys,

Tidal is working normally here, and received a text from Paul saying his access was working again yesterday evening. Perhaps a glitch at the Tidal service of some kind ?


 on: June 19, 2020, 09:24:26 pm 
Started by Scroobius - Last post by manisandher
Hi all, I'm not sure if this will be useful...

I stream Tidal with our TV in the kitchen. A couple of days ago Tidal stopped working on the TV. The message asked us to log into Tidal from any other device and to input the code shown on the TV. I logged in using the Tidal app on my phone, input the code, and Tidal starting working immediately.

I've just checked, and I can log into Tidal using XX 2.10 (on my music server).

Hope this helps. (And I hope everyone's well.)


Pages: [1] 2 3 4 5 6 7 8 9 10
Powered by MySQL Powered by PHP Powered by SMF 1.1 RC2 | SMF © 2001-2005, Lewis Media Valid XHTML 1.0! Valid CSS!
Page created in 0.087 seconds with 10 queries.