I am a happy user of dBpoweramp and also use a Nucleus One with internal SSD.
Below is a rough description of my workflow to digitize my large CD collection and place it on my Nucleus One server.
First, I rip the album to the local drive on my workstation (mine is Windows, yours is a Mac). Any necessary manipulations of the ripped albums is completed there before copying them to the Roon monitored directories/folders on the Nucleus One (N1). Any necessary manipulations of the ripped albums is completed there before copying them to the Roon monitored directories/folders on the Nucleus One (N1). That N1 SSD is network mounted to my workstation.
I keep the same folder hierarchy on the N1 as I used on my workstation. dBpoweramp has its own rules for how is creates the folder hierarchy (including the names of folders and digital music folders), but you can modify the root directory of the relative paths & the naming convention.
Even if I think my rip, folder/file names, and metadata tagging is good, I keep these files on my workstation until I verify that Roon displays them properly. If I need to make adjustments to my digitized files, I make these on my workstation. Then, before re-copying them over to the N1 SSD, I delete those files on the N1 SSD and execute a “cleanup library” to eliminate any residual information. Then I re-copy them over, check the results, & repeat until everything is good. (Most of the time the initial files copied over are good).
Sometimes a tweak is need to the Roon representation of the new album which does not require corrections to the source files.
If I have a clean addition of the digital files to the N1 SSD, I then copy the same files to an external drive, as my backup of the data. I use a USB attached external drive for that. If paranoid, there would be a periodic copy of that backup collection to another external drive that is stored off-site in a safe place (such as bank safe deposit box).
Finally, I delete those files from the workstation.
dBpoweramp verifies the rip against an accurate rip database of many rips of the identified album and identifies any tracks that do not match (usually due to imperfections or difficulty reading the ripped disk. There are also rare situations where the album is not in the accuraterip database & thus is unable to identify your rip as verified. When either situation occurs, dbPoweramp has a “secure rip” mode that does multiple rips, identifies the questionable frames and then does very careful re-rips of those frames. When a track is good, secure mode only take twice the time as a normal rip at the same speed. At the other extreme, a very bad CD track can take 24 hours and still not declared the rip as being good (then you may choose to listen to the digitized file and see if it sounds acceptable). I have many tracks & entire albums) which are not “accurate-rips” but were announces as being “secure rips”.
The other essential dBpoweramp service (after reading the disc, but before the rip) is collecting metadata values to store in the digital file’s tags. It accesses multiple databases, suggests tag values by looking for agreements, and lets you examine what values each database suggested. It is not uncommon for me to override the dBpoweramp’s chose of values and click a different value from one of the providers. Rarely, I feel a need to manually type in a value (song name, artist) from the CD insert. I sometime chose different Album Artwork.
If I later want to adjust the metadata tags in the post-rip digitized files, I use the free mp3tag software [I donate money to the developer] to make those changes. While the name reflects it’s origins, it works with several file format including the FLAC format that I prefer.