R13 (.1) Browser woes

[selig]

Yup, I have that collection too, as well as many others and no problems here.
I copied them from the original disks, most folders have 50-100 files MAX in them.
I thought the whole problem was when you put over 1000 files in a single directory?

I have thousands of files within a single directory, yes, but the files are within subdirectories. However, the categories and tags I want to apply to these files are based on a top-level directory, not the parent directory of the files.

For example:
Impulse Responses/LiquidSonics/Reverberate/*.wav
Impulse Responses/BOOM/Fields & Spaces/Alley 01 45m/*.wav
Impulse Responses/BOOM/Fields & Spaces/Canyon 01 Echo 0m/*.wav

I want to mark all those 25.000 files within "Impulse Responses" with the category "Impulse Response" so I can quickly filter for only those files in RV7000. This should be possible when switching to "flat" view which recursively shows all files of the directory you're currently in. But it's not possible to select more than 1000 files at a time and it's hard to graphically select not more than that anyway. Same for my music samples directory, same for my music loops directory, same for my foley archive directory.

Apologies if I was being dense, I THINK I'm understanding what is going on now.

[bitley]

always store stuff in refills of your own guys. Old song files, everything. I have at least 8 in house refills where I store like a zillion files. Build at once. Extremely effective.

[ab459]

Another observation - not first time i noticed behavior when indexation stopped (and no cpu usage) but you click in browser to shared folders (in shortcuts section) and they looks empty by some reason.
Then helps select command "Rescan shortcut" (indexation starts resp and content become be visible).

[Tiefflieger Rüdiger]

always store stuff in refills of your own guys. Old song files, everything. I have at least 8 in house refills where I store like a zillion files. Build at once. Extremely effective.

I'm not going to convert 4+TB of open format audio files into a proprietary niche format that needs to be split every 4GB. Instead, they should improve the scalability issues of their software since it is one of the key features of the Reason 13 update.

Hosts like Reaper or Bitwig scale much better with the same data. For instance, Reaper manages to present a search result for the same data within a fraction of a second while staying below 200MB of RAM consumption. Reason OTOH grows beyond 2000MB of RAM when the search result is a large set and takes more than a minute to complete. And this comparison is even unfair towards Reaper because it is able to read tons of more data from my library, since Reason doesn't support flac or wavpack on Windows and shows much more metadata than Reason's browser.

[bitley]

It's free to use the universe you want to when travelling in the musical spaceship. I have my wife and I love her, her name is Reason. I can't possibly see why you need such behemounts of data but if you like that, go with that. I come from the hardware sampler history so I love crunching data to get the essential snippets. I hope you at least optimize your song files.

[moneykube]

always store stuff in refills of your own guys. Old song files, everything. I have at least 8 in house refills where I store like a zillion files. Build at once. Extremely effective.

That is a good idea if you only use reason.
But what about using multiplatform files like audio files, that you can use in many different apps and also many plugins within reason?
This applies for wave tables, IRs, and the zillion audio samples, audio stems, songs, everyone likely has a portion of > some more than others.
The refill solution may help for reason only content... I will look at that. Thanks. I have a lot of reason only files.
I have been breaking my audio file folders into smaller sets... I was good before with 4000 files or so in each folder up until now.
LOL>> On the 4th or is it the 5th full day of mitigating and rearranging the files my drives ? > I removed over a million and a half audio files to other external disks, that won't be hooked up to the computer at the same time as reason >> and therefore won't be indexed over and over again.
I must admit some audio folders were/are indeed far larger than that 4000 files in each folder, which I am now slowly dealing with.
They already were categorized by type and function. My wave tables alone took 7 folders in order to have them as a 1000 files or less in each folder.
In 50 years of music making I have collected and made MANY audio files. Folders inside folders, inside folders, inside other folders ....
I am sure this must be the place that is bogging down the browser here, but again, it was never a problem in previous versions of reason.
Embracing this future has been painful so far. It is taking much of my time instead of speeding up my work flow.
I have to do this with two drives at once manually because every drive I have> Video / Audio / Internal drive, and other data drives > have a clone backup.
It takes many days to copy one drive to another, so I am trying to save at least some time doing this. It hurts my brain though.
The million and a half files I moved, which were a little over half my audio files> took an entire day to move to other drives.
Apple fried 6 external drives once with a firmware update and faulty logic board that sent power to externally powered drives therefore frying them.
Had I not made a clone of every drive> by types of files and content> I would have lost my entire film and audio career that exists on these drives.
It cost me over a $1000 to replace the drives, and 2 weeks too reclone the drives on the replacement drives that apple never replaced, even though Apple was the cause for the drive failures.
I would get a message... there is not enough power to power an already powered drive. They needed no power. POOF... they were toast.
I have worked in many studios troubleshooting many computers for many years, and have never seen nothing like it in 30 plus years working in film and audio production studios. Much like I have never witnessed such a slowdown, because of my audio files (perhaps?)> in any other reason version > since starting with reason 2.5.adapted. Then 3 and up... I only missed purchasing reason 8 as it didn't appeal to me.
One thing I don't know that I should know> What is the best way to get rid of purgeable files on mac... and are they necessary? Anyone
I have 38.78 GB of purgeable files on my mac internal drive, that I would like gone... if possible.

[moneykube]

PhillipOrdonez
" The thing with 1000 is that you can not select more than 1000 at once to tag them all. Nothing more.
This is how misinformation spreads. It’s all like that game where you whisper the thing to the one next to you and at the end of the line the thing they say is completely different from what was initially said ‍♂️"

Since the thread is locked I could not reply
To be fair> Selig did say this>>>

"I’m not excusing RS for not allowing this, but I also cannot imagine many folks have single folders containing that many individual files. For example, this never came up during testing."
--------------
So, I took this as a "possible" reason the browser was slow for me but also qualified it in another thread that I did not know for sure. I am entirely on board for not having to do this, as I have way too many audio and midi files > I had only started the process, as a faint hope clause > since reason studios has not offered a solution yet. I have all sorts of folders over a 1000 files. I am happy I "misread" what he said, and that you corrected me. Thank you.
I'm grasping at straws to solve this issue that you are not experiencing. Some of us ARE experiencing this, and trying what we can to solve it.

[PhillipOrdonez]

PhillipOrdonez
" The thing with 1000 is that you can not select more than 1000 at once to tag them all. Nothing more.
This is how misinformation spreads. It’s all like that game where you whisper the thing to the one next to you and at the end of the line the thing they say is completely different from what was initially said ‍♂️"

Since the thread is locked I could not reply
To be fair> Selig did say this>>>

"I’m not excusing RS for not allowing this, but I also cannot imagine many folks have single folders containing that many individual files. For example, this never came up during testing."
--------------
So, I took this as a "possible" reason the browser was slow for me but also qualified it in another thread that I did not know for sure. I am entirely on board for not having to do this, as I have way too many audio and midi files > I had only started the process, as a faint hope clause > since reason studios has not offered a solution yet. I have all sorts of folders over a 1000 files. I am happy I "misread" what he said, and that you corrected me. Thank you.
I'm grasping at straws to solve this issue that you are not experiencing. Some of us ARE experiencing this.

I’m sorry you’re recorriendo issues with the browser and hope they can be resolved soon. I’m confident you’re in contact with support and they’re doing their best to sort it out for you and everyone else having indexing issues

[ab459]

Well, for NOW, it seems i already can't say that browser\indexation make problem.
Having waited a couple of times before (for the end of indexing activity) now I for example, also add all my other separate folders with refills, and scanning/indexing occurs a;ready in about seconds now.
As well after relaunch Reason (no activity\cpu usage).

So, advice to those who still have this problem - it seems that just need to wait for the process to finish the first time you launch R13. Although this can take a really long time, even several hours. But you can just minimize the program and go about your business.
And then, during subsequent launches, you will find that everything has returned to normal idle (and adding other folders will not cause so long indexation).

[chimp_spanner]

Regarding selecting and tagging more than 1000 samples at a go, I think this is a reasonable request. If you have a master folder of things like drum one shots, you would certainly want to be able to bulk apply basic tags like "Snare" or whatever. So I'm surprised that this is a limitation.

[bitley]

Reason support issues should surely be better directed to Pheads imho There must be more to all this than "browser woes", for instance, just my view.

[moneykube]

Reason support issues should surely be better directed to Pheads imho There must be more to all this than "browser woes", for instance, just my view.

While we wait for support at "Reason Studios" (not Pheads)> to reply with a solution, after making a ticket >
"what "is the harm of trying to find our own solutions, within a forum thread of other users > that are indeed experiencing similar issues ?
Forums are all about that... or am I misinformed ?
Sometimes answers have been found by other users here > much quicker than the speed support seems to be working at to solve said issues.
People here have been helped on a number of issues > besides, and including browser issues
Just my view.
And why is "R13(.1) Browser woes" > now retitled this on the main forum page under reason general >> after I replied to you?

Screen Shot 2025-01-10 at 1.23.50 PM.png

Another glitch in the matrix? I replied to your other thread about your competition > just before replying here.
Follow the white rabbit into the future

[joeyluck]

Reason support issues should surely be better directed to Pheads imho There must be more to all this than "browser woes", for instance, just my view.

While we wait for support at "Reason Studios" (not Pheads)> to reply with a solution, after making a ticket >
"what "is the harm of trying to find our own solutions, within a forum thread of other users > that are indeed experiencing similar issues ?
Forums are all about that... or am I misinformed ?
Sometimes answers have been found by other users here > much quicker than the speed support seems to be working at to solve said issues.
People here have been helped on a number of issues > besides, and including browser issues
Just my view.
And why is "R13(.1) Browser woes" > now retitled this on the main forum page under reason general >> after I replied to you?
Screen Shot 2025-01-10 at 1.23.50 PM.png
Another glitch in the matrix? I replied to your other thread about your competition > just before replying here.
Follow the white rabbit into the future

Well technically the nickname "propellerheads" can still be used for tech nerds. We can all be propellerheads who use Reason

The comment you are quoting was posted to the wrong thread and moved here, and looks like the topic title for that comment moved with it. I fixed it.

[moneykube]

Well technically the nickname "propellerheads" can still be used for tech nerds. We can all be propellerheads who use Reason
The comment you are quoting was posted to the wrong thread and moved here, and looks like the topic title for that comment moved with it. I fixed it.

thanks... yes my main shortcut and folder > is still called propellerheads to this day.

[bitley]

I looked at my self made haircut the other day and yes. Propellerhead.

[moneykube]

I looked at my self made haircut the other day and yes. Propellerhead.

Outstanding
I do my own propellerhead haircuts as well

[MrFigg]

And that's the Browser trying to index again. Can't access any refills. Pretty grim.
Is it possible that it re-indexes every time a new device is installed?

[moneykube]

And that's the Browser trying to index again. Can't access any refills. Pretty grim.
Is it possible that it re-indexes every time a new device is installed?

The manual says indexing is constant for some odd reason.
You would think once it has indexed everything it would know where stuff was... but no.
R13 starts -indexing when just loading an instrument or patch. This happens if you drag it in from your drive or use the browser.
Soooo... a new device is also very likely, and very probable.
There is a lot of waiting involved in this workflow improvement.

[Heigen5]

But indexing used to be perfect in the R12 - why did it need to be changed?

[jam-s]

But indexing used to be perfect in the R12 - why did it need to be changed?

One word: Tags

[selig]

But indexing used to be perfect in the R12 - why did it need to be changed?

One word: Tags

This is why programmers laugh when folks make a “simple” suggestion for a feature to be added, and say “it should be easy, it’s just a few lines of code”.

[Arrant]

And that's the Browser trying to index again. Can't access any refills. Pretty grim.
Is it possible that it re-indexes every time a new device is installed?

Same here, it never settles down and stabilises for a longer period. There’s always going to be changes on a disk (not Reason-related), which is why I keep thinking that scanning everything is the wrong design.

[Heigen5]

One word: Tags

This is why programmers laugh when folks make a “simple” suggestion for a feature to be added, and say “it should be easy, it’s just a few lines of code”.

Is true for lots of the things indeed. But every developer is different and there might be lots of differences how well something was developed.

[buddard]

And that's the Browser trying to index again. Can't access any refills. Pretty grim.
Is it possible that it re-indexes every time a new device is installed?

Reason does rescan on every startup and at regular intervals (and immediately when a change is detected in a shortcut etc), but it should be much faster and only affect things that actually changed (for example., a ReFill or RE is not rescanned unless it has a new date or version).

It doesn't sound right that you can't access ReFills during this time -- Sounds like a bug.

[Heigen5]

(for example., a ReFill or RE is not rescanned unless it has a new date or version).

Yes, one would think that this kind of a method i.e. only scanning for new content would be part of the system. Even though my experience with R13.1 seems pretty good. When I open R13 and press Browser, I can see the indicators appearing every time, but they disppear in few seconds and things are settled for me.