I’m not sure what you mean by “workflow”, though. If it is continuously writing it has a very hard time reading the index.
#BPM SUGGESTER TRIAL#
If you have no large locations and observe the index cache not increasing make a backup of the file it will save time if you are going the trial and error route to find what folders or locations cause the slow indexing read/write. After I removed large locations from my lists I added them back in manually after rebuilding and observed how quick it would be added to the index, sometimes you have to open the folder you added to initialise indexing though. Building the index should be quick enough, depending on how much data there is in your lists it should take between 20 - 30 mins (based on my data that was about 200gb).
It will rebuild as soon as it opens, if it takes a long time to build there is something causing it to write and delete data simultaneously, the only way to tell for sure if it is doing this is to rebuild fully and when finished it will be increasing/decreasing by about 4bits every second or so, if it is building by about 4 bits per/second it means something is fucky. Windows: %AppData%\Local\Propellerhead Software\Reason MacOS: ~/Library/Application Support/Propellerhead Software/Reason/Plugin Screenshots The file should be named _ReasonIndex_v4.dat found in these locations: Once you delete the index file it will rebuild when you start reason again. The old indexed data will still be in the index file. If your index file is doing this or has done this I'd recommend rebuilding it if you condensed your lists. The index file appears to write then delete the data constantly when the bug occurs. Mine is working well at the moment and opens quick after moving some older refills out of indexed folders and rebuilding the index. I spent about 4-5 days trying to investigate what might be causing it and came to the conclusion that it is based on either large locations (1 to 100gb and over), duplicated refills, or corrupt data or bad samples in the folders, I've no idea what the cause is though. favo list (loading bar every time you reopen reason) it means the indexing is not working as it should, when indexing is working it opens locations extremely quick and searching everywhere is responsive. If it is falling back on that old search opening folders and.
What happens if you make a backup when no issue occurs, set the backup to read-only and restore/replace it after a reboot. Its only now after rebooting my whole computer that the problem has returned.ĭo you think what I've posted is a solution in search of a problem, or a problem in search of a solution. I can restart Reason and the problem is still gone, so there were no more "logical conclusions" to make other than to expect that this was a suitable fix.
The problem goes away after deleting the index and letting it rebuilt. I don't know if you're trying to be helpful or condescending but I'll add some more info. When you start adding things back in and the issue occurs again, then the logical conclusion is whatever is put back in is what is causing the issue, you can and have to narrow it down to what is causing it to perform slow, it is just basic troubleshooting of the problem but it can take time to do so because once the index is corrupted you have to rebuild it without that folder or thing you added. So in order find out what that is you have go back to the basic list by removing things and rebuilding, namely large locations. If the issue is still present after deleting the index and reason rebuilds it then logical conclusion is that there is something in your lists making it perform slower than its designed speed. Well there is a little more to it than just deleting and rebuilding.
0 kommentar(er)
