MuTools

MuTools · Post by **MuTools** » Wed Jul 04, 2012 1:48 pm

Please send me a MuLab session (.MuSession) that uses NoiseMaker in the way you use it and a step-by-step so that when i load the session and perform your steps then that alert should come. Thanks.

fluffy_little_something · Wed Jul 04, 2012 2:41 pm

Usually it goes like this: I just open a new session of Mulab as always. Right after that I open Noisemaker via the VST selector and load one of my patches to modify it. That is all I do as I currently limit myself to sound design. I don't use Mulab as such, I might as well use Savihost

I don't record anything, I don't use any Mulab effects or anything else in Mulab for the time being.
Nor is it easy to reproduce the error, I have had Noisemaker open for an hour now, played around with various patches, even suspicious ones, still no error message. Seems to be a random problem, I will tell the makers of Noisemaker about it, maybe they can help

MuTools · Post by **MuTools** » Wed Jul 04, 2012 3:11 pm

Note that that alert can only come when closing a session (eg quitting MuLab) or when monitoring notes in the multi-sample editor. So that alert will not come while you're playing around with NoiseMaker. I really don't understand why that alert pops up.

fluffy_little_something · Wed Jul 04, 2012 3:37 pm

Right, and in that half dozen times or so it has happened so far I was always closing Mulab because there was a problem, specifically because the sound was gone all of a sudden. Next time I will try to open a MUX after the Noisemaker sound is gone (can a VST plugin alone crash?!), that should tell me if it is a Noisemaker problem or a Mulab problem.
Since nobody else here seems to have that problem and probably hardly anyone else here uses Noisemaker, it is likely not a Mulab problem.

So don't waste your time on it in vain for the time being

MuTools · Post by **MuTools** » Wed Jul 04, 2012 4:10 pm

fluffy_little_something wrote:Right, and in that half dozen times or so it has happened so far I was always closing Mulab because there was a problem, specifically because the sound was gone all of a sudden.

Aha! That's an interesting piece of the puzzle.
Yes this info relates perfectly with why that alert pops up because that alert implicitly means that the audio engine is not running anymore.
So now we should try to find out why the audio engine stops working.
Is there anything on your system that could interfere with your ASIO driver?

fluffy_little_something · Wed Jul 04, 2012 7:34 pm

I have no idea what might be stopping the audio engine. When it stopped today, I was only playing on my keyboard and turning knobs on the VST, there was no other program that could have interfered.
Mulab and Noisemaker have been running for hours now, without the error. I was even out of the house for an hour, still running

Maybe I just have to live with such occasional errors...

MuTools · Post by **MuTools** » Wed Jul 04, 2012 8:10 pm

Mmm, there must be some reason... But i think the reason is outside MuLab.
I think something is interfering with the audio driver. I don't suspect NoiseMaker. The above is all brainstorming. Maybe some reason will popup some day..?

fluffy_little_something · Thu Jul 05, 2012 7:26 pm

Odd, I just tried a 64-bit version of Mulab for the first time, the most recent one you published today, and when launching Mulab it says that it couldn't start the audio engine.
I never got that message on the 32-bit version.

MuTools · Post by **MuTools** » Thu Jul 05, 2012 7:44 pm

Maybe because it can't find a 64 bit ASIO driver?

fluffy_little_something · Thu Jul 05, 2012 8:02 pm

I have just reinstalled the latest version of the 64-bit driver for my sound card from the Asus website. Still, same message and no sound...

PS: It works now, there are several 64-bit drivers and when I tried another one in the Audio setup, it worked

My VSTs seem to work as well. Patches are still there. Maybe this switch to 64-bit has solved the other problem as well

Now all I have to do is wait for the multi-core support

fluffy_little_something · Tue Jul 10, 2012 3:33 pm

Yesterday I compiled my first own drum kit, played it, saved it, but today it says that the preset file (i.e. the MuDrum kit) can not be loaded. Is it because of the external .wav file samples I included in the kit?

Also, I guess it would be better if, when trying to close Mulab, it did not ask whether or not one wants to save the session if one has already saved it manually and not changed anything after that.

And I would like it if during playback the moving vertical green progress bar stopped when nothing has been recorded after a certain point on the time line. It should also stop when one stops recording and is prompted to enter a name.
It would also be cool if that vertical green progress bar turned red while recording

MuTools · Post by **MuTools** » Tue Jul 10, 2012 4:10 pm

fluffy_little_something wrote:Yesterday I compiled my first own drum kit, played it, saved it, but today it says that the preset file (i.e. the MuDrum kit) can not be loaded. Is it because of the external .wav file samples I included in the kit?

Please email me that .Mux file so i can research what's wrong.

fluffy_little_something · Tue Jul 10, 2012 5:43 pm

mutools wrote:
fluffy_little_something wrote:Yesterday I compiled my first own drum kit, played it, saved it, but today it says that the preset file (i.e. the MuDrum kit) can not be loaded. Is it because of the external .wav file samples I included in the kit?
Please email me that .Mux file so i can research what's wrong.

Um, how?! We all have emails disabled

MuTools · Post by **MuTools** » Tue Jul 10, 2012 5:59 pm

http://www.mutools.com/company-contact.html

fluffy_little_something · Tue Jul 10, 2012 6:08 pm

Oh, I had already forgotten you have a website

MuTools

KVR Audio

Just a few remarks from a Mulab newbie...