Meridian Unplugged - Powered by MrTechGuy.co.uk Forums Discussion Meridian - Streaming Hardware with Roon Application Roon - How do I add my MC200 Sooloos library

Matsaly

If you have successfully connected the Mac to the MC200 then you need to add it in Roon, from the main window select the three horizontal lines click on it and then select settings, then select storage, then in the section marked as WATCHED FOLDERS select add folder then you can browse for the MC200 music2 folder.

If you have not connected the Mac to the MC200 then do exactly as above except when you go to WATCHED FOLDERS select the lower section NETWORK FOLDER and put the smb:// command in the network path box, then select add folder at the bottom.

Roon should then add your music from the MC200.

Cheers

Russ

I don't think you need to add SMB etc - at least you didn't have to when I tried it - adding it actually caused it to give an error. But that was on a pre-release version of Roon so may have changed for release version.

Kudos to Russ who reached out to me and was kind enough to walk me through the setup during our phone call.

Thanks to his effort (and everyone else's input) Roon is able to access the content of my MC200.

As posited- it was my user error that caused the problem. I was unaware that one had to "add" the MC200 to the watched folder in the Roon app.

Since Roon automatically detected my iTunes library when I first installed it, I wrongly inferred that roon would automatically find the path to my MC200 once I mounted it.

Russ is a true gent and an asset to the HH community. Many thanks to the admins and other helpful HH's as well.

A very much deserved "Well Done" to Russ for going the extra mile to sort Matsaly out

A Gent indeed!!

Hear hear, no applause though I'm afraid Russ

Can you tell us how Roon is coping with the metadata from your Sooloos MC200 library.
I have an Native exported library which works well and am curious as to wether this export step is now necessary.

Yep, I agree, Russ is a gent.

Chris

Russ is a gentleman and a scholar.

I'm two-thirds of the way though a native export of my Sooloos library. It's taken just under two weeks so far. I've found that a lot of files have been corrupted, so it's a real pain to have to re-rip those discs and then have to delete the duplicate files that are created in the Roon library as those discs are reexported.

Some of my discs are in the IoW, so I also need to make a note of what to bring back next time I'm down there. Sadly Sooloos does not allow the export of the list of corrupted files in CSV.

Some of my files are lost forever (for example some of my Society of Sound downloads where I've lapsed my subscription) because the files are corrupted on the back up as well as in the library.

Generally it shows that you're better off having a separate Roon library, I think.

Sorry Dominic
But just trying to fully understand what I think you're said

Do you mean that

a) the Track Files were non-corrupt and would play just fine within Sooloos

b) but the Sooloos Export procedure resulted in Corrupt files??

If so, How did you determine that the Sooloos exported files were Corrupt??.....was it based on what Roon was reporting??

The files will not play in Sooloos. They were fine when they were imported, so it must be down to disk corruption.

When I migrated to the QNAP I did a backup and restore rather than a native export in order to preserve the metadata. All of these files backed up and restored perfectly recently.

The native export for Roon is a different matter, perhaps because the export actually tries to tag the files it is a more robust test of corruption? I know they're corrupt since the native export tells me they are and can't export. I end up with a lot of albums with missing tracks.

I've tried copying many of the files from the library and doing a FLAC to FLAC conversion using XLD and they all give a "Fail to decode" error.

Did you have either backup falling over or restore falling over (hanging/crashing) when you did that recently ?

It could be that the files were broken in the process.

The back up continually crashed due to Control:Mac not being fit for purpose.

However it certainly would not account for the number of tracks that have been corrupted (well over 200, maybe 300 so far). Sometimes one an album, sometimes practically the whole album.