Pi2 Design Idiot-Proof Ready-To-Go RPi/AES Streamer

I have not looked at updating the image recently. Is there something specific in a newer version that you’re looking for?

 

Looking for an update for hopefully better integration of Qobuz in Volumio. The Volumio changelog is a little light on specifics but the latest 3.512 added a few things and 3.435 might have some updates applicable to my specific issue with Volumio Premium. Qobuz likes to disappear from the browse list at times to select it. After a restart, it might take a while (a couple hours) for the Qobuz icon to show up as well. Just wondering if you had an updated image in the works before I fumbled through it myself. I'm assuming the auto power off sequence, USB Host and External Antenna still need to be added to a stock Volumio image. Thanks for your input.

 

You can use the Volumio update command built into the interface. The Mercury specific pieces are in a protected file called user_config.txt on the SD Card and the update tool won't overwrite that.

If that solves your issues let us know and we will look at making that our new version.

 

Well, that was easy. I had been hesitant to upgrade Volumio in the interface thinking it would overwrite the Mercury config file. Thank you for the clarification. This thing really is idiot proof. Now running 3.512 and Qobuz pops right up as it should after a restart.

 

if you don’t mind, give us an update in a week or so that way we all know that it wasn’t just a random occurrence that it happens to work today!

 

Hi Michael,

I always seem to think of a question to ask on a weekend. Please feel free to wait until the work week to answer.

I seem to remember you commenting at one point on the Raspberry Pi being a noisy sucker ( like most general purpose computers). You have kindly given us a jumper to allow the Pi and the Pi2AES to be powered separately. I wondered if you have ever measured a difference in output between powering them together or separately? I notice that you separated the Compute module from the signal area in the Mercury.

 

I know I did this awhile ago, but there was little or no difference for the original PI2AES. I will update this for the new 2.0 and see what we get. I will only be looking at Jitter since I believe measuring analog noise on the digital lines is not very useful (sorry @GoldenOne) unless it is quite large and/or your DAC has piss-poor internal layout and design.

 

In honor of the hot summer we are taking 20% off the PI2AES-LITE. It is now $199! Quantities are limited and once they’re gone.

The LITE has the same core design and 5V input as the new PI2AES 2.0, but is without the AES balanced and the I2S over HDMI. Now that the PI 4 is more readily available this makes a super high quality streamer for under $300 total. And as with the 2.0 the clear acrylic case is included.

Ok that’s enough marketing drivel!

 

not drivel, as some of us actually prefer spdif/BNC and appreciate the discount

 

Noob here, is there any sonic difference between the mercury v1 and v2?
best,
Josh

 

Don't think there is any sonic difference except V2 has buffered I2S out for Sonnet/Metrum DAC + dip switches for I2S LVDS and a nicer case with 2.5mm DC input

 

Quick question, hope it is not too off topic. Finally grabbed a normally priced Pi4 again and thinking of snagging a Pi2AES-Lite. Specs say coax S/PDIF out and AES BNC out. My Gungnir specs mention S/PDIF BNC in. I know AES and S/PDIF use the same data format with some subcode differences, my question is if these are the same enough to be compatible (put simply, can I use the BNC out from the Pi Hat to my Gungnir BNC in and have it work?)

 

single-ended AES (BNC) is the connection I used w my pi2 and Gungnir Multibit. sounded great.

 

Just saw this news on the Pi2AES site about the Mercury V2, what a bummer.

"Mercury V2 Update - 08/03/2023
Due to CM4 module issues, Mercury V2 is currently out of production. We do not expect the situation to change before the end of this year at the soonest."

@Michael Kelly keep up the good work, we appreciate you

 

To clarify, AES and SPDI/F use the exact same data stream and encoding. The only differences are the connectors and balanced not being an option for SPDIF. In general AES was designed for studio use with longer cables and noiser environments. SPDI/F was Sony and Philip's answer to reduce cost for the consumer market.

 

I use BNC to BNC with my pi2aes and gungnir A2. I also use a BNC (pi2aes side) to coax cable on my BF2.

 

Thanks for the replies. Most of the Googling I did talked about impedance matching but that would be for balanced to single ended conversions, so with a proper short 75 Ohm BNC terminated cable I should be good to go. Appreciate the confirmation. I also have an Urd now, but don't want to go down the USB rabbit hole just yet.

 

With AES you want to match the impedance of 110ohm for balanced or 75 ohm for BNC. This is to allow the full length per the specification. Typical usage in the home makes it less critical but still desirable.

 

also, do not use balance to single ended converters. Use the single ended Yeah that is already coming out of the Streamer. Or use balanced if your device has balanced. That’s the reason we put the different interfaces.

 

I’m a long-time user of JRiver. I’ve only seen a few mentions of JRiver in this thread. How easy or challenging is it to run JRiver on the Mercury streamer? JRiver sells SD cards with the JRiver software, Raspbian Linux, and Engen already pre-installed. Besides installing the SD card and configuring the output settings within the JRiver software, would I need to make any configurations to the Mercury streamer to make it work with JRiver?

Here’s the SD card that JRiver sells:
https://jriver.com/Id/