what (daisy chaining) did you try and what is you solution now?
If I remember correctly some of you preferred the PN directly to the router or to a “normal” switch/LAN distributor - was it you @Michaelb and @Dan_M ? - instead of another “audiophile” switch.
I’m a bit tired of box count - no I won’t sell my 500 system - but in regards of switches, LPS, media converter and all the different cables inbetween.
I got rid of my nucleus + LPS in favour of a ZENITH MK3 and I’m very happy with the result. One box less, overall better sound (not only with the sense app) and the Sonore oM v2 + LPS was not making any difference to my cisco doing the converting that I’m using anyway.
Therefore I’m thinking about buying a PhoenixNET and sell my etherRegen + Farad Super 3 - a combination that I like a lot - and also skip the fibre conversion, go directly router to PN and PN to ZENith and ND555.
I will do a demo of course but I’m curious what your experiences are, especially regarding fibre conversion before the PN - does it really help or is the PN so good that it doesn’t need anything else?
The Phoenixnet is in my 500 series system. I had an Etheregen and found i preferred the sound of the ER feeding the Phoenixnet. Others have found differently. Just choose yourself.
What Gazza said about listening to find what’s best for you in your system.
I used to daisy chain two EtherRegens powered by a very competent Sean Jacobs DC3+ linear power supply, but preferred the PhoenixNet without either EtherRegen downstream (and of course to them).
On the cable front, I prefer the Belden CatSnake 6a to BJC and most others, but the Shunyata Omega is a significant step up (as it should be for the price).
EE8 into PN into pulsar for me. Not sure it sounds better than PN alone but the EE8 is used in a different room to connect the router to the zen mini that is my Roon server so I use it as a switch to go from there to the PN in my listening room.
Router/modem directly connected to PhoenixNet. The initial chain was: router/modem → Cisco 2960 → PN, but overhere dynamics are far better without a Cisco in the middle! Success.
On @Cohen1263 's advice I first got EE8 with Farad. Later added PhoenixNet and daisychained them. At moment EE8 is out of system and trying just PhoenixNet.
I enjoyed the two daisychained. See how thing go but PhoenixNet alone is very good.
Tried a PN with and without various combinations of 2960 & EE8 in the chain and out of it.
In the end I prefer the straight EE8. The PN added a sluggish bloaty bass, softening the sound and slowing things perceptually. I sold it after 5 months of trying to love it.
I’ve got my PhoenixNet connected to the lounge switch (a Ubiquiti Unifi PoE switch). I’ve not been able to detect any benefit from daisy chaining, and if I’m honest I got the PhoenixNet because I wanted a present for myself.
I demoed a Melco switch with LPS (including a week with aDot fibre converters also running on individual LPS’es), and I totally empathise with the box count dilemna.
The PhoenixNet looks nice, works well, and most importantly sounds good.
Very similar experience to @GraemeH with the PN. Had it on an extensive home trial (30 days+) but it ‘softened’ the sound too much for my liking. Mind you with FW 3.10 that would be a blessing!!
Recently switched out the Cisco at the router end of the chain for an ee16, which is currently available at a bargain price. For the 5m run to the ee8 rack switch, I settled on Supra 8 after testing various expensive options. The patches at each end of the streaming chain are AQ diamond and the final leg is the sublime SR Sigma.
I was very happy with the sound signature of my system until the infamous FW update.
I would say that the inclusion of the SR Sigma in my streaming chain had the most profound positive effect.
@Geko and others have achieved similar results with the SR Sigma streaming cable. Certainly worth a try.
Once the debacle with FW3.10 is resolved I may try an ifi elite PSU on the Sky router and ee8. Anyone been down that rabbit hole??
Thanks @GraemeH I did try an ifi on the Sky router and experienced the same result as you. But with all the current FW issues, I was unsure if the listening results were valid. Appears they were.
