MuTools

MuTools · Post by **MuTools** » Wed Jul 09, 2014 8:22 pm

fluffy_little_something wrote:Any idea when the release will be so we get our eternal keys? Days, weeks, months, years from now?

Days.

Just wondering because Mulab is so subtle that I tend to forget I am still using a preliminary version. Today I noticed, though, as the sound went away periodically...

Did you order an upgrade yet? If yes you should already have an initial M6 user key. If not, mail me. (no PM)

fluffy_little_something · Wed Jul 09, 2014 8:28 pm

Ah, just days. Fine, no problem, I will wait

runaudio · Post by **runaudio** » Wed Jul 09, 2014 9:30 pm

i wish while browseing loops they would stay in sync with your track while playing useing wav loops any chance on next update

fluffy_little_something · Thu Jul 10, 2014 10:13 am

There is a new thread on Mux in the Instruments forum. Assuming there will be an update for that as well in the wake of Mulab's, you might list the key Mux improvements in that thread in order to appeal to potential customers

http://www.kvraudio.com/forum/viewtopic ... 2&start=15

MuTools · Post by **MuTools** » Thu Jul 10, 2014 4:38 pm

There is a new M6.0.31 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.30:

Fixed a display bug in the "Edit MIDI Input Channel Targets" dialog.
"Add Audio Track": Better positioning of the new audio part. (if any)
Added support for saving/reloading the sample markers near the source sample file.
Changed the "Default Mouse Tool" default to "Arrow".
+ other small improvements

fluffy_little_something · Thu Jul 10, 2014 4:46 pm

I can kind of reproduce the error now I get and described pages ago.

Oddly, Mulab in this case saves two log files with the same time, one of which is always all emtpy. The other one shows little, like this:

08:40:13:295 Started Logging
08:40:13:296 MS Windows Home Edition
08:40:13:296 MuLab FREE 6.0.28 32 bit
08:40:13:296 /C:/Users/KDB/Desktop/zu sichern/meine musik/MuLab/MuLab.exe
08:40:24:191 File[96] fn=VstSynth#12.Png, ec=2
08:40:33:467 Trance Lead 1 has VST version 2300
08:40:33:701 File[96] fn=HideWindow#08.Png, ec=2
08:40:34:135 File[96] fn=Options#17.Png, ec=2
08:40:34:136 File[96] fn=FileSaveAs#17.Png, ec=2
08:40:34:137 File[96] fn=FileOpen#17.Png, ec=2
08:40:34:138 File[96] fn=ArrowRightGS#12.Png, ec=2
08:40:34:139 File[96] fn=ArrowLeftGS#12.Png, ec=2
08:40:34:140 File[96] fn=ModuleProcessLed#28.Png, ec=2
08:40:39:281 Trance Lead 1 has VST version 2300

That's it.
I can't close Mulab via x, so I have to shut it down via the Windows Task Manager.

All I did was load two instances of Trance-Pro (also "works" with the Professional and the D-707 drum module as I just found out, will try other synths as well) and switch back and forth between the two a couple of times.
Sooner or later one instance keeps playing and reacting to the external keyboard, but the GUI is dead, so no more switching or shutting Mulab down.
It is also interesting to note that every time it happens, one of my six cores goes to 100 and stays there more or less until I shut Mulab down.

The next time I launch Mulab, it does not ask me whether to continue logging, and logging is off.

bbreakz · Post by **bbreakz** » Thu Jul 10, 2014 9:20 pm

Is there a way to enlarge a currently selected track while the others stay minimized?

I also like keeping certain tracks large all the time. Is there a way to keep that while enlarging a different track, while the others remain smaller?

Thanks

runaudio · Post by **runaudio** » Thu Jul 10, 2014 9:48 pm

bbreakz i wish that to instead of drag all tracks down to be able resize one track would be good on the next update would be great thanks

runaudio · Post by **runaudio** » Thu Jul 10, 2014 11:38 pm

i wish mulab when it scans your plugins it put them into folders when u have bundles of plugins it hard find the one you want quickly is there any way u can have your plugins inside folders
in mulab thanks

MuTools · Post by **MuTools** » Fri Jul 11, 2014 7:33 am

bbreakz wrote:Is there a way to enlarge a currently selected track while the others stay minimized?

Currently not.

MuTools · Post by **MuTools** » Fri Jul 11, 2014 7:35 am

runaudio wrote:i wish mulab...

Just for your info: http://www.kvraudio.com/forum/viewtopic ... 9&t=357048

MuTools · Post by **MuTools** » Fri Jul 11, 2014 7:48 am

fluffy_little_something wrote:I can kind of reproduce the error now I get and described pages ago. ...
All I did was load two instances of Trance-Pro (also "works" with the Professional and the D-707 drum module as I just found out, will try other synths as well) and switch back and forth between the two a couple of times.
Sooner or later one instance keeps playing and reacting to the external keyboard, but the GUI is dead, so no more switching or shutting Mulab down.

Good to hear you can kind of repeat it with Trance-Pro. Can you also repeat it with Synth 1 or ASynth?

fluffy_little_something · Fri Jul 11, 2014 8:35 am

mutools wrote:
fluffy_little_something wrote:I can kind of reproduce the error now I get and described pages ago. ...
All I did was load two instances of Trance-Pro (also "works" with the Professional and the D-707 drum module as I just found out, will try other synths as well) and switch back and forth between the two a couple of times.
Sooner or later one instance keeps playing and reacting to the external keyboard, but the GUI is dead, so no more switching or shutting Mulab down.
Good to hear you can kind of repeat it with Trance-Pro. Can you also repeat it with Synth 1 or ASynth?

Why you would think that is a good thing to hear is beyond me. Two of those three plugins are my standards, one of those two I can't replace because it allows me to make patches I can't do with Synth1 or whatever. So at the end of the day I would have to switch to another DAW that does not have that incompatibility. So far it looks like a SE incompatibility as all 3 plugins I have listed are SE.

As I said, kind of. Sometimes it takes half an hour to reproduce it, sometimes just 10 seconds. Will try it with Synth1 later today.

MuTools · Post by **MuTools** » Fri Jul 11, 2014 8:50 am

fluffy_little_something wrote:
mutools wrote:
fluffy_little_something wrote:I can kind of reproduce the error now I get and described pages ago. ...
All I did was load two instances of Trance-Pro (also "works" with the Professional and the D-707 drum module as I just found out, will try other synths as well) and switch back and forth between the two a couple of times.
Sooner or later one instance keeps playing and reacting to the external keyboard, but the GUI is dead, so no more switching or shutting Mulab down.
Good to hear you can kind of repeat it with Trance-Pro. Can you also repeat it with Synth 1 or ASynth?
Why you would think that is a good thing to hear is beyond me.

Hope you didn't take that wrong. It's meant from a technical perspective: When a prob is repeatable, that's an important step forward in narrowing down the cause.

Will try it with Synth1 later today.

Thanks. Looking forward to your results.

fluffy_little_something · Fri Jul 11, 2014 11:29 am

mutools wrote:
fluffy_little_something wrote:
mutools wrote:
fluffy_little_something wrote:I can kind of reproduce the error now I get and described pages ago. ...
All I did was load two instances of Trance-Pro (also "works" with the Professional and the D-707 drum module as I just found out, will try other synths as well) and switch back and forth between the two a couple of times.
Sooner or later one instance keeps playing and reacting to the external keyboard, but the GUI is dead, so no more switching or shutting Mulab down.
Good to hear you can kind of repeat it with Trance-Pro. Can you also repeat it with Synth 1 or ASynth?
Why you would think that is a good thing to hear is beyond me.
Hope you didn't take that wrong. It's meant from a technical perspective: When a prob is repeatable, that's an important step forward in narrowing down the cause.

Will try it with Synth1 later today.
Thanks. Looking forward to your results.

You might include the free P8 in your VST list as you further develop 32-bit Mulab's VST compatibility. It is not a "big one", but still widely used by non-professionals in certain genres and almost identical to the two plugins I am having problems with. A typical representative of the SE world one might say.

First I thought it might be a problem when using two instances of the same synth. But that is not the case as it also happens when I used two very different synths (Tarkus and Trance-Pro).

Now, let's see if I can get Synth1 to crash Mulab

By the way, I noticed that the last line of all logs is xyz has VST version 2300

Yesterday I had another, probably unrelated, crash, this is what it said:

09:30:17:055 Started Logging
09:30:17:056 MS Windows Home Edition
09:30:17:056 MuLab FREE 6.0.28 32 bit
09:30:17:056 /C:/Users/KDB/Desktop/zu sichern/meine musik/MuLab/MuLab.exe
09:30:23:648 File[96] fn=VstSynth#12.Png, ec=2
09:30:35:481 STANDARDS has VST version 2300
09:30:36:592 File[96] fn=HideWindow#08.Png, ec=2
09:30:37:210 App[445]
09:30:37:218 File[96] fn=Options#17.Png, ec=2
09:30:37:219 File[96] fn=FileSaveAs#17.Png, ec=2
09:30:37:220 File[96] fn=FileOpen#17.Png, ec=2
09:30:37:221 File[96] fn=ArrowRightGS#12.Png, ec=2
09:30:37:222 File[96] fn=ArrowLeftGS#12.Png, ec=2
09:30:37:223 File[96] fn=ModuleProcessLed#28.Png, ec=2
09:30:40:743 STANDARDS has VST version 2300
09:34:38:351 Delete VST Plug-In "STANDARDS" ? => Yes
09:34:41:223 Delete VST Plug-In "STANDARDS" ? => Yes
09:34:42:935 Delete Track "Rack 3" ? => Yes
09:34:43:870 Delete Track "Basic Synth Rack" ? => Yes
09:34:45:558 Delete Composition "MuLab Session" ? => Yes
09:34:47:598 Delete Rack "Basic Synth Rack" ? => Yes
09:34:48:942 Delete Rack "Rack 2" ? => Yes
09:34:49:919 Delete Rack "Rack 2" ? => Yes
09:42:42:841 Gonna shutdown ASIO engine
09:43:03:390 A serious error has occured. => OK

MuTools

KVR Audio

MuLab 6.0.35 released