Old 11-10-2018, 01:44 PM   #1
Eddy
Human being with feelings
 
Join Date: Jun 2017
Posts: 211
Default crashing - something is corrupted, but what?

Hi, I am demoing some plugins and they are crashing Reaper (portable install) on reopening projects. So I tried a fresh portable install and they work fine with that.

What files should I transfer from the new fresh portable install so that I keep all my existing modifications but just bring in a new working version of whatever is causing the crashing?

eg what .ini files

I really do not want to have to redo all my mouse modifiers, reinstall all my reapack stuff etc and start from scratch so any tips that can help me avoid that would be great

thanks, eddy
Eddy is offline   Reply With Quote
Old 11-10-2018, 02:49 PM   #2
solger
Human being with feelings
 
solger's Avatar
 
Join Date: Mar 2013
Posts: 3,139
Default

Are there perhaps any crash logs/reports which might give some hints about possible problem sources: https://forum.cockos.com/showthread.php?t=36653


In general, it's quite difficult to guess what might be causing issues without knowing more info. But you can basically try the following:

1) Make a backup of your current Reaper config by copying the entire portable Reaper folder to a different backup location and/or via Preferences > General > Export configuration (make sure that all category boxes on the left are checked)
2) Import only one config category at a time into a fresh portable install to see when or after importing which files things start to break
__________________
ReaLauncher
solger is offline   Reply With Quote
Old 11-10-2018, 02:53 PM   #3
Eddy
Human being with feelings
 
Join Date: Jun 2017
Posts: 211
Default

Quote:
Originally Posted by solger View Post
Are there perhaps any crash logs/reports which might give some hints about possible problem sources: https://forum.cockos.com/showthread.php?t=36653


In general, it's quite difficult to guess what might be causing issues without knowing more info. But you can basically try the following:

1) Make a backup of your current Reaper config by copying the entire portable Reaper folder to a different backup location and/or via Preferences > General > Export configuration (make sure that all category boxes on the left are checked)
2) Import only one config category at a time to see when (after importing which files) things start to break
thanks - I will give that a go - looks like something in the reaper.ini is crashing things
Eddy is offline   Reply With Quote
Old 11-10-2018, 03:14 PM   #4
Eddy
Human being with feelings
 
Join Date: Jun 2017
Posts: 211
Default

reaper.ini is the culprit. This has happened a few times to me over the years - How does one protect the reaper.ini file from being corrupted?
Or is this inevitable and I should back up the reaper.ini every few days so that I have a working version always at hand. If so is there a way to automate this backup process?
Eddy is offline   Reply With Quote
Old 11-11-2018, 03:17 AM   #5
solger
Human being with feelings
 
solger's Avatar
 
Join Date: Mar 2013
Posts: 3,139
Default

Quote:
Originally Posted by Eddy View Post
reaper.ini is the culprit. This has happened a few times to me over the years - How does one protect the reaper.ini file from being corrupted?
Or is this inevitable and I should back up the reaper.ini every few days so that I have a working version always at hand. If so is there a way to automate this backup process?
Yeah, it's a good strategy in general to make regular backups (time-wise and also before installing updates, just in case).

For automating the process you can use a file backup software to copy the entire portable Reaper folder - which already includes both the application & resource files (including the .ini config files) - automatically on a pre-defined schedule (like every day, week, month, etc.) to a pre-defined backup location. Available software options can vary depending on the operating system.





For trying to find the culprit inside the reaper.ini, you can basically try to compare the contents of the reaper.ini from a fresh install to the 'corrupt' reaper.ini - manually (via a text editor) or via a file comparison software. In case there aren't any obvious differences visible (like a specific preference is enabled in the 'corrupt' reaper.ini and not in the other one, or vice versa) you can try to merge the differences from the 'corrupt' reaper.ini file into a fresh one stepwise (section-by-section, block-by-block or line-by-line) until it breaks again in order to narrow down possible problem sources.

But it might probably take less time and effort to start with a fresh reaper.ini and going through the preferences again manually (after importing only the 'working' .ini config files)

If you like, you can attach the 'corrupt' reaper.ini to a post, as well. So I can also try to check if anything inside the file might look suspicious.
__________________
ReaLauncher

Last edited by solger; 11-11-2018 at 03:59 AM.
solger is offline   Reply With Quote
Old 11-11-2018, 04:04 AM   #6
Eddy
Human being with feelings
 
Join Date: Jun 2017
Posts: 211
Default

Quote:
Originally Posted by solger View Post
Yeah, it's a good strategy in general to make regular backups (time-wise and also before installing updates, just in case).

For automating the process you can use a file backup software to copy the entire portable Reaper folder - which already includes both the application & resource files (including the .ini config files) - automatically on a pre-defined schedule (like every day, week, month, etc.) to a pre-defined backup location. Available software options can vary depending on the operating system.





For trying to find the culprit inside the reaper.ini, you can basically try to compare the contents of the reaper.ini from a fresh install to the 'corrupt' reaper.ini - manually (via a text editor) or via a file comparison software. In case there aren't any obvious differences visible (like a specific preference is enabled in the 'corrupt' reaper.ini and not in the other one, or vice versa) you can try to merge the differences from the 'corrupt' reaper.ini file into a fresh one stepwise (section-by-section, block-by-block or line-by-line) until it breaks again in order to narrow down possible problem sources.

But it might probably take less time and effort to start with a fresh reaper.ini and going through the preferences again manually (after importing only the 'working' .ini config files)

If you like, you can attach the 'corrupt' reaper.ini to a post, as well. So I can also try to check if anything inside the file might look suspicious.
thanks solger - a very kind offer to have a look, but I have a new install working and will try a better backup strategy and see how that goes.


... But if this happens again I will be back
Eddy is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 05:09 AM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2018, vBulletin Solutions Inc.