I’d love any other feedback on this release. The updates to the iOS and Android version is a substantial code to the code base.
@Stephen After a day of using the Android remote, I haven’t noticed any problems. Compared to before, it seems to load sections faster and, overall, the experience is smoother.
I was playing for a few hours yesterday using random view on the album browser.
In-out of a lot of albums, adding tracks to queue.
All seemed very responsive except for when I dig into an artist from the album. The artist page often takes quite a while to load with info, discog Occasionally it would load quickly but generally not.
I haven’t used the iOS/iPad remotes much but haven’t noticed any problem when I did. Can’t say I noticed anything significantly better either, sorry ![]()
The Android clients haven’t made it to the play store, UK.
This seems to be happening on each recent early access release. Can you monitor and resubmit.
For now, the “expected” outcome is it runs at least as well as the current released version or maybe a bit better.
This was mostly to upgrade the code base, but it was significant. Even more so for Android.
I’ll pass this along.
No complaint, I get it, making the transition and keeping the overall quality nearly without noticeable bugs is an achievement ![]()
Hi-
So it took me a half dozen retries on TestFlight to get the new remote. However, I have to say it’s been pretty fast & flawless since I got it. This strikes me as though it must have been a substantial rewrite, and – at least so far – it’s good. On newer iPhone 17 pro, and older 15 pro.
I have no real helpful comments (though I see there are some kinks to work out on iPad rotation), so I just thought I’d start the conversation. I’m sure there will be road bumps, and I’m sure I’ll experience some of them, but I love this emphasis on infrastructure, stability, speed, etc. And things (from my perspective) have been coming at a fairly fast clip. So thank you.
It sounds like the delay is a result of the google play review process or something?
The changeset was nearly 500 files ![]()
A chunk of that was adding a ton of tests. The hope is to reduce the likelihood of regressions in the future.
Probably, but if it gets stuck for a while, from experience it’s normally quicker to withdraw the build and resubmit.
There are a couple of old-time strange behaviors that although not critical, still persist in IOS. I use it as my main remote on different iPads everyday and I can highlight:
- When dealing with albums with a ton of files (hundreds or more), the list keeps scrolling slowly and randomly. Many times after selecting a track, it will jump out of sight, positioning the view somewhere else on the list.
- When fast tapping in a song list, the row will get shaded and will appear periodically while scrolling thru the list.
- Speed: the time between pressing play and start hearing the song. This has improved over lhe last months to an expected state. Whenever a new version is deployed, the first thing I do is to randomly browse thru many albums and quickly start songs. Sometimes it is required to restart the server to get a good response and it has been great at least for 6-8 months. However there are times of the day (specially late at night) that things don’t go that smooth and I can’t imagine what can be the reason (internet, background server tasks, the phase of the moon). I also notice that flac files play faster than mp3. I imagine this is because the ffmpeg decoding. I am talking of millisecinds, but noticeable.
I have something that isn’t in the current EA release that might help with the scrolling. I’ll try and look into the other things as soon as I have a chance.
Some of these, and most likely 3, are partially a reflection of the roon server hardware and performance issues. I notice some issues more when I connect with my old NAS vs other Roon cores I have at home.
I agree performance depends on the hardware base. I have tried several platforms (NAS, mac mini M2, Intel i7 and today a Ryzen 9, 32GB with Rock). Despite the platform, the strange behavior has been constant along the years. as I said, nothing to die for, but you asked… ![]()
Thank you for checking it.
Ah, and now that we are here, just bringing again Search. I thought this was already a commodity until I found Roon. Still very complicated (to me at least). I never find what I request and when it appears it resides on a service, not my library. Having to first search and then filter and then scroll and then touch my nose and look up… is very complicated. This is the -only- thing I don’t like about Roon. Having a fuzzy search like in any other app, musical or not, is one of my best wishes (besides winning the lottery!)
Also in UK like @ged_hickman1 and will revert to downloading .apk’s - still on build 1663 so two versions behind now. With early access it makes it a bit difficult to provide timely feedback when relying on the Play store. It tended to much quicker.
ARC APK won’t load for me over the play store version.
Don’t want to blow it away and have to do all the downloads again, ten times of it being blown away by screwing up is enough ![]()
Yes, been there many a time. And went there again just now
. Flagellation and all that. I stopped keeping ARC downloads a while ago, and can reset my settings blind, which makes it a moderately less cruel experience. Ah well.
Catholics do as Catholics will. ![]()