I was transferring old projects to the new versions and noticed that MuLab doesn't use the clipboard when copying notes, tracks, etc.
As I understand it, copying occurs in the local memory of the running application, and data cannot be copy-pasted even between two running apps with the same version.
I think this feature should be added. I can imagine that when the tenth version of the program comes out, and I won't be able to convert projects made on the previous version for... god knows what reason (MuLab 8 very often could not convert projects made on MuLab 7), then at least I will be able to copy-paste notes. It will be much faster than exporting MIDI for each separate track.
MuLab should use the clipboard
-
- KVRAF
- 13862 posts since 24 Jun, 2008 from Europe
MuLab 8 can load projects made with MuLab 7.
In fact MuLab 9 can load any project made with any version of MuLab, even MuLab 1, be it that it might need 1 or 2 conversion steps, depending on how old the project is.
For all projects made with MuLab 4 or up, it only takes a single conversion step to load it into MuLab 9: Open the project in MuLab 8 and resave it.
In fact MuLab 9 can load any project made with any version of MuLab, even MuLab 1, be it that it might need 1 or 2 conversion steps, depending on how old the project is.
For all projects made with MuLab 4 or up, it only takes a single conversion step to load it into MuLab 9: Open the project in MuLab 8 and resave it.
-
- KVRer
- Topic Starter
- 6 posts since 10 Dec, 2022
I can't. If your program leaves a log file somewhere with debug information about why the conversion failed, I could attach it in the next message.mutools wrote: Tue Aug 06, 2024 5:12 pm MuLab 8 can load projects made with MuLab 7.
Open the project in MuLab 8 and resave it.
You do not have the required permissions to view the files attached to this post.
-
- KVRAF
- 13862 posts since 24 Jun, 2008 from Europe
Log files are stored in your MuLab/User/LogFiles subfolder.
Please email the corresponding logfile for the screenshot you shared to
Please email the corresponding logfile for the screenshot you shared to
-
- KVRAF
- 13862 posts since 24 Jun, 2008 from Europe
It has nothing to do with the fact that it is a MuLab 7 file.
The log file contains an Out Of Memory error.
You're using MuLab 8 32 bit so you're limited to theoretically 4 GB in total, but practically that will be less.
Try using MuLab 8 64 bit. That will enable all available RAM you have in your system.
The log file contains an Out Of Memory error.
You're using MuLab 8 32 bit so you're limited to theoretically 4 GB in total, but practically that will be less.
Try using MuLab 8 64 bit. That will enable all available RAM you have in your system.
-
- KVRer
- Topic Starter
- 6 posts since 10 Dec, 2022
Thank you, this really helped, I was able to open the project.mutools wrote: Tue Aug 06, 2024 6:09 pm Try using MuLab 8 64 bit. That will enable all available RAM you have in your system.
Now the second problem is that MuLab 8 Free only has 32-bit version for Windows while MacOS has 64-bit.
I downloaded the legacy version, but it is labeled as "Demo" and does not allow me to save the project.
You do not have the required permissions to view the files attached to this post.
-
- KVRAF
- 13862 posts since 24 Jun, 2008 from Europe
I see that you have a MuLab 9 App User Key so i've emailed you a temporary MuLab 8 User Key so that you can use MuLab 8 to upgrade all your MuLab 7 projects and make them compatible with MuLab 9.
I know the conversion step is not funny but up to now there are only 2 points in the whole MuLab lifetime ( = 20 years) where there was a project file data break: MuLab 4 and MuLab 9. It really is necessary, for R&D healthiness, that sometimes old legacy code ballast is dropped, but with the conversion bridge, so that no single project is lost.
Be sure to have a look at this doc page: https://www.mutools.com/info/M9/docs/mu ... jects.html
It contains useful info to optimize the upgrade process.
I know the conversion step is not funny but up to now there are only 2 points in the whole MuLab lifetime ( = 20 years) where there was a project file data break: MuLab 4 and MuLab 9. It really is necessary, for R&D healthiness, that sometimes old legacy code ballast is dropped, but with the conversion bridge, so that no single project is lost.
Be sure to have a look at this doc page: https://www.mutools.com/info/M9/docs/mu ... jects.html
It contains useful info to optimize the upgrade process.
-
- KVRist
- 120 posts since 9 Apr, 2023
You mean like having two Mulabs open, the same MuLab 9,
and copying something from one project open on one, into a project opened in another one?
I tried that, when I was trying to rebuild a Mux from a former project in a new project.
It doesn't work.
It can be worked around in 2 or three steps,
but it might be a useful extra ability if it could do that.
and copying something from one project open on one, into a project opened in another one?
I tried that, when I was trying to rebuild a Mux from a former project in a new project.
It doesn't work.
It can be worked around in 2 or three steps,
but it might be a useful extra ability if it could do that.