MU.LAB 2 Test C

Official support for: mutools.com
Post Reply New Topic
RELATED
PRODUCTS

Post

pljones wrote:Is there a quick way to delete samples from a session?
Right-click a sample -> "Delete"
The MuSession I'm about to upload has three racks containing synths: K2, a Sampla (SamplaAh Rack) and CM101. The mixdowns from these are also captured in Samplas. It's only K2 that has a problem. It's definitely a problem between MULAB and K2 (but, like I say, Reaper and K2 don't appear to disagree the same way ;)).

(Once I get the K3 demo, I'll try it. It might be worth £100 if the bug's fixed there.)
Looking forward to the session, will research it again. Please also re-describe the exact problem.

Thanks.

Post

mutools wrote:Right-click a sample -> "Delete"
Whereabouts? In Sampla? When I get the popup menu to pick a sample from, I can't delete. I just want to get rid of samples I no longer need -- I don't want to have to load them first...

<edit>Well, it's not to messy...</edit>
mutools wrote:
pljones wrote:The MuSession I'm about to upload has three racks containing synths: K2, a Sampla (SamplaAh Rack) and CM101...
Looking forward to the session, will research it again. Please also re-describe the exact problem.
Right, fresh session:

http://www.drealm.info/mu.lab/Ah2.7z
http://www.drealm.info/mu.lab/Ah2-mixdowns.7z

The session has a single sequence which can be directed at each of the four racks containing a synth. The mixdowns are in the second file. If you compare K2 and K3 mixdowns, you'll hear next to no difference. If you compare them with the Sampla mixdown, you hear that the K2 mixdowns are cutting the notes short. If you then play the sequence through K3 demo with the PukeWeed_A.nkm loaded, you'll hear it should sound like the Sampla mixdown.
Last edited by pljones on Sun Aug 03, 2008 9:35 pm, edited 1 time in total.

Post

Damn.

Managed to crash MULAB whilst deleting racks. I've lost the crash report...

Post

Multisampla:
-I made a small drumkit and I couldn't hear anything playing it with my keyboard until I also pressed the keys in the multisample keyboard on the screen (as if that "unlocks" them or whtatever)

-A faint ghost image of a red connector line appears whenever I press a note in the keyboard window. Moved all the windows out of the way and the strange line goes from an empty spot to the upper left of the MPA right to the main audio output.

Post

pljones wrote:
mutools wrote:Right-click a sample -> "Delete"
Whereabouts? In Sampla? When I get the popup menu to pick a sample from, I can't delete. I just want to get rid of samples I no longer need -- I don't want to have to load them first...
No, just right-click on the sample name.
Right, fresh session:

http://www.drealm.info/mu.lab/Ah2.7z
http://www.drealm.info/mu.lab/Ah2-mixdowns.7z

The session has a single sequence which can be directed at each of the four racks containing a synth. The mixdowns are in the second file. If you compare K2 and K3 mixdowns, you'll hear next to no difference. If you compare them with the Sampla mixdown, you hear that the K2 mixdowns are cutting the notes short. If you then play the sequence through K3 demo with the PukeWeed_A.nkm loaded, you'll hear it should sound like the Sampla mixdown.
I can't repeat this here. I've been trying to get a faulty mixdown by doing what you describe but all mixdowns are ok here. I tried both 16 and 32 bit mixdowns. I also switched my audio device to different buffersizes but mixdowns were always ok.

This is the result of a mixdown of your above session with the sequence going to the K3 rack, with the PukeWeed_A.nkm loaded:

http://www.mutools.com/mulab/test20/mixdown20080804.mp3 (temporary link)

All 'ah' samples play full out because of the long 25 sec release in K3.

All normal.

I have no idea what could be causing the strange mixdowns :?

Post

pljones wrote:Damn.

Managed to crash MULAB whilst deleting racks. I've lost the crash report...
Was it while music was playing or when stopped?

Did the crash occur exactly at the moment you chose "Delete" for the rack?

Post

Bonteburg wrote:Multisampla:
-I made a small drumkit and I couldn't hear anything playing it with my keyboard until I also pressed the keys in the multisample keyboard on the screen (as if that "unlocks" them or whtatever)
Maybe you were playing in an empty octave first time?
-A faint ghost image of a red connector line appears whenever I press a note in the keyboard window. Moved all the windows out of the way and the strange line goes from an empty spot to the upper left of the MPA right to the main audio output.
Can you please send a screenshot?

Thanks.

Post

mutools wrote:
pljones wrote:Whereabouts? In Sampla? When I get the popup menu to pick a sample from, I can't delete. I just want to get rid of samples I no longer need -- I don't want to have to load them first...
No, just right-click on the sample name.
Where? The only place I find samples are inside Sampla. Then I have to load them as the current sample in that Sampla before I can right-click-delete them. Really, I want somewhere at Session level I can just tidy up.
This is the result of a mixdown of your above session with the sequence going to the K3 rack, with the PukeWeed_A.nkm loaded:
http://www.mutools.com/mulab/test20/mixdown20080804.mp3 (temporary link)
:? indeed! yes, that's perfect isn't it? Hmm, that points at it being a problem local to my PC somehow... Strange, though, that using Reaper doesn't trigger it. So it's something about how MULAB runs on my PC. Do you detect for / assume any CPU capabilities used during mixdown?
mutools wrote:
pljones wrote:Damn.
Managed to crash MULAB whilst deleting racks. I've lost the crash report...
Was it while music was playing or when stopped?
Did the crash occur exactly at the moment you chose "Delete" for the rack?
The sequencer was stopped. I'm almost certain it was exactly after releasing the mouse from "Delete" (but before hitting "Yes").

Post

pljones wrote:
mutools wrote:No, just right-click on the sample name.
Where? The only place I find samples are inside Sampla. Then I have to load them as the current sample in that Sampla before I can right-click-delete them. Really, I want somewhere at Session level I can just tidy up.
Sure, you're right, i first misunderstood.

Yes, such 'administrative' functions will be added asap.
This is the result of a mixdown of your above session with the sequence going to the K3 rack, with the PukeWeed_A.nkm loaded:
http://www.mutools.com/mulab/test20/mixdown20080804.mp3 (temporary link)
:? indeed! yes, that's perfect isn't it? Hmm, that points at it being a problem local to my PC somehow... Strange, though, that using Reaper doesn't trigger it. So it's something about how MULAB runs on my PC. Do you detect for / assume any CPU capabilities used during mixdown?
No, mixdown just writes to a file what is normally rendered to the audio output.

It's really a very strange issue.

I've been listening to your mixdowns again and it's not that the notes are simply cutoff on note off positions, they're a bit longer. And what also is very strange is that their release time is dependent on the pitch, like in a sampler.

So i would like to know what part of the sample Kontakt is playing. I assume the end part, because the notes stop.

A pity i don't have the issue here. Otherwise i would edit the sample in an audio editor and apply a pitch ramp to it. Then mixdown with MU.LAB and listen what's in the mixdown.

This would reveal what part of the sample Kontakt is actually playing.

And this could be a helping part of the puzzle.
mutools wrote:
pljones wrote:Damn.
Managed to crash MULAB whilst deleting racks. I've lost the crash report...
Was it while music was playing or when stopped?
Did the crash occur exactly at the moment you chose "Delete" for the rack?
The sequencer was stopped. I'm almost certain it was exactly after releasing the mouse from "Delete" (but before hitting "Yes").
I'll keep an eye on it. Thanks.

Post

I'm a little confused by the way MU.LAB handles audio parts - I programmed a sequence and mixed it down with "create new part" checked. Audio File appears and plays fine but I can't see any meter going up and down in a rack. So I go to the upper right menu and choose "put into rack" and choose "Rack C, slot 1", still no meter action. (Rack C now shows a "plug" called "Audio output" which I take to be my file.)
I put a VST effect into Rack C, nothing. Whilst playing back I decide to delete "Audio Output" from the rack wich is a big mistake - frozen audio loop, "reset realtime engine", no luck. Quit.

Importing an audio file isn't a problem. Mixing down a sequence as a new part is creating the weirdness.

I haven't done a lot of audio yet but this feels weird. Will do further testing. :)

edit: changed the target to "Rack XY mixer strip" and it works OK....

Post

The new part which results from a mixdown is routed by default straight to the main "Audio Output".

This is because a mixdown is expected to contain everything and so MU.LAB by default assumes it's best to stream it 'dry' to the audio output.

Of course you can easily change the target for the mixdowned part e.g. to a rack, and so it's easy to further process the mixdown if you want.

Note that the "Audio Output" is MU.LAB's final audio output object that sends the audio to your audio device.

So that's why you didn't see any level meters moving because the mixdowned part didn't go via a rack.

Putting the Audio Output in a rack is conceptionally weird and won't work because the audio output does not have any outputs (as you can see in the MPA) because it only sends the audio to the audio device driver, and so it would block the audio in the rack.

Hope this clarifies things.

Post

Bonteburg wrote:Whilst playing back I decide to delete "Audio Output" from the rack wich is a big mistake - frozen audio loop, "reset realtime engine", no luck. Quit
Deleting the Audio Output indeed unintentionly causes an audio loop instead of pure silence.

Will be finetuned.

Post

Thanks Jo!

It's typical of me to be late for the recording stuff - I'm normally a sequencing/mixdown guy. :oops:

Post

I like how the rack desk is automatically attached to the main window; however, I am very glad that you still have the option to separate the views - which is great for dual-monitors. The ability to simple toggle the rack desk with the F1 key makes it so easy to see you track layout. I much prefer this than having to resize frames in other software. Great job!
Keep it Pimpin'

Josh

Post

mutools wrote:I've been listening to your mixdowns again and it's not that the notes are simply cutoff on note off positions, they're a bit longer. And what also is very strange is that their release time is dependent on the pitch, like in a sampler.

So i would like to know what part of the sample Kontakt is playing. I assume the end part, because the notes stop.
The notes start at the right point, with the correct attack, hold, decay and sustain (if they get that far) and release - except they seem to get shortened. See this screen shot. The upper track is the K3 mixdown, the lower track the Sampla mixdown. The K3 notes are clearly getting chopped. But as you say, it appears to be note number... (I wouldn't jump to the conclusion it's pitch...)
http://www.drealm.info/mu.lab/Ah2.png
(Clearly my Sampla patch isn't identical to the K3 patch but I assume you can hear that it's closer than the image!! :lol:)

Post Reply

Return to “MuTools”