Reason 13 Browser "User Library"

[FGL]

So this new browser is extremely difficult to test. You always come across ancient patches that you get stuck on. Ultimately, however, all the guesswork about the function of the "User Library" folder has resulted in me rearranging all the storage spaces to get things in order. It was overdue anyway.

Everything works so far, but the "User Library" folder is still giving me a headache. I put a copy of a refill in there. And that worked. Reason doesn't recognize an alias here. Then I thought to myself, that can't be it. Actually, individual patches would make more sense. So I deleted this refill. But the refill continues to exist like a zombie. Now Reason refers to the original file on the second SSD.

At least I have something in the "User Library" now, but I can't manage it and use it for something useful.

Does anyone have a sensible idea for using this "User Library"?

[MattiasHG]

For some context: User Library is meant for your own custom patches (it's also the default patch save location). Your ReFills are best put in the ReFill folder. These are just handy shortcuts that are automatically indexed and available in the Locations section of the browser, meaning if you put stuff there Reason will be aware of them and they'll show up in All Locations when filtering. Just like before, if you have the same ReFill in several places Reason will only recognize one copy which can be a bit confusing. We're hoping to make that more clear in the future.

If you're getting weird behaviors of stuff not updating in the index, I'd appreciate a report to support.

[FGL]

Thank you for the explanation. In the end, I basically figured it out in a similar way. If anything would make sense in this place, it would be individual patches. But with hundreds of patches, it doesn't really make sense.

So I could now duplicate all the patches in this folder and they would then be found there, sorted by device. Then I delete them again and have saved space. Otherwise, the folder forces me to at least keep my patches on the main hard drive. Separate from the other music data.

But because Reason now prefers to store patches there, you have to be as careful as a lynx if you want to keep things in order here.

[Teebie]

I have 168 gig refill folder on my mac - i just drag the folder to the shortcuts then all my favourites now have Refills and instuments that took me months to sort out now - thanks the lot - i do need to press the up button on this though

[Teebie]

Yea i take that back - there are so many things effecting where you put your refills - your r13 browser favs your shortcuts etc- if you put the refills in the refill folder or on an SSD or on the HD Drive if you have iCloud on if you put them different places you get different results - most of my favs do not mirror how it was in reason 12 - i have been at this for 2 days - as i say you get so many different results with what in your shortcuts or favourite lists within the r13 browser its unreal - i have tried just about everything

think i might need to go back to r11 or r12 until this is fixed and mirrors what i have in r11 or r12 there Iam still indexing the now so will give it another hour - the SSD re mounting after every restart is a pain in the bottom - this is an apple issue though it does not help reason at all - this mounting issue has happened on all the IOS after monterey - shocking

took me 3 days to get native 15 collectors edition all working too with r13 - make sure to add your native content to the file settings in reason preference as this speeds the loading process up of native but the r13 browser needs to be looked at from the reason genusies

Right now Iam trying - my 168 gig reason refills folder in the refills folder within reason studios folder - -
i have also tried putting all my 168 gig .rfl files in the refill folder too - that didn't work with my favourites in the r13 browser - so annoying

will try adding the location from my SSD after the above -

PS reason 11 opens in 5 seconds - r 13 takes 25 seconds

[Teebie]

If deleting the cache does not work then uninstall reason - Mac delete the reason studios folder and the app in applications - then run companion to re install
definitely take all your .rfls out of sub folders as put them in the Refills folder under reason studios - when i done this i now get the indexing status up and its been there for over 30 mins
All my favourite lists and shortcuts are now showing after the above as i checked them in r11 and r12 to make sure as i was missing tonnes of stuff in them before i done the above


also seeing some other good notes in the manual under browser - pulled out some good points below
https://docs.reasonstudios.com/reason13 ... ut-refills


Samples (Wave and AIFF files) are compressed to about half their original file size when stored in ReFills, without loss of quality.
In Reason, you can use the Browser to list and access the embedded sounds and other components within the ReFills, just as if the ReFills were folders on your hard disk.
Furthermore, if a song makes use of components from ReFills, Reason will tell you which ReFills are required.

We strongly recommend not to put ReFills in Favorite Lists. Instead, use the User Library or Shortcuts Location
for ReFills, see “User Library” and “Shortcuts”.

Computer
• The Computer heading holds links to the User and Desktop folders on your computer.
These are not included in "All Locations". Use these for navigating to folders that you want to add as Shortcuts!

To the right are buttons for selecting view mode: Flat list or Tree (showing folders).
Different locations have different default view modes when you go there. In some cases you cannot change the
view mode (“All Locations” is always a Flat list for example, while the folders under "Computer" will always be in
Tree mode).

ReFills is a subfolder in the Music/Reason Studios folder on your computer. Reason Companion will install the op-
tional Drum Supply and Loop Supply ReFills in this folder, and you are also encouraged to move any ReFills you
have downloaded or purchased there. This will ensure that they are indexed and included in "All Locations".

[jimhanner]

For some context: User Library is meant for your own custom patches (it's also the default patch save location). Your ReFills are best put in the ReFill folder. These are just handy shortcuts that are automatically indexed and available in the Locations section of the browser, meaning if you put stuff there Reason will be aware of them and they'll show up in All Locations when filtering. Just like before, if you have the same ReFill in several places Reason will only recognize one copy which can be a bit confusing. We're hoping to make that more clear in the future.

If you're getting weird behaviors of stuff not updating in the index, I'd appreciate a report to support.

Hi Matthias. I've been putting my User Patches in a folder called that, under my main Reason folder. Now, even when I open a patch from that folder and make a change, when I go to save it (over the previous version) the UI takes me to this new User Library folder. Is there anywhere that I can specify my 'User Patches' folder as the default instead of 'User Library'?

FWIW I mainly have to do this because Reason Drum Kits *still* doesn't save changes to patches with a song. Any chance of this ever being fixed?

Thanks,

Jim

[MrFigg]

Right...Favourites in the Browser. I drag my refill folder in and the little round arrow starts spinning and never stops. I can get to my refill folder by navigating through "this computer" and it finds everything straight away. Am I doing something wrong?

[jam-s]

The first indexing run might take a few hours depending on the size of your Refill/sample collection.

[MrFigg]

The first indexing run might take a few hours depending on the size of your Refill/sample collection.

Thanks. It's massive. Probably just as easy to go via "This PC".
Incidentally, the manual says that they strongly recommend not putting refill folders in favourites. Why would that be?

[bigguy1]

For some context: User Library is meant for your own custom patches (it's also the default patch save location). Your ReFills are best put in the ReFill folder. These are just handy shortcuts that are automatically indexed and available in the Locations section of the browser, meaning if you put stuff there Reason will be aware of them and they'll show up in All Locations when filtering. Just like before, if you have the same ReFill in several places Reason will only recognize one copy which can be a bit confusing. We're hoping to make that more clear in the future.

If you're getting weird behaviors of stuff not updating in the index, I'd appreciate a report to support.

Hi Matthias. I've been putting my User Patches in a folder called that, under my main Reason folder. Now, even when I open a patch from that folder and make a change, when I go to save it (over the previous version) the UI takes me to this new User Library folder. Is there anywhere that I can specify my 'User Patches' folder as the default instead of 'User Library'?

FWIW I mainly have to do this because Reason Drum Kits *still* doesn't save changes to patches with a song. Any chance of this ever being fixed?

Thanks,

Jim

Same here. My own patches folder is also somewhere else. Would be cool to specifiy the place where user patches should be saved. And tbh I think its very annoying that every time I want to save a patch it brings me to the user folder. Why can't it remember where I saved the last patch and open up this folder like it was Reason 12.

[Loque]

Hi Matthias. I've been putting my User Patches in a folder called that, under my main Reason folder. Now, even when I open a patch from that folder and make a change, when I go to save it (over the previous version) the UI takes me to this new User Library folder. Is there anywhere that I can specify my 'User Patches' folder as the default instead of 'User Library'?

FWIW I mainly have to do this because Reason Drum Kits *still* doesn't save changes to patches with a song. Any chance of this ever being fixed?

Thanks,

Jim

Same here. My own patches folder is also somewhere else. Would be cool to specifiy the place where user patches should be saved. And tbh I think its very annoying that every time I want to save a patch it brings me to the user folder. Why can't it remember where I saved the last patch and open up this folder like it was Reason 12.

Agree percent

[tanni]

Saving patches in Reason 13.1 in Windows is, for me, a significant step down from the previous version of Reason. When saving a patch, the folder: “User Library” is now always suggested and I have to click 10 times to go to the correct folder where the patch should be saved. In the previous Reason version, Reason always remembered the last storage location for different patches from the respective synths. That was really good. Now I have to click dozens of times every time I save, which is extremely annoying. I have created a very well-stocked library over the years, and everything has its place there.

[Heigen5]

Same here. My own patches folder is also somewhere else. Would be cool to specifiy the place where user patches should be saved. And tbh I think its very annoying that every time I want to save a patch it brings me to the user folder. Why can't it remember where I saved the last patch and open up this folder like it was Reason 12.

Agree percent

I agree too. Some kind of a workaround would be creating your own folder and add it to the locations list (would be from one click away then).
By the way, why wouldn't the save as remember the location too, if you happened to load a file from your harddrive? It would make sense that the save as leads you to the folder where your last loaded file was.

[Noise]

If they want to force us to use the new library location, they could meet us halfway.
For example, if a user saves a patch inside that location, it will allow to use the last folder in the library

hint: you can use a mklink (symbolic link) to redirect the User Library to another drive & folder.
( just don't add it again into the reason favorites, to avoid double indexing)

[bigguy1]

Agree percent

I agree too. Some kind of a workaround would be creating your own folder and add it to the locations list (would be from one click away then).
By the way, why wouldn't the save as remember the location too, if you happened to load a file from your harddrive? It would make sense that the save as leads you to the folder where your last loaded file was.

I just put a link to my regular patches folder in the user folder. Now I am at least close to where it should be with one click.

[AnotherMathias]

I just put a link to my regular patches folder in the user folder. Now I am at least close to where it should be with one click.

I don’t have one folder for my patches, I have dozens (hundreds, possibly), depending on the device and my different categories of sounds.

Does RS think that we should just dump it all into one big user folder, and sort it out using tags and searches?

[FGL]

I agree too. Some kind of a workaround would be creating your own folder and add it to the locations list (would be from one click away then).
By the way, why wouldn't the save as remember the location too, if you happened to load a file from your harddrive? It would make sense that the save as leads you to the folder where your last loaded file was.

I just put a link to my regular patches folder in the user folder. Now I am at least close to where it should be with one click.

I also think that this is the right way to quickly save patches in the designated place.

But I now also think that the method as provided in the program has its justification and also its advantages.

A) You also have to take tagging into account here. When you save a patch, it is not tagged at first. So you have to search for and find this patch in the folders in order to tag it. That also takes time.

B) But if the patch is first saved at the highest level of the user library, it is easy to find there. And you can tag it there first and then move it to the relevant folder and find it easily. Moving it to the right folder then takes time.

I'm not sure here. Both ways seem logically justified to me.

[FGL]

I just put a link to my regular patches folder in the user folder. Now I am at least close to where it should be with one click.

I don’t have one folder for my patches, I have dozens (hundreds, possibly), depending on the device and my different categories of sounds.

Does RS think that we should just dump it all into one big user folder, and sort it out using tags and searches?

IMHO, it's only about this case, where you organize large amounts of patches. And you can now do that easily and conveniently with the program. Hopefully there will be some kind of predefined order. And you don't have to change this, you just have to let the program index the respective storage locations. Tagging is then an unavoidable step, but you can start with the important patches first.

The advantage is that you can now really find everything, even things that used to be hidden away in forgotten subfolders.