Are you still experiencing the issue, @Bluebeat, while using the Early Access 1197 build?
@James_McKeand I don’t have build 1197 installed, I’m waiting for the regular build. I don’t want to sign up for early access, because I won’t always have the time to report problems with those builds (or want to experience those problems ).
Yeah…I’ll probably go back to the production build given I’m not seeing any real change with 1197. Thanks for your feedback.
Thanks for the feedback. Unfortunately, that doesn’t sound very promising. I had high hopes for a new build. I will test it here when the production build is available.
The whole album needs gapless playback to sound right and I have zero problems with the album on Qobuz. All tracks are gapless with B1197 even when I click within 10 seconds of the end of track.
I’m on early build and so far no problems either. I was having gaps since end of Nov and up until this new build. So the fix worked for me. At least so far.
One thing to make sure is the both the app and the core are updated to the latest early build. Sometimes you get notice the app updated in Test Flight but still need to go to settings in the app and update the core.
With apologies to those still hitting issues, I can report that things continue to be stable here today on early access build 1197, and the fix appears to be addressing most of the problems I was encountering.
However, I can also confirm that the short track specific issue I referenced upthread still continues to occur consistently, and it does indeed affect both Qobuz and Local file playback (tested with the same versions of the same albums, at the same resolution). This still results in gapless/buffering/delays (a track in an album of ~10 seconds or less seems to be the trigger).
Finally, as has been the case up until now, neither of these scenarios (playback of either local or Qobuz album with very short track) triggers gapless/buffering/delays issues in the current early access build of ARC - nice to have an alternative option as a workaround
Much thanks and respect to all of the early access/beta testing community for helping to sort this issue out. I’m going to semi patiently wait for the next regular update as well. We’re only 60 days into 2.0? Maybe I’m off a little bit with the time, I will just hope that the developers team will get to the basics first and work their way out. With ARC, CarPlay yada yada etc. I hope that they haven’t been spread too thin. Last evening I counted 55 posts to the support topic in 12 hrs, that’s a lot of work and time consuming for them. I’m wishing them well and hope they can get through this tough season soon
Not sure where you get 60 days from, it came out in September so a bit longer than that.
Like I said………I’m new to the Roon family. Been traveling between homes etc. times fun when you’re having flies. Guess I’m only 60 days into a life sentence
In this case perhaps we need to organize a hunger strike
No way! No gapless and then still hungry to the bones?!
By the way, it works for me without any problems until now, no hungry gaps threatening
You’ve got a point, all this angst over Gapless is making me hungry We shall start the hunger strike after a large brunch break It will remain in effect until supper time…….
I envy you. I’m listening to the new Arctic Monkeys album “The Car” right now - 8-15 second gaps between tracks. Last week it went through without a hitch.
EDIT: Core reboot - fixed for the next hours…
Really sorry, too bad.
It doesn’t seem to be that easy to find the cause of the problem, at least I’m keeping my fingers crossed that it won’t take that long.
Has anyone found a solution to this? The problem doesn’t occur when streaming ripped CDs so the problem is between Qobuz and Roon.
It’s quite telling that there are few replies from Roon Inc., despite many comments here telling of the same problem. Perhaps the money people drop on Roon every month isn’t enough for them to look seriously at the problem.
I dropped half a month’s salary last year buying a lifetime subscription and will shortly be asking for it back since they are NOT providing the service they describe.
I am going to have to eat my words a bit…While I did have problems during the first listens after moving to the Early Access build, I have now have consistent SUCCESSES - even on albums that previous were consistently problematic. So…keeping my fingers and toes crossed that it continues working.
Not sure why I had the initial problems…maybe I just needed one more Core reboot; regardless, I’m relatively nervously happy at the moment.
Thank you for the feedback on gapless playback on early access. In case you haven’t yet, please give your core a restart after updating.
For those who are still experiencing delays between gapless tracks, we’ll need to grab some new time stamps (date and time) of when you run into this issue. Including the track name would be helpful as well.
I’ll be on standby for the above
Are you really? I would have thought you could replicate the problem quite easily.
I’m beginning to think Roon is not quite user-friendly. All I want is a good listening experience. Instead, we are placated with questions your technicians should know about and a suggestion we download another ‘early’ version (as if I would know how to do that) which is probably filled with other bugs.
Here’s a suggestion, people at Roon: release an update when you know it works. Otherwise, don’t.
There are quite clearly lots of people who never experience this, I am one. Given how the forum lights up if there are wide-spread issues, I would guess that it’s not many people who do. Doesn’t make it unimportant but more difficult to replicate
It was posted in this post just a few posts up:
I.e., this link explains it:
I, like many, am not that computer literate. You should remember that some of us haven’t a clue how to access early release programs.
Updates should not be released until they are tested. There’s no excuse (and you shouldn’t try to make one) for a buggy version.
I’ve paid Roon enough, so there’s no excuse for a bad release.