Interesting trick. Not quite what I expected but works well enough with Chrome 63.0.3239.108/Linux Mint 18.2. Can't find an equivalent for Firefox 57.0.1/LM.
Regards,
Kent
On Windows 10 it eliminates the double scroll bars on the browse tab. It also cleans up the scroll bars on the other tabs, like the playlist scroll bar and the scroll bars on the library tab.
Just installed beta 12 on a RPi 3 successfully applying the modified script from Heeboo. No problems at all, the script ran flawlessly. Big thanks to Heeboo and Koda!
@Tim: Using Moode since 2.6 and still impressed by your and all the other contributors work. Re donation: I just wrote an email to you.
+1
The script (subject to internet connection) works perfectly. HeeBoo’s ‘modified’ one-card script is the way to go for nearly every implementation imo.
I am using RoonBridge Tim with Moode.
I managed to install Moode doing the command line steps. Phew that was a journey but I got there with the help on this thread.
If someone can get this far, installing RoonBridge is a walk in the park. It's just 3 commands via ssh:
1. Download the easy installer:
curl -O http://download.roonlabs.com/builds/roonbridge-installer-linuxarmv7hf.sh
2. Make the installer script executable:
chmod +x roonbridge-installer-linuxarmv7hf.sh
3. Run the installer script:
sudo ./roonbridge-installer-linuxarmv7hf.sh
That's all!
But if it can be part of the main install, that's a nice bonus.
Same for me. I was using 3.8.4 with Audirvana up to last week.
Just installed Moode beta 12. I have RoonBridge working fine but Audirvana can't see Moode.
Did you end up solving this?
looks like it's the bootstrap CSS that is the issue, I commented out the rule for line 474 in bootstrap.min.css;
Code:
.tab-content{/* overflow:auto; */}Paul
It hasn't got the 40 pin GPIO connector
This one works a treat for less then 15 bucks (blimey must have been watching too much US tv)
I2S Interface Special HIFI DAC+ Audio Sound Card For Raspberry PI B+/2B | eBay
Set it up as a HiFiBerry DAC+
Thank you for the trick.
it hasn't got the GPIO but it has the I2s connectors.
Isn't it ok to connect to the kali? I used to connect a 9028 card like this and it was working.
But no success with the 9038 card for now.
I don't use MPD but after I disabled volume control in MPD settings and applied that setting, I rebooted and Audirvana finally saw Moode UPnP.
Yay.
hello!
i'm trying to stream audio from a bluetooth device (android phone, windows laptop) to moode audio 4.0
I have a usb bluetooth dongle connected to my Pi2
But i cannot see any bluetooth menu or config in moode ?
My dongle is supported, i can see it on other distribs (like openelec)
thanks
i'm trying to stream audio from a bluetooth device (android phone, windows laptop) to moode audio 4.0
I have a usb bluetooth dongle connected to my Pi2
But i cannot see any bluetooth menu or config in moode ?
My dongle is supported, i can see it on other distribs (like openelec)
thanks
hello!
i'm trying to stream audio from a bluetooth device (android phone, windows laptop) to moode audio 4.0
I have a usb bluetooth dongle connected to my Pi2
But i cannot see any bluetooth menu or config in moode ?
My dongle is supported, i can see it on other distribs (like openelec)
thanks
Menu Configure / Audio ... Scroll Back ... you will find Bluetooth Speaker and Speaker Sharing and under theses Configure Bluetooth and Restart Bluetooth
First enable with setting on Bluetooth Speaker and don’t forget to set it, then go to configure Bluetooth
@Tim EQ is not applied when Airplay?
Pretty sure about this on my moode 4b12.
Measured with external mic and REW, no matter the EQ curve I set, the output is always the same when I airplay..
If i stream a file using airplay it's not being equalized.
I play the same file from moode HDD and it works.
now... It's my fault or can you reproduce it too?
(tip: set -24db EQP bands or cut some frequency in the EQG and you see it quickly if it's being applied)
Pretty sure about this on my moode 4b12.
Measured with external mic and REW, no matter the EQ curve I set, the output is always the same when I airplay..
If i stream a file using airplay it's not being equalized.
I play the same file from moode HDD and it works.
now... It's my fault or can you reproduce it too?
(tip: set -24db EQP bands or cut some frequency in the EQG and you see it quickly if it's being applied)
Hi,
Correct, its because I only coded the MPD outputs to use Crossfeed and the EQ's. It's possible for the other renderers to use the eq's but it would require some coding effort. If you want to try Airplay with an EQ email me and I'll show you what code to change for testing it out
-Tim
I successfully built the moode 4 beta 12 image on a Raspberry Pi 2B using the manual build recipe.
As I don't plan to use Bluetooth, I skipped that part of the build process (Step 4.2).
Also I won't use the local UI, so I skipped the Component 8 - Local UI display step (and Component 9 - Allo Piano 2.1 Firmware step as I don't have that board).
Is it good in this way?
Would it cause any trouble in the future, like when using the in-place update feature?
As I don't plan to use Bluetooth, I skipped that part of the build process (Step 4.2).
Also I won't use the local UI, so I skipped the Component 8 - Local UI display step (and Component 9 - Allo Piano 2.1 Firmware step as I don't have that board).
Is it good in this way?
Would it cause any trouble in the future, like when using the in-place update feature?
Hi @kdan,
I definitely wouldn't skip Bluetooth, its part of the core enhanced network stack that also includes Host AP mode. There is a likelihood that an updated version of bluetooothd and its configs will be part of the next in-place update (to BETA 13).
The optional components can be skipped but there is no guarantee that a future update won't include a part belonging to one or more of them. Generally this is not going to cause any problems.
-Tim
I definitely wouldn't skip Bluetooth, its part of the core enhanced network stack that also includes Host AP mode. There is a likelihood that an updated version of bluetooothd and its configs will be part of the next in-place update (to BETA 13).
The optional components can be skipped but there is no guarantee that a future update won't include a part belonging to one or more of them. Generally this is not going to cause any problems.
-Tim