R13 (.1) Browser woes

[WOO]

I did a little test today. I opened up reason 11 suite and it started up in in less than 2 minutes. I then opened up an old project done in 11 and it loaded up in seconds. Closed out of 11 opened up reason 13. It took 10 minutes for 13 to open up. Loaded up the same project that took seconds to load in 11 and it took a minute to open in 13. All the while the spinning wheels denoting indexing? were spinning wildly and was very slow to open up folders. I have not added one item to this computer since installing this latest update. In fact I have started up reason and then just left it unattended for hours and hours on two occasions now, since the latest update letting it index to its heart content.

[WOO]

I started up reason today and it took 11 minutes to open a blank project and as a test I turned off anti virus software to see if that might be causing the slow start up this time. It didn't. As soon I the empty project opened, I opened the browser and sure enough the all locations spinning wheel was doing its thing. But today my packs and refills folder are showing nothing in them whereas last night they were just fine. All I did was use reason for a few hours last night shut it down btw it shuts down much quicker, and then today start it up and besides taking an extra minute more than the day before to start, my refills and packs folder are empty. What is going on with this messed up program? I still have 11 suite and it loads up 5 times faster, about 2 minutes but also when I load up something in 11 suite it loads in seconds whereas in 13 it can take minutes for a project to open up. And this nonstop indexing is using some serious resources on my system. Anyway to shut off indexing? Are the folks at reason looking into that feature or are the just going to move on, as this issue is not worth fixing? I know I can file a ticket with them but in all the years of filing tickets after much back and they still have never resolved one issue.

[MrFigg]

Hmm. Yeah. Not wanting to repeat the same thing over but this browser thing is really making the program unusable for me at the moment. I hope very much that they’ll find the problem and not just take it over to the next Reason release.

[mind2069]

Hmm. Yeah. Not wanting to repeat the same thing over but this browser thing is really making the program unusable for me at the moment. I hope very much that they’ll find the problem and not just take it over to the next Reason release.

Is the browser that bad for everybody or is it only certain computers/cpu

I've been waiting to upgrade from 12 but they just cant seem to nail the browser, have all the senior developers quit at reason studios

We have been into this browser talk for such a long time, it's getting ridiculous, why have they gone in a route that they cant solve, the browser works fine on Reason 12, they could of just keep making it better from what seemed to be a more solid foundation.

I havent hear any other daw's having a browsers issue stick for such a long time, maybe it's me because I'm not on all other forum, is the browser an issue every daw struggle with?

[joeyluck]

Hmm. Yeah. Not wanting to repeat the same thing over but this browser thing is really making the program unusable for me at the moment. I hope very much that they’ll find the problem and not just take it over to the next Reason release.

Is the browser that bad for everybody or is it only certain computers/cpu

I've been waiting to upgrade from 12 but they just cant seem to nail the browser, have all the senior developers quit at reason studios

We have been into this browser talk for such a long time, it's getting ridiculous, why have they gone in a route that they cant solve, the browser works fine on Reason 12, they could of just keep making it better from what seemed to be a more solid foundation.

I havent hear any other daw's having a browsers issue stick for such a long time, maybe it's me because I'm not on all other forum, is the browser an issue every daw struggle with?

No it is not for everybody. Certain people have different experiences with their particular setups. It's important to remember to report your specific issues and not assume that they are known issues or that your issues are the same as others, caused by the same things.

[Mataya]

Working in 13, 6 months after purchase...browsing after a 27 hours of indexing. Finally have a nice loop going. Open the browser again, Reason not responding with a buzz sound coming from speakers. I know I can "file a ticket", but god damn how many tickets do you need to figure out it's not working properly? Just give me an alternative like when it actually worked and we can all go browsing our own way. Feels like with every major release a new thing comes up that keeps pushing me away from it and yet I keep on upgrading. How stupid am I?

M

[SoundObjects]

Lucky I don't have problems with my own Reason 13.2 browser using Windows.
But I think to remember from an other DAW that Windows Explore indexer
could cause problems.
Maybe try turning it on or off in Windows settings.

[jam-s]

Is the browser that bad for everybody or is it only certain computers/cpu

It seems to get worse the more Refills, patches, and sample content you have in the folders that are indexed (by default). Using HDD's for storage instead of SSD's also seems to worsen the situation.

[WOO]

Lucky I don't have problems with my own Reason 13.2 browser using Windows.
But I think to remember from an other DAW that Windows Explore indexer
could cause problems.
Maybe try turning it on or off in Windows settings.

Didn't work for me. But thanks for the tip. I know the folks over at reason spent a massive amount of time tagging everything so at the very least once its done indexing have the option to turn it off.

[SoundObjects]

Is problems the same at Mac and PC Windows platforms ?
Because it works on some computers it could be some third party
conflict thing.

Once there also was a problem with viruscheckers checking the index
files everytime they changed (indexing).
This might also be worth to check.

[ambi]

I did a little test today. I opened up reason 11 suite and it started up in in less than 2 minutes. I then opened up an old project done in 11 and it loaded up in seconds. Closed out of 11 opened up reason 13. It took 10 minutes for 13 to open up. Loaded up the same project that took seconds to load in 11 and it took a minute to open in 13. All the while the spinning wheels denoting indexing? were spinning wildly and was very slow to open up folders. I have not added one item to this computer since installing this latest update. In fact I have started up reason and then just left it unattended for hours and hours on two occasions now, since the latest update letting it index to its heart content.

If it takes you 2 minutes to open Reason 11 or 10 minutes to start Reason 13, you probably need a new computer. Even on my 14 year old laptop Reason 13 starts within 5-15 seconds.

The browser's performance is not my main problem. But I think it has a lot of workflow issues and the more I work with the new browser, the more workflow issues I do find.

Currently I try to avoid opening the browser whenever I can and often use the Windows Explorer instead to do things like putting samples into places.

[Exowildebeest]

I don't understand why this new browser needs to spend absurd amounts of time "indexing" (millions of samples and patches in thousands of folders) in the first place. Just open the folder and show me the contents, for goodness sake. Windows Explorer and many other software and utilities do that just fine. Why the struggle here? If it has anything to do with the new "tagging" feature, then just ditch it. It's hardly an essential feature.

I was going to complain about the lack of colour in the new browser - coloured file icons are a very useful visual cue for quickly identifying what you're looking at - but that seems like a minor issue now...

[Mataya]

Seems like browser is indexing stuff that are in my system32 folder or any. I think the problem would be much smaller if I could just point the browser to a folder/folders I want it to look for samples. Like in FL studio. No need to search on all my drives, every folder etc. Is he going trough my sampler sample banks with .wav's? I don't need those to be "indexed" or whatever. Not every . wav on my PC is important for my production. I don't understand really how it works, but I can see it's not good for me.

tx
M

[WOO]

I have a bunch of waves plugins which are known to slow down the opening of reason. I also have a bunch of ujam plugins and I believe ujam runs thru some verification process before starting up which may slow down the loading but I'm not sure. Maybe someone could enlighten me as to whether or not that could be a problem with ujam plugins. I most certainly need a new computer as this hp windows desktop may be as old as 10 years maybe more, but its well within the specs for reason 13. As to the very long loading times that started as soon as I updated to 13 and has gotten worse with each update. It also seems to get a little jiggy every time windows updates itself. It could be a hardware issue. But what I do know is the indexing runs nonstop while reasons running which causes the occasional playback hangs and glitching.

[esme]

my browser is random
sometimes index sometime not
sometime fast sometime slow
no sense and not right

[Arrant]

my browser is random
sometimes index sometime not
sometime fast sometime slow
no sense and not right

Those are great lyrics for the next Reason Studios competition

[vondersulzburg]

By Suno

https://suno.com/song/a64d033c-1baf-47d ... 0fO2EOEa7a

[WOO]

By Suno

https://suno.com/song/a64d033c-1baf-47d ... 0fO2EOEa7a

Now that's funny. Well done. Maybe we could have a contest immortalizing the many bugs in reason in song fashion like you just did.

[selig]

Current Reason 13 startup time: 12 seconds. Past versions took only 11 seconds. Totally acceptable for me.

The only thing I can suggest is to keep digging as to why some folks are having issues and others are having none.

In that spirit, here’s my current setup. I’m running a system a few years old (2022):
Mac Studio M1 Max w/32 GB RAM running Sequoia 15.1.1.
I have a 2TB internal SSD that has 1.36 TB free (could be a factor), with samples stored on external SSD.
16 GB samples, 20k items.
48 GB ReFills, 21k items.
18 GB VST3s, 438 items.
20 GB AU, 724 items.
205 REs.

Reason indexing hasn’t taken any longer for me than it does with LUNA or Resolve.
I’ve never seen it indexing a second time except for after I’ve updated plugins or added new plugins.
That’s all I got, unless I’m forgetting something?
[update: just updated to Arturia X and re-indexing took just over one minute longer than normal booting.]

[Arrant]

Good job on the browser song dude

Current state of affairs:
While indexing is in progress, patch selector arrows do not work from any device. Once indexing is done, they work fine.
The browser still takes time to fill up if I select locations with a lot of patches in them, but it does work. Slightly annoying, but workable.

I have taken previous posters' advice of removing the big PX7 refills, reducing the amount of patches by around 250.000.
This does help. Upgrading to 13.2 also helped considerably.

Functionally I am far from happy with the browser and want it gone, but at least now I can see how it works.

[aquil]

If it takes you 2 minutes to open Reason 11 or 10 minutes to start Reason 13, you probably need a new computer. Even on my 14 year old laptop Reason 13 starts within 5-15 seconds.

Nah, I think it just shows that Reason 13 isn’t fully optimized yet. We all have multi-core processors these days, so they could definitely load a bunch of stuff in parallel. So why does Reason 13 take so much longer to start compared to Reason 11? Probably because things like browser database initialization and maybe even index refreshing are handled in a way that seriously slows down the startup, depending on your storage hardware and the amount of patches, samples, and so on.

[jam-s]

Even loading the SQlite database that contains the file index data can take some time if it has grown to several GiB in size.

[StephenHutchinson]

Today I tested the browser wait times with Reason 13.1d330 on both my MacMini M1 and M4.

Both R13.1 machines have the exact same folder structure, and are on separate SSD drives. The contents contain ReFills, patches etc. for a total of 254,385 items

The MacMini M1 clocked in a 3 minutes 50 seconds
The MacMini M4 clocked in at 1 minute 18 seconds

I haven't upgraded to 13.2 as of yet on these machines because when I installed 13.2 on a laptop, I was met with the insanity of having to manually delete hundreds of "stranded" or "missing" shortcuts one at a time.