hi, i recently sold reason because it was just too complicated. i own reaper, but hate the idea of an open studio. i really miss reason and used it for 3 years but don't miss its extreme learning curve. ive known about mutools for a while now but it always seemed like it was just too basic even by my standards.
i prefer a very simple setup but mutools seemed very limited. that's changed with mutools going on v4 which seems to be powerful, yet simple to use. im not keen on the lack of multicore which seemed to be promised in v4 but seems to be in v5. at the same time, mutools seems to use very little cpu. i would compare it to reason 3.0 before multicore. workflow wise, it seeems like i would find this program enjoyable.
what are the unbiased views of mutools, and would you recommend it based on my preferred workflow?
sell me on mutools.
-
AstralExistence AstralExistence https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=265049
- KVRAF
- 2276 posts since 19 Sep, 2011
-
- KVRAF
- 5573 posts since 30 May, 2006 from Hollow Earth
For one, MuLab is excellent for Reason rewire, second MuLab has something similar and better then the Combinator called Mux, but I think now it's called SimpleSynth? Third the sound engine of the internal synths is superb.
The Pianoroll is soooo practical and this is why I use it for Reason.....
Not being a power user I will let the others fill in with goodies
The Pianoroll is soooo practical and this is why I use it for Reason.....
Not being a power user I will let the others fill in with goodies
ABEFLGMOPPRRST 
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
I have great respect for reason because of its integration and realistic approach. These are also main directives for MuLab. But MuLab also offers you more directness and openess. Whether MuLab is the best tool for you is difficult to say for me as each person has his own optimal workflow and so the best thing you can do is play around with MuLab 4 Free (pre-release) and see if it feels right for you. If you have any questions about using MuLab or if you don't find the features you're looking for, post your questions here in the forum!
About multi-core:
To clarify: I never promised multi-core in M4. I'm careful with promises because once i promise something i absolutely want to realize it. And previously i had not yet enough info to make such promise. Even at this point i still can't promise MC, even though i already did some R&D on it and that was very promising. But MC is a tricky challenge and i think i'll only be able to make the promise once i got the R&D completely done.
What i do promise though is that soon after M4 is released i'll launch a poll here on this forum about which features are most wanted. And i'm sure MC will be on top. And then i do promise that i'll focus on MC as top priority for MuLab. Believe me: I'm eager to give MuLab multi-core power!
About multi-core:
To clarify: I never promised multi-core in M4. I'm careful with promises because once i promise something i absolutely want to realize it. And previously i had not yet enough info to make such promise. Even at this point i still can't promise MC, even though i already did some R&D on it and that was very promising. But MC is a tricky challenge and i think i'll only be able to make the promise once i got the R&D completely done.
What i do promise though is that soon after M4 is released i'll launch a poll here on this forum about which features are most wanted. And i'm sure MC will be on top. And then i do promise that i'll focus on MC as top priority for MuLab. Believe me: I'm eager to give MuLab multi-core power!
-
- Hun #3
- 4265 posts since 25 Mar, 2002 from A quaint little village just south of Hamburg, Germany
The modular area (even though I hardly use it myself) is a main selling point in my opinion. Simple, rock solid and incredibly powerful.
-
AstralExistence AstralExistence https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=265049
- KVRAF
- Topic Starter
- 2276 posts since 19 Sep, 2011
im sitting on this because ive experienced like 10 crashes in a 2 hour period.Bonteburg wrote:rock solid
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
Is that using MuLab 3 or 4?
If it's about M4, then can you repeat the crashes by doing a bunch of specific steps? If yes, then please let me know that crash repeat pattern so i can fix the problem. If no such repeat pattern, then please describe what you were doing.
I'm ready for bug killing!
If it's about M4, then can you repeat the crashes by doing a bunch of specific steps? If yes, then please let me know that crash repeat pattern so i can fix the problem. If no such repeat pattern, then please describe what you were doing.
I'm ready for bug killing!
-
- Banned
- 897 posts since 8 Jan, 2005 from Detroit
i havent had a single crash the whole time i have tested m4 beta, and im on a p4 single core. 10 crashes in 2 hours? sounds like problems with your system. mulab is not crashy. scrutinize your ram, if its mis-matched then that could be your problem. do you optimize your machine for music production?
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
Coincidentally i have been jamming with M4 for around 2 hours earlier tonight in search of bugs and workflow issues, but all went ok.
But i did encounter some crashes last week during a wild jam and i still did not found any concrete reason for what i encountered at that time. And eventhough i tightened the code on several places i assume there are still some f***ing bugs in there
Really want to find the repeat patterns that locate these bugs.
Currently there is one known crash bug in M4.0.87: If you do "Mixdown" to a sample and enable "Create New Part", then delete the resulting part and rack and repeat the same mixdown, then M4 crashes. That's already fixed in the next version.
But i did encounter some crashes last week during a wild jam and i still did not found any concrete reason for what i encountered at that time. And eventhough i tightened the code on several places i assume there are still some f***ing bugs in there
Really want to find the repeat patterns that locate these bugs.
Currently there is one known crash bug in M4.0.87: If you do "Mixdown" to a sample and enable "Create New Part", then delete the resulting part and rack and repeat the same mixdown, then M4 crashes. That's already fixed in the next version.