If I may ask, why do you have so many tabs open in the first place? Also, I'm pretty sure that it's "technically impossible" to just close the one faulty project you have while keeping others alive due to the way audio processing and computing works. And this isn't just an issue with Reaper as a software. Someone correct me if I'm wrong!
I know this isn't helpful to the actual issue, but I'll say it anyway.
These "problems" always turn out to NOT be a REAPER problem. It's always a rogue plug-in, user error, or some other thing that the user ends up coming back to say "I found the problem, it was because...." and the reason always turns out to be something OTHER than a REAPER issue.
Then, of course, there are those who have too much "pride" to actually come back and admit that their temper tantrum was completely mis-guided and mis-placed.
For some reason, today Reaper asked me if I wanted to open that failing project or not...I know it should do that, was wondering why it didn't..and now does... And yes, it opened up all projects except the one that failed (which would crash reaper entirely)
Thanks to Bruceqld though, you're the man!
Last edited by Torben Scharling; 07-10-2022 at 11:50 AM.
I know this isn't helpful to the actual issue, but I'll say it anyway.
These "problems" always turn out to NOT be a REAPER problem. It's always a rogue plug-in, user error, or some other thing that the user ends up coming back to say "I found the problem, it was because...." and the reason always turns out to be something OTHER than a REAPER issue.
Then, of course, there are those who have too much "pride" to actually come back and admit that their temper tantrum was completely mis-guided and mis-placed.
Your mis-guided and mis-placed unprovoked spew towards a stranger online, is something you will have to live with, not I.
Nowhere did I by the way talk about something OTHER than REAPER. I am specifically talking about how REAPER REACTS AND HOW IT BEHAVES AND DISBEHAVES
Last edited by Torben Scharling; 07-10-2022 at 11:51 AM.
If I may ask, why do you have so many tabs open in the first place? Also, I'm pretty sure that it's "technically impossible" to just close the one faulty project you have while keeping others alive due to the way audio processing and computing works. And this isn't just an issue with Reaper as a software. Someone correct me if I'm wrong!
Your mis-guided and mis-placed unprovoked spew towards a stranger online, is something you will have to live with, not I.
And your mis-guided and mis-placed paranoia and childish defensiveness is probably something you've been living with all your life.
Read what I said again. It was a general comment based on how often people come back and reveal that the problem had nothing to do with REAPER. I never said YOU had too much pride to come back and admit the fault was on your end, but the fact that it hit a nerve is pretty revealing.
Quote:
Nowhere did I by the way talk about something OTHER than REAPER.
Exactly. That was my point. Thanx for re-enforcing it.
In what way? Can you tell me a software that can only crash one project and not the main program?
Browsers, for example, sandbox tabs in subprocesses such that one crash won't tank the main process.
I suspect REAPER may be able to implement project (tab) isolation without a significant architectural overhaul, at least assuming the source of the crash is a plugin and not REAPER itself (which is typically the case). It already supports running FX in their own dedicated processes, or a single separate shared process. If it split the difference and had a separate process per project that hosted all the project's FX, it could insulate itself from a project-local crash caused by misbehaving FX in that project.
Browsers, for example, sandbox tabs in subprocesses such that one crash won't tank the main process.
I suspect REAPER may be able to implement project (tab) isolation without a significant architectural overhaul, at least assuming the source of the crash is a plugin and not REAPER itself (which is typically the case). It already supports running FX in their own dedicated processes, or a single separate shared process. If it split the difference and had a separate process per project that hosted all the project's FX, it could insulate itself from a project-local crash caused by misbehaving FX in that project.
Well, that's interesting! Thanks for correcting me, tack!
I do wonder though if that would be possible for DAWs such as Reaper? I doubt the only problem would be seperate fx processes...
Thread should be called "unasked questions" as the op deleted first post .mods please detete. useless now
Useless? The commentary by some of you is useless, I agree. If you where to ask kindly, perhaps we could get this thread back on the right track, and I could explain to you what happened and what needs to be fixed.
As Tack and I have tried to explain to you, this is not an uncommon practice in more mature software (that the main program does not crash, only the plugin or tab crashes and can be closed and re-opened inside the non-crashed program), and thus this should be high priority for any dev and user, regardless of useless questions such as the amount of open projects in tabs - this and other attacks or steering away from the topic, not trying to problem solve, is considered trolling and highly unappreciated.