MuTools

MuTools · Post by **MuTools** » Fri Jul 11, 2014 12:40 pm

Ok as you indicated that it's especially about SE plugins i did a test using the SE synth plugin "Lektro" see http://www.xenobioz.com/search/label/VSTI
I plugged in 2 instances in M6.0.31 with multi-core enabled, opened both editors and have been switching between the editors like hell, also opening-closing them many many times, all while they were playing. Didn't notice anything wrong here.

fluffy_little_something · Fri Jul 11, 2014 1:16 pm

Don't know that one, and since I don't want to use it, it is irrelevant to me.

I still don't know under which conditions the error happens, sometimes it doesn't happen during an entire session, then after just a few seconds. Either way, since I can't rely on it, it's a problem. Especially since Mulab crashes in a way that the previous session is gone. So work would be lost.

MuTools · Post by **MuTools** » Fri Jul 11, 2014 2:06 pm

I recommend looking for another VST plugin that can do the job, a plugin that does not crash. Most VST plugins work fine in MuLab. Wish the VST SDK was made more accurate, that would have avoided the VST implementation noise. I sent several such requests to Steinberg in the past, but no reply. If i get clear indications that a certain VST related problem is on MuLabs' side, i'll certainly research and tune things where necessary, as i did already many times in the past. But in this case, based on the info i got and on the test i did, this is not the case now. So i hope you can find a stable VST plugin that gives the sound you want.

DHR53 · Post by **DHR53** » Fri Jul 11, 2014 2:14 pm

O.K. I'm experimenting with some audio loops as I've never used that much audio before but I thought I would check out what MuLab does with audio as I'm familiar with Logic and Live mainly... I've had mixed results with placing drum loops in. If there close to the tempo they seem to work o.k. but beyond about 20 bpm not too good. I'm on a Mac though so this may be a OSX version anomaly...

I've also been trying just midi clips (drum loops) placed into a track and adding a MuDrum. What I'm getting is the clip comes it at it's original tempo regardless of what my session is? I can't change it... Which is not what I want of course. Hmmm...

MuTools · Post by **MuTools** » Fri Jul 11, 2014 2:24 pm

DHR53 wrote:O.K. I'm experimenting with some audio loops as I've never used that much audio before but I thought I would check out what MuLab does with audio as I'm familiar with Logic and Live mainly... I've had mixed results with placing drum loops in. If there close to the tempo they seem to work o.k. but beyond about 20 bpm not too good. I'm on a Mac though so this may be a OSX version anomaly...

I don't think this is OSX specific. It's just that it's important the the audio markers which indicate the slices that they are positioned well. MuLab includes an auto-slicer algorithm that automatically slices the drumloop. This works fine with many loops but sometimes the audio of a loop is more difficult to analyze right and then the markers are not positioned perfectly and then when changing the tempo a lot you'll hear that. So in that case open the sample editor and finetune the markers then "Update Sliced Sample Part" as explained on http://www.mutools.com/info/docs/mulab/ ... mples.html

The new video shows an example with a drumloop that is auto sliced fine, as well as a drumloop that needs adjustement. Tip: When you have finetuned the slice markers for a certain drumloop, you can then save the markers via right-click on the sample display -> Save Markers. Then you don't have to do it again for that drumloop.

I've also been trying just midi clips (drum loops) placed into a track and adding a MuDrum. What I'm getting is the clip comes it at it's original tempo regardless of what my session is? I can't change it... Which is not what I want of course.

I assume the MIDI file includes a tempo event. Then that's imported too. You can edit the tempo events via right-click on the composer timebar or right-click on the tempo display. Eventually remove the tempo event(s) that were imported from the MIDI file.

DHR53 · Post by **DHR53** » Fri Jul 11, 2014 2:36 pm

And that's done by right-clicking the tempo indicator? Because I've been dbl. clicking the tempo and putting in a new setting, and it resets back to the loop tempo when the play head starts at the beginning?

MuTools · Post by **MuTools** » Fri Jul 11, 2014 2:48 pm

Right-click tempo display -> "Edit Tempo Changes". This opens the event list editor which shows tempo events. If you want you can delete all imported tempo events by Select All + Delete.

fluffy_little_something · Fri Jul 11, 2014 4:30 pm

I know now where the unrelated error came from. As I wanted to delete all other racks and tracks I accidentally got with the mouse in the empty space ABOVE a rack and pressed the delete key on the keyboard, which lead to the dialog "Delete Composition Mulab Session". As I was deleting several tracks and racks, I did not read the text and simply pressed return to confirm.
After that, when I tried to drag and drop the synth (but it seems anything from the browser will do) into the track column, there was that severe error.

liquidsound · Post by **liquidsound** » Fri Jul 11, 2014 4:47 pm

Would it be more flexible to have the "Last Used" pencil or arrow tool as the default?
In this way it can adapt to the current workflow chosen by usage rather than "universal preference".
That allows anyone to choose accordingly instead of each time we use it and where.
Last Used allows for more predictability I guess.

MuTools · Post by **MuTools** » Sat Jul 12, 2014 9:09 am

fluffy_little_something wrote:I know now where the unrelated error came from. As I wanted to delete all other racks and tracks I accidentally got with the mouse in the empty space ABOVE a rack and pressed the delete key on the keyboard, which lead to the dialog "Delete Composition Mulab Session". As I was deleting several tracks and racks, I did not read the text and simply pressed return to confirm.
After that, when I tried to drag and drop the synth (but it seems anything from the browser will do) into the track column, there was that severe error.

Thanks for the details! Confirmed. Fixed in the next version.

MuTools · Post by **MuTools** » Sat Jul 12, 2014 1:48 pm

There is a new M6.0.32 update in http://www.mutools.com/mulab/forsythia/

How to update: Update your current .app/.exe and .ID by these new files.

What's changed since M6.0.31:

Fixed a problem and possible crash bug when deleting the only single composition in a session.
"Add Track" does not pre-set the target module anymore but just creates a clean empty track.
+ Other small improvements.

fluffy_little_something · Sat Jul 12, 2014 6:54 pm

Thanks for the key, seems it's getting longer and longer with every version, I hope I'll never have to enter it manually like with the Windows key

runaudio · Post by **runaudio** » Sat Jul 12, 2014 7:05 pm

us windows users dont have to type it in just copy and paste thank you very much for the key

fluffy_little_something · Sat Jul 12, 2014 7:09 pm

runaudio wrote:us windows users dont have to type it in just copy and paste thank you very much for the key

Oh really, glad you told us how to do that, I really would have typed it in

runaudio · Post by **runaudio** » Sat Jul 12, 2014 8:53 pm

on the next video you make could show us how to rewire please

MuTools

KVR Audio

MuLab 6.0.35 released