Printable View
Hi,Quote:
Originally Posted by mikmas
I've never tried direct connection between Pi and Mac.
A fellow from NZ sent me some info on getting hot-plug usb to work, just have not gotten to that particular item on my to-do list yet. Eventually it will work :-)
Regards,
Tim
Hi Jo,Quote:
Originally Posted by The Black Adder
Yes, wired Ethernet will be a lot faster, but you would need to shut down, pull wifi adapter, plug in ethernet cable then boot up. Then reverse after the copy is complete to get the Pi back on WiFi.
Regards,
Tim
Thanks, Tim.
To be honest, I think I'll just use Ethernet anyway.
Cheers
Jo
So frustrating, I kept loosing my library.
So formatted my sd card, and loaded the latest test image.
Worked great this morning, loading the nas library really quickly.
However, I started mucking around with one or two of the settings ( resampling rates)- and now I'm loosing the volume.
And then the library has gone again. Damn.
Oh hang on...
Fired up MPoD player on the phone.. Hit/ ticked ' outputs' in settings, and it's all working again.
Lordy. Time for a drink.
Hi Steve,Quote:
Originally Posted by SteveW
Very odd.
Whenever the UI starts behaving really strangely, hangs, no audio, etc. one of the following is suspect:
- bad or corrupt SD Card
- failing power supply
- network issue
I would suggest trying a new SD card.
Regards,
Tim
Hi Steve,Quote:
Originally Posted by SteveW
Just want to make sure I get this symptom right, but when you say "losing my library" do you mean that the NAS folder disappears from the Browse panel, or do you mean that when u press "Library" tab it comes back blank and shows 0 tracks?
Regards,
Tim
Hi Tim
Many thanks for your involvement.
The library was just 'lost'. Wish I'd taken a screen shot, as actually I think it showed one track.
I reformatted a card this morning and loaded your new 'test' version.
Started having problems again.
I am also wondering if MPoD interferes with the Moode player settings?
Anyway.. Just tried revising the settings to this
http://i82.photobucket.com/albums/j2...pseehosqf5.png
Now my library has started to update ( over 29,000 tracks)
Now stuck at just over 8000, as here..
http://i82.photobucket.com/albums/j2...pstlehszjz.png
Just realised what you meant Tim.Quote:
Originally Posted by TimCurtis
The library is there, but zero tracks.
I can access the library through other software like Plug Player or one of Linn's UPNP controllers Songbook Lite- where the full library is shown.
Hi Steve,Quote:
Originally Posted by SteveW
The way the Library loader was originally designed lends itself to issues with some large collections. I've improved it quite a bit but had to stay within the limits of the original design. You may have to use the Browse panel to select music, or an external app like MPoD...
Andreas, the fellow who is working on Moode 3 project has redesigned the Library loader so it will work nicely with large collections but Moode 3 project will probably take a year to complete since it involves a ground-up rewrite and debug of the entire code base :-)
Regards,
Tim
Hi Tim
Understood.
Great tip though, of using Browse to access the library. It's all there, and by using the drop down menu it's easy enough to get what you want onto the playlist.
Well done.
Thank you.
When my son was working in Greece he used to hear a saying - 'You make plans, and God laughs'
Just checked my library and thought of this
http://i82.photobucket.com/albums/j2...psjpsu1nqf.png
I have just spent about 6 hours over 2 days trying to get Moode running again, after a random "nothing happens" failure.
I have now renamed FBA Frustration Based Audio!
Anyway, I have wiped most of the foam from around my mouth and my blood pressure is back below 300. In order to save some other poor sod (and myself, next time) a heart attack, here is my setup procedure - modified from Tim's readme.
It is specific to my particular setup of IQDAC+, USB hard drive and USB dongle for remote control. Hopefully it's of some help for others:
Moode Audio Payer SD Card Setup
Use Moode 2.3 image (not Zip file, this needs to be unzipped using 7-zip):
C:\Users\dave\Downloads\moode-sdimg-r23\moode-sdimg-r23
Use Winddiskimager to write IMG file to SD card.
Then…..
================================================== ===============README: PLAYER SETUP Moode Audio Player, (C) 2014 Tim Curtishttp://moodeaudio.org Designed for Raspberry Pi================================================ ================= NOTE: Use http://moode -or- http://moode.local 1. INITIAL SETUP a) insert sd card (but not USB wireless dongle) b) connect ethernet cable c) connect USB storage device (if any) 2. POWERING UP - IF USB AUDIO DEVICE a) power on Raspberry Pi without USB audio device connected b) http://moode c) plug audio device device into USB port d) reboot - IF I2S AUDIO DEVICE a) power on the Raspberry Pi with I2S audio device connected b) http://moode c) Menu, Configure, System d) select i2s audio device then SET e) reboot (via Settings, Power off, Reboot)f) Set MPD to hardware volume WARNING: Set volume to 0 and stop play back before changing this setting.g) Select Customise, Hardware volume curve – set to Logarithmic - VERIFY/SET ALSA VOLUME a) http://moode b) Menu, Configure, System c) Press SET after entering appropriate value (no need to reboot) - VERIFY AUDIO PLAYBACK a) http://moode b) Click a radio station from the Playlist c) Check correct operation of volume control 3. TIME ZONE AND AUDIO DEVICE DESCRIPTION a) http:/moode b) Menu/System, Timezone c) Menu, Customize, Audio device description, Device 4. ADD SOURCE CONTAINING MUSIC FILES - USB STORAGE DEVICE a) http:/moode b) Menu, Configure, Sources c) press UPDATE MPD DATABASE button d) WAIT for completion (no spinner on the Browse tab) e) click Browse tab then Menu, Refresh - NAS DEVICE a) http://moode b) Menu, Configure, Sources c) click NEW button to configure a music source (MPD DB update initiates automatically after SAVE) d) WAIT for completion (no spinner on the Browse tab) e) click Browse tab then Menu, Refresh At this point a FULLY OPERATIONAL PLAYER exists. ================================================== ===============CUSTOM CONFIGSCustomize the player configuration by using any of the followingprocedures.============================== =================================== 1. CHANGE PLAYER HOSTAND NETWORK SERVICE NAMES a) http:/moode b) Menu, Configure, System c) Press SET after entering appropriate value in each name field d) reboot 2. CHANGE PASSWORD FOR USER ROOT a) ssh root@moode (pwd moode) b) passwd root (prompts will follow) c) reboot 3. CONFIGURE FOR WIFI CONNECTION a) power off (from Menu/Turn off) b) insert wifi dongle c) power up (leave eth cable connected!) d) http://moode e) Menu, Configure, Network f) configure a wifi connection (can take ~ 60 seconds to complete) BTHub3-????Security WPA/WPA2 Personal Note: WLAN “Not Used” should change to the WLAN addressNote 2: 1st got “No Interface Present” then refreshed the page using Windows (top left) refresh. This seemed to work. g) power off, unplug eth cable, power upThis bit seems to be random with several attempts needed and the patience of a bloke dressed in orange robes! 4. DISABLE ETH0 INTERFACE FOR FASTER BOOT - WARNING: this is for an already operational WIFI setup! a) /var/www/tcmods/r23/cmds/utility.sh edit-eth0 b) # out the eth0 lines c) reboot ================================================== ===============END README============================================ =====================
Check ALSAMixer settings by running Putty. 192.168.1.104
Login as Pi
Password: raspberry
Explanation of volume settings:
http://theartofsound.net/forum/showt...er-Help/page10
Haha, don't you just love computers. All the paragraph formatting has disappeared up microsoft's rear end.
Hi,Quote:
Originally Posted by SteveW
Glad to see that it's working :-)
I see that you are using IOS. The appearance of Moode can be improved by adding it as a "Home Screen" app. When this is done, the Browser frame is removed and it will look a native app :-)
Press the "rectangle-with-arrow-sticking-out-the-top" icon on the footer bar, then press "Add to Home Screen". You will find the Moode app on one of your Home Screen pages.
Regards,
Tim
Hi Dave,Quote:
Originally Posted by Starterman
Good to here its working and that your vital signs are returning to normal :-)
What is the USB remote control dongle that u are using? Sounds interesting.
I'm making a new Volume Control guide as a PDF that can be viewed/downloaded from moodeaudio.org that reflects a change I've made to the code so the ALSA volume (%) field on System config will show the actual volume %. Currently it is showing the value from the ALSAMIXER slider scale which is not a % but a "mapped or hybrid value" according to ALSA guy.
I'll tune up the setup guide a bit too.
Regards,
Tim
Hi Tim,
If it is any use I can email you my personalised setup guide - which has my additions in blue, but is actually legible, unlike the pasted in version above. It is written from the point of view of somebody who is not particularly computer literate.
Sorry if I mislead you, the Wifi dongle is a standard one. I meant that I use it so that I can control the Pi from a browser (with no ethernet connection), not that it enables an actual remote control handset as such. This is the one:
http://www.modmypi.com/raspberry-pi/...ongle-nano-usb
Is there an easy way to duplicate my micro SD card, in case I have another problem?
Could I also clarify that I am doing the power down procedure correctly:
System Menu -> Turn-off -> Power-off
Wait until the green light has stopped flashing (in my case about 10 seconds after the USB drive has spun down) then turn off the 5V PI/DAC supply.
The reason for asking is that I cannot see any other way to power up, other than turning on the 5V supply, when following step 3:
3. CONFIGURE FOR WIFI CONNECTION
a) power off (from Menu/Turn off)
b) insert wifi dongle
c) power up (leave eth cable connected!)
Also, since going from V2.1 to V2.3 my bootup time has gone from 90 seconds to 'ages'. I never managed to work out how to do step 4:
4. DISABLE ETH0 INTERFACE FOR FASTER BOOT
- WARNING: this is for an already operational WIFI setup!
a) /var/www/tcmods/r23/cmds/utility.sh edit-eth0
b) # out the eth0 lines
c) reboot
I have no idea where to look to do 4a.
Sorry for more questions!!
Cheers,
Dave
Hi Dave,Quote:
Originally Posted by Starterman
Here are answers to your questions :-)
(1) I can email you my personalised setup guide
Yes, please email me the document. I am looking for input on how to improve the admittedly sparse setup guide.
(2) Is there an easy way to duplicate my micro SD card
Not that I am aware of. I just copy the image to the card.
(3) Could I also clarify that I am doing the power down procedure correctly:
The procedure is correct. The Raspberry Pi LED will flash 10 times during shutdown. Then disconnect power.
(4)bootup time has gone from 90 seconds to 'ages'
This is odd. My Pi's boot up < 1min, usually 30 secs even without the fast boot patch.
Here is how to do 4a. It must be done from a terminal session to Moode. Use the PuTTY app if you are on Windows, otherwise for Mac or Linux just open a terminal and ssh in.
Linux/Mac
ssh root@moode (pwd = moode)
Windows
PuTTY, host name = moode, connection type = ssh, then press OPEN button, a terminal window will open and password prompt will appear (pwd = moode)
Once the Moode command prompt appears in the terminal window, enter the command string in step (1) below. If you are using Moode 2.4 test release then replace r23 with r24
(1) /var/www/tcmods/r23/cmds/utility.sh edit-eth0
This opens the network interface config file in the nano editor
==================
auto lo
iface lo inet loopback
auto wlan0
iface wlan0 inet dhcp
wireless-power off
wpa-ssid <YOUR-SSID-NAME>
wpa-psk <YOUR-WIFI-PASSWORD>
auto eth0
iface eth0 inet dhcp
==================
(2) Put comment char (#) in front of last two lines as follows:
#auto eth0
#iface eth0 inet dhcp
(3) Save the file by entering the keystrokes below. <return> is the return or enter key
Ctrl-x
y
<return>
(4) reboot
Regards,
Tim
Excellent Tim
Many thanks
Damn...
Went from this last night
http://i82.photobucket.com/albums/j2...ps4rzaiowv.png
To this first thing this morning.
http://i82.photobucket.com/albums/j2...ps9mw7svlb.png
Still.. Not a major problem as MPoD app on the iPhone has retained the whole library.
Many thanks Tim!!!
I have emailed you my version of your user guide.
If I feel brave enough I will have a go at disabling the ethernet code. :eek:
In the meantime I'm happy to listen to some tunes.
"(2) Is there an easy way to duplicate my micro SD card
Not that I am aware of. I just copy the image to the card."
Image writer for windows allows you to copy a image from your SD card to your computer hard drive, you should then be able to write that image to a new SD card which would give you a duplicate of your origanal Sd card. I have not treid this but I think it sholud work.
I think this is a general computer issue rather than a Moode issue. I cannot connect to the gui using http://moode , I have to enter the actual ip address (i downloaded ip Scanner to find out the ip address of the pi). Anyone know what I need to do to fix this?
It rarely works for me eitther but does on occasion. Not worked out the reason yet Stuart. I always just use the local ip anyways which if you find your router address will be easy to find. The router address will always stay the same but unless you change at router to static addresses the the pi may change when switched off and back on(normally if nothing else has been assigned a ip then it will stay same). Its easy to find anyways.
I asume it may be a router or a browser issue
Hi There,Quote:
Originally Posted by killie99
I've always had to input the ip address of Moode but I just created a link on the desktop or home screen of my ipad using the ip and that connects just fine.
Cheers,
Alistair
I use Rocket Dock to keep the desktop tidy but this is the general idea
http://i739.photobucket.com/albums/x...psc6b2azyz.jpg
and the details
http://i739.photobucket.com/albums/x...psazeeorfx.jpg
Hope this helps
Cheers,
Alistair
It does work. :)Quote:
Originally Posted by Kit1cat
Great, that's handy to know. :)Quote:
Originally Posted by Canetoad
I find if I use the hostname in a browser to connect to my box, I have to use the port number too - don't know what port moode runs on but on mine I go http://diepi:4040 (cos my subsonic server is on port 4040) and I can get through (I can also use ipaddress:4040 for the same thing)Quote:
Originally Posted by killie99
Also recommend (if you can) using your router to reserve a particular IP address for the pi so it's always in the same place (numberwise).
Hi Steve,Quote:
Originally Posted by SteveW
Very odd.
I notice that "Updating" appears in the Browse button. Is an MPD database update in progress when you press the Library tab button?
Regards,
Tim
@Steve,
I forgot to mention something regarding the really really slow boot time.
If after selecting REBOOT in Moode the "Connecting" page with the big spinner appears and the Browser is left open, Moode sometimes does not reconnect. This can make it seem as if the reboot is taking forever because the Moode UI does not come up. In this case just close the browser tab and open a new one and access Moode afresh. A typical reboot up to the point when Moode UI is available takes < 1 min. Ssh access to Linux on the Pi is usually available < 30 secs.
Regards,
Tim
Hi Stuart,Quote:
Originally Posted by killie99
The symptom "cannot access by name and must use ip address" suggests a configuration issue in the router or that the router does not include either DNS or mDNS name resolution services.
Moode WebUI is basically a web site accessed via standard http port 80. There are three urls that can be used to access Moode depending on how names are resolved on the network.
(1) http://moode
(2) http://moode.local
(3) http://IP-ADDRESS-OF-PI
For example on my home network, my router, an ASUS RT-N66U, includes a DNS name resolution service that automatically places the host name of the Pi in its database when the Pi receives its ip address from the router. This allows the router to resolve the host name "moode" to its ip address in the url http://moode.
Another approach used by routers is to include a name resolution service called Multicast DNS or mDNS instead of DNS (Unicast DNS). This service performs name resolution for host names with a .local suffix. In this case http://moode.local should work.
Lastly, if name resolution service is not present in the router, the ip address can be used.
Regards,
Tim
Tim
Having played around with both Volumio and RuneAudio, I have to say I'm very impressed with Moode - all sorts of stuff that required fiddling about in the others "just works" in Moode.
The Internet Radio selections are great and nice to have them all pre-setup - especially the Linn and Naim stations. One observation though: the BBC Radio 3 link does not appear to be the HD (320k) stream, but shows up in Audio info as a 128k stream. Any chance this could be changed?
One thing that would make Moode perfect in my opinion - the ability to tell it to play tracks at random from a complete NAS or local USB source.
Great work, Tim!
Rob
Hi Rob,Quote:
Originally Posted by robtweed
Thanks for the nice compliment! I really appreciate it :-)
The BBC stations are all 128k MP3 streams and not the new 320k HLS streams. Apparently MPD, the music server engine that Moode uses, does not yet have the capability to decode the HLS format. I think the capability will be developed for MPD because there are a lot of UK audio enthusiasts asking for HLS support on various forums.
If you want to try random song play from an entire source, use the Browse panel to add NAS/folder or USB/folder to the Playlist then press the random button on the Playback panel. I'm not sure what the track limit is for the Playlist, but I just tested ~3500 tracks from a test NAS/Music folder. At one point in the past I think I tested successfully at ~ 12K tracks.
The only issue is that the automatic scroll-to function that positions the currently playing item in the Playlist within the viewable area does not seem to work quite right. Another opportunity for bug fixing :-)
Regards,
Tim
Hi Tim.
Would you know why track titles/artists are not displayed whilst listening to BBC channels? Other stations like Jazz Groove display them so just wondered if this is something to do with the station decoding or Moode itself?
Thanks
Josie
Hi,
@robtweed, I forgot how much I enjoy random play. Thanks for bringing it up :-)
Tim
Hi Jo,Quote:
Originally Posted by The Black Adder
Its because the station does not include the "Title" metadata tag in its stream. If a station includes the Title tag its usually formatted as "Album - Song Title" like you see when playing The Jazz Groove. Other stations just stuff the song title in the "Title" tag. When a station does not include the Title tag, Moode just displays the station URL.
The reason radio stations don't include some or any metadata in their streams has to do with the type of streaming software they use and whether they have a process for providing the metadata.
Actually, the logic in Moode for dealing with radio station metadata is pretty complex because stations don't follow the rules and do all sorts of bad things with metadata.
Regards,
Tim
Ah.. I see.Quote:
Originally Posted by TimCurtis
Thanks Tim. Sorry for the questions but, how come my DAB radio displays information on BBC channels? Is that something totally different?
Thanks
Jo
Hi Jo,Quote:
Originally Posted by The Black Adder
I'm not familiar with "DAB radio" but after reading about it, DAB sounds somewhat similar to the XM/Sirius and HD Radio digital broadcast systems in the States. XM/Sirius is a subscription based over-the-air digital broadcast systems, and HD radio is the digital equivalent of analog FM radio. The market for these systems is primarily car audio.
The stations DAB and Internet broadcasts would likely be using separate streaming systems. The DAB system is including metadata.
Regards,
Tim
I think Dab, like tv etc uses PIP's(programme information platform) for metadata. the internet streams might not
Hi Tim, I use a Netgear WNR3500L but I don't see anything about mDNS in the menu's. I think I can use Tomato firmware on it, I'll need to see if that might work.Quote:
Originally Posted by TimCurtis
Tim
Many thanks for the responses to my earlier questions!
One further question - or more like looking for tips. I have some live material I've recorded at uncompressed 96/24. If I store the files on my NAS source (actually a USB drive attached to a Mac Mini on my home network), I can't play them without serious sound break-up: it would seem that even though everything is connected over hard-wired Ethernet, either the file isn't being streamed to Moode on the Raspberry Pi fast enough, or the buffer on Moode isn't correctly sized. I've tried all sorts of buffer sizes on Moode, from very small to very large, with some improvements here and there, but I still get break-up.
Perhaps there are options I can use when defining the NAS source on Moode that would allow me to tune how the files are sent to the Raspberry Pi over TCP - eg packet size etc? Any suggestions / advice welcome.
Placing the files on a local USB drive on the Pi solves the problem, so it's not entirely critical. 44/16 sources (both uncompressed and Apple Lossless) stream just fine from the Mac by the way, so it's clearly an issue with the sheer rate of streaming that's required with 96/24 files that's the issue.
Cheers
Rob
Tim
Your suggestion on random play worked perfectly. I'd missed that trick of adding the entire source to the playlist - nice one! By the way. it seems to cope with my iTunes library of >11,000 tracks just fine.
Now I'm very happy! I'm now getting all audio sources being sent bit-perfectly and un-tampered-with to my Caiman II DAC via the Pi/Moode/Digi+. All other solutions I'd used did things like re-sampling to 48/16 (eg Apple TV), or were impossible to determine if/how they were tampering with the original stream.
This is a great, and crazily low-cost streaming solution! A great combination with the Caiman II too - I have it connected from the Digi+ via the co-ax wired connection (pro 75 Ohm cable), simply because the 2 Toslink connections on the Caiman were already in use for other devices with only Toslink connections.
One suggestion - on the play screen, it might be an idea to have the playlist in its own separate scrollable div tag so you can still scroll up and down in the main area where the play and volume controls reside. I think it might help make that screen more usable with very large playlists. Alternatively have a view option where you can disable / turn off the playlist display altogether from that screen so the responsiveness of the screen isn't affected by having to cope with a very large playlist.
I'm tempted, Tim, to see what I could do with a bit of Node.js on the back-end, and React.js / React Native on the front.... but then again work has a habit of getting in the way of such fun stuff!
Thanks, BTW, to this forum and its participants which is how I discovered all about these options, components and tricks/suggestions in the first place.
Rob
Hi Rob,Quote:
Originally Posted by robtweed
The two symptoms below suggest a bottleneck either in the Mac Mini, the file sharing protocol or configuration being used in the Mini, or less likely but still possible, an issue in the network device (router or switch) that connects both the Pi and the Mini.
(1) If I store the files on my NAS source (actually a USB drive attached to a Mac Mini on my home network), I can't play them without serious sound break-up
(2) Placing the files on a local USB drive on the Pi solves the problem
It's not a streaming protocol (like what a radio station uses) that occurs between NAS and Pi but rather a file transfer protocol (like a file copy). The Pi believes the NAS is a locally attached disk even though it is somewhere else on the network. The sample rate of the song file is not a factor and buffer changes in MPD should never be required.
To troubleshoot this I would start with a 30 sec ping test initiated on the Pi and to the Mini while playing a song located on the Mini in Moode to see what the round trip times look like and also whether there is any packet loss. We want to see 0% packet loss :-)
Stress Test Comparator: this is what a ping test looks like from a Pi-1B (OC'd to 1GHz) over WiFi to my file server (ms1) while Moode is playing a 120MB DSF (DSD rip) song file located on the server. This Pi is connected to a BerryNOS Red TDA1543 DAC and configured for SoX resampling at 16/176.4 kHz. CPU runs at 75% for DSF resampled. I play DSF, 24/96 FLAC, etc from file server to this Pi and never any audio glitches.
Authenticated to rp1 ([192.168.1.51]:22).
Linux rp1 4.1.10+ #820 PREEMPT Sun Oct 4 15:33:59 BST 2015 armv6l
___ ___ ___
/ _ \ / _ \< /
/ , _// ___// /
/_/|_|/_/ /_/
Moode Audio Player
Release 2.4
This software is provided for free by
the copyright holders and contributors
and comes with no expressed or implied
warranties or any other guarantees.
Last login: Tue Oct 20 11:09:52 2015 from 192.168.1.155
root@rp1:~# ping ms1
PING ms1.home.local (192.168.1.21) 56(84) bytes of data.
64 bytes from ms1.home.local (192.168.1.21): icmp_req=1 ttl=128 time=3.01 ms
64 bytes from ms1.home.local (192.168.1.21): icmp_req=2 ttl=128 time=5.54 ms
64 bytes from ms1.home.local (192.168.1.21): icmp_req=3 ttl=128 time=2.40 ms
64 bytes from ms1.home.local (192.168.1.21): icmp_req=4 ttl=128 time=4.97 ms
64 bytes from ms1.home.local (192.168.1.21): icmp_req=5 ttl=128 time=5.71 ms
64 bytes from ms1.home.local (192.168.1.21): icmp_req=6 ttl=128 time=2.72 ms
64 bytes from ms1.home.local (192.168.1.21): icmp_req=7 ttl=128 time=5.00 ms
64 bytes from ms1.home.local (192.168.1.21): icmp_req=8 ttl=128 time=5.49 ms
64 bytes from ms1.home.local (192.168.1.21): icmp_req=9 ttl=128 time=3.25 ms
64 bytes from ms1.home.local (192.168.1.21): icmp_req=10 ttl=128 time=1.13 ms
64 bytes from ms1.home.local (192.168.1.21): icmp_req=11 ttl=128 time=5.43 ms
64 bytes from ms1.home.local (192.168.1.21): icmp_req=12 ttl=128 time=5.95 ms
64 bytes from ms1.home.local (192.168.1.21): icmp_req=13 ttl=128 time=6.26 ms
64 bytes from ms1.home.local (192.168.1.21): icmp_req=14 ttl=128 time=5.18 ms
64 bytes from ms1.home.local (192.168.1.21): icmp_req=15 ttl=128 time=5.54 ms
64 bytes from ms1.home.local (192.168.1.21): icmp_req=16 ttl=128 time=4.31 ms
64 bytes from ms1.home.local (192.168.1.21): icmp_req=17 ttl=128 time=3.92 ms
64 bytes from ms1.home.local (192.168.1.21): icmp_req=18 ttl=128 time=5.62 ms
64 bytes from ms1.home.local (192.168.1.21): icmp_req=19 ttl=128 time=2.86 ms
64 bytes from ms1.home.local (192.168.1.21): icmp_req=20 ttl=128 time=2.36 ms
^C
--- ms1.home.local ping statistics ---
20 packets transmitted, 20 received, 0% packet loss, time 19031ms
rtt min/avg/max/mdev = 1.131/4.336/6.268/1.462 ms
root@rp1:~#
Regards,
Tim
Hi Rob,Quote:
Originally Posted by robtweed
Playlist is scrollable separate from the main playback panel. Are u not getting any scrollbars or scrolling action when the huge playlist is loaded?
Regards,
Tim
Sorry, Tim, you're right - the Playlist is separately scrollable.
However I am finding that having such a huge playlist loaded into the browser is clobbering the performance of the rest of the page (I'm using Chrome on a Macbook Air) - everything becomes really sluggish
Rob
Thanks Tim
Well I'm getting 0% packet loss on all tests, but when I get the audio glitches, it's at times when the ping time spikes occasionally above 15-20ms. Most of the time the ping time is around 4ms, during which time the sound is just fine as you'd expect.
The servers upstairs are connected through an ethernet powerline extender, so I guess that might be a culprit for the occasional long round trips. The Mac Mini does nothing else but act as a music server, so there shouldn't be any problem there. I can only otherwise assume there's other network traffic causing some occasional congestion.
BTW what's your recommended MPD buffer settings (I can't remember what the original settings were)
Rob
Hi Rob,Quote:
Originally Posted by robtweed
The sluggish performance is due to the design of the Playlist loader in Moode. It reads the entire Playlist into the Browsers memory space. This is ok 99% of the time since typical Playlist is not too large.
I like your suggestion for an option to "turn off the Playlist [loader]". This would effectively solve the performance issue. The Playlist would still exist on the server (Pi) and random play would still work from an entire NAS or USB source.
I'll have to play around with this a bit and see what happens :-)
Regards,
Tim
Hi Rob,Quote:
Originally Posted by robtweed
The result of the ping test and the presence of Powerline adapters strongly suggests the bottleneck is the Powerline adapters.
Default MPD settings:
- Audio buffer size (KB) 2048
- Buffer fill before play 20%
Regards,
Tim