https://volumio.org/forum/equalizer-t45-10.html
Similar to that ^^^ .
1. You need the ALSAEQUAL package or build it from source.
2. /etc/asound.conf must have the ALSAEQUAL plugins and controls.
3. MPD must know to call equal.... Either by edit /etc/mpd.conf or by making ALSAEQUAL the default sound device.
Similar to that ^^^ .
1. You need the ALSAEQUAL package or build it from source.
2. /etc/asound.conf must have the ALSAEQUAL plugins and controls.
3. MPD must know to call equal.... Either by edit /etc/mpd.conf or by making ALSAEQUAL the default sound device.
Just received a KALI re-clocker and a PIANO 2.1 DAC to go with it. Works perfectly and sounds very nice with the "IQaudio PI-DAC" settings.
The only little drawback is that it tells me that it is using the Burr Brown PCM5122 running at 24 bit 192 kHz. The PIANO2.1 has two PCM5142's which apparently support 32bit / 384 kHz. Is there a setting that can handle the full potential of this board ? Thanks ;-)
edit
I think I have the answer
http://www.diyaudio.com/forums/pc-based/271811-moode-audio-player-raspberry-pi-542.html#post4905612
edit 2 the proposition "IQAudio Pro" doesn't work for me.
The only little drawback is that it tells me that it is using the Burr Brown PCM5122 running at 24 bit 192 kHz. The PIANO2.1 has two PCM5142's which apparently support 32bit / 384 kHz. Is there a setting that can handle the full potential of this board ? Thanks ;-)
edit
I think I have the answer
http://www.diyaudio.com/forums/pc-based/271811-moode-audio-player-raspberry-pi-542.html#post4905612
edit 2 the proposition "IQAudio Pro" doesn't work for me.
Last edited:
Congrats on releasing 3.0 !
I use Advanced Kernel, CPU governor=performance, MPD scheduler policy=FIFO
Sound output is pretty nice.
One thing I noticed is about "View status of database update." link at DLNA server config section.
By unknown reason, the URL is incomplete. it says "http://:8200"
html code is
<a id="dlnasvc-link" href="http://:8200" target="_blank">View status </a>
Hiroyuki
I use Advanced Kernel, CPU governor=performance, MPD scheduler policy=FIFO
Sound output is pretty nice.
One thing I noticed is about "View status of database update." link at DLNA server config section.
By unknown reason, the URL is incomplete. it says "http://:8200"
html code is
<a id="dlnasvc-link" href="http://:8200" target="_blank">View status </a>
Hiroyuki
The issue you are seeing is not a Moode issue but an issue with mDNS/Bonjour/Avahi - you are changing devices quicker than it is propagating the changes.
Give your devices different names; leaving them all set to 'moode' is always going to be problematic.
Your NAS is using outdated security protocols for samba. Can you update it to a more modern version, one that uses ntlmssp? That is the default for nearly all up-to-date OSs
I know that doesn't answer your question about moode saving your options, but it's another approach at a fix.
What NAS are you using?
Hi sergbug,
normally, your router should have an option like 'always assgin device X to the same ip' That would clear things, I guess.
Rüdiger
normally, your router should have an option like 'always assgin device X to the same ip' That would clear things, I guess.
Rüdiger
Last edited:
Yes! it probably 100% bonjour, i will change and see. Thanks!
Mostly i use only one at a time, but it is enough to mix devices for a moment to make problems for bonjour.
but that do nothing with "moode.local" problem.
i tested in 4 different locations. and it not always work everywhere ((
different LAN configs influence this i guess. but what exactly?
in case onboard Pi Wi-fi-AP is disabled, moode.local doesnt work and router password is forgotten, configuring device becomes quite a not a 2second job...
my router ASUS rtn-66U doesnt have it (
but it behaves like that most of the time, until... (i'll check bounjour and device name issue)
the talk about IP changes started from webGUI problem.
on iphone 5s with HomeScreenAPP everything is fine.
but if i go directly form safari i always cant get to the end of song list.
Another side of moode system SQ wise
optimisations...
on linux x86 system (quite the same thing with windows server 2012 phil optimized) it is easy hearable that:
1) Interruption priorities changes sound a bit
2) rearranging quad core cpu cores between apps to "isolate" OS from player gives effect
3) very strong influence (but system dependable) is caused by different system timers HPET/TSC etc
4) on x86 boards there are always spread spectrum modulator, controlled form bios settings. and it can do very good job for sound or opposite )) system dependable too ))
is it possible to do same optimisations with moode and Pi3? or maybe they are already done?
on point 3) it is clear that HPET is the hardware timer, so there are no HPET on Pi, but may be there are some different "clever" things for Pi?
optimisations...
on linux x86 system (quite the same thing with windows server 2012 phil optimized) it is easy hearable that:
1) Interruption priorities changes sound a bit
2) rearranging quad core cpu cores between apps to "isolate" OS from player gives effect
3) very strong influence (but system dependable) is caused by different system timers HPET/TSC etc
4) on x86 boards there are always spread spectrum modulator, controlled form bios settings. and it can do very good job for sound or opposite )) system dependable too ))
is it possible to do same optimisations with moode and Pi3? or maybe they are already done?
on point 3) it is clear that HPET is the hardware timer, so there are no HPET on Pi, but may be there are some different "clever" things for Pi?
Last edited:
my router ASUS rtn-66U doesnt have it (
but it behaves like that most of the time, until... (i'll check bounjour and device name issue)
the talk about IP changes started from webGUI problem.
on iphone 5s with HomeScreenAPP everything is fine.
but if i go directly form safari i always cant get to the end of song list.
Hi,
I have RT-N66U and if you open the LAN, DHCP Server page there is a setting titled "Manual assignment". Enable this then enter MAC address and corresponding IP address for your devices.
Or you could just assign Static IP address in Moode Network config screen.
-Tim
Hi,
You could experiment with #2 in Moode 3.0 by editing /lib/systemd/system/mpd.service and trying different settings for CPUAffinity. This only applies to Pi-2B/3B (multi-core)
After making changes to this file run the cmd below then restart MPD.
systemctl daemon-reload
As for #1, IRQ reassignment can be done but I have no experience with it and from what I read it can easily produce an unstable system.
-Tim
yes i know it, thanks, Tim.
my motivation on that issue is not to get things done right only in my exactly house, i can deal with that.
the real task, i think, is to manage LAN by moodeOS in the way, so every not technical person can do it in case of router or home ISP change etc
so if "moode.local" will work in 100% cases, and webGui in on most devices, everybody can then be happy with DHCP without any router settings, knowing IP protocol etc
Zootalaws,
I woke up this morning and gave myself a dope-slap. You probably know most of this already; I just want to establish I'm capable of thinking once I have my coffee 🙂
1) a hostname in the .local pseudodomain will not be resolved simply because I change DNS servers. mDNS is a separate service to begin with and .local is just a clever hack to get to it. Android includes libraries which allow one to resolve mDNS queries (and there are Android apps which use them; see below) but Android doesn't use them when an app like any of our web browsers asks for it to resolve a hostname 😡
2. changing DNS servers won't fix the underlying problem that Android doesn't use the information provided by most DHCP servers via option 15-Domain Name and option 119-Domain Search. Android just passes the naked hostname like "moode" to the server and you know what happens next.
3. mDNS-aware Android apps: I don't know of any mainline web browser for Android which is mDNS aware. However, there are a number of Android zeroconf browsers. Two I've used are Bonjour Browser and Zeroconf Browser. They tell me more than I usually want to know about services being offered on my LAN but they also tell me the IPs of my Moode players. Not the only way to play---I often use a traditional local network scanner like Fing---but the zeroconf browsers prove the underlying Android libraries work.
It's been 8 years since the first release of Android and Google remains unresponsive to the deafening outcry of users to make Android play well with Apple and Microsoft technology. The forum threads keep getting longer and longer. You'd think by now a Chrome-alternative like Firefox or Opera would fill the void. Opera, for example, now has its own VPN capability built-in, which shows they're capable of bypassing Google's DNS; one wouldn't think mDNS is a big step for them.
Regards,
Kent
Last edited:
Hi,
Not being able to resolve http: //moode or http: //moode.local is a network or client issue that is external to Moode or moodeOS.
-Tim
Last edited:
had the same issue with Safari... Firefox solved the problem with http:moode.local .. renaming multiple devices with moode running (hostname in the moode GUI) would be a good idea I'd guess
sadly ((
but can you guess what local network settings, router settings or browser etc can affect this? in case it can be fixed once it will be a good compromise for setting up moodeOS for non technical person. for my Mom for example )) much easier than doing static IP and wait for problem to begin later after ISP technical guy visit ))