Minor changes to ViMusic Japanese localization, and is Brotli suitable for streaming?

Hello, I'm incompetent.

The repository name was hard to understand as is, so I added "ja" at the end. It's a hassle, so the old repository remains as is. I'm sorry that I tried to fork directly from Android Studio and didn't understand Git Push well, so it didn't end up being forked (T_T)

It's a hassle, so I'll write the changes here.

Settings - Changed "外見" (Appearance) to "外観" (Appearance)
Parameters - Changed the gl parameter related to region to JP, which will display Japanese songs in Quick Picks.

Why does nothing appear when I set hl to ja in the parameter settings (´・ω・｀)
If I search, it appears, so video acquisition itself is OK.

However, it seems that acquisition from artists is not working, and it didn't work when I tried with other languages, so is this simply a restriction on the Innertube API? I'm not very knowledgeable, so it was a bit tough for me.
But, I'm reasonably satisfied with the current situation, so I think it's fine as it is.

A good point about this app is that it caches songs once acquired, which is very helpful for saving data.
In terms of song coverage, it handles a lot of international music, but since I love music, I can't stop using NextCloud, especially when including music I've digitized from old CDs and records. I wish I could strengthen NextCloud's music playback more, but it seems quite difficult (´・ω・｀)

Since the NextCloud app is also open-sourced, if I modify it a lot, maybe it's possible...!?

ViMusic seems to be performing compression with Brotli, so if both the server and app support Brotli, will streaming become super strong?

The answer was on Wikipedia.

https://ja.wikipedia.org/wiki/Brotli
>This involved rewriting parts of the encoder, adding improvements such as increased compression ratio, faster encoder/decoder, improved streaming API, and adjustable compression quality levels. Additionally, this new version also improved cross-platform compatibility and reduced memory usage.

Hmm, it seems there's a lot of value in incorporating Brotli for strengthening streaming.

Also, why does moving the playback bar in the NextCloud app not work, but it works in CloudBeats...?

And then there's the UI...

I really like ViMusic's UI, so if I could load NextCloud with it, it would be amazing.
Among the playback apps I've used in the past, I like it the most.

Apple Music -> Various displays are noisy, and the standard 2-column display for songs on my page is quite hard to see, making it troublesome to browse old music.

YouTube Music (Original) -> The otaku-ish color scheme is good, but the song search results are hard to see.

I don't know about Spotify because I don't like its sound quality, so I only tried it at first and haven't used it since.
I especially feel that the sound resolution is low. In that regard, Apple Music, perhaps thanks to its long history of handling music, felt like it had relatively good sound quality, so I used it before.

There are other free music software like AIMP, but they're too noisy with too many features packed in.
In contrast, I feel that ViMusic's UI is the best, being simple yet not losing convenience.

So, thank you, although the conversation is all over the place, if I get motivated, I'd like to make the NextCloud app itself specialized for playback.
I'm doing too many things in parallel, so I don't know what's what... Is it like my room...? Hey!

End.

And then there's the UI...

Related Posts