MuTools

sl23 · Post by **sl23** » Wed Jul 18, 2012 1:00 pm

Will multicore support mean support for hyperthreading too or is that already supported?

MuTools · Post by **MuTools** » Wed Jul 18, 2012 1:19 pm

Yes MuLab MC will support hyperthreading too. In fact, hyperthreading is transparant to apps.

janamdo · Post by **janamdo** » Sat Jul 21, 2012 3:47 pm

If you don't have problems you can use a old version(s)..i do the same for now

Mirt Klaar · Post by **Mirt Klaar** » Sat Jul 21, 2012 5:53 pm

mutools wrote:Yes MuLab MC will support hyperthreading too. In fact, hyperthreading is transparant to apps.

When MuLab MC will be ready?

DHR53 · Post by **DHR53** » Sat Jul 21, 2012 6:51 pm

Yes, I think it's a little much to keep reloading the app all the time. I'm worried I'll forget something and screw up the install. Plus I've noticed that some old templates don't work properly... and I've had to redo my template a couple times. My last template wouldn't change tempos, but after redoing it it works fine now? Hmmm.

Questions? Is there a way to show all automation for tracks? Or show automation for a selected track??? I am a confirmed kybd. shortcut user. The more the better!

...really getting a workflow with MuLab to the point I actually prefer it to some "other" DAW's here lately.

A few fixes for the Mac version and I'm good for the long run!

MuTools · Post by **MuTools** » Sat Jul 21, 2012 9:07 pm

Mirt Klaar wrote:
mutools wrote:Yes MuLab MC will support hyperthreading too. In fact, hyperthreading is transparant to apps.
When MuLab MC will be ready?

That's still unknown. As soon as MUX Vst is released, next big step is MuLab's multi-core implementation. Multi-core support is something special and it's difficult to predict how much R&D time it will take. Part of the research is already done, but still work to do.

MuTools · Post by **MuTools** » Sat Jul 21, 2012 9:16 pm

DHR53 wrote:Plus I've noticed that some old templates don't work properly...

What doesn't work anymore? Please elaborate.

Questions? Is there a way to show all automation for tracks? Or show automation for a selected track??? I am a confirmed kybd. shortcut user. The more the better!

All possible shortcuts are listed in "Manage Shortcuts".

A few fixes for the Mac version and I'm good for the long run!

I know which OSX fix you mean. I did already research that one in depth and could not find the reason. OSX is just behaving weird on that point. During the M5 R&D stage, i'll most probably rewrite the entire OSX layer using Cocoa instead of Carbon and hopefully that will improve things. MuLab for OSX runs fine on most OSX systems, only on some systems there seems to be some quirks.

DHR53 · Post by **DHR53** » Sat Jul 21, 2012 10:28 pm

Hmmm... So is anyone who uses OSX Snow Leopard able to launch MuLab and NOT have to open the midi setup? I'd like to know what their setup is? It seems strange that I never had the problem till I loaded Snow Leopard, but it's not a showstopper. It just makes the experience a little less legitimate somehow...

My Template was locked on 70 bpm would not change. I had to create a new template?

I'm wondering if anyone is using Lion or Mountain Lion? And do they have the midi start bug?

Mirt Klaar · Post by **Mirt Klaar** » Sun Jul 22, 2012 4:41 am

mutools wrote:
Mirt Klaar wrote:
mutools wrote:Yes MuLab MC will support hyperthreading too. In fact, hyperthreading is transparant to apps.
When MuLab MC will be ready?
That's still unknown. As soon as MUX Vst is released, next big step is MuLab's multi-core implementation. Multi-core support is something special and it's difficult to predict how much R&D time it will take. Part of the research is already done, but still work to do.

I understand. Thanks for reply and for the great work you're doing.

toxicoh · Post by **toxicoh** » Sun Jul 22, 2012 12:48 pm

DHR53 wrote:Hmmm... So is anyone who uses OSX Snow Leopard able to launch MuLab and NOT have to open the midi setup? I'd like to know what their setup is? It seems strange that I never had the problem till I loaded Snow Leopard, but it's not a showstopper. It just makes the experience a little less legitimate somehow...

My Template was locked on 70 bpm would not change. I had to create a new template?

I'm wondering if anyone is using Lion or Mountain Lion? And do they have the midi start bug?

My system has been working fine with each update.

I did have to go to Apple's Audio Midi Setup utility long time ago to set up the midi devices. I'm using an Edirol UM-1 and a TonePort UX1 via USB. It "just works".

Mulab remembers my MIDI settings if everything's plugged in when the program starts.

Mattox · Post by **Mattox** » Sun Jul 22, 2012 5:44 pm

New owner here, just wanted to say that I'm super surprised by MuLab, there is a hell of a lot more going on under the hood than first meets the eye. Really enjoying the flexibility of the MUX; I feel like I have much more control over my signal flow than on most other DAW's.

Few feature requests:

1. Drum maps for the piano roll
2. Ability to save/load custom virtual piano layout, we would then have the ability to map scales to the virtual keyboard. I use this mostly when I'm making music on my laptop.

Performance so far has been pretty good; first I tried to make a new dnb track using a few drum samples & 10 instances of Z3ta+ 2 and I was sitting at about 120% cpu which wasn't the best, but I switched the instances of Z3TA2+ to kiloHears One and it dropped to about 40%.

Looking forward to multi-core support

pljones · Post by **pljones** » Sun Jul 22, 2012 6:15 pm

1. Drum maps for the piano roll

Loadable ones would be nice. Not fixed "GM says this" ones...

Indeed, this would be neat for triggering all sorts of things, then, not just drums. Basically a bunch of text labels and a MIDI note assignment grid that could be used in place of the piano in the piano roll... mmmm...

MuTools · Post by **MuTools** » Sun Jul 22, 2012 8:00 pm

Added on the wishlist.

Just initial brainstorming: I think such layout should be defined by the target module of that sequence part. Right?

pljones · Post by **pljones** » Sun Jul 22, 2012 10:31 pm

As I wandered off I started wondering about that.

Take Kontakt. I could have a piano, a set of loops and two drum kits with different mappings all loaded into one instance. Somehow it needs to handle multi-timbral instruments... If you ignore that, then yes, part's target seems to be the defining factor. So maybe just factor in "per channel" as an option (i.e. if the channel is actively important to targeting)?

Reincke · Post by **Reincke** » Mon Jul 23, 2012 7:22 am

mutools wrote:Just initial brainstorming: I think such layout should be defined by the target module of that sequence part. Right?

Yep!

MuTools

KVR Audio

MuLab 4.3.9