02-20-2020, 10:16 PM
Any chance the updated librespot would solve the 'pop' noise between each track problem?
Thank you for your donation!
Cloudsmith graciously provides open-source package management and distribution for our project.
|
Upcoming moOde 6.5.0
|
02-20-2020, 11:48 PM
(02-20-2020, 10:16 PM)partytime-excellent Wrote: Any chance the updated librespot would solve the 'pop' noise between each track problem? Seems like a trick question, akin to "when did you stop beating your wife?" I just finished listening to the first dozen tracks in the "#SpotifyTBT: Song of the Year" list. Rpi4B, Khadas Tone Board, moOde 6.4.2. No pops. Regards, Kent 
02-21-2020, 02:20 AM
Did your compile of librespot on arm6 ever finish?
I'm trying on a 0W and it seems to b taking forever on librespot-protocol... At this same spot about 4 hours in on a Pi-1B it just aborted. I'm leaning toward v0.1.1 being an arm7-only release for moOde unless someone comes up with a build recipe that can be run on an arm7 Pi and generate a binary that will also run on arm6. Code: pi@rp2:~/librespot-0.1.1 $ cargo build --release --features alsa-backend
02-21-2020, 04:22 AM
(This post was last modified: 02-21-2020, 04:22 AM by TheOldPresbyope.)
@Tim Curtis
I think it succeeded but I accidentally closed the terminal before I checked that the compile was actually complete. The resulting binary seemed ok. I used readelf -A to check it, for example. One thing though, the binary was smaller by almost 1.5MB than the one in your release. I've just now started a second build from scratch to make sure everything was ok. I also saw that the protocol stuff was taking an inordinate amount of time. I wasted what time I had available this afternoon and evening trying to set up and cross compile on my x86 linux laptop using https://github.com/rust-embedded/cross After weeding out the usual blunders by successive approximation (I never claimed to be a Rustacean!) I ran into a build error I couldn't get past Code: thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: "Cross compilation detected. Use PKG_CONFIG_ALLOW_CROSS=1 to override"', src/libcore/result.rs:1188:5I see lots of posts about this Err value but no actionable answer. Setting the environmental variable in Linux doesn't resolve the error. The cross compile is done in a dynamically started Docker container and I probably need somehow to set the variable inside it. Pity. I was hoping to be able to report a blazing fast build! Maybe armed with what I learned about Rust today I can muddle through a cross compile on an RPi4B. As for the RPi1B, doesn't it seem likely this is an just another memory size issue? When I'm running on the RPi0w, I see up to 60MB of swap being used. Of course using swap will cause the gears to grind even slower. Regards, Kent (02-21-2020, 04:22 AM)TheOldPresbyope Wrote: @Tim Curtis You can always use the crossbuild framework that I sponsored some time ago. I'm currently using to build packages targeted for specific architecture (rpi, rpi2, rpi3) tuning relative compiler parameters, from my laptop. A full build takes (with all packages kernel, mpd, blue-alsa, shairport...) less than 1 hour on a core i7-7700...
02-21-2020, 11:29 AM
@badbat75
Ouch! As soon as I saw your username I remembered I’ve got your posts stored away. They say forgetting things is a sign of old age, but I forget why  Regards, Kent
02-21-2020, 11:33 AM
(02-21-2020, 11:29 AM)TheOldPresbyope Wrote: @badbat75 If you want to use it, download the development branch (I found a bug today on rust build :-) ) Create a file like this in project folder to build stand-alone package: Code: # Build recipe for test packagesI use this to test new version of the packages. Of course it builds also dependant libraries, if you don't want them, strip at the end of the build.
Here you can find your binary for bcm2835 (armv6 for raspberry Pi 1)
strip the usr/lib directory if you don't want overwrite libportaudio files. It has been built in 10 mins on a vm with 2 cores, on my company laptop :-) I forgot the link to my builder: https://github.com/badbat75/bbcrossbuild...evelopment
02-21-2020, 01:06 PM
@Tim Curtis
246m to complete the build of librespot-master-51a634d on an RPi0W. Binary again is 10841412 bytes, compared to 12622936 bytes in moOde 6.4.2. Haven't started building 0.1.1 yet. With a fresh cup of coffee I finally noticed the section "Passing environment variables into the build environment" in the referenced cargo cross document and now have moved on to another missing bit in the process. Haven't fired up @badbat75's environment yet nor took a look at building on RPi4B. IIRC, building moOde directly on the target device is a desideratum for you. Fair enough, but some of us are impatient  Regards, Kent
02-21-2020, 02:22 PM
It's looking like too much work just for old armv6. Those single-core Pi's don't have the horsepower to run moOde 6 very well anyway so I'm leaning toward librespot v0.1.1 for armv7 only.
In any case the real solution for old armv6 is to just get a super nice Pi-3A+ :-) |
|
« Next Oldest | Next Newest »
|
