I have a project that crashed when loading a waves plugin into P&M Chainer. MuLab saved the crashed project but I cannot open the saved crashed project or the original. What I'd like to do would be open the MUPROJECT File and edit it to remove the last plugin added. I believe it would then open. In Orion when something like this happened I could open an empty session and merge a project that crashed by selecting the plugins I wanted to load. Is there any way I could do something like that?
Thanks
Edit a project
-
- KVRAF
- 13864 posts since 24 Jun, 2008 from Europe
When you savea project, MuLab first backups the previous versionofthe project file to X.PuProject.backup. Maybe you canuse that version?
-
- KVRist
- Topic Starter
- 388 posts since 28 Oct, 2002
Afraid not, it was a new (to me) error dialogue box with red background that said something about an error and saving it. That then was saved at a higher level than the user folder, both that and the original just will not open now and I would like to further work on them.mutools wrote:When you savea project, MuLab first backups the previous versionofthe project file to X.PuProject.backup. Maybe you canuse that version?
-
- KVRAF
- 13864 posts since 24 Jun, 2008 from Europe
-
- KVRist
- Topic Starter
- 388 posts since 28 Oct, 2002
That's strange, when I open the MuLab folder I can see "Berlin 3 cs#Crashed" ( Berlin 3 cs was the original working title) the file at the highest level not in, user/library/MuProject. But still, I cannot open it, or Berlin 2, (I saved it as V3 due to the significant changes I was making). As I said is there any way I can "open" the file to edit it so I can open it again?mutools wrote:The backup file is in the same folder as your original project file.
-
- KVRAF
- 13864 posts since 24 Jun, 2008 from Europe
If you can't find it manually, try searching your computer for *.MuProject.Backup" files.heks wrote:That's strange, when I open the MuLab folder I can see "Berlin 3 cs#Crashed" ( Berlin 3 cs was the original working title) the file at the highest level not in, user/library/MuProject. But still, I cannot open it, or Berlin 2, (I saved it as V3 due to the significant changes I was making).mutools wrote:The backup file is in the same folder as your original project file.
No.As I said is there any way I can "open" the file to edit it so I can open it again?
-
- KVRAF
- 1925 posts since 29 Mar, 2013
Just a thought.
if you know which plugin caused the crash, would renaming that plugin temporarily, so Mulab couldnt load it, allow Mulab to open the project but with a report that it couldnt find it.
if you know which plugin caused the crash, would renaming that plugin temporarily, so Mulab couldnt load it, allow Mulab to open the project but with a report that it couldnt find it.
Beauty is only skin deep,
Ugliness, however, goes right the way through
Ugliness, however, goes right the way through
-
- KVRAF
- 13864 posts since 24 Jun, 2008 from Europe
Yes good idea, that might work, depending on what happened during the VST saving its data. It's certainly worth a try.
-
- KVRist
- Topic Starter
- 388 posts since 28 Oct, 2002
Thanks bibz1st, just tried that and it did not open, didnt seem to even start to load or look for anything.. Found a backup file but it opens with notepad not MuLab. I'll call it quits with that tune and it looks like I cant use my waves plugins as they or the hosts make Mulab unstable.bibz1st wrote:Just a thought.
if you know which plugin caused the crash, would renaming that plugin temporarily, so Mulab couldnt load it, allow Mulab to open the project but with a report that it couldn't find it.
Thanks for both of you trying to help. 
-
- KVRAF
- 13864 posts since 24 Jun, 2008 from Europe
As stated in the docs: You first have to rename the .Backup file tosome new name with extension .MuProject.
-
- KVRist
- Topic Starter
- 388 posts since 28 Oct, 2002
Oh!,,, will try that. Sorry, I prefer to make music rather than readmutools wrote:As stated in the docs: You first have to rename the .Backup file to some new name with extension .MuProject.
-
- KVRAF
- 13864 posts since 24 Jun, 2008 from Europe
Pls do read thedocs, they're full of relevant info. The time i have to repeat things here slows down the R&D of new versions. Not said in a harsh way, said in a mathematical way, there are only a limited number of working hours per day and i'm but a single indie dev. Thx for your understanding.
Apart from that: I've taken note about checking if i can improve that backup naming from X.MuProject.Backup to X.Backup.MuProject, that would be more logical and easier for the user. Will check that at some later time.
Apart from that: I've taken note about checking if i can improve that backup naming from X.MuProject.Backup to X.Backup.MuProject, that would be more logical and easier for the user. Will check that at some later time.
-
- KVRist
- Topic Starter
- 388 posts since 28 Oct, 2002
Thanks Jo, I eventually got a backup version working. I found one of win 10's updates had turned the view "file name extensions" off, so I was changing what was visible pointlessly. Did read that section of MuTools Docs and realised I had read it when I first bought MuLab, but at the time was not relevant to getting up and going with my new purchase.
I have spent some time this morning reading MuDoc's Questions & Answers and Troubleshooting. I did notice that some of the answers assumed a MuLab conceptual language which don't register unless you speak "MuTool" and although I'm new to MuLab I've been using various DAWS since 2002 I found I did have to read a number of sections a few times to "get it". So, I'm wondering if it would be helpful for users who have a problem, to read a "problems sticky thread" (a bit like support pages have) with links to the relevant MuTools Docs and threads that cover the solution (I know there's a search facility ,,,but have you ever used it? life too short trawling though pages and pages of posts containing "Mu" this and that which are vaguely associated to the topic) . I'm not suggesting Jo does this, possibly appoint some mods to manage it?
Why suggest this? One fundamental problem I have noticed reading Kvr over the years, is when "problem solving", power users and new users have experiential and conceptual Knowledge differences (besides normal language barriers) . The "newbie" may have a gap in knowledge or terminology and the power user subconsciously presumes that's a "known", therefore delivers advice at a level that basically "does not compute" for the "newbie". It can be a difficult line to walk between spoon feeding and knowledgeable jargon. Which is why a sticky link thread may be useful facility
What does everyone else think?
I have spent some time this morning reading MuDoc's Questions & Answers and Troubleshooting. I did notice that some of the answers assumed a MuLab conceptual language which don't register unless you speak "MuTool" and although I'm new to MuLab I've been using various DAWS since 2002 I found I did have to read a number of sections a few times to "get it". So, I'm wondering if it would be helpful for users who have a problem, to read a "problems sticky thread" (a bit like support pages have) with links to the relevant MuTools Docs and threads that cover the solution (I know there's a search facility ,,,but have you ever used it? life too short trawling though pages and pages of posts containing "Mu" this and that which are vaguely associated to the topic) . I'm not suggesting Jo does this, possibly appoint some mods to manage it?
Why suggest this? One fundamental problem I have noticed reading Kvr over the years, is when "problem solving", power users and new users have experiential and conceptual Knowledge differences (besides normal language barriers) . The "newbie" may have a gap in knowledge or terminology and the power user subconsciously presumes that's a "known", therefore delivers advice at a level that basically "does not compute" for the "newbie". It can be a difficult line to walk between spoon feeding and knowledgeable jargon. Which is why a sticky link thread may be useful facility
What does everyone else think?-
- KVRAF
- 5383 posts since 25 Jan, 2014 from The End of The World as We Knowit
Personally, I observe that many problems are specific to one user, so a sticky may not save time. I actually recommend reading the Docs, exploring the right-click context menus, and taking apart a Demo. The Docs are not long, have lots of pictures with links to videos, and a Search. I find MuLab is very consistent, so understanding how it is organised will increase your enjoyment a lot!heks wrote:What does everyone else think?
Last edited by Michael L on Sat May 13, 2017 9:01 am, edited 1 time in total.
F E E D
Y O U R
F L O W
Y O U R
F L O W
-
- KVRAF
- 13864 posts since 24 Jun, 2008 from Europe
I agree with Michael. And i also don't want to duplicate info too much as it also means duplicate work. Best is to have a central docs, imho. They're the essential info sheets about MuLab and MUX Modular, together with the MuTools youtube tutorials at http://www.youtube.com/mutools
That said i commit to improve & extend these docs wherever necessary and maybe one day they'll also be more integrated with MuLab/MUX itself. But for complex apps like DAWs sometimes reading docs is inevitable, imho. Don't look at it as a waste of time, it's a gain in being creative with your tools.
That said i commit to improve & extend these docs wherever necessary and maybe one day they'll also be more integrated with MuLab/MUX itself. But for complex apps like DAWs sometimes reading docs is inevitable, imho. Don't look at it as a waste of time, it's a gain in being creative with your tools.