1.2.0 Feedback Thread

gcrk

Hi everyone!

We just released Funkwhale 1.2.0-rc1 yesterday. Its the first release candidate, which means it contains all the features and we wont do major changes until the final release of version 1.2.0. This phase is mainly intended for bugfixing and translations. More information are available in our blog: https://blog.funkwhale.audio/funkwhale-120-rc-release.html

How does 1.2.0 work for you? Do you experience any bugs, issues, problems? Let us know!

LinusCDE

Hi,

EDIT: As stated in the reply, this seemed to by my fault.

just updated to it. After the update the language changed to english and I didn't really mind. When checking out the buttons in the navbar (since one got remove as far as I can tell) and the selected language was actually still German (="Deutsch"). I tried a bit with changing the selected language back and forth (also others) but it seems to be always english now matter what.

As you can see in the screenshot, the language is still in english even though german is selected.

[upl-image-preview url=https://forum.funkwhale.audio/assets/files/2021-12-18/1639861625-521678-grafik.png]

This is in chromium, but also tested it in firefox with the same result (the maybe odd look is just the chromiums app + a small userscript I made which adds floating back/forward nav buttons and style the main navbar (the colored titlebar is a kde color theme override rule).

Just read the notes and the overall release seems really cool. I'm currently trying to get rid of spotify (which will probably happen only slowly) by using it as a drop-in replacement where I had the app on my desktop. The new arm docker support is also greatly appreciated.

1 Hour later: Realized I forgot to rebuild the docker containers. If the languages are dependant on the backend (changed nginx config, or something else other than simply serving static files in the same manner as in 1.1.4) I might have fucked this up.

I really need to migrate to the new docker setup now that arm is supported. Will probably do so in the next couple of days. Also won't miss that building python deps (pip) took about 15 minutes on a fairly fast arm64 machine (not a rpi or rockchip). Also wont need to rebuild the frontend manually and can probably add a label to make the setup autoupdate with watchtower as nearly everything I selfhost does. :+1:

LinusCDE

Yeah that language issue got resolved when switching to the official images and using the frontend shipped with the container. Just need to figure out why my Music isn't playing now, but this isn't the first time, so should be not that difficult to fix.

LinusCDE

Is there any command to upgrade the database? I get this error when attempting to play any song: https://haste.cosmos-ink.net/onigawojip.log

Using the funkwhale/funkwhale:1.2.0-rc1 (arm64) image with the recommended docker-compose.yml (used this config previously already).

LinusCDE

Found that solution. First checked for the django interface whether it shows anything (never used django, only a bit flask). Then searched for how to migrate a django app and found the migrate command (thanks for keeping me save by preventing makemigrations).

python manage.py migrate did the trick:
[upl-image-preview url=https://forum.funkwhale.audio/assets/files/2021-12-18/1639871010-194786-grafik.png]

Would guess that since the rc isn't strickly a release and still displays as 1.1.4 it didn't trigger it automatically. Works now like a charm!

LinusCDE

One thing I noticed is that the player at some time starts to randomly show the "loading progress bar" while just playing. Sometimes controls can bring it back (restart the song) and I also got one time where two songs played at once and only one was controllable.

gcrk

@LinusCDE So it seems most of your problems are already solved. We have the update process documented, I just did not linked it since its a prerelease 🙂 https://docs.funkwhale.audio/admin/upgrading.html

LinusCDE One thing I noticed is that the player at some time starts to randomly show the "loading progress bar" while just playing. Sometimes controls can bring it back (restart the song) and I also got one time where two songs played at once and only one was controllable.

Those two things seems to be valid bug reports, we have problems with parallel playing tracks for some time now. Maybe @JuniorJPDJ knows something? For the loading bar I'd appreciate some logs/a way to reproduce it.

LinusCDE

It's pretty hard to reproduce, but got it now again. Seems pretty random, and the js console logs don't show anything interesting.

Edit: The only common thing, seems that if it bugs, it will do so fairly often until the entire page gets reloaded (which then is kinda chance again). On the other hand if it works, the player works flawless for hours. So maybe some reference problem on initialization??

AMoonRabbit

One thing I am not sure about is the About page, to me it feels redundant having to click "About this Pod" and then click "About this Pod"/Learn More to actually get to the Pod's about page. For logged in users that is, but also the box on the left is also somewhat redundant when logged in so I guess it'd be good for logged in users to skip this screen when going to the about?

[upl-image-preview url=https://forum.funkwhale.audio/assets/files/2021-12-22/1640209832-282137-image.png]

I am loving the changes to the profile menu at the top, and some of the other changes too.