Krisbee

Michael, You say you started by using netctl, was that with ifplugd using [email protected] and [email protected]? All the standard ARCH ARM LINUX images seem to be setup that way. But any testing I've done of Arch in a VM showed this combination always attempted to mount network shares before any network connection was fully working. So you had to use systemd.automount for network shares. You may also find other services dependent on a working network connection can fail to start. But, using netctl alone, as you plan to do, restores some sanity and network mounts don't need systemd.automount etc. The challenge would be to extend the Ympd web interface to allow the user to configure network interfaces and network shares. For a simpler approach, it shouldn't be too hard to write a bash script to let the user pick/configure the appropriate netctl profile, enable it and restart the associated service.

Just thought I'd drop by and save you from the first sign of madness - talking to yourself. I don't have any ARM devices so I can't use/test your image myself, apart from within QEMU. Unfortunatey latest systemd in ARCH and QEMU don't work well together. You have an interesting blog and I think archpile is a worthy alternative to the likes of volumio etc if you're not so focused on their WebUI. You've made some sensible suggestion about network and remote fs mounts on your blog, but it is possible to to use a combo of wpa_supplicant and systemd-networkd and so handle both wired and wireless connections, dhcp or static, with systemd-networkd alone. Switching between dhcp and a static ip on a given interface would need a script. Some basic refs: systemd-networkd with wpa_supplicant to manage wireless with roaming support | BeaverIs.Me Using systemd-networkd with wpa_supplicant to manage wireless network configuration with roaming Good riddance netctl For nfs/cifs network shares, systemd.automount is not necessarly as long as you can guarantee the network is properly up before remote mounts are attempted. The use of systemd-networkd for all connection types would ensure this, as it pulls in the systemd-networkd-wait-online.service and you should get something like this: systemd-analyze critical-chain The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. graphical.target @5.158s └─multi-user.target @5.158s └─getty.target @5.157s └─[email protected] @5.156s └─systemd-user-sessions.service @5.098s +56ms └─remote-fs.target @5.056s └─mnt-disk1.mount @4.417s +636ms └─remote-fs-pre.target @4.355s └─nfs-client.target @4.355s └─rpc-statd.service @3.844s +510ms └─rpcbind.service @3.316s +468ms └─network.target @3.314s └─systemd-networkd.service @3.104s +205ms └─dbus.service @2.781s └─basic.target @2.764s └─timers.target @2.754s └─shadow.timer @2.750s └─sysinit.target @2.730s └─swap.target @2.730s └─dev-disk-by\x2duuid-dd5b2346\x2db151\x2d4e3f\x2d89d9\x2d5dbe22a8252a.swap @2.686s +43ms └─dev-disk-by\x2duuid-dd5b2346\x2db151\x2d4e3f\x2d89d9\x2d5dbe22a8252a.device @2.685s Personally, I would prefer to have a single app/config that covers all connections types rather than using a mixture of say dhcpcd, systemd-networkd and wicd. But then once you've decided on wired or wireless, dhcp or static. I guess the user would tend to stick to their chosen config. I'm useless at writing bash scripts, but made a start on something to switch from dhcp to static on a wired connection with systemd-networkd already enabled on a system. #!/bin/bash # # usage set_network interface mode # assumes interface is a valid name # accepts dhcp as a valid mode, otherwise sets to static # int=$1 mode=$2 DIR=/etc/systemd/network Address=192.168.1.149/24 Gateway=192.168.1.1 if [[ "$mode" == "d*" ]] then cat > myifcfg.network <<-EOF [Match] Name=$int [Network] DHCP=yes EOF else cat > myifcfg.network <<-EOF [Match] Name=$int [Network] Address=$Address Gateway=$Gateway EOF fi rm -f $DIR/*.network mv ifcfg.network $DIR/ ip link set $int down ip add flush dev $int systemctl restart systemd-networkd Next stage is to parse "ip link show" to get available interface devices, user selects interface and connection type, and if static inputs address, gateway etc. Plus extend script to setup systemd-networkd as necessary and work with wireless connections.

Mredel, Which distro did you install on your BBB? The latest "BBB-eMMC-flasher-debian-7.4-2014-02-16-2gb.img" has a hiface audio module built-i,n but only for the 3.13 kernel. Yet it seems to be configured to boot a 3.8 kernel. I don't have a BBB so can't help beyond that. Best to ask in main section the forum.

mredel, The Hiface evo needs a USB driver to be complied and installed on your BBB. What is relatively straightforward on a standard PC/laptop is a lot more involved when using hardware like the BBB or RPi. Try posting a message under "music server" asking how to build the hiface evo snd-usb-asyncaudio module for the beaglebone black.

Well, if you don't want to use MPD or LMS, that leaves DLNA/Upnp audio servers. But it seems you have already decided to buy into JRMC.

There's little to do in Lubuntu, see my earlier posts in this thread about installing a low-latency kernel and installing and configuring deadbeef, for example, for bit-perfect palyback. Did you setup VLC with the vlc-plugin-jack? If you had been following the AP-Linux instructions, which are peppered with "must do this .." amd "must do that ...", you would have setup jackd and deadbeef, or audacious, for audio playback and not VLC which I think AP-Linux would regard as "big player" and "They are not basic music players and they use various databases and services that are resource demanding. And we don’t want that in our Linux box." Playing audio | AudioPhile Linux So according to AP-Linux, you shouldn't be running audio software that might actually be useful to you!

Do you mean is sshd runnnig on Daphle, and can you connect to it via ssh? The answer is no. Daphile is locked down, there's no way to get to a terminal and use the command line in Daphile.

You prefer AP-Linux because it sounds better to you, or because it looks better or is easier to use? Without knowing how you configured Lubuntu or what software you were running on it, I won't comment on your preference. Hatred is too strong a word. But, yes there are many who dislike AP-Linux because they believe it promotes a false picture of using Linux for audio playback, added to that the AP-LInux website contains info which is either wrong or misleading. If you wish to control your Linux based audio player from a phone or tablet and not use ssh/vnc, then you probably need to use something other than AP-Linux. The audio software running on your Linux PC needs to operate in server/client mode with the audio server on the PC and the audio client on your phone/tablet. Three popular examples of audio software the works like this are: MPD - Music player Daemon used with clients like Mpad & Mpod LMS - Logitech Media Sever with Local Player Plugin (squeezelite) and remote control clients like ipeng and orange squeeze miniDLNA - An audio server that works with any DLNA/UPnP client These plainly do not fit with AP-Linux insistence that you must use an RT kernel combined with Jackd for best audio SQ. Have a look at VoayageMPD, Vortexbox and Daphile if you don't wont to install and configure a standard Linux distro. Right now, my perference would be for a minmal Debian server style install with no desktop that uses LMS + squeezelite and pure ALSA (no pulse audio). Audio playaback can be controlled remotley via the in-built LMS web-browser interface, or by clients on phones/tablets.

Russ, When you're ready just install Daphile on your hard drive using the options under "settings>system firmware". One possible gotcha is that I don't know if Daphile expects the hard drive to have a traditional DOS/MBR on a system with trad BIOS(or UEFI working in compatibility/legacy mode), or if it can handle (U)EFI and drive with GPT. I've only made brief use of Daphile in a virtual machine.

Daphile will install on quote "empty disk without existing partitions" ..... You will have to find another Linux distro you can put on a USB stick first. Then use "fdisk" at the command line to delete all partitions on your netbook's internal drive before you can install daphile. How to delete a partition using fdisk.

What was missing was any mention of the word "NAS" in your last post. You speak of THE buffer, as if there may only be one involved in terms of the transmission of data form NAS to music server and music server to DAC, that seems too simplistic. Of course anyone is free to try, but I don't use MPD much at the moment, and not with remote data.

Well, I don't know what's going on in your network but there's no reason why ping response time between hosts should be influenced by mpd.conf settings. The ping command is interface specific and you're not testing the connection to a specific port on your mpd server. In any case, unless you are using MPD for network streaming, the network traffic between MPD server and client is confined to command data and sending audio file lists etc. which is not that time critical, although scrolling through very large music libraries could be slow. Use ssh to connect to your mpd server and turn mpd off ( /etc/init.d/mpd stop) and then repeat your ping exercise. Any difference? You'd have to have a good understanding of the MPD code and ALSA's own buffer and memory management and USB controller frames etc. to decide if changing those particular MPD settings could influence SQ. I would pay heed to the developer's comments. Reducing buffers may simpler make your CPU work harder by servicing more frequent interrupts as the buffer empties more quickly than needed, and in the worse case you'd get under-runs.

Linefader, Firstly I should say I don't have a Mytek Stereo 192 DAC and have no experience of playing DSD files using MPD. But this thread implies DSD support ( of some type – via the dsdiff plugin) has existed since MPD version 17.2 Voyage Linux - mpd.conf and DSD files And for DSD over USB ( DoP v1) you just needed to add “dsd_usb yes” to your mpd.comf file, e.g: audio_output { type "alsa" name "MyPlayer" device "hw:0,0" dsd_usb "yes" } According to RMP bone, Fedora 19 has MPD version 0.17.3, whereas the latest is 0.18.4. Type “/usr/bin/mpd –version” on the CLI to get feedback on what your version of MPD supports. Vortexbox uses fedora and this thread discusses the playback of DSD files: DSD on Vortexbox - VortexBox user forum According to comments made here the Mytek Stereo 192 DAC may only work via firewire, or SPDIF output that supports bit perfect playback of 176.4K content. The latter would be coax SPDIF, and unlikely to be toslink. I guess this is why you were trying to get the MPD version here to work for DSD over USB: Install guide for MPD with DSD support As was said elsewhere, unless you have the correct dependencies installed on Fedora, the version of MPD-DSD you compile will not have the correct support. After you compile it, “mpd –version” should show what is missing. You should be using yum to search for libraries you need. E.g the development version of libflac is called libflac-devel-xxxx, so a “yum search libflac” should show the devel version to install. You would need to read https://github.com/lintweaker/mpd-dsd/blob/master/INSTALL carefully to find which additional development packages would need to be installed on Fedora 19. . But is this necessary? The latest version of MPD might include Jurgen Kramer's patches. You'd have to search/ask on Voyage-linux Info Page As to your question about AP-Linux. It's just Debian Mint with a few extras. So if the standard mint installer allows an external HD to be picked as a destination for the install, then yes it should work. But you'd have to think where and how you wanted GRUB2 to work. For example, install GRUB2 on the external HD partition, and not the external MBR would allow to use Fedora's Grub2 to boot ap-linux. Or install GRUB2 in the external HD MBR if your laptop's BIOS is happy to boot from an external HD. PS Rather than ap-linux, what about the latest version of VoyageMPd. Did you see this comment: I have just moved my alix 2d2 to voyage mpd 0.9rc2, with snd-usb-mytek installed. I have also enabled dsd_usb and dsdiff_native in mpd.conf. But after running mpc update, the database does not contain my dff files at all. Have I missed anything? Appreciate your help and enlightenment. Thanks falcongate See page 19 of http://www.computeraudiophile.com/f10-music-servers/new-linux-os-aimed-computer-audiophiles-voyage-mpd-5505/

When this happened, and you connected to the device running voyageMPD via ssh, had mpd stopped? Did you check the contents of /var/log/mpd/mpd.log for error messages?

I'm not using Voaygae MPD at the moment, and 0.7 is an old version, but IIRC voyage mpd is configured to automatically detect a usb stick and an MPD update via a client will add audio files to the "music library". Voyage MPD uses an internal directory inside "/var/lib/mdp/music" called "usbmount" which points to the audio data on the usb stick. So, if you then copy the same audio data from your usb stick to another directory within "/var/lib/mdp/music" , the music files will naturally appear twice follwing another mpd update if the usb sitkc has not been unplugged. Unplug your usb sitck and do another mpd update and you will back to just one copy appearing in your mpd client. Voyage MPD is working as designed. The "problem" is with the way you are using it. If you simply want to copy the audio from your usb stick. Do not do an mpd update until after the copy is complete and you have removed the usb stick.