Hi @noris,
Have just tried the export again with same result i.e. beachball and program unresponsive almost immediately thereafter.
I pressed the Export button at 18:45 GMT today 17th March 2020.
Should I force quit the program or leave alone for now?
Many thanks for the help.
Hi @David_Miles,
Thanks for letting me know the timestamp. I have gone ahead and activated diagnostics mode for your account and what this action does is automatically upload a log-set to our servers for analysis.
Please force-quit the program and open it once more to ensure that this report comes through, thanks!
Hi @David_Miles,
I can confirm that logs have been received and I have passed them on to QA for further analysis. It may take a bit of time to hear back from QA regarding analysis but in the meantime feel free to continue using Roon as you would normally do. Once I have further information I will reach out once more, thanks!
Hi @David_Miles,
I appreciate your patience until I had a chance to discuss your case with QA.
QA has informed me that this is a known issue, and a ticket has been submitted to the dev team for review regarding this behavior.
I can’t comment on when exactly this behavior will be addressed, but we are aware and working on it. I appreciate your patience until this reaches the front of the dev queue!
Core Machine (Operating system/System info/Roon build number)
SonicTransporter i5 Roon 1.7, build 528
Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)
Audio gear (818v3, SonicTransporter) is wired and isolated on dumb Netgear switch. Rest of network consists of Ubiquiti APs, Switch, etc. For this issue I tried both wired into dumb switch and WiFi.
Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)
N/A
Description Of Issue
Exporting a playlist hangs Roon remote 1.7, build 528 on both MacOS 10.14.6 (Mojave) and 10.12.6 (Sierra). A playlist with 3 tracks that all play hangs Roon remote (only Force Quit will work) when I try to export it. Tried both wired to dumb switch that has my Roon core on it as well as WiFi.
Also tried rebooting Roon core as well as both MacBooks running Roon remote.
Hi @soundserge,
Thank you for your report. We are aware of this issue and are working on it, please see above:
And ??? 5 months … and no solution ?
So… It’s been some days now that your QA is “working” on that … It’s getting a little bit frustrating with this problem.
The only solution until now seems to be a complete delete of the library and to start again. But after some time, I now have the same problem again, but still no solution from your side…
Hi everyone,
We met with our team to discuss the current status of this investigation is still with our development team. We’ve upped the priority on this and, while it will not be able to make it into our next release, we are hoping that a release in the near future will include an improvement here. You have our apologies for the ongoing trouble!
Roon Labs,
The issue was reported in this thread on March 15, 2020. On March 18 a ticket was opened. The issue/ticket/thread sat for 4 months with no update until another member persisted and got the same response from you, and you “upped the priority”. It is now September 20, a full SIX MONTHS since the issue was reported, since the ticket was opened, and 2 months since you 'upped the priority". What’s the status? Are there any notes in the ticket? Is this being worked on? Do you need to up the priority again?
Hi @DonaldLL,
Thanks for your patience here! I just checked the status of the ticket and I see that it’s actively being worked on.
As per policy, I can’t comment on when the work on the ticket will be fully completed and ready for release, but there have been recent updates, so it is making it’s way through the queue!
It’s been now MONTH since this issue first was reported!!! Now, another update, but still NO fix for that. Sorry it is getting really annoying! @noris: Any comments?
I don’t understand the strategy used.
A bug is clearly identified and no effort is made to fix it. It looks like Apple … It is not a bug but a feature … Versions follow one another and clearly identified bugs are ignored and not fixed … Warning. Take customers for what they are not …
Hi everyone,
Our QA team is testing some potential solutions for this issue — I can’t make any guarantees on a timeline as we are still testing this, but this remains a high priority issue for us and we’ll be sure to update everyone as soon as we have more information.
Dylan,
With all due respect, if this is being treated as high priority and a solution has not beed developed since March 15, 2020 (NINE months ago), you have bigger problems than I imagined.
Apparently this “problem” is not considered all that important by the Roon folks. How else could it survive this long without even an attempt to fix it.
It makes me wonder why any of us customers should bother reporting obvious bugs.
Happy Holidays,
A new version and a major bug still not fixed …
It has been going on for almost a year now …
Never seen a team of developers unable to fix their own software … And I work in computer science … Shame on them …
I hope that we will soon see competitors in Roon and then there …