MuTools

MuTools · Post by **MuTools** » Sun Feb 14, 2010 7:31 pm

NBV wrote:Other reports:

1. Virtual MIDI keyboard needs a mechanism to change octaves.

You can scroll the keyboard by:

* Right-click and drag
* [Ctrl]+MouseWheel
* Scrollbar

2. The names of numerically named folders (i.e. folders named 01, 02, 03...)
are not displayed in the "file" menu browsers.

Fixed in the next version. Thanks!

Calum · Post by **Calum** » Sun Feb 14, 2010 11:03 pm

mutools wrote:
NBV wrote:Other reports:

1. Virtual MIDI keyboard needs a mechanism to change octaves.
You can scroll the keyboard by:

* Right-click and drag
* [Ctrl]+MouseWheel
* Scrollbar

I think NBV means a mechanism for changing octaves on the assigned keys rather than assigning each note individually. For example, right clicking or control clicking the root note from C1 to C2 could force all the other assigned notes to jump up an octave. I think this would be a nice feature.

By the way, QWERTY keyboard option works a treat on MAC keyboards

NBV · Post by **NBV** » Sun Feb 14, 2010 11:19 pm

Calum wrote: I think NBV means a mechanism for changing octaves on the assigned keys rather than assigning each note individually. For example, right clicking or control clicking the root note from C1 to C2 could force all the other assigned notes to jump up an octave. I think this would be a nice feature.

By the way, QWERTY keyboard option works a treat on MAC keyboards

Yes, that is just what I meant, thank you.

Another thing I just noticed (very weird): Ctrl+C, Ctrl+V are not working for
copy and paste. I also defined them by myself in the keyboard shortcuts editor, and it is still not working.

liquidsound · Post by **liquidsound** » Mon Feb 15, 2010 12:06 am

Can a sine wave be added to the LFO component in MuLab "Other PlugIn" for M3?
We use it a lot in Reason and it gives a sweet Panning, Gain etc.
Why is it missing....?

fceramic · Post by **fceramic** » Mon Feb 15, 2010 1:27 am

Strangest thing happened when I tried using the Xils 3 Le synth. I had the output of Mulab send to Propellerhead Record.
It just made some insane feedback and the audio went to shits. I had to delete it and then it took a little while for the audio to go back to normal. Though now that track wouldnt work so I had to restart Mulab.
Ultra Analog works just fine so I wonder what's causing Xils 3 to create feedback.

I'm using aggregate device to route the audio between the apps.
This also happened when Mulab was just using my interface output.

Also another annoying bug is that Mulab cant seem to decide weather to use my keyboard's midi output B and A, so I have to change the midi settings back and fourth.

Mulab really has some of the strangest bugs I have ever seen in Audio software!

NBV · Post by **NBV** » Mon Feb 15, 2010 4:13 am

Bug: selected a sequence and pressed Ctrl+C, then Mu.Lab shutted down with a crash warn. Did it three times. Got it logged.

Improviser · Post by **Improviser** » Mon Feb 15, 2010 8:31 am

NBV wrote: Another thing I just noticed (very weird): Ctrl+C, Ctrl+V are not working for
copy and paste. I also defined them by myself in the keyboard shortcuts editor, and it is still not working.

I too noticed (in M 3.0.19 and M 3.0.20 only), that Ctrl+C and Ctrl+V didn't work for copying and pasting in the sequence editor.

I thought maybe these shortcuts had been discontinued (while I wasn't paying attention !).

I used to use them a lot, so I therefore created my own shortcut - via "Edit -> Preferences -> Edit Shortcuts" (without any problems, in my case).
Hopefully it's bug, and/or it can be restored.

Les J.

MuTools · Post by **MuTools** » Mon Feb 15, 2010 8:33 am

Calum wrote:
mutools wrote:
NBV wrote:Other reports:

1. Virtual MIDI keyboard needs a mechanism to change octaves.
You can scroll the keyboard by:

* Right-click and drag
* [Ctrl]+MouseWheel
* Scrollbar
I think NBV means a mechanism for changing octaves on the assigned keys rather than assigning each note individually. For example, right clicking or control clicking the root note from C1 to C2 could force all the other assigned notes to jump up an octave. I think this would be a nice feature.

I see what you mean. Added to the whishlist.

By the way, QWERTY keyboard option works a treat on MAC keyboards

Thanks for confirming!

MuTools · Post by **MuTools** » Mon Feb 15, 2010 8:35 am

NBV wrote:Another thing I just noticed (very weird): Ctrl+C, Ctrl+V are not working for copy and paste. I also defined them by myself in the keyboard shortcuts editor, and it is still not working.

In the composer, there is an issue with Cut-Copy-Paste indeed, working on it.

MuTools · Post by **MuTools** » Mon Feb 15, 2010 8:38 am

liquidsound wrote:Can a sine wave be added to the LFO component in MuLab "Other PlugIn" for M3?
We use it a lot in Reason and it gives a sweet Panning, Gain etc.
Why is it missing....?

Technical reasons. Anyway, a triangle wave is very close (i know, it's not the same). It's on the whishlist to add many more kinds of modulators at proper time.

MuTools · Post by **MuTools** » Mon Feb 15, 2010 8:47 am

fridtjof wrote:Strangest thing happened when I tried using the Xils 3 Le synth. I had the output of Mulab send to Propellerhead Record.
It just made some insane feedback and the audio went to shits. I had to delete it and then it took a little while for the audio to go back to normal. Though now that track wouldnt work so I had to restart Mulab.
Ultra Analog works just fine so I wonder what's causing Xils 3 to create feedback.

I'm using aggregate device to route the audio between the apps.
This also happened when Mulab was just using my interface output.

Maybe you're creating an infinite audio loop somewhere, like A outputs to B, B outputs to C, C outputs to A? Maybe this oo loop is created outside MU.LAB? From what you describe it sounds like that.

Also another annoying bug is that Mulab cant seem to decide weather to use my keyboard's midi output B and A, so I have to change the midi settings back and fourth.

In MU.LAB's MIDI Setup (Edit menu), your MIDI keyboards out A and B should have different names, right.

Now if you set the first output to Out A and the second output to Out B, then this should not change. Are you saying it does change there?

Mulab really has some of the strangest bugs I have ever seen in Audio software!

It seems so. I'm as much surprised as you.

MuTools · Post by **MuTools** » Mon Feb 15, 2010 8:49 am

NBV wrote:Bug: selected a sequence and pressed Ctrl+C, then Mu.Lab shutted down with a crash warn. Did it three times. Got it logged.

OSX or Windows?

Can you give a more detailed step by step?

fceramic · Post by **fceramic** » Mon Feb 15, 2010 9:41 am

I contacted the Xils3 developer. This bug happened in AU lab as well, so it must be quite serious.
It probably has something to do with the instrument's audio input creating some nasty feedback.

NBV · Post by **NBV** » Mon Feb 15, 2010 2:20 pm

mutools wrote:
NBV wrote:Bug: selected a sequence and pressed Ctrl+C, then Mu.Lab shutted down with a crash warn. Did it three times. Got it logged.
OSX or Windows?

Can you give a more detailed step by step?

I had this composition with just two MIDI sequences. Then I highlighted the second sequence to copy and paste it (after I defined shortcuts Ctrl+C and Ctrl+V in the shortcut editor) then I pressed Ctrl+C and Mu.Lab showed this prompt which says "A serious error has occured. This may be caused by the applicaton or by any plugins! ..."

I'm running Windows XP SP2 on a Intel CPU 2140 @ 1.60 GHz
2 Gb RAM. At the point the bug occured, I was employing a Line 6 Guitar Port interface, with the latest drivers, and Pod Farm, the Line 6 amp simulation software. But I reproduced the bug with a Sound Blaster Live! and ASIO4all driver.

Here is the log of the last time it happened, a few minutes ago. It has happened four times, exactly the same way. If you need the other logs, just let me know:

Code: Select all

00:18:55:649 Started Logging
00:18:55:658 fnts[413] OK
00:18:55:663 MS Windows XP Professional
00:18:55:663 MU.LAB FREE 3.0.20
00:18:55:663 /d:/Datos de Nerio/sequencers/mu-lab 3 - betas/MULAB 3-0-20/MULAB.exe
00:18:56:340 Gonna startup audio engine
00:18:56:340 Gonna startup ASIO engine
00:18:56:473 ASIOGetChannels (inputs: 4, outputs: 2)
00:18:56:473 ASIOGetBufferSize (min: 128, max: 4096, preferred: 512, granularity: -1)
00:18:56:473 ASIOGetSampleRate = 44100.000000
00:18:56:473 ASIOOutputReady() - Not supported
00:18:56:566 CreateAsioBuffers done. NumIns=4, NumOuts=2. Gonna AllocateBuffers with size 512
00:18:56:566 ASIOGetLatencies OK: InLat=654, OutLat=1309
00:18:56:587 ASIOStart OK
00:18:56:688 mdnptngnclss_wn[31] 10 Midi Input Ports:
00:18:56:688 mdnptngnclss_wn[41] 0=MIDI Yoke NT:  1
00:18:56:688 mdnptngnclss_wn[41] 1=MIDI Yoke NT:  2
00:18:56:688 mdnptngnclss_wn[41] 2=MIDI Yoke NT:  3
00:18:56:688 mdnptngnclss_wn[41] 3=MIDI Yoke NT:  4
00:18:56:688 mdnptngnclss_wn[41] 4=MIDI Yoke NT:  5
00:18:56:688 mdnptngnclss_wn[41] 5=MIDI Yoke NT:  6
00:18:56:688 mdnptngnclss_wn[41] 6=MIDI Yoke NT:  7
00:18:56:688 mdnptngnclss_wn[41] 7=MIDI Yoke NT:  8
00:18:56:688 mdnptngnclss_wn[41] 8=UART MIDI SB Live!
00:18:56:688 mdnptngnclss_wn[41] 9=GuitarPort
00:18:56:689 mdtptngnclss_wn[29] 13 Midi Output Ports:
00:18:56:689 mdtptngnclss_wn[39] 0=B: Sintetizador MIDI SB Live!
00:18:56:689 mdtptngnclss_wn[39] 1=MIDI Yoke NT:  1
00:18:56:689 mdtptngnclss_wn[39] 2=MIDI Yoke NT:  2
00:18:56:689 mdtptngnclss_wn[39] 3=MIDI Yoke NT:  3
00:18:56:689 mdtptngnclss_wn[39] 4=MIDI Yoke NT:  4
00:18:56:689 mdtptngnclss_wn[39] 5=MIDI Yoke NT:  5
00:18:56:689 mdtptngnclss_wn[39] 6=MIDI Yoke NT:  6
00:18:56:689 mdtptngnclss_wn[39] 7=MIDI Yoke NT:  7
00:18:56:689 mdtptngnclss_wn[39] 8=MIDI Yoke NT:  8
00:18:56:689 mdtptngnclss_wn[39] 9=A: Sintetizador MIDI SB Live!
00:18:56:689 mdtptngnclss_wn[39] 10=UART MIDI SB Live!
00:18:56:689 mdtptngnclss_wn[39] 11=Sint. SW de tabla de ondas GS
00:18:56:689 mdtptngnclss_wn[39] 12=GuitarPort
00:18:57:729 Start with... Answer=Open SIETE-M3.MuSession
00:19:04:627 Gonna shutdown ASIO engine
00:22:24:973 Error rgn[17]

Best Regards.

Bonteburg · Post by **Bonteburg** » Mon Feb 15, 2010 3:47 pm

When I only record a MIDI sequence but the Audio button (little wave thingie) is also active, instead of saying "recording too silent" like it used to, MU.LAB creates a sequence with a very low metronome sound drowned out by a big noise floor. Is this meant to happen?

afterthought:
Maybe "Audio Recording Threshhold" defaults to another value now, will check.

MuTools

KVR Audio

M3 Tests