Select Next Patch... Broken?

[Sargie]

In Reason 13 the select next / previous patch buttons don't seem to do anything... sometimes they work after an interminable wait... sometimes they don't seem to work at all. Same thing for clicking on the "name of the patch" window.

Both these used to be instant in Reason 12... now it seems I have to go into the Browser to choose a new patch in any reasonable amount of time.

Anyone else seeing this? Am I doing something wrong?

[aquil]

I can confirm. It works, but they are just extremely delayed.

[MattiasHG]

In Reason 13 the select next / previous patch buttons don't seem to do anything... sometimes they work after an interminable wait... sometimes they don't seem to work at all. Same thing for clicking on the "name of the patch" window.

Both these used to be instant in Reason 12... now it seems I have to go into the Browser to choose a new patch in any reasonable amount of time.

Anyone else seeing this? Am I doing something wrong?

Please report this to support and include when it doesn't work. Specific instruments or patches loaded? What happens? It should work and has been working during beta test too, so we'd appreciate your help in pinning down what would cause your issue.

[Deep Schulzz]

In Reason 13 the select next / previous patch buttons don't seem to do anything... sometimes they work after an interminable wait... sometimes they don't seem to work at all. Same thing for clicking on the "name of the patch" window.

Both these used to be instant in Reason 12... now it seems I have to go into the Browser to choose a new patch in any reasonable amount of time.

Anyone else seeing this? Am I doing something wrong?

Exactly the same here....

[aquil]

Please report this to support and include when it doesn't work. Specific instruments or patches loaded? What happens? It should work and has been working during beta test too, so we'd appreciate your help in pinning down what would cause your issue.

I’ve just created a ticket (#179302). I also recorded a short video and noted it in the ticket. My assumption is that it mainly occurs when browsing samples, especially if you have a large sample library. Maybe the search generally becomes slower when the index database is very large.

[esme]

ive found the new browser good but much slower than the old one especially on those next/prev buttons and also clicking on the patch name in an instrument it can take 2 or 3 seconds to show me the other patches. in reason 12 it is instant.

but i do love the new browser on the whole. id like to move it to another screen and have it stay there.

[Aosta]

ive found the new browser good but much slower than the old one especially on those next/prev buttons and also clicking on the patch name in an instrument it can take 2 or 3 seconds to show me the other patches. in reason 12 it is instant.

but i do love the new browser on the whole. id like to move it to another screen and have it stay there.

Isn't R13's tag line 'Your sound, faster'?
Not at the moment

[rorystorm]

definitely a significant lag if I try and change to the next patch using the arrow keys on the device. New patch is instantaneous using the browser.

make of that what you will.

[Loque]

I speculate the a re-indexing is going on. Maybe there are also external hard drives, large files or big folders involved.

Maybe also old cache files create problems and it could be a good idea to delete them.

[MattiasHG]

I speculate the a re-indexing is going on. Maybe there are also external hard drives, large files or big folders involved.

Maybe also old cache files create problems and it could be a good idea to delete them.

Yeah, that's what we're looking at now too. In the report we've gotten we found one culprit was an external drive that was still indexing and another was a Dropbox folder that was not sync'd offline.

Please continue sending reports, support will ask you to run a logging version so you can send us logs which will help a lot in pinning down when it might be slow. They also have additional steps to try.

[esme]

i dont use an external drive and i dont keep any reason files in dropbox. i dont have very many files or refills either. how can i tell if it is still indexing?

id probably be happier with the slow listing if i had never experiences the instant version in reason 12!
even if it stays as it is i much prefer the new browser to the old one even if it feels very slow in places.

[chimp_spanner]

Up/down arrows working okay over here. MBP M1 Max and M3 Max, Sonoma 14.5.

Also, I didn't realise these would go up and down the same as if you were in your tagged browser session. So that's actually really cool.

**EDIT: okay no scratch that, having to press buttons multiple times to change presets on a device. Weird, definitely didn't notice that in testing.
**ANOTHER EDIT: scratch *that*, it's Synchronous specifically that's doing it because there are duplicate patch names in different parent folders. Everything else is working fine.

[chimp_spanner]

I speculate the a re-indexing is going on. Maybe there are also external hard drives, large files or big folders involved.

Maybe also old cache files create problems and it could be a good idea to delete them.

Yeah, that's what we're looking at now too. In the report we've gotten we found one culprit was an external drive that was still indexing and another was a Dropbox folder that was not sync'd offline.

Please continue sending reports, support will ask you to run a logging version so you can send us logs which will help a lot in pinning down when it might be slow. They also have additional steps to try.

Should we just submit bugs through the normal channel or should I use my beta profile?

[RandomSkratch]

...because there are duplicate patch names in different parent folders.

I thought the duplicate issue was going to be resolved in the new browser but I was wrong. I don't know why they kept the same folder structure. If a patch is a featured patch, it was included in the root of the device's patches AND in the assigned category subfolder. With Tags, you don't need a file/folder display, just tag something as "device showcase" or "featured" or something... Or force the browser to hide duplicate patches when in flat mode.

[MattiasHG]

Yeah, that's what we're looking at now too. In the report we've gotten we found one culprit was an external drive that was still indexing and another was a Dropbox folder that was not sync'd offline.

Please continue sending reports, support will ask you to run a logging version so you can send us logs which will help a lot in pinning down when it might be slow. They also have additional steps to try.

Should we just submit bugs through the normal channel or should I use my beta profile?

Both works

[PeZiK]

I speculate the a re-indexing is going on. Maybe there are also external hard drives, large files or big folders involved.

Maybe also old cache files create problems and it could be a good idea to delete them.

Hi, I'm experiencing this dreadful lag in the new browser. Has this been fixed?

Where can I find those old cache files on Windows 11 to delete?

P.

[Loque]

I speculate the a re-indexing is going on. Maybe there are also external hard drives, large files or big folders involved.

Maybe also old cache files create problems and it could be a good idea to delete them.

Hi, I'm experiencing this dreadful lag in the new browser. Has this been fixed?

Where can I find those old cache files on Windows 11 to delete?

P.

viewtopic.php?f=4&t=7514631

[PeZiK]

Thanks Loque - this should be a sticky!

Edit : it is a sticky, silly me.

P.

[hamsterfactor]

Ah, so this bug is still there. I reported it during the initial beta testing for 13.

After 13 was released I was unable to confirm, since further testing of 13 requires a license (or R+).

[PhillipOrdonez]

Ah, so this bug is still there. I reported it during the initial beta testing for 13.

After 13 was released I was unable to confirm, since further testing of 13 requires a license (or R+).

It’s not there anymore