Please post a screenshot of your "Options-Locations-Sound Sets" page setup.

Trucky

As requested:



FWIW: This is one area of S1 that truly needs some developer eyes. The "Scan Locations" part of this dialog is truly wonky. But first a little backgrounder...

When I installed this specific "clean" instance of Studio One (v6.2.1) back in early Feb 2024 (brand new machine) - as with all my settings - I specifically came into this dialog - set the top two locations to my L:\ drive and then DELETED all existing scan locations that Studio One pulled out of thin air and manually added the L:\ location path - since I have my actual soundsets on L:| (as noted under Installation)

Clicked OK on it - thinking that single scan location (let's call it Location 1) was going to be my only location.

But then a few days later - when doing a few final checks on the environment - I come back into this dialog and I see that Studio One has magically added scan locations 2 and 3 - for purposes unknown. Not only were they added to Scan Locations by a mysterious force - these two paths do not actually exist anywhere on my computer.

Then - today - per this request - I come in here again - and now I see Scan Location 4 (with red arrow) - also which does not actually exist on my hard drive.

After your request for a screencap - I managed to highlight Location 4 and clicked Remove to get it out of the scan locations area BUT cannot remove locations 1, 2 or 3 now at all.

If I try to highlight any one of these paths - the item is not highlighted. Pressing the Remove button does nothing.

UPDATE; After dropping that 4th path - I do not see that strange Scanning Sound Sets dialog anymore.

But something is still really off with this dialog - probably need a bug report on it.

VP

I'm using the default locations as shown here but the top entry for soundsets you're using should be fine for the path to your external drive (as long as it performs well)...

I think the "All Locations" path was added to make it easier for 3rd party DAWs to access PreSonus Hub plugins as the Public path permissions usually has less restrictions.

Trucky wroteI'm using the default locations as shown here...

I think the "All Locations" path was added to make it easier for 3rd party DAWs to access PreSonus Hub plugins as the Public path permissions usually has less restrictions.

Fair enough - but I have 82.3 GB of soundsets. Won't be putting those on the ole C Drive anytime soon

I am willing to consider moving these to my D:\ drive - over to (D:\Documents\Studio One\Sound Sets) which is my main default user data directory anyway.

But I first need to be able to clean up this dialog - and if the Remove Button is not working and these old paths cannot be removed - I might be signing up for trouble here.

What does the Reset button at the end of Installation Paths do?

If I can find a way to totally reset this dialog to default paths - might be good to just use them.

VP

Vocalpoint wroteWhat does the Reset button at the end of Installation Paths do?

It just sets both locations back to the default paths.

Trucky

Took a page from your install and reset everything back to the default sound set paths. Moved all my sound sets back to the default location and now I have just two scan paths (the defaults) and was able to clean up the other L:\ references etc.

But - even after all that - I once again see this oddball dialog popping up.

I am starting to think this has nothing to do with the actual paths/locations - but potentially with the sound sets themselves.

My install is not just typical "Presonus" content - mine contains the VERY huge Toolbox II sound set (40GB) from Kulture Sounds and their newest entry DrumBox (3.9GB) which could very well be causing this issue.

At first glance - my gut says this is some sort of "delay" parsing the sound sets - but only DEV could tell us exactly what is happening during this "scanning sound sets" routine.

It is not impacting Studio One startup or causing any other issues that I can see.

Will consider it to be normal - until someone tells me it's not.

VP