MuTools

SparkySpark · Post by **SparkySpark** » Sat Apr 06, 2019 9:44 am

sl23 wrote: Sat Apr 06, 2019 9:03 am But then I coulda sworn there was an Audio to MIDI converter in there somewhere!

Well there is MIDI to audio: play some notes on the MIDI keyboard and you'll hear sound coming from your speakers!

sl23 · Post by **sl23** » Sat Apr 06, 2019 11:19 am

No way! That's ingenious! When did that come about? I must've blinked and missed that one!

SparkySpark · Post by **SparkySpark** » Sat Apr 06, 2019 11:25 am

sl23 wrote: Sat Apr 06, 2019 11:19 am No way! That's ingenious! When did that come about? I must've blinked and missed that one!

szabi · Post by **szabi** » Sat Apr 06, 2019 5:32 pm

sl23 wrote: Sat Apr 06, 2019 9:03 am Mine doesn't, tho I can't remember if there's a setting for this. I'm sure years ago that it used to?
But then I coulda sworn there was an Audio to MIDI converter in there somewhere!

It can still happen sometimes (did for me this or last week), without having funny modules. I'm not sure about the exact conditions (just guessing: may depend on previous app/prj open activity, perhaps if there has (not) been a recent project, or some peculiar user choices on startup), but when the "Start" project template gets loaded, it happens.

Just tried opening the "Start" template manually, and it did auto-play for me. But the funny thing is: only once. Now I can't do it again.

(I'm still on 0.58, though.)

(Note: couldn't see a cfg. option for this just by a quick browsing thru now.)

agbasoun · Post by **agbasoun** » Sat Apr 06, 2019 8:18 pm

Just tried it and I am blown away. Been waiting for the audio sequencing and time stretching for so long!! Can't wait til it's officially released. I already have so many ideas

Thank you Jo so much for all your hard work.

SparkySpark · Post by **SparkySpark** » Sun Apr 07, 2019 6:25 am

I can confirm the auto play. Thought it was per design, though I would rather have it not playing.

I thought this is the default behaviour of new installs (?).

RichardSemper · Post by **RichardSemper** » Sun Apr 07, 2019 7:53 am

I have just noticed a change in behaviour in the Project Modular Area since version 8-0-56
in versions 8-0-52 and previous, clicking an item in the modular area would transfer the MIDI Input focus to that module. Since 8-0-56 this no longer happens, though a double click to open the module does transfer the focus.
Clicking a track in the composer still switches focus as before.
Note:
- the Activate Module Editor Auto MIDI Focuses Module is set to On as default
- Project Automatic MIDI Input Focus is ticked

UPDATE - a further check show this is only in 64bit version, the 32bit version works as before.

MuTools · Post by **MuTools** » Sun Apr 07, 2019 11:00 am

Thanks Richard, i found the bug, will be fixed in the next update.

bibz1st · Post by **bibz1st** » Sun Apr 07, 2019 11:24 am

Regards the auto start, isn't it to do with whether you do a save whilst your project is still running, simple answer, just stop then save.

MuTools · Post by **MuTools** » Sun Apr 07, 2019 11:41 am

About auto play: It's a reserved case. The only case MuLab will auto start playing a project is when launching MuLab for the first time(s) and the "Start" project is opened.

jamiethelin · Post by **jamiethelin** » Sun Apr 07, 2019 4:04 pm

I have encountered a strange bug regarding extreme time stretch values.

Using a time stretch of around 10000 on 'EDM kick 14' from the default library, there is some white noise in the right channel towards the end of the sample.

Here is a link to a sample project and an exported wav version of what I'm hearing for you to investigate: https://we.tl/t-tAS8JHsJDl

Furthermore following is my current audio setup:

Audio Drive Type: MME Audio Output
Audio Drive Name: Microsoft Sound Mapper
Samplerate: 44100 Hz
MME Number of Blocks: 8
MME Block Size: 512
Num Audio Processor Threads: Auto (2)
CPU Load Limit %: Off

Thanks.

MuTools · Post by **MuTools** » Sun Apr 07, 2019 6:52 pm

Can repeat it, will research & fix it. Thx for reporting this!

T. · Post by T. » Mon Apr 08, 2019 7:07 pm

Hello everbody,
I have a strange behavior with my V-Station VST (2.02 /64 bit) over here: for some reason Mulab 8 doesn't like it.... I tried to add the plugin to the plugin list several times. It ends always with the same result: MuLab crashes and dissappears (poof!).
I attached a screenshot where the file scanning stops every time befor crashing.
It works perfect in MuLab 6 (64bit).
And it's the only plugin I have problems im MuLab8 so far.
Any Idea? Does anybody else still use it too?
May be it's just too old?

Thanks!
Thomas

MuTools · Post by **MuTools** » Tue Apr 09, 2019 1:21 am

Thomas can you find a related crash report in Windows' event viewer?

MuTools · Post by **MuTools** » Tue Apr 09, 2019 1:38 am

M8.0.60 is available in http://www.mutools.com/mulab/m8/

What's changed:

The "Choose Color" context menu item has been replaced by a new method to color parts and racks:
Project menu -> Show Color Picker -> Drag-drop a color on parts, racks, etc.
Of course you can assign a key shortcut to "Show Color Picker".
Also sample events can be individually colored now.
Spectral stretching: In some cases there could be bad audio in the stretched audio. Fixed.
Clicking a module in the modular area did not move MIDI focus to that module anymore. Fixed.
Finetuned the audio slicer algorithm so to avoid markers too close to audio start.
Other little improvements.

How to update:
Windows: Replace the current MuLab.exe and MuLab.ID by the new versions.
MacOS: Replace the current MuLab.app by the new version.

MuTools

KVR Audio

MuLab 8.0.66