MuTools

DHR53 · Post by **DHR53** » Sat Jan 14, 2012 2:34 pm

Thanks, Jo... I am so used to Logic that it takes a little brain refiguring for me to get used to some of this stuff. One thing I noticed on the Mac version that seems strange, when I move the cursor to a spot in the arrange window, then hit the marker key cmnd. the marker is placed a few beats away from where the cursor is? Is that supposed to be that way... Maybe Mac version. Should go where the cursor is. Right?

Also is there a way to remove the keyboard across the top? Or was that a feature request everyone wanted... Ha!

Thanks.

MuTools · Post by **MuTools** » Sat Jan 14, 2012 3:08 pm

DHR53 wrote:Thanks, Jo... I am so used to Logic that it takes a little brain refiguring for me to get used to some of this stuff.

So you got the mouse wheel scrolling now?

One thing I noticed on the Mac version that seems strange, when I move the cursor to a spot in the arrange window, then hit the marker key cmnd. the marker is placed a few beats away from where the cursor is? Is that supposed to be that way... Maybe Mac version. Should go where the cursor is. Right?

It's snapped, like all composer actions, to the current grid.
You can change the grid bu the little grid panel in the bottom right of the composer.

Also is there a way to remove the keyboard across the top? Or was that a feature request everyone wanted... Ha!

No removable at this point.

That Focussed Module Panel is especially useful for displaying and editing which module takes MIDI input. In certain case you might want to drag-drop a module on the display so to set MIDI input to a specific sub-module.

So the Focussed Module Panel is needed anyway. And i thought it's generally handy to connect a keyboard to it, as the space would otherwise be unused, and so now you can always quicky monitor or even play and record the Focussed Module.

Hope i explain well.

DHR53 · Post by **DHR53** » Sun Jan 15, 2012 6:02 am

Regardless of what I set the grid to, the markers are placed randomly "around" where my cursor is placed. Not on the bar or beat the cursor is positioned on??? That is, If I use the key cmnd. I've set for this in the shortcuts... Goes where the cursor is if I use the menu to do this.

Also, when I record more notes into an existing sequence in a track... it creates a subtrack, is it supposed to do that? Can these be merged or recorded notes be blended into the existing sequence? i.e. with a behavior change???

Thanks...

MuTools · Post by **MuTools** » Sun Jan 15, 2012 10:28 am

DHR53 wrote:Regardless of what I set the grid to, the markers are placed randomly "around" where my cursor is placed. Not on the bar or beat the cursor is positioned on??? That is, If I use the key cmnd. I've set for this in the shortcuts... Goes where the cursor is if I use the menu to do this.

Ah, by shortcut, i see. Ther indeed is a little bug there, fixed in the next version.

Also, when I record more notes into an existing sequence in a track... it creates a subtrack, is it supposed to do that? Can these be merged or recorded notes be blended into the existing sequence? i.e. with a behavior change???

When you select a sequence part before (finishing) recording, then MuLab will give you several options among which to merge the new recording into that sequence part.

Hope this helps.

DHR53 · Post by **DHR53** » Sun Jan 15, 2012 4:17 pm

Ah, I think I did that by accident once... Ha! I discovered that I had to right click on the screen to pop up the sequence options screen? Right clicking on the sequence I didn't get the options to merge... Hmmm that might be a bug. I did get the takes to merge, by clicking the screen... not the sequence? Is there any documentation on the dials and functions of the MuSynth? I was looking at the docs, and maybe I missed some of the modularity stuff. I'm really getting in to making sounds on the fly with the MuSynth... it makes most of the noises I need! Ha!

Thanks...

DHR53 · Post by **DHR53** » Mon Jan 16, 2012 12:20 am

Er, found all the docs on them... Never Mind. Is the MuSynth in the Factory instruments, with 2 oscillators a created synth from the modules? Or is it a separate synth?

janamdo · Post by **janamdo** » Mon Jan 16, 2012 10:00 pm

Ofcourse has Mutools used the self created modules for the Musynth..look at Instrument-[devices]-basic synth and look at the avaibele modules in the deep editor
There was someone who had already construct his own synth on this forum..but when it is final and public?

DHR53 · Post by **DHR53** » Tue Jan 17, 2012 5:28 pm

I've reviewed all the modules listed on the site, but the large 2 oscillator synth that come sup when you select some of the factory presets seems to be a pre-made synth. As opposed to modules? It's a great synth, but most of the presets are not even using both of the oscillators... has awesome potential! I'm trying to create some patches with it using both oscillators... needs a mod matrix. There is so much stuff to mess around with in here it's crazy... Ha!

A couple things I'd like to see after working with 4.0 recently:

1. Select areas of the interface with tab key, then select tracks, racks or sequences with the arrow keys (kybd)

2. Expand the selected track with kybd. cmnd. i.e. all tracks small excpet the selected track which expands

3. Advance cursor by beat or bar in arrange window. Not just by marker or loop area

4. Reduce the number of "Are you sure you want to make that change" dialogs that ask the user to input O.K. seems like too much of those for some reason...

MuDrum is awesome... really liking that. Effects, samples, sends, add synth to that and it's perfect. Or maybe you can now? Hmmm...

Bonteburg · Post by **Bonteburg** » Tue Jan 17, 2012 6:46 pm

DHR53 wrote:4. Reduce the number of "Are you sure you want to make that change" dialogs that ask the user to input O.K. seems like too much of those for some reason...

+1... especially on saving a file when you haven't made any changes since the last saving. But we've had that discussion (what constitutes a change etc). I'm personally OK with the way it's now.

MuTools · Post by **MuTools** » Tue Jan 17, 2012 8:01 pm

Bonteburg wrote:
DHR53 wrote:4. Reduce the number of "Are you sure you want to make that change" dialogs that ask the user to input O.K. seems like too much of those for some reason...
+1... especially on saving a file when you haven't made any changes since the last saving. But we've had that discussion (what constitutes a change etc). I'm personally OK with the way it's now.

I assume you mean on quit, right?

Besides that confirmation, which "are you sure..." alerts are really redundant for you guys?

DHR53 · Post by **DHR53** » Tue Jan 17, 2012 9:06 pm

Hmmm... seems like everything has an o.k. dialog. I'll write them down tonight when I'm working with it and see how many I count. And what they were for. It's one of those things that I noticed, but I can't remember all the situations...

Bonteburg · Post by **Bonteburg** » Sat Jan 21, 2012 8:05 pm

M 4-0-99:

Mixdown reimported into a new musession won't play any more than the first bar (incidentally the loop end point) in the arranger window, even with 'play entire file' (ie all of it is visible) activated.

Moving the loop end point fixes this. Putting the loop end point to its default position (end of bar 1) doesn't repeat the proeblem.

OSX 10.6.8

MuTools · Post by **MuTools** » Mon Jan 23, 2012 11:32 pm

Researched this. I assume you were mixing down to the same audio file that was just imported after a previous mixdown, right? Next version has improved behaviour in this case.

Reincke · Post by **Reincke** » Tue Jan 24, 2012 8:27 am

Hi Jo,
I got a reproducable problem when upgrading any session (like "cappuccino") from 3.2.14 to 4.0.99. While upgrading, several popups telling me everything is okay ("Upgraded 1 sessions, 0 failed", "Stopped logging"). After that there is no more window visible, but the process still occurs in task manager. The log file seems to be okay. This will happen even if I cancel the upgrade from the select sessions folder dialog. Opening a M3 session with 4.0.99 still works. Version 4.0.97 also works fine. Any idea?

Jochen.

Bonteburg · Post by **Bonteburg** » Tue Jan 24, 2012 10:03 am

Bonteburg wrote:M 4-0-99:

Mixdown reimported into a new musession won't play any more than the first bar (incidentally the loop end point) in the arranger window, even with 'play entire file' (ie all of it is visible) activated.

Moving the loop end point fixes this. Putting the loop end point to its default position (end of bar 1) doesn't repeat the proeblem.

OSX 10.6.8

mutools wrote:Researched this. I assume you were mixing down to the same audio file that was just imported after a previous mixdown, right? Next version has improved behaviour in this case.

No - it just happened with the „New" template and a random audio file that wasn't created with MULAB. Again, I could solve the problem by moving the loop point once. (BTW it appears to work with both default loop points).

MuTools

KVR Audio

M4 Test