Agreed and I have failed many times. The last time I tried doing it from scratch I saved all my inputs from Step 3 until 12 in a .txt so I could go back and double check. When I reviewed all the lines of recipe 1.9 were in the file. I looked for errors in the feedback from the commands and the only time I found an issues was in Step 10. I had to run "
echo "/var/local/moode.sqsh /var/www squashfs ro,defaults 0 0" >>/etc/fstab. I ran justecho "/var/local/moode.sqsh /var/www squashfs ro,defaults 0 0". So I then typed in both lines and it seemed to carry on.
As someone with zero experience I knew this was going to be an uphill battle, but what the hell. Gotta keep on truckin'
Thanks
Running Rpi 3 with MoOde beta9. With BT initialized and configured on beta9 and paired to my MotoG5 as the source I am able to send music from phone through BT to my analogue speakers. The issue I am having is the sound is choppy. Consistently the sound cuts out every 4 seconds and then carries on for another 4 seconds. Is this most likely due to my environment or my MoOde install / config?
If you’re using wifi and BT, that’s the most likely cause - they share antenna and attenuator and if using both will be constantly be swapping back and forth between the two, as well as from transmit to receive. They can coexist, but if you have other BT devices in range, the constant scanning/discovering process can be very wireless-disruptive. Turn off any BT you’re not actively using.
There I sn’t much infrastructure between the BT device and the player - check usual things like metal cases, noisy power supplies, routers, fluoro lights (including low-energy bulbs).
So much wireless on the 2.4GHz band, but BT does spread-spectrum jumping about. Maybe push your home wifi up to a higher frequency (ch 9, for example) and doing a scan of what is around may help? The worst culprits for wireless interference are those tasks that try and check status - ‘are you there?’ ‘Are YOU there?’ ‘yes, I’m here, whatcha doin?’ ‘Just hangin... whatchoo doin?’ ‘Nada...’ ‘cool...’ ‘whatcha doin now?’ ‘Same as’... 🙂
In theory, the maximum bitrate is 2.1Mbit/sec. if you are pushing high-bitrate source, it might not cope, so be aware of big FLACs.
In my experience BT is great for exchanging bizcards, swapping text files and printing.
Without knowing anything about your environment it’s pretty hard to give a diagnosis. Try turning stuff off and moving stuff around.
There I sn’t much infrastructure between the BT device and the player - check usual things like metal cases, noisy power supplies, routers, fluoro lights (including low-energy bulbs).
So much wireless on the 2.4GHz band, but BT does spread-spectrum jumping about. Maybe push your home wifi up to a higher frequency (ch 9, for example) and doing a scan of what is around may help? The worst culprits for wireless interference are those tasks that try and check status - ‘are you there?’ ‘Are YOU there?’ ‘yes, I’m here, whatcha doin?’ ‘Just hangin... whatchoo doin?’ ‘Nada...’ ‘cool...’ ‘whatcha doin now?’ ‘Same as’... 🙂
In theory, the maximum bitrate is 2.1Mbit/sec. if you are pushing high-bitrate source, it might not cope, so be aware of big FLACs.
In my experience BT is great for exchanging bizcards, swapping text files and printing.
Without knowing anything about your environment it’s pretty hard to give a diagnosis. Try turning stuff off and moving stuff around.
So how is that a lot easier than Ctrl c, right click mouse (anywhere in the putty window)?
I spent 4 hours this Saturday trying to build from scratch using the recipe 1.9. Using terminal on OSX. No success. I give up. Will wait after final version in december to get a pre-built image if someone dare to share it despite the infamous GPL threat. Not a very big deal though. I have moode 3.8.4 installed, rock solid, never crashes, and delivering high quality music. I can live without bluetooth and parametric equalizer.
Remy
how u doin... 🙂
You are correct, running wifi to connect Rpi to the NAS and internet. Other potential BT devices that may conflict my sons Bose wireless headphone, BT mouse on the Mac. Tested with only mp3 podcasts, no flac. I just changed to channel 9 and scanned again but the cutting out problem is still there.
In my case, there is not that great of a use case for BT audio so I am not going to sweat it. Need to spend time working on scratch building recipe. I am going to drop STEP 10 and see if that does the trick.
I've build beta 9 using the 1.9 recipe - all well as running the new player, using the web interface, connecting to NAS and streaming via Airplay.
But the only output that works, is the local output via jack and via hdmi. There is no output via USB or I2S.
Any ideas?
But the only output that works, is the local output via jack and via hdmi. There is no output via USB or I2S.
Any ideas?
I have just managed to connect a Lenovo Yoga tablet to Moode Bluetooth.
Started to play JB-R2 through the Tunein pro app and was suprised to hear music.
This did not last for long as it started to buffer every 30 secs or so.
Switched the stream from 320 kbps MP3 to 64 kbps AAC and it seemed pretty stable.
Then tried BBC 6 vi the BBC Radio iPlayer app and Guy Harvey seemed as normal.
Returned to the 320 MP£ stream on JB-R2 and that seems to have settled down.
I'm using a rpi3b with Ethernet to a Switch and Ethernet to the Router.
Distance between Pi and Tablet is 3/4 metres.
I had no idea about the GPL threat. I had to go back through the 12344533 pages and find it. I guess Volumio and Rune are being nasty in protecting their MPD.
I installed both and they were terrible, Rune especially bad and clunky. I hope the've gotten better, but Arch Linux does not take advantage of the Arm 32-bit floating point like Raspian does.
Anyway, PM me and I'll shoot you my image....ahem...possibly. 😉
I guess it's too much to reverse engineer an MPD.
OK i decided to give it a last try after reading through a few tips posted previously and this time i managed to have a working image 😀. Bluetooth working well so far. Establishing the first connection is a trial and error thing: initialize the moode bluetooth, restart moode, connect, restart the cell phone. Once you connect for the first time, you will have no problem connecting subsequently. Once you are bluetooth connected, moode will stop playing the radio or whatever it was playing and from the android phone you can play music, youtube, podcast, all will be streamed to moode using BT. Quite stable so far and the delay is hardly noticeable.
Remy
Attachments
Because terminal is easier to use than putty. ssh is native to Mac, Terminal is a native Mac OS utility. Just as with Linux machines.
Windows has its slashes all screwed up, among other things.
It wasn’t a Windows vs Mac thing, it was a statement of fact, to someone that clearly has both windows and Mac machines at his disposal.
I started off with PCs using DOS and eventually Windows 1.0 onward, and it has formed the bulk of my income over more than 40 years. I mostly worked at the OS level integrating diverse server platforms in their hundreds and thousands.
There’s a very good reason I don’t reach for a Windows PC, if I can avoid it, although there’s usually a few servers hanging around the house.
For internet work, programming, server control, networking, Mac is superior, unless you are using windows technologies, which I don’t.
And after all that you didn’t answer the question. BTW the DOS I started with was years before PCs were ever invented......
Hi,
Beta10 code has been finished for about a week now and I'll probably upload it next week, hopefully with an adapted version of Koda's wonderful automated moOde image builder 🙂 Then I can concentrate on SL's NewUI.
Goal is that Beta10 + Image Builder + NewUI becomes moOde 4.0 final release. Something like that.
-Tim
Last edited:
Sweet.
I was impressed by Koda's first cut; I'm convinced a supported version of this image builder will go a long way toward putting moOde into the hands of folks who just want to enjoy the music.
Regards,
Kent