audio1

Many thanks.

Hi. I've been using the Allo capacitance multiplier with the Allo 19V SMPS, to feed a TPA3118 amplifier, but now I would like to use the cap multiplier with a 32V SMPS, into a TPA3250 amplifier - and this is at the upper limit of the cap multiplier's published specifications. Will the cap multiplier be OK at 32V ... or if the SMPS output is not perfect - even 33 or 34V? Or is there some component(s) on the board that I could replace to keep everything safe? Maybe just use a bigger heatsink on the MOSFET? I intend to set the board to drop 0.3V. Thanks.

Only temporarily, while troubleshooting.

Oh, and for those wanting cutting edge native DSD playback, check out the Cronus reclocking interface for BeagleBone Black, by Twisted Pear Audio. This provides a high quality digital transport, but you still need a DSD-compatible D/A converter.

Since 2013 I had been happily ripping SACD's with my custom-firmware PlayStation 3, until it died last year. So I'm very grateful to ted_b, Maldur, and other contributors for this new method. With a Pioneer BDP-160, purchased recently second-hand, I'm now back in business. I offer the following 3 tips: 1. Under Windows 8 the sacd_extract ISO copy from network process works perfectly. But if I reboot into my Windows XP-SP3 installation on the same computer, the process fails, with this error message: libsacdread: Can't open 192.168.1.160:2002 for reading In both cases my firewall software was turned off. I already know that sacd_extract works fine under Windows XP for SACD extraction from local file sources, say, from ISO to dsf. But it seems that Windows XP is no good for SACD extraction via network. 2. I see people dealing with how to determine the blu-ray player's IP address, and I suggest it's more straightforward to specify a fixed IP address, yourself. For the Pioneer, connect it to your router, then power up. In the menu, go to Network > Information > Next Screen this will show you the network settings that the player has assigned automatically (by DHCP) on power-up. Take note of the IP address - in my case 192.168.1.5 Now press "Return" to go back to Network > IP Address Setting > Next Screen change "Auto Set IP Address" to "Off" now with the arrow keys you can change the IP address. Keep the first 3 fields, in my case 192.168.1. and just change the 4th field to a higher value, such that it should never conflict with other IP addresses handed out by the router. I chose "160" because this matches my model number, and is easy to remember. So my fixed IP address is 192.168.1.160. Keep the existing "Subnet Mask", "Default Gateway" and "DNS1" values - these would have been determined automatically, and remain correct. I can confirm that these settings are held in memory, even when the unit is fully disconnected from power. Now when you connect to the blu-ray player from your Windows/Mac/Linux computer, you always know the correct IP address. You don't need to keep modifying your sacd.cmd file. 3. For the problem of dsf files playing back with "clicks" between tracks, this (known) problem has been fixed from the release of sacd_extract ver 0.3.8. I notice that the download links in the early posts contain sacd_extract 0.3.7, so obviously I suggest everyone should update to 0.3.8 - https://github.com/sacd-ripper/sacd-ripper/releases

Ah, I may have confused the issue by mentioning MPD. Sure, MPD's output can be configured to stream, but this is not its default mode. Normally MPD outputs audio at the "server" end. Networked clients control the playback, thus making them glorified remote control units. So forget about MPD for the moment, and consider a conventional audio player application such as XMMS/Rhythmbox/Amarok/Aqualung; my question relates to how these applications would access files over a network, versus how a rendering client accesses a network stream.

Hello. I'm about to build a music server system, and I know I could save time (and money?) by buying an off-the-shelf system, but I want the satisfaction of self-built. I built my own amp/pre-amp, and I'm reasonably proficient with compiling Linux applications and drivers, though I haven't yet attempted cross-compiling for ARM. So to my question: Can someone please comment on the technical/practical differences between the "streaming" network audio model, as used by many commercial devices, compared to direct file access over a network, as used by Music Player Daemon? It seems to me that MPD's file-access method, whether using NFS or SMB, would be technically more straightforward and elegant compared to the somewhat complicated streaming method? Is the popularity of streaming only because of the ability to have multiple clients, and multiple outputs?