Jump to content
  • The Computer Audiophile
    The Computer Audiophile

    Geek Speak: How To Build A BeagleBone Black MPD Music Server

    thumb.jpgWarning the following article contains some geeky stuff. What follows is a step by step guide to building a tiny 2.4" x 0.82" x 3.54" Linux music server. It's not rocket science and the instructions make the process fairly easy, but the article isn't for everybody. Thanks to CA readers K-man and Richard Dale for additional information and tweaks for setting up the BeagleBone Black so it runs great. Please note there are many ways to setup and configure the BBB. This is just one way using either Mac OS X or Windows. Readers are encouraged to leave comments with additional tips, tricks, and tweaks. I will update this article accordingly.[PRBREAK][/PRBREAK]

     

    1-Pixel.png

     

     

     

    1-Pixel.png

     

     

    opening.jpg

     

     

     

    1-Pixel.png

     

     

     

     

    Introduction

    The new $45 BeagleBone Black motherboard has excited many computer audio entusiasts. This tiny board has enough power and ports to run a Linux based MPD music server. In addition, Logic Supply has released a new BeagleBone Black case in a very cool orange color as well as a more traditional black. The case is made specifically for the BBB. All the ports line up perfectly and the finished product with BBB inside looks really neat. I attached the four rubber feet to the bottom of my Logic Supply case and the BBB sits nicely on any of my audio components without scratching itself or the other device. The case is made of sturdy metal, unlike the plastic options available heretofore. If you have a BBB or are going to pick one up I'd pick up the Logic Supply case as well.

     

    bbb-board.jpg

     

     

    1-Pixel.png

     

     

    Here is a list of requirements and step by step instructions for the BBB-MPD server running Linux from the built-in eMMC flash drive.

     

     

     

    Requirements:

     

     

     

    1-Pixel.png

     

     

    Step By Step Mac

     

    - Connect the MicroSD card using an adapter to a Mac or PC.

    - Open Disk Utility (Applications > Utilities > Disk Utility), select select all volumes under the MicroSD card, then select Unmount. In my example the volume is named 8GB. (Image Link ex.png)

    - Install The Unarchiver (App Link ex.png)

    - Download the Debian Wheezy image (Direct Link ex.png). During the download if asked a question about the file extension .img or .xz, click "Use .xz" (Image Link ex.png)

    - Double-click the downloaded Debian Wheezy image. This will open The Unarchiver and automatically extract the needed image file (BBB-eMMC-flasher-debian-7.4-2014-03-27.img)

    - Open the Terminal app (Applications > Utilities > Terminal)

    - Type -> sudo su (without the arrow ->)

    - Enter your password if asked.

    - Type -> diskutil list

    - Take note of the disk number of the MicroSD card connected to your computer. My MicroSD card is listed as /dev/disk1. The MicroSD card should be easily identifiable by its small size. My MicroSD card is listed as 7.9 GB (Image Link ex.png)

    - Type -> sudo dd if=

    - Drag the Debian Wheezy image file on to the Terminal window to automatically fill in the path to the file (Image Link ex.png) You can also type this in manually if desired.

    - After dropping the image file on to the Terminal window the command line should read something like this >> dd if=/Users/chris/Desktop/BBB-eMMC-flasher-debian-7.4-2014-03-27.img (Image Link ex.png).

    - Make sure there is a single space after the path to the Debian Wheezy image file entered in the previous steps.

    - Type -> of=

    - Then enter the disk number of your MicroSD card. In my case this is /dev/disk1

    - The text should look something like this of=/dev/disk1 (Image Link ex.png).

    - Make sure there is a single space after the path to your MicroSD card entered in the previous steps.

    - Type -> bs=1m

    - The entire line should now look something like this >> dd if=/Users/chris/Desktop/BBB-eMMC-flasher-debian-7.4-2014-03-27.img of=/dev/disk1 bs=1m

    - Here is an image of my Terminal (Image Link ex.png)

    - Hit Enter on your keyboard and wait for the image to be written to the MicroSD card. This will take several minutes and appear like your computer is stuck. Please wait for the command to finish.

    - Once the image has been written to the MicroSD card the Terminal window will list something like this

    700+0 records in

    700+0 records out

    734003200 bytes transferred in 393.606273 secs (1864816 bytes/sec) (Image Link ex.png)

    - If you receive an error message stating "Resource busy" (Image Link ex.png) you likely skipped step 2. Please unmount the volume and try again.

    - Open Disk Utility (Applications > Utilities > Disk Utility), select the MicroSd card, click Eject or Eject Disk via the right-click menu.

    - Place the MicroSD card into the BeagleBone Black's MicroSD card slot.

    - Hold down the small Boot Switch / Button ex.png while connecting the power supply to the board.

    - As soon as one of the User LEDs illuminates, release the Boot Switch / Button.

    - The User LEDs should continue flashing while the MicroSD card image is copied to the on-board eMMC flash memory. The process should take about five minutes.

    - When all four User LEDs are illuminated steady, pull the power supply from the board and remove the MicroSD card.

    - Connect an Ethernet cable to the board and re-connect the power supply.

    - The BeagleBone Black will boot into Debian Linux.

    - Install the LanScan application from the App Store Link ex.png

    - Open LanScan and click Lan your Scan.

    - Once the network scan has completed locate the BeagleBone Black's IP address. The vendor will be listed as Texas Instruments. My BeagleBone Black's IP address is 10.0.1.179 (Image Link ex.png)

    - Open the Terminal app (Applications > Utilities > Terminal)

    - Type -> sudo su

    - Enter your password if asked.

    - Type -> ssh root@

    - After the @ symbol type the IP address of your BeagleBone Black and hit enter. Mine looks like this ssh [email protected] (Image Link ex.png)

    - You should receive a message about the authenticity of the of and the RSA key fingerprint. Type the entire word YES and hit enter.

    - You'll then be asked for the root password to login to the BeagleBone Black. Enter root as the password.

    - Here is an image of the entire login sequence (Image Link ex.png)

    - From here the Mac OS X and Windows configuration is the same because the work is done on the BeagleBone Black. Skip to the BeagleBone Black OS configuration.

     

     

     

     

     

     

     

    Step By Step Windows

     

    - Connect the MicroSD card using an adapter to a Mac or PC.

    - Install 7-Zip Link ex.png

    - Install Win32 Disk Image Link ex.png

    - Download the Debian Wheezy image (Direct Link ex.png).

    - Right-click the downloaded Debian Wheezy image. Select 7-Zip in the right-click menu, then select Extract Here. The file BBB-eMMC-flasher-debian-7.4-2014-03-27 will appear next to the downloaded image when the extraction is complete. (Image Link ex.png)

    - Open Win32 Disk Imager

    - Make sure the MicroSD card drive letter is selected under Device (Image Link ex.png)

    - Select the small folder to the left of the Device drive letter and browse to the file extracted using the 7-Zip program. You will need to click the drop-down arrow above the Cancel button (lower right) and select *.* to show all files (Image Link ex.png). (The Debian Wheezy image is extract without the .img file extension). Once *.* is selected you can select the file BBB-eMMC-flasher-debian-7.4-2014-03-27 that was extracted using the 7-Zip program. Don't select the .xz compressed file. (Image Link ex.png)

    - Click the Write button and Yes to any popup questions.

    - Eject the MicroSd card when Win32 Disk Imager finishes writing the image.

    - Place the MicroSD card into the BeagleBone Black's MicroSD card slot.

    - Hold down the small Boot Switch / Button ex.png while connecting the power supply to the board.

    - As soon as one of the User LEDs illuminates, release the Boot Switch / Button.

    - The User LEDs should continue flashing while the MicroSD card image is copied to the on-board eMMC flash memory. The process should take about five minutes.

    - When all four User LEDs are illuminated steady, pull the power supply from the board and remove the MicroSD card.

    - Connect an Ethernet cable to the board and re-connect the power supply.

    - The BeagleBone Black will boot into Debian Linux.

    - Download the PuTTY application Link ex.png

    - Download the Advanced IP Scanner application Link ex.png

    - Open Advanced IP Scanner and click the Scan button.

    - Once the network scan has completed locate the BeagleBone Black's IP address. The manufacturer will be listed as Texas Instruments. My BeagleBone Black's IP address is 10.0.1.179 (Image Link ex.png)

    - Open the PuTTY application and enter the IP address of your BeagleBone Black. I've entered 10.0.1.179 (Image Link ex.png)

    - Click Open, then click Yes to the PuTTY Security Alert (Image Link ex.png)

    - Enter root at the login prompt (Image Link ex.png)

    - Enter root as the password.

    - The screen should look like this (Image Link ex.png)

    - From here the Mac OS X and Windows configuration is the same because the work is done on the BeagleBone Black. Skip to the BeagleBone Black OS configuration.

     

     

     

     

     

     

    BeagleBone Black OS configuration.

     

    After using PuTTY or the OS X Terminal app to connect via SSH to the BeagleBone Black you'll need to run several commands to update and configure the BBB as an MPD server.

     

    - Type -> apt-get update

    - Hit Enter and wait for the update to complete.

    - Type -> apt-get upgrade -y

    - Hit Enter and wait for the upgrade to complete.

    - Type -> reboot

    - Hit Enter and wait for the BBB to restart

    - Reconnect to the BBB via SSH using PuTTY or OS X Terminal app as described above.

    - Type -> apt-get install mpd ncmpc alsa-base cifs-utils -y

    - Wait for the installation to complete.

    - Type -> apt-get remove apache2 -y

    - Wait for the removal to complete.

    - Type -> apt-get autoremove -y

    - Wait for the removal to complete.

    - Type -> mkdir /mnt/music

    - Type -> nano /etc/fstab

    - Hit the down arrow to the botom of the file that was opened with the previous command.

    - You will need the IP address of your NAS drive on which your music collection is stored. Use the aforementioned IP scanning tools if necessary. You will also need the Share name of the folder on your NAS. For example when I connect to my NAS I use the IP address 10.0.1.18 and the Share name is Audio. Audio is just a folder on the NAS.

    - Add the following line to the bottom of this opened file (nano /etc/fstab), substituting your NAS IP and Share name rather than using my information. Replace the ********* with the actual password to your NAS Share. Here is an image of my file (Image Link ex.png)

    //10.0.1.18/Audio/Music /mnt/music cifs defaults,username=admin,password=********** 0 0

    - After entering this information press Control O (Control key plus the letter O) then his enter to save the file.

    - Hit Control X (Control key plus the letter X) to close the file.

    - Type -> mount -a

    - Type -> nano /etc/mpd.conf

    - Make the following changes to the mpd.conf file that was opened with the previous command.

    Remove the # symbol in front of the following lines

    zeroconf_enabled "yes"

    zeroconf_name "BBB Music Player"

    mixer_type "hardware"

    bind_to_address

     

    Change the line -> bind_to_address "localhost"

    to -> bind_to_address "0.0.0.0"

     

    Change the line -> music_directory "/var/lib/mpd/music"

    to -> music_directory "/mnt/music"

     

    Find the Alsa Audio Output section and make it look like this, placing # symbols in front of the bottom four options and changing the device to hw:1,0. The name can be changed to USB DAC or anything else if you'd like.

     

    audio_output {

    type "alsa"

    name "USB DAC"

    device "hw:1,0" # optional

    # format "44100:16:2" # optional

    # mixer_device "default" # optional

    # mixer_control "PCM" # optional

    # mixer_index "0" # optional

    }

    - After entering this information press Control O (Control key plus the letter O) then his enter to save the file.

    - Hit Control X (Control key plus the letter X) to close the file.

    - Type -> nano /etc/modprobe.d/alsa-base.conf

    - Arrow to the bottom of the file and add the following text -> options snd-usb-audio nrpacks=1

    - After entering this information press Control O (Control key plus the letter O) then his enter to save the file.

    - Hit Control X (Control key plus the letter X) to close the file.

    - Type -> nano /etc/inittab

    - Place the # symbol in fron of the following lines

     

    1:2345:respawn:/sbin/getty 38400 tty1

    2:23:respawn:/sbin/getty 38400 tty2

    3:23:respawn:/sbin/getty 38400 tty3

    4:23:respawn:/sbin/getty 38400 tty4

    5:23:respawn:/sbin/getty 38400 tty5

    6:23:respawn:/sbin/getty 38400 tty6

     

    - After entering this information press Control O (Control key plus the letter O) then his enter to save the file.

    - Hit Control X (Control key plus the letter X) to close the file.

    - Type -> nano /etc/default/cpufrequtils

    - Add the following text -> GOVERNOR="performance"

    - After entering this information press Control O (Control key plus the letter O) then his enter to save the file.

    - Hit Control X (Control key plus the letter X) to close the file.

    - Type ncmpc

    - Once the app opens hit Control U (Control key plus the letter U) to update the MPD database with all the music stored on your NAS. This may take awhile depending on how much music you have and how fast your network and NAS are.

    - Hit the letter Q to exit the ncmpc window. The Database update will continue.

    - NCMPC can be used to play music, but the interface is pretty crude compared to MPoD on the iPhone or MPaD on the iPad.

     

    Remote Control

    - Install MPoD or MPaD from the app store

    MPoD Link ex.png

    MPaD Link ex.png

     

    If using MPoD, open the app and select the target looking icon in the upper left corner of the Now Playing window. You should see the your server listed. Select the server and tap the Done button. Second, select the gear icon next to the target icon on the Now Playing Screen. Then select Refresh Local Cache to populate the app with the database of music stored on your NAS and available to the server. Now you'll be able to browse through the bottom of the app selecting Artist, Album, Song, and more.

     

    [ATTACH=CONFIG]6521[/ATTACH] [ATTACH=CONFIG]6519[/ATTACH] [ATTACH=CONFIG]6520[/ATTACH]

     

     

     

     

     

     

     

    Please let me know if you find errors in this guide. I will keep it updated as appropriate. Tips, tricks, and tweaks are also encouraged!

     

     

     

     

    1-Pixel.png

     

     

     

     

    Image Gallery

     

    [ATTACH=CONFIG]6515[/ATTACH][ATTACH=CONFIG]6512[/ATTACH][ATTACH=CONFIG]6509[/ATTACH][ATTACH=CONFIG]6516[/ATTACH][ATTACH=CONFIG]6513[/ATTACH][ATTACH=CONFIG]6510[/ATTACH][ATTACH=CONFIG]6507[/ATTACH][ATTACH=CONFIG]6514[/ATTACH][ATTACH=CONFIG]6511[/ATTACH][ATTACH=CONFIG]6508[/ATTACH][ATTACH=CONFIG]6517[/ATTACH][ATTACH=CONFIG]6518[/ATTACH]

     

     

    1-Pixel.png




    User Feedback

    Recommended Comments



    Just have to ask. Library updates fine, and MPAD is connected. The only thing I'm having problems with now is the player is stuck on pause. If I hit play it just goes back to pause immediately. USB DAC is listed as an output. Not sure what has changed. Lots to still learn I see.

    Did you get this to work? You ay have to restart the BBB if your DAC was unplugged and replugged in because the BBB won't send power to the DAC unless the DAC is there at boot.

    Share this comment


    Link to comment
    Share on other sites

    Has anyone done a careful comparison of the Beaglebone with other audio servers? I see a lot of technical discussion about how to get it up and running, but not much about its sound quality beyond the most basic review.

    Share this comment


    Link to comment
    Share on other sites

    Did you get this to work? You ay have to restart the BBB if your DAC was unplugged and replugged in because the BBB won't send power to the DAC unless the DAC is there at boot.

     

    Unfortunately not, but what you mention makes sense. I ran the shutdown command to turn the BBB off, connected the Halide Bridge, but no luck. I think I may have to reboot it once it's connected to make sure it is getting power. My DAC is not locking on to the Bridge, I'm guessing now because the Bridge isn't getting power.

    Share this comment


    Link to comment
    Share on other sites

    Unfortunately not, but what you mention makes sense. I ran the shutdown command to turn the BBB off, connected the Halide Bridge, but no luck. I think I may have to reboot it once it's connected to make sure it is getting power. My DAC is not locking on to the Bridge, I'm guessing now because the Bridge isn't getting power.

    Shut it down, pull the power, connect the Bridge, reconnect the power. Should work fine.

     

    Id run the command "aplay -l" to make sure the device is visible.

    Share this comment


    Link to comment
    Share on other sites

    Hi Guys - Just an update.

     

    I linked to the newest version of the Debian image file in the instructions. And, I did some testing with NFS versus SMB/CIFS. Using NFS I couldn't get playback without pops and ticks. I switched back to SMB/CIFS and all is well. Probably a config issue on my end. Not sure what to tweak.

    Share this comment


    Link to comment
    Share on other sites

    Shut it down, pull the power, connect the Bridge, reconnect the power. Should work fine.

     

    Id run the command "aplay -l" to make sure the device is visible.

     

    This worked for me. I probably wasn't paying attention to how I was connecting things with the power.

    Share this comment


    Link to comment
    Share on other sites

    Hi Guys - Just an update.

     

    I linked to the newest version of the Debian image file in the instructions. And, I did some testing with NFS versus SMB/CIFS. Using NFS I couldn't get playback without pops and ticks. I switched back to SMB/CIFS and all is well. Probably a config issue on my end. Not sure what to tweak.

     

    This is what I have in my /etc/exports (NAS):

     

    /volume1/music *(ro,async,no_wdelay,no_root_squash,insecure,anonuid=0,anongid=0)

     

    My /etc/fstab entry (Beaglebone):

     

    10.0.1.x:/volume1/music /mnt/music nfs soft,intro,ro,rsize=32768 0 0

    Share this comment


    Link to comment
    Share on other sites

    Has anyone done a careful comparison of the Beaglebone with other audio servers? I see a lot of technical discussion about how to get it up and running, but not much about its sound quality beyond the most basic review.

     

    I second this thought. Just wondering how different would it be from a Raspberry Pi or Cubox

    Share this comment


    Link to comment
    Share on other sites

    Not all NAS are created equal because the suggested settings as decribed in the BBB setup dit not work for me mounting the NAS share.

    Mout errors (95) were the only reponse from the BBB

     

    Searching internet and trying different combination this one works for me:

     

    //192.168.1.xx/Data/Music /mnt/music cifs username =admin,password=wwadmin,iocharset=utf8,sec=ntlm 0 0

     

    My NAS is a Netgear Readynas Duo V1 with the latest firmware from last month.

     

    Playing works fine with sometimes only some small hiccups the first seconds of a new track played. Have to see how to improve this ... maybe some buffer settings ?

    Share this comment


    Link to comment
    Share on other sites

    Not all NAS are created equal because the suggested settings as decribed in the BBB setup dit not work for me mounting the NAS share.

    Mout errors (95) were the only reponse from the BBB

     

    Searching internet and trying different combination this one works for me:

     

    //192.168.1.xx/Data/Music /mnt/music cifs username =admin,password=wwadmin,iocharset=utf8,sec=ntlm 0 0

     

    My NAS is a Netgear Readynas Duo V1 with the latest firmware from last month.

     

    Playing works fine with sometimes only some small hiccups the first seconds of a new track played. Have to see how to improve this ... maybe some buffer settings ?

     

    You might be able to fine tune CIFS by increasing the size of the buffers.

     

    It might be worth trying NFS to remotely mount the disk rather than use SMB/CIFS. I googled for 'Netgear Readynas Duo NFS' and it does look as though is has NFS although you might need to enable it from the command line. See an earlier post from k-man for an example /etc/fstab entry on the BeagleBone, and /etc/exports line on the NAS.

     

    On the other hand, Chris Connacker said that he got clicks and pops with NFS that went away when he used CIFS. In my own network I have found that NFS is more efficient.

    Share this comment


    Link to comment
    Share on other sites

    My /etc/fstab entry (Beaglebone):

     

    Code:

     

    10.0.1.x:/volume1/music /mnt/music nfs soft,intro,ro,rsize=32768 0 0

     

    Oops I made an error! "intro" needs to be amended to "intr", otherwise a mount error will arise.

    [color=#3E3E3E]10.0.1.x:/volume1/music /mnt/music nfs soft,[/color][b]intr[/b][color=#3E3E3E],ro,rsize=32768 0 0[/color]

     

    As Richard pointed, I tried both cifs and nfs mounts, preferring nfs. But I didn't play about with the various options in the Synology DiskStation Manager for the Windows share (re MTU size).

    Share this comment


    Link to comment
    Share on other sites

    I am completely new to Linux and it's files.

     

    Because I have a very short dip in sound during the first second of a track when I skip back or forward or select a track direct (not when playing a complete album) I guess it is a buffer issue when the computer has to adapt to an (unexpected) user command.

     

    In the alsa-base.config I see some buffer setting with a "#" before it.

    Is it correct that I have to remove the # to "activate" the setting and change the settings / numbers behind it to take full control over the buffer ?

     

    Any practical info on what buffer settings to try would be helpfull ... I already read some articles but somehow the information does not really trigger my understandings of the whole process ...

     

    P.S. do I need to reboot something before such settings take effect or do I only need to stop end re-start playback ?

    Share this comment


    Link to comment
    Share on other sites

    Any practical info on what buffer settings to try would be helpfull ... I already read some articles but somehow the information does not really trigger my understandings of the whole process ...

     

    P.S. do I need to reboot something before such settings take effect or do I only need to stop end re-start playback ?

     

    Oystein,

     

    I'm new to Linux too so I didn't play around with the alsa-base config settings. An alternative approach would be to try amending the MPD Internal Buffering settings in /etc/mpd.conf:

     

    Screen Shot 2013-08-12 at 18.01.01.png

     

    So deleting the # before 'audio_buffer_size' and 'buffer_before_play', and change to any appropriate figure (e.g. 1024, and 4% as a suggestion).

     

    Save the changes, then reboot or type:

    sudo /etc/init.d/mpd restart

     

    ...activates the changes.

    Share this comment


    Link to comment
    Share on other sites

    @k-man

     

    Thank you for your suggestions. I will try these and see what works best.

     

    Looking into the cross-fading option of MPD is read on their Wiki page that these settings also determine the crossfader behaviour.

    Music Player Daemon Crossfading Troubleshooting - Music Player Daemon Community Wiki

     

    Because I will build something special I started a project topic in the "Music Servers" section where I will coninue my observations and building progress.

    http://www.computeraudiophile.com/f10-music-servers/my-beaglebone-black-integrated-dac-music-server-streamer-project-page-17181/#post247550

    Share this comment


    Link to comment
    Share on other sites

    Hi there, nice piece of work!!!

    It works like a charm, but it doesn't tag my sacd files?

    My Raspberry with Raspify shows all of my dsf files, and plays them to my Teac 501, same config .... but slight klicking sound from usb port :-((

    With 192kHz and 24 bit my beaglebone rocks!!!

    Share this comment


    Link to comment
    Share on other sites

    The small dip at the start of a new track is still present (many times but not always) when I select a new track manually. No problems when a playlist is processed. Repated pressing the |< button in MPad to restart the track over and over again every 3 seconds it happens approx. 50% of the times.

     

    To describe the problem more clearly: when a track starts playing within a few tenths of a second the sound volume dips for half a second and comes back to normal.

    Sounds if somebody turns the volume down and up very quickly. This all happens in the first 1-1,5 sec.

    No clicks or any other undesired effects ... only the volume goes down and up ... it is a fluent change so not unterrupted by a hard off and on again like a switch.

     

    I tried different settings for buffer and nrpacks:

    - big buffer, high % before play (16M/50%)

    - smaller buffer, high % before play (4M/50%)

    - really small buffer, high % before play (1M/50%)

    - big buffer, low % before play (16M/10%)

    - smal buffer, low % before play (2M/10%)

    And tried above settings with nrpacks 1, 20 and 50.

     

    Ofcourse I removed the ""#" at the buffer lines in mpd.conf to active this funtionality ;-)

    I could really notice a bigger delay before play starts with the high buffer settings but for nrpacks I did not notice any difference.

     

    Any suggestions ??

     

    P.S. ... besides this little annoyance the sound is beautifull .... I will do A/B this weekend but I think it sounds better than my Win7/JRiver setup.

    Share this comment


    Link to comment
    Share on other sites

    Looking into the cross-fading option of MPD is read on their Wiki page that these settings also determine the crossfader behaviour.

    Music Player Daemon Crossfading Troubleshooting - Music Player Daemon Community Wiki

    Sounds to me like crossfading can be eliminated by setting the buffer before play to 100%.

     

    With my Squeezelite configuration I have the 'Crossfade' to OFF in the Logitech Media Server Settings.

    Share this comment


    Link to comment
    Share on other sites

    After lots of testing and trying I discovered a lot ...

     

    The often short dip at the beginning of a track is not computer related. My Windows PC with JRiver 17 has the same issue.

    Because I had the crossfading (smooth, 0,5 sec) active I never really noticed until I did some comparissons this morning between the PC and BBB.

    Now I also noticeded that the connection with the DAC is lost for a very short moment when I skip track ... not during playback of a complete album because the LED blinks red when I do skip. My DAC was always installed behind some other equipment so I never looked at it during playback and maybe forgotten since I bought it. Also when paused a track and resume playback the same problem on PC and BBB.

    So is it NAS/network related of does my DAC play tricks on me?

     

    The big discovery (for me at least ;-) was to activate any new nrpacks settings you need to reboot the BBB.

    I tried some higher nrpacks before but this apparently did not make any difference.

     

    This morning powered up again the last change of nrpacks settings (100) became active and no playback possible.

    Set nrpacks at 20 and playback worked again.

    At many songs I had problems now with clicks and plops and finally discoverd that this issue was solved lowering nrpacks even more (set on 5 now).

     

    P.S. crossfading is a function inside the ncmpc console.

    When you press "x" on your keyboard you can toggle between crossfading "off" or "10 sec" but it is related to your buffersettings (memory vs. %-before-play). Maybe some other day I will look into it and try different settings.

    Unfortunate crossfade does not work when skipping tracks ... only when you play an album and the next track already fades in at the end of the current track.

    Share this comment


    Link to comment
    Share on other sites

    I am having trouble mounting music files from my VortexBox on the BBB Music Server. I seem to get mount error(13) permission denied.

     

    /etc/fstab configurations that I have tried:

     

    1) //192.168.0.XXX/storage/music/flac /mnt/music cifs defaults,username=root,password=XXXX 0 0

    2) //192.168.0.XXX/storage/music/flac /mnt/music cifs guest,_devnet 0 0

     

    No joy or mount for that matter with either fstab configuration!

     

    Any help is greatly appreciated!

    Share this comment


    Link to comment
    Share on other sites

    I had similar problems and the settings advised here did not work for me. I guess some NAS need different commands.

     

    This one workerd for me:

     

    //192.168.1.xx/Data/Music /mnt/music cifs username =xxxxxx,password=xxxxxx,iocharset=utf8,sec=ntlm 0 0

     

    Please be aware that your NAS share is set correct otherwise no mount command will ever work.

    Share this comment


    Link to comment
    Share on other sites

    @Oystein

     

    Thanks for you reply!

     

    I have figured out how to mount the VortexBox FLAC shares with NFS and have the BeagleBoard Black Music Player up and running! See my post in the Forums under Music Servers for the details.

     

    I have to say for the $62 I have invested in this project (I already had a 5V switching PS and a nice 5V Linear Regulated PS) that the cost/performance ratio is "off the charts"!

     

    The BBB Music Player running with a nice 5V Linear Regulated PS produces exceptional sound quality. I have heard boutique equipment at the $9.5K level that can't touch this as a digital source!

     

    No fan noise or noisy computer PS!

     

    All things considered, this is a very worthwhile project in terms on time and money spent!

     

    It will replace a SqueezeBox Touch with Linear Regulated PS in one of my systems!

     

    I would encourage all who have some Linux experience to undertake this project!

    Share this comment


    Link to comment
    Share on other sites

    @Oystein

    Thanks for the reponse!

     

    I got the VortexBox file shares mounted with NFS. I have copied my post from the Forums:

     

    OK, gang we have ignition and liftoff! I got the VortexBox files to mount using nfs. Had to:

    1. apt-get install nfs-common

    2. Edit /etc/fstab file to 192.168.0.105:/storage/music/flac /mnt/music nfs soft,intr,ro,rsize=32768 0 0

    3. mount -a

     

    And the magic happened! The VortexBox flac files mounted!!

    I sort of followed the recipe from this link: BeagleBone Black as an MPD server

     

    I am now able to play the files into my Twisted Pear Dual Mono Opus DAC with USB receiver!

     

    Listening to Ben Webster at the moment via this front end source!

     

    Sound quality is excellent even with a standard SqueezeBox Touch (switching) power supply!Sorry about the bold font! I could not change it after cutting and pasting from my post on the Forums!

    Share this comment


    Link to comment
    Share on other sites

    Chris, noob here. I have JRiver on my network and just want to send music from my server to the BBB and onto my Dac using the Gizmo app. I'm getting stuck on the commands that follow Type -> nano /etc/fstab. I've entered the ip of my server and the folder of my music files but now I'm not sure if I need to enter a login and password. I guess this is where my brain is stuck. Any help is appreciated.

    Share this comment


    Link to comment
    Share on other sites

    Ordered my beaglebone. .. I have a raspberry pi and a pogoplug running squeezelite , and i will have this runnng the same soon .

    Share this comment


    Link to comment
    Share on other sites

    Hello. I have run into an issue when following Chris' instructions. Upon reaching the point of install when I type "mount -a", I get a response back from the BBB that says "mount point cifs does not exist". Then, the BBB returns to "root@arm:~#". Everything to this point seems to track correctly. What am I doing wrong? Thanks. JCR

    Share this comment


    Link to comment
    Share on other sites




    Guest
    This is now closed for further comments




×
×
  • Create New...