build git, add username/pass/token/quality to mpd.conf in a plugin block:
input {
plugin "tidal"
token ""
username ""
password ""
audioquality "LOSSLESS"
}
I wrote a little python script that converts a tidal album to a m3u for now as no ui.
the m3u just has like :
tidal://track/16909094
tidal://track/16909095
tidal://track/16909096
in it.
and it just works, aside from a little issue as it loads the next track, but not sure if that is just on my network, still testing
I've just upgraded to v4 and so pleased that I did - many thanks for your continued endeavours Tim and for making this process easy.
One minor thing, I've tried Moode's Bluetooth configuration utility several times now but still haven’t succeeded in pairing my bluetooth dongle with anything. Moode seems be able to 'see' my bluetooth USB dongle and if, via the ssh console, I use the ‘lsusb’ command its listed as: ‘Bus 001 Device 005: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)’. Similarly, the android phone I’m trying to pair displays ‘Moode Bluetooth’, but when I click on this I’m asked to provide a pin, and this is my problem: I’ve tried all the default pin combinations I can think of (‘0000’, ’1111’ and ‘1234’ etc) - nothing works and as a result the pairing fails.
I’ve stumbled upon a suggestion that the pin could be set using the ‘bluetooth-agent’ command but have got it into my head this doesn’t work on Stretch Lite. Please, can anyone help..
One minor thing, I've tried Moode's Bluetooth configuration utility several times now but still haven’t succeeded in pairing my bluetooth dongle with anything. Moode seems be able to 'see' my bluetooth USB dongle and if, via the ssh console, I use the ‘lsusb’ command its listed as: ‘Bus 001 Device 005: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)’. Similarly, the android phone I’m trying to pair displays ‘Moode Bluetooth’, but when I click on this I’m asked to provide a pin, and this is my problem: I’ve tried all the default pin combinations I can think of (‘0000’, ’1111’ and ‘1234’ etc) - nothing works and as a result the pairing fails.
I’ve stumbled upon a suggestion that the pin could be set using the ‘bluetooth-agent’ command but have got it into my head this doesn’t work on Stretch Lite. Please, can anyone help..
Last edited:
You can't.
Hmmm i think you have to start from scratch ... it looks like a corrupt SD.
File use by script is corrupt (content is not what we must have) and apt db looks locked !
The message should never arrive at this case is really weird because our script was built to avoid this !!!
Regards
Last edited:
next problem.
airplay. Enabled, given a name, moode says that it is running but there is no receiver available. I've got a few older versions of moode running where it works fine!
Are there logs for shairport somewhere that I can find to see what is going wrong?
Thanks for the quick help!
airplay. Enabled, given a name, moode says that it is running but there is no receiver available. I've got a few older versions of moode running where it works fine!
Are there logs for shairport somewhere that I can find to see what is going wrong?
Thanks for the quick help!
build git, add username/pass/token/quality to mpd.conf in a plugin block:
input {
plugin "tidal"
token ""
username ""
password ""
audioquality "LOSSLESS"
}
I wrote a little python script that converts a tidal album to a m3u for now as no ui.
the m3u just has like :
tidal://track/16909094
tidal://track/16909095
tidal://track/16909096
in it.
and it just works, aside from a little issue as it loads the next track, but not sure if that is just on my network, still testing
Ok, so its basically an authentication plugin for tidal:// URI's which is cool but how does one browse ones Tidal albums?
-Tim
Hi,
From the Bluetooth config screen
BlueMoode version 1.3
1) SCAN for devices.
First, put your device in discovery mode and verify that it discovers Moode Bluetooth. You may have to turn Bluetooth off/on on your device to accomplish this. The default duration of the scan is 20 seconds.
2) Connect your device to Moode Bluetooth. You may have to initiate the connection as soon as your device is discovered and appears in the SCAN results. After a successful connection the pairing is stored.
No PIN is required because the SCAN automatically trusts every BT device it discovers.
-Tim
Hi,
To verify that shairtport-sync is actually running use the cmd below
pgrep -l shairport-sync
You could also try turning on moOde debug logging in System config and then examine /var/log/moode.log for anything suspicious.
-Tim
I'm back! Ok, I did that. Started from scratch. Now it gets to trying to install rotary encoder driver and stops:
I've rebooted a couple times but it always shows the same thing.
Code:
////////////////////////////////////////////////////////////////
//
// STEP 5 - Install Rotary encoder driver
//
////////////////////////////////////////////////////////////////
** Compile WiringPi
wiringPi Build script
=====================
WiringPi Library
[UnInstall]
make: Warning: File 'libwiringPi.so.2.44' has modification time 7.2 s in the future
make: Nothing to be done for 'all'.
make: warning: Clock skew detected. Your build may be incomplete.
make: Warning: File 'libwiringPi.so.2.44' has modification time 7.1 s in the future
[Install Headers]
[Install Dynamic Lib]
ldconfig: File /usr/local/lib/libwiringPi.so.2.44 is empty, not checked.
ldconfig: File /usr/lib/libwiringPi.so is empty, not checked.
make: warning: Clock skew detected. Your build may be incomplete.
WiringPi Devices Library
[UnInstall]
ldconfig: File /usr/local/lib/libwiringPi.so.2.44 is empty, not checked.
ldconfig: File /usr/lib/libwiringPi.so is empty, not checked.
[Compile] ds1302.c
[Compile] maxdetect.c
[Compile] gertboard.c
[Compile] piNes.c
[Compile] piFace.c
[Compile] lcd128x64.c
[Compile] lcd.c
[Compile] scrollPhat.c
[Compile] piGlow.c
[Link (Dynamic)]
[Install Headers]
[Install Dynamic Lib]
ldconfig: File /usr/local/lib/libwiringPi.so.2.44 is empty, not checked.
ldconfig: File /usr/lib/libwiringPi.so is empty, not checked.
GPIO Utility
[Compile] gpio.c
[Compile] readall.c
[Compile] pins.c
[Link]
/usr/lib/gcc/arm-linux-gnueabihf/6/../../../libwiringPi.so: file not recognized: File truncated
collect2: error: ld returned 1 exit status
Makefile:55: recipe for target 'gpio' failed
make: *** [gpio] Error 1
** Compile failed
** Error: image build exited
** Error: reboot to resume the build
** Thu 15 Feb 14:32:20 UTC 2018
////////////////////////////////////////////////////////////////
//
// STEP 5 - Install Rotary encoder driver
//
////////////////////////////////////////////////////////////////
** Compile WiringPi
wiringPi Build script
=====================
WiringPi Library
[UnInstall]
make: Nothing to be done for 'all'.
[Install Headers]
[Install Dynamic Lib]
ldconfig: File /usr/local/lib/libwiringPi.so.2.44 is empty, not checked.
ldconfig: File /usr/lib/libwiringPi.so is empty, not checked.
WiringPi Devices Library
[UnInstall]
ldconfig: File /usr/local/lib/libwiringPi.so.2.44 is empty, not checked.
ldconfig: File /usr/lib/libwiringPi.so is empty, not checked.
make: Nothing to be done for 'all'.
[Install Headers]
[Install Dynamic Lib]
ldconfig: File /usr/local/lib/libwiringPi.so.2.44 is empty, not checked.
ldconfig: File /usr/lib/libwiringPi.so is empty, not checked.
GPIO Utility
[Link]
/usr/lib/gcc/arm-linux-gnueabihf/6/../../../libwiringPi.so: file not recognized: File truncated
collect2: error: ld returned 1 exit status
Makefile:55: recipe for target 'gpio' failed
make: *** [gpio] Error 1
** Compile failed
** Error: image build exited
** Error: reboot to resume the build
** Thu 15 Feb 14:39:28 UTC 2018
////////////////////////////////////////////////////////////////
//
// STEP 5 - Install Rotary encoder driver
//
////////////////////////////////////////////////////////////////
** Compile WiringPi
wiringPi Build script
=====================
WiringPi Library
[UnInstall]
make: Nothing to be done for 'all'.
[Install Headers]
[Install Dynamic Lib]
ldconfig: File /usr/local/lib/libwiringPi.so.2.44 is empty, not checked.
ldconfig: File /usr/lib/libwiringPi.so is empty, not checked.
WiringPi Devices Library
[UnInstall]
ldconfig: File /usr/local/lib/libwiringPi.so.2.44 is empty, not checked.
ldconfig: File /usr/lib/libwiringPi.so is empty, not checked.
make: Nothing to be done for 'all'.
[Install Headers]
[Install Dynamic Lib]
ldconfig: File /usr/local/lib/libwiringPi.so.2.44 is empty, not checked.
ldconfig: File /usr/lib/libwiringPi.so is empty, not checked.
GPIO Utility
[Link]
/usr/lib/gcc/arm-linux-gnueabihf/6/../../../libwiringPi.so: file not recognized: File truncated
collect2: error: ld returned 1 exit status
Makefile:55: recipe for target 'gpio' failed
make: *** [gpio] Error 1
** Compile failed
** Error: image build exited
** Error: reboot to resume the buildI've rebooted a couple times but it always shows the same thing.
That would need a front end, I just have a cron job that pulls my favourites into .m3u files.
I can share that python code if it's useful.
Ok it does appear. But I think I have larger problems. It appears to just be rebooting after some random time.. bit wierd. Its doing some avahi kung foo then boom... straight into booting.. 
Code:
Feb 15 15:41:58 moodeKitchen systemd[1]: apt-daily-upgrade.timer: Adding 39min 33.099707s random time.
Feb 15 15:41:58 moodeKitchen systemd[1]: Started Daily apt upgrade and clean activities.
Feb 15 15:41:58 moodeKitchen systemd[1]: Started Clean PHP session files every 30 mins.
Feb 15 15:41:58 moodeKitchen systemd[1]: Reached target Timers.
Feb 15 15:41:58 moodeKitchen systemd[1]: Started Raise network interfaces.
Feb 15 15:41:58 moodeKitchen systemd[1]: Started Save/Restore Sound Card State.
Feb 15 15:41:58 moodeKitchen dhcpcd[363]: dev: loaded udev
Feb 15 15:41:58 moodeKitchen avahi-daemon[361]: Found user 'avahi' (UID 108) and group 'avahi' (GID 112).
Feb 15 15:41:58 moodeKitchen avahi-daemon[361]: Successfully dropped root privileges.
Feb 15 15:41:58 moodeKitchen avahi-daemon[361]: avahi-daemon 0.6.32 starting up.
Feb 15 15:41:58 moodeKitchen avahi-daemon[361]: Successfully called chroot().
Feb 15 15:41:58 moodeKitchen avahi-daemon[361]: Successfully dropped remaining capabilities.
Feb 15 15:41:58 moodeKitchen avahi-daemon[361]: Loading service file /services/udisks.service.
Feb 15 15:41:58 moodeKitchen kernel: [ 0.000000] Booting Linux on physical CPU 0x0
Feb 15 15:41:58 moodeKitchen kernel: [ 0.000000] Linux version 4.9.79-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611) ) #1091 SMP Tue Feb 6 13:18:45 GMT 2018
Feb 15 15:41:58 moodeKitchen kernel: [ 0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d
Feb 15 15:41:58 moodeKitchen kernel: [ 0.000000] CPU: div instructions available: patching division code
Hi Tim,
I got the same dongle as he does and in the config screen I cannot run any of the commands. It looks like the "RUN" button is inactive.
I checked if the dongle is detected and it looks fine:
Code:
root@moode:/home/pi# lsusb
Bus 001 Device 005: ID 148f:5370 Ralink Technology, Corp. RT5370 Wireless Adapter
Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubalso, dmesg shows this:
Code:
[ 11.072574] Bluetooth: Core ver 2.22
[ 11.072700] NET: Registered protocol family 31
[ 11.072710] Bluetooth: HCI device and connection manager initialized
[ 11.072739] Bluetooth: HCI socket layer initialized
[ 11.072761] Bluetooth: L2CAP socket layer initialized
[ 11.072820] Bluetooth: SCO socket layer initialized
[ 11.151964] usbcore: registered new interface driver btusbWhat else should I check to make sure I have bluetooth working?
[edited:***STOP THE PRESSES*** A new moOde 4.0 I built just last night has now disappeared while I was doing something else.
***]
@streamerguy
So 4.0 was still freezing with
1) a fresh install,
2) no software modifications (I ask this because I see in your previous install's moode.log dump that, in addition to trying the unstable kernel, you had bumped up to mpd-0.20.17),
3) wired ethernet,
4) a USB DAC,
5) UPnP renderer enabled?
This configuration has been working fine for me, albeit with a white-label USB DAC and BubbleUPnP instead of JRiver.
There's no special driver loaded for your DAC, right?
For the sake of completeness, what happens if you try running the same install but without the external DAC, i.e., with mpd configured to the on-board audio device?
Regards,
Kent
Last edited:
@keithg
It took me a minute to realize you've pasted the STEP 5 output from successive retries.
Surely this listing starts with the output from your second try because it says the build script found that some files were already compiled and a library (.so) file had already been created (albeit with a future time stamp, probably an artifact of the lack of a hardware clock on the RPi). The build can't proceed unless things are cleaned up.
The problem is your output doesn't show why the build failed on the first pass so I'm hesitant to suggest a hack at this point. However, if you can ssh into your RPi and find the directory in which wiringPi is being built (I suspect it is /home/pi/mosbuild/wiringPi-96344ff but read the relevant portion of mosbuild_worker.sh) then you can try
Code:
./build cleanThe worst that can happen is that it fails again in which case you probably should start again from scratch.
Regards,
Kent
Have you another SD Card. I suspect that your current one has some bad sectors !
Check the following...
In System /Config turn bluetooth on
Audio /config /Renderers set bluetooth on if casting to a speaker
In SEL set MPD output to bluetooth device
Check to see if the run button is active...
Hi all,
If any one other than Kent and Tim were following my queries on Pi0w building I'll just follow up to say it appears to have been a build issue on the Pi0w. Have built it on a Pi3 and the used the build in two Pi0's with no freezes etc.
I'll have another go at running a Pi0w build another day.
Now I just need to figure out all the options.... Happy for now.
F
If any one other than Kent and Tim were following my queries on Pi0w building I'll just follow up to say it appears to have been a build issue on the Pi0w. Have built it on a Pi3 and the used the build in two Pi0's with no freezes etc.
I'll have another go at running a Pi0w build another day.
Now I just need to figure out all the options.... Happy for now.
F