[Investigating] RoonOS 3.0 (build 274) - Roon CD Ripper output not written or not readable

This seems related to the changes made in access permissions with RoonOS 3.0

In my workflow I rip to a folder “CD-Rips” on an internal drive in the NUCi7. This morning I ripped, or tried to rip, a newly acquired CD. Apparently succesful.

The folder CD-Rips has been configured as an ignored path within Roon’s storage locations.

I check and post-edit newly ripped files as needed and copy them into an appropriate watched folder.

With this build of RoonOS:

  • The CD Ripper bundled with RoonOS reports successful completion (see above) but no new files or folders are visible / accessible from Android and MacOS. (see below) Access from Android and MacOS is still allowed anonymously/unauthenticated.

  • Pre-existing files and folders are still visible - I can see, move, copy and delete the folders and files for 3 ripped CDs that pre-date RoonOS 3.0

  • After removing the CD-Rips folder from Ignored Paths, the 3 pre-existing rips are correctly ingested into Roon, but nothing else.

  • As an anonymous user, I can still add, copy, move an delete files and folders within CD-Rips

Maybe the Ripper has no write permissions but doesn’t report this to the user? Or the files are written but neither Roon nor anonymous users have read permission?

Hi, @ToneDeaf, thank you for your report! May I ask you to please reproduce this issue one more time and let me know the timestamp? I’d like to pull a diagnostic report from your machine, hopefully, our dev team will be able to find the culprit there.

Thanks!


Ivan

Hi Ivan,

I’ll try with a few other CDs when home and report - but after reinstalling build 274 and power cycling the NUC once more for good meassure I was able to successfully rip the same CD this morning, with files visible, editable etc. So it may have been a one-off.

(tried yesterday but was reminded that it’s not possible to re-rip within 24 hours once success has been reported by the RoonOS Ripper :roll_eyes: )

Got it, thank you, @ToneDeaf! If you see this again please let me know the timestamp and don’t reboot your RoonOS box after that so that the diagnostics report contains a clean error state (hopefully).

Thanks!


Ivan