-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature] Support ARMv6 #179
Comments
Can you try the image tagged as feature-f179b01-bullseye-squeezelite-1.9.8? |
Uhm not quite sure that this will be working, just let me work on it a little more. |
Sorry, can you tell me what does this command output?
|
Sure. On my Pi B+ it outputs: armv61 I just pulled the image and was able to start the container. It seems to work, but i can't test ist completely because i think i have to configure a little bit to hear output through the Hifiberry Amp2. Thanks for your work! |
I am happy to know that this works. Let me know if I can help with the configuration.
This leaves me with two choices:
2a) Add a variable named PREFER_SOURCEFORGE_BINARY, which will run the sourceforge binary, if available. It will generally be the case, apart for the armv6 images The initial obvious choice should be option 1, but I don't like to have to maintain two branches, so I will try to accomodate the situation down the road. |
Oh dear, I'm sorry that i have caused such trouble with my request. For the armv6 version on a Pi B+ with a Hifiberry Amp+ i can confirm that it works. |
Glad to know it works.
If this works I will gladly add a preset for your card for easy configuration |
I also should have fixed the build process (not solution 2 yet), you might want to try the tag |
These modifications are available in branch |
I don't know if it's possible to just configure the container. aplay -l on my unmodified config.txt looks like this: The Hifiberry Amp+ seems not to be present that way. |
Ok, so it's probably ok to leave it as it is :-) |
Hello, I have reviewed the build process and created a distinct workflow for sourceforge versions, which will not include a armv6 version. |
Hello, i will try the new container out next week and report back. To your question from yesterday. I did not change anything else beforehand. I installed a fresh Pi OS, installed docker and pulled the image. And since the Hifiberry did not show up in |
Pulling the image for armv6 with just giof71/squeezelite:latest is working fine. I witness a little bit of stuttering when a stream starts. I already tried different buffer sizes (1024, 4096, 8192), but it had no real effect. In the past i just used a pre-built image called Squeezeplug from Max2Play. I had no stuttering with that setup. Cheers |
Hello @CrimsonAC, glad to hear that the image works... can you post you compose/run file? Thanks |
My docker compose looks like this right now:
I already tried with buffers: And also tried sampling rates out of desparation :) What do you mean by 'similar configurations on other platforms'? I have not done that yet, but i could try soon. |
Sorry, I meant with a different device using architecture arm/v7, arm64, amd64 |
Ok, I've tried a few things now. But the Pi B+ and Pi Zero work flawlessly as well with that aforementioned Max2Play Image. Here are the container logs from the stuttering Pi Zero. They go on and on kinda indefinately. I scrolled down to a point where i guess all initialization work is done and it starts playing the track, since the kind of output repeats itself. Setting default value for SQUEEZELITE_MODE: [ALSA] === END-- Available audio devices === === BEGIN Loading presets === [08:25:40.997986] sendSTAT:171 ms_played: 0 [08:25:41.084120] sendRESP:226 RESP |
Ok not a lot to see from the logs here, apart from this: download this version: https://sourceforge.net/projects/lmsclients/files/squeezelite/linux/squeezelite-1.9.9.1419-armel.tar.gz/download uncompress it and mount the folder to a path (example:
start the container as usual, then do: docker-compose exec squeezelite-hifiberry bash you should be dropped to /app/bin now replace the binary "squeezelite" with the one you just downloaded.
Now make sure the binary is executable. Just execute:
exit the shell (CTRL-D) restart the container, without recreating it (or your changes would be reverted):
See if this changes something! Fingers crossed |
Thanks again for your support. I really appreciate that. Unfortunately, swapping the squeezlite binary inside the container has no positive effect. But that triggered an idea i didn't have before, i do not know why ;-) And it works. No stuttering, noticeable better reaction time to user input. |
Glad to hear that! So do you plan on running squeezelite natively on that board? |
Yeah, i guess i'll have to do that. |
Ok good to hear. |
I used the get-docker.sh script from https://get.docker.com |
And, another thing, maybe more interesting than the prior, has to do with the build process.
that will result in an image named |
Wow, it took about half an hour to build the container on that old Pi. But as i have said, i thought the buffering between LMS and the Squeezelite Player is what causes the issue. So i went over to those additional ALSA parameter with But while i was testing and changing and evaluating, it has gotten way better. In fact the stuttering is now gone. Then i felt quite stupid, because i forgot one of THE IT rules ;-) Sorry for all the hassle, but at least i learned a few things along the way with containers. And your armv6 container can indeed be useful for others, that may have some old Pis lying around. Thank you very much! |
Hello, I'am happy that this works for you now! So the binary worked because you restarted lms... Cheers |
I think you opened the issues yourself after my post in the Discussions section. At least i cannot find a button/option to close it. Cheers |
Thank you so much, all the best for you as well! |
Hello @CrimsonAC , today I have removed some old images with the "-armv6" substring from Docker Hub. You probably already know that the current images (minus the sourceforge version) all support armv5 which should be ok for you. Please tell me if this is the case, otherwise I might rebuild (and leave available) a custom image. Cheers. EDIT: typo, now -> know |
Sorry @CrimsonAC I forgot that in the end you probably did not even need the arm/v6 version. |
That's right. In the end, the little problems i had, have been the LMS itself and not the Pi Zero or your image. |
Would you like to post some photos of your setup? Of course if this is no trouble. |
Originally posted by @CrimsonAC in #175 (comment)
The text was updated successfully, but these errors were encountered: