Hello Jo,
for me this version is very instable. And I think I dont overuse my pc power. RAM is around 3 from 8 used, CPU is between 30 and 40 percent. After this crash I have told dealing with the different versions and the win 7 problem now lot of other crazy but repeated crashes:
I have loaded Avatar ST from H.G. . It works but as soon as I try to open it Puff.....
I deleted it, reloaded it but cant open again. So it is crazy: it IS in the project and runs but cant change anything with it.
Exactly the same with Stringstudio VST from AAS.
And with Kontakt, so it could not be blamed on the VST.
T-Racks S3 (the old Beat mag version) I can open in an empty project but not in the above mentioned project. The same with the above mentioned, opening in a new empty project works.
Maybe it would help if I turn "start logging" on, does it produce kind of logfile and where to find ?
The "felt" load of used instruments/samples/tracks/racks is maybe 2/3 of that when my Tracktion projects become instable so that could not be normal.
Kind regards,
Richard
For me instable ....
-
- KVRAF
- 13865 posts since 24 Jun, 2008 from Europe
I don't thinkM6.2.7 is "very instable". You're the first to say something like that. I recommend erasing all your MuLab installs and start from a completely fresh install. Then re-set everything, step by step, and insert relevant tests in between steps, so you know when something goes wrong. Then only use VSTs of which you are 100% sure they're rock solid. NI Kontakt definitely is a good VST plug-in, so if there are probs with Kontakt feel free to accurately describe the prob. So after this fresh install first add NI Kontakt and see how it works in a new session. Please stay cool and try to narrow down things in a logical and technical way.
-
- KVRAF
- Topic Starter
- 1670 posts since 13 Jan, 2014
O.k., I will do this and start from scretch. I am just little sad of loosing all the installed VST and the actual project though it was nothing really that importent.
Does that mean I will have to register the new version again ? Hope that wont give any problems with the already made registration cause I am not sure too find evry little "rest" of the old installations. Still dont understand how it comes to that path I have mentioned before:
C:\Users\User\AppData\Local\VirtualStore\Program Files (x86)\mulab-6-0-28-win32\User
Sorry if my critic sounded too harsh but I did not say it IS instable but just for ME it actually looks like. I have no experience with the UL version and with the Free version of course you did not have the possibility to reach the limits.
Kind regards,
Richard
Does that mean I will have to register the new version again ? Hope that wont give any problems with the already made registration cause I am not sure too find evry little "rest" of the old installations. Still dont understand how it comes to that path I have mentioned before:
C:\Users\User\AppData\Local\VirtualStore\Program Files (x86)\mulab-6-0-28-win32\User
Sorry if my critic sounded too harsh but I did not say it IS instable but just for ME it actually looks like. I have no experience with the UL version and with the Free version of course you did not have the possibility to reach the limits.
Kind regards,
Richard
-
- KVRist
- 117 posts since 7 Oct, 2014 from Suisse
Carrefull with Vst and Vsti ! I m currently sorting about 300 vst and vsti . Some of them can crash asio audio , some can crash mulab6 , and some of then can destroy a session.
I have even found presets in a working VstI who can crash asio audio......
Some vsti are working but are making a crash on next loading Vsti.
My advice try allways vst on a test session before using on a serious project. Make backup on session befor using VST.
If you have a problem with Vst look into VST manager if Vst has been disabled , and remove broken links.
Take care to use 32bit Vsti with 32bit Mulab and 64bit Vsti with 64bit Mulab.
C:\user.... is that your installation folder of Mulab ?? I hope no......
I have even found presets in a working VstI who can crash asio audio......
Some vsti are working but are making a crash on next loading Vsti.
My advice try allways vst on a test session before using on a serious project. Make backup on session befor using VST.
If you have a problem with Vst look into VST manager if Vst has been disabled , and remove broken links.
Take care to use 32bit Vsti with 32bit Mulab and 64bit Vsti with 64bit Mulab.
C:\user.... is that your installation folder of Mulab ?? I hope no......
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
That will happen if you do not read and follow the installation instructions.tatanka wrote:Still dont understand how it comes to that path I have mentioned before:
C:\Users\User\AppData\Local\VirtualStore\Program Files (x86)\mulab-6-0-28-win32\User
MuLab runs without Administrator privileges but - unless you change its default settings - stores data under the folder you installed it into.
Windows will not let an application write to the Program Files folder, to avoid installed programs getting corrupted.
What it does is fake up the names of files on disk. This makes it really, really difficult to understand what is happening on your own computer.
Therefore, the MuLab installation instructions clearly tell you not to install MuLab under the Windows Program Files folder, specifically in order to avoid problems with Windows interfering with the normal operation of MuLab.
-
- KVRAF
- 1925 posts since 29 Mar, 2013
I wouldnt rule out your pc being maxed out, especially if there is long release times or/and lots of reverb on the presets you were playing at the time. I say this as ive just had Mulab crash for the first time while using only 1 instance of Uhe Hive and all because of long reverb/release times and too many notes. I dont usually have problems so have put it down to that.
Not saying you dont know youre own pc but its something to investigate.
Not saying you dont know youre own pc but its something to investigate.
Beauty is only skin deep,
Ugliness, however, goes right the way through
Ugliness, however, goes right the way through
-
- KVRAF
- Topic Starter
- 1670 posts since 13 Jan, 2014
Hello,
thank you all for you thoughts and ideas. I think main problem might have been that I only used the free version over years and never cared about installation, just downloaded, unzipped wherever the downloaded file was and run it.
Never had ANY problems over the years, I think sometimes might have had up to ten different versions installed but as I said it never causes any problems. Maybe because of the only 4 tracks, maybe because of the only 8 VSTi, I dont know.
So when I finally bought the UL version I must admit (blame it on me I know) I dont really cared about intallation cause I thought I had enought experience with that over the years.
And eveb then have no problems when I copied the folder to the program directory UNTIL after some weeks I get a VSTi (Sampletank 2.5) with problems with the write protection. The normal solution I know from other DAW was just to run the DAW with administrator rights but that seems to be one thing you should not do at all in Mulab cause after that the problems begun.
To be doing it all the right way now could you please take a look to my second attempt and at the questions still left over:
- I will delete all mulab.exe and corresponding files/directories especially user directories
- Unzip the actual version again
- put the unzipped files just direct under C:/mulab
- Then start the program from there and put the user key in the program again
- Hope that runs
- Then start evrything from scratch (VST, user mux, projects etc.)
Questions:
- does it work without problems to just use the user key again without really "uninstalling" the user key in the already licensed version (just deleting the directory with the licensed mulab.exe)
- can I just copy my user mux from an backup file of the "corrupted" installation to the new user directory ?
- Can I reopen my actual projects done with the corrupted version when the VST are reinstalled or better not ?
Would be very glad for some advices before I start it all new.
Kind regards,
Richard
thank you all for you thoughts and ideas. I think main problem might have been that I only used the free version over years and never cared about installation, just downloaded, unzipped wherever the downloaded file was and run it.
Never had ANY problems over the years, I think sometimes might have had up to ten different versions installed but as I said it never causes any problems. Maybe because of the only 4 tracks, maybe because of the only 8 VSTi, I dont know.
So when I finally bought the UL version I must admit (blame it on me I know) I dont really cared about intallation cause I thought I had enought experience with that over the years.
And eveb then have no problems when I copied the folder to the program directory UNTIL after some weeks I get a VSTi (Sampletank 2.5) with problems with the write protection. The normal solution I know from other DAW was just to run the DAW with administrator rights but that seems to be one thing you should not do at all in Mulab cause after that the problems begun.
To be doing it all the right way now could you please take a look to my second attempt and at the questions still left over:
- I will delete all mulab.exe and corresponding files/directories especially user directories
- Unzip the actual version again
- put the unzipped files just direct under C:/mulab
- Then start the program from there and put the user key in the program again
- Hope that runs
- Then start evrything from scratch (VST, user mux, projects etc.)
Questions:
- does it work without problems to just use the user key again without really "uninstalling" the user key in the already licensed version (just deleting the directory with the licensed mulab.exe)
- can I just copy my user mux from an backup file of the "corrupted" installation to the new user directory ?
- Can I reopen my actual projects done with the corrupted version when the VST are reinstalled or better not ?
Would be very glad for some advices before I start it all new.
Kind regards,
Richard
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
Just put the key into the new version once it's running. Nothing else needed.tatanka wrote:- does it work without problems to just use the user key again without really "uninstalling" the user key in the already licensed version (just deleting the directory with the licensed mulab.exe)
I'm not quite clear what you mean. I would get up and running with your user key installed first, then take a back up of C:/mulab at that point. If you copy the old User folder into the new install, it should work -- but if it doesn't, you just delete c:/mulab and put the back up back. (You could try copying over piece by piece down through the user sub-folders, too, backing up each time nothing breaks.)tatanka wrote:- can I just copy my user mux from an backup file of the "corrupted" installation to the new user directory ?
There should be no problem with old projects.tatanka wrote:- Can I reopen my actual projects done with the corrupted version when the VST are reinstalled or better not ?
-
- KVRAF
- Topic Starter
- 1670 posts since 13 Jan, 2014
Thank you pljones,
hello Braserox while making your big vst check have you any experience with H.G. Fortune synths ? One of the problems I had with AvatarST, just lately someone has made wonderful presets for this I really would like to use. I know/already had "in general" problems with The Dreammachine and Wheels of fortune from H.G. (and the bunch of other wonderful machines he invented) but think that is caused by the synths/synthedit problems. Apart from AvatarST I am not actual using them but...
Another big "bunch" is all the nusofting things, I really love them and have just lately bought but know of course they have some problems (crashed Tracktion for example cause user bank administration just dont work). Any experience with them ? In the project where I realized the problems modelonia and mircrorock worked fine, but....
Would be very nice if you have some experience and could share.
Kind regards,
Richard
hello Braserox while making your big vst check have you any experience with H.G. Fortune synths ? One of the problems I had with AvatarST, just lately someone has made wonderful presets for this I really would like to use. I know/already had "in general" problems with The Dreammachine and Wheels of fortune from H.G. (and the bunch of other wonderful machines he invented) but think that is caused by the synths/synthedit problems. Apart from AvatarST I am not actual using them but...
Another big "bunch" is all the nusofting things, I really love them and have just lately bought but know of course they have some problems (crashed Tracktion for example cause user bank administration just dont work). Any experience with them ? In the project where I realized the problems modelonia and mircrorock worked fine, but....
Would be very nice if you have some experience and could share.
Kind regards,
Richard
-
- KVRAF
- Topic Starter
- 1670 posts since 13 Jan, 2014
Has nothing to do with installation, have evrything done like Jo told me and like in the list I posted. Not even copied user files. Did not install any VST for the start.
After installing evrything new on C:/Mulab I have opened the old project file and located evry VST in the projec new. Then saved the file under a new name, reopened it. Then I tried to open evry rack from right side on. First one, dk+, worked. And then, second one, KONTAKT, crashed the project like before. Did anyone say Kontakt stable and fine.... I am sure it is, so it has NOTHING to do with the concrete VST I am sure.
I will go on now locating one VST after the other, saving the project after each new located VST and see what will happen. But I am absolutely sure it had nothing to do with the installation.
Would be thankful for any other ideas what might crash the project but as long as I find out for me Mulab for my project IS instable.
After installing evrything new on C:/Mulab I have opened the old project file and located evry VST in the projec new. Then saved the file under a new name, reopened it. Then I tried to open evry rack from right side on. First one, dk+, worked. And then, second one, KONTAKT, crashed the project like before. Did anyone say Kontakt stable and fine.... I am sure it is, so it has NOTHING to do with the concrete VST I am sure.
I will go on now locating one VST after the other, saving the project after each new located VST and see what will happen. But I am absolutely sure it had nothing to do with the installation.
Would be thankful for any other ideas what might crash the project but as long as I find out for me Mulab for my project IS instable.
-
- KVRist
- 117 posts since 7 Oct, 2014 from Suisse
hy tatakan
I only use free vst and some time demos.
I dont have the money for vst . I have real synthesizers when i really want to make music
For vst testing there are some hints for all vst.
Download allways on creator site or where he says to download .
Try to download last updates but dont throw avay older release. Some develloper want to put more and more in new release.
This make vst havy and you will stuck in memory overload.
Big problem with presets you have to test if preset belongs to right release. If not some case vst can crash mulab.
I allways start with one vst to see if it works.
if not working i dont keep.There are so much ,free filter and synth . And dont forget Mux you can do a lot with.
The problem with VstI you never can be shure, if one is working it dont mean it will work with 2 or 3 other from other manufacurer.
Also be carefull with instruments with arpagiator or include sequencer.
Some Vst have there own save format, so fpx and fbx dont work.
I have all free NFG synth , and i will take a look at them.
The most important thing in computer music is to learn how synths are working.
Every manufacturer wants to make the best sound on hard synth or virtual synth and make the brightest demo to blind user.
But in the end you cannot use there sound in your own creation, because it dont sounds you own personnality.
I have a site but it is only in french, where is explain how i use synthesizers. And ther are some basics.
Its juste m own point of view.
But sorry its only in french.
http://music.armuco.ch/doku.php?id=soundtech
I only use free vst and some time demos.
I dont have the money for vst . I have real synthesizers when i really want to make music
For vst testing there are some hints for all vst.
Download allways on creator site or where he says to download .
Try to download last updates but dont throw avay older release. Some develloper want to put more and more in new release.
This make vst havy and you will stuck in memory overload.
Big problem with presets you have to test if preset belongs to right release. If not some case vst can crash mulab.
I allways start with one vst to see if it works.
if not working i dont keep.There are so much ,free filter and synth . And dont forget Mux you can do a lot with.
The problem with VstI you never can be shure, if one is working it dont mean it will work with 2 or 3 other from other manufacurer.
Also be carefull with instruments with arpagiator or include sequencer.
Some Vst have there own save format, so fpx and fbx dont work.
I have all free NFG synth , and i will take a look at them.
The most important thing in computer music is to learn how synths are working.
Every manufacturer wants to make the best sound on hard synth or virtual synth and make the brightest demo to blind user.
But in the end you cannot use there sound in your own creation, because it dont sounds you own personnality.
I have a site but it is only in french, where is explain how i use synthesizers. And ther are some basics.
Its juste m own point of view.
But sorry its only in french.
http://music.armuco.ch/doku.php?id=soundtech
-
- KVRAF
- Topic Starter
- 1670 posts since 13 Jan, 2014
O.k. seems that just capacity of Mulab was exhausted.
I have tried as I told, relocating VST after VST from the project that makes the problems.
After 10 from 15 Racks Mulabs just stops asking for missing VST when trying to open the old project file though they are definitely NOT in the VST Plugin Repository of Mulab.
Clear conclusion for me: something inside of Mulab was just overwhelmed.
Next conclusion: that was definitely not even 2/3 from Tracktion 5 capacity (same midi file with same VST, no problem with all 15 tracks and racks), maybe a little bit more then 50 %. It has not even come near to asking for the vst-effects in my mux master-rack.....
Last conclusion for me: Jo asked me when I mentioned Tracktion as main DAW for finally rendering the files why and what from my point of view are the benefits but after this first extensive test with mulab the answer for me is clear: 10 racks with 10 tracks just not enough, so its (under my circumstances in this case, I dont want to generalize this) just a lack of capacity in Mulab.
Fast, easy test of VST, ideas and maybe songs with not to many tracks or "resource-intensive" VST Mulab is o.k. for me, but not for the songs I have done in Tracktion now and will (have to) do in Tracktion in the future.
I have tried as I told, relocating VST after VST from the project that makes the problems.
After 10 from 15 Racks Mulabs just stops asking for missing VST when trying to open the old project file though they are definitely NOT in the VST Plugin Repository of Mulab.
Clear conclusion for me: something inside of Mulab was just overwhelmed.
Next conclusion: that was definitely not even 2/3 from Tracktion 5 capacity (same midi file with same VST, no problem with all 15 tracks and racks), maybe a little bit more then 50 %. It has not even come near to asking for the vst-effects in my mux master-rack.....
Last conclusion for me: Jo asked me when I mentioned Tracktion as main DAW for finally rendering the files why and what from my point of view are the benefits but after this first extensive test with mulab the answer for me is clear: 10 racks with 10 tracks just not enough, so its (under my circumstances in this case, I dont want to generalize this) just a lack of capacity in Mulab.
Fast, easy test of VST, ideas and maybe songs with not to many tracks or "resource-intensive" VST Mulab is o.k. for me, but not for the songs I have done in Tracktion now and will (have to) do in Tracktion in the future.
-
- KVRist
- 117 posts since 7 Oct, 2014 from Suisse
Have loaded all NFG
They work all as single instrument
Exeption for Wizard there is librarie probleme . Some antivirus find errors in Synthedit libraries and announce them as troyan . These easiest way to solve the problem is copy the broken library from a working plugin and replace the anoying library.
For Wizard its "spring2.sem" ou have to replace. These kind of problem can happen with other plugins made with synthedit.
Well known problem , happen often after updates of synthedit... As user just replace the broken library files when there is a problem.
They work all as single instrument
Exeption for Wizard there is librarie probleme . Some antivirus find errors in Synthedit libraries and announce them as troyan . These easiest way to solve the problem is copy the broken library from a working plugin and replace the anoying library.
For Wizard its "spring2.sem" ou have to replace. These kind of problem can happen with other plugins made with synthedit.
Well known problem , happen often after updates of synthedit... As user just replace the broken library files when there is a problem.
-
- KVRAF
- 1925 posts since 29 Mar, 2013
http://www.kvraudio.com/forum/viewtopic ... 8#p5930848
I know synth1 is very light on cpu but still I had 28 of them in that project plus some FX too.
I know synth1 is very light on cpu but still I had 28 of them in that project plus some FX too.
Beauty is only skin deep,
Ugliness, however, goes right the way through
Ugliness, however, goes right the way through
-
- KVRAF
- Topic Starter
- 1670 posts since 13 Jan, 2014
Hello bibz1st,
that is my next conclusion: if I have some time I will try out a project with some "low" on cpu VSTi an see what happens. But I cant hide that I was kind of shocked about these big problems just "add the beginning" of my Mulab UL experience. And about this big difference compared to Tracktion. Of course I can kill Tracktion too (mostly when I overuse the ram with samples), but in this Mulab Project was nothing special. Just a short list as far as I remember:
- Modelonia (2 X)
- Microrock
- DK+
all from Nusofting
- Kontakt
- Sampletank
Sampler, light on CPU, RAM was only 3,5 from 8 so that must not be the problem
- Eclipsis (2 X)
- AvatarST
- Pyrite Free
As I mentioned before, while trying to reconstruct the project Mulab stopped asking for the missing plugins even before it comes to any effects in the mastering channel (where I had put some together for a mastering mux).
The problem occured not while playing but with player in rest and just opening a loaded and before working plugin, so Midinotes etc. must not be a problem the same.
Would be glad for any additional tips, I am not grumbling and havent tried that long time with the free version for now giving up soon after buyhing the UL but...
Richard
that is my next conclusion: if I have some time I will try out a project with some "low" on cpu VSTi an see what happens. But I cant hide that I was kind of shocked about these big problems just "add the beginning" of my Mulab UL experience. And about this big difference compared to Tracktion. Of course I can kill Tracktion too (mostly when I overuse the ram with samples), but in this Mulab Project was nothing special. Just a short list as far as I remember:
- Modelonia (2 X)
- Microrock
- DK+
all from Nusofting
- Kontakt
- Sampletank
Sampler, light on CPU, RAM was only 3,5 from 8 so that must not be the problem
- Eclipsis (2 X)
- AvatarST
- Pyrite Free
As I mentioned before, while trying to reconstruct the project Mulab stopped asking for the missing plugins even before it comes to any effects in the mastering channel (where I had put some together for a mastering mux).
The problem occured not while playing but with player in rest and just opening a loaded and before working plugin, so Midinotes etc. must not be a problem the same.
Would be glad for any additional tips, I am not grumbling and havent tried that long time with the free version for now giving up soon after buyhing the UL but...
Richard