MuLab 9.0.59 App + Plugin

[pljones]

In m9 the behaviour is the same. The hover text shows the value, as does the edit box. The sample position display in the main ui shows a vertical line which denotes the position in the file rather than a numeric value. This line moves left or right according to the value chosen.

Ah, is that what it is... not a very clear UI design, I think. Having a clear start / loop / end mark on the wave display (getting highlighted if the input field was selected), with the sample position displayed either as a marker id or sample ("!marker name" to differentiate) would be much more useable, I think.

[pekbro]

So a lot of times, I will leave the beta open overnight or when I go to work. I always turn off the
HW mixer or mute the I/O or something. Typically when I go back to the beta, it has stopped working.
The level meter on the default track, which I don't really use will be stuck at the max level. I have to
delete the track, stop the audio engine or restart to get it working again.

I do the same thing with other DAWs, such as FL Studio, Live, Studio One, Reaper etc. None of them
exhibit the same problem. This is a fairly recent clean installation of win 10 Pro with only about
70 vst plugins installed, Focusrite Scarlett 2i2, latest everything etc...

[carlca]

"All I want for Christmas is..." - complete this well known song excerpt

[MuTools]

Despite using it for several hours each day, and trying many things I really have no issues to report so far, (other than perhaps the number of modules I needed to update from earlier projects to work in m9).

Please elaborate on that sentence between the brackets.
Is there an M9 issue?

Great work Jo
Have a Great Christmas and a Happy New Year!

Thanks Richard.
And warm Christmas wishes to you too!

[MuTools]

So a lot of times, I will leave the beta open overnight or when I go to work. I always turn off the
HW mixer or mute the I/O or something. Typically when I go back to the beta, it has stopped working.
The level meter on the default track, which I don't really use will be stuck at the max level. I have to
delete the track, stop the audio engine or restart to get it working again.

Is that using M9.0.10?
Do you also use MUX effects or synths?
Was there a composer playing?

Last week i have been hunting and fixing a couple of difficult bugs that could have been the cause.
So please make sure to repeat that test with the next M9.0.11. (available soonish)

[pekbro]

Is that using M9.0.10?
Do you also use MUX effects or synths?
Was there a composer playing?

Yes M9.0.10
No MUX, no synth,
Nothing playing...

Last week i have been hunting and fixing a couple of difficult bugs that could have been the cause.
So please make sure to repeat that test with the next M9.0.11. (available soonish)

Will do thanks...

[RichardSemper]

(the number of modules I needed to update from earlier projects to work in m9)
Please elaborate

I refer to the fact that m9 will not load project files, mux presets, multisample files and muclips, which were saved before about february 2019. Fixed easily by loading them into latest mulab 8, upgrading and re-saving them. It seems I had quite a lot of these so it took some time to go through the process.
Not complaining at all, this kind of thing is to be expected with major upgrades sometimes. However, it is worth noting that the same issue applies to a lot of the mulib collection also.

[MuTools]

I refer to the fact that m9 will not load project files, mux presets, multisample files and muclips, which were saved before about february 2019. Fixed easily by loading them into latest mulab 8, upgrading and re-saving them. It seems I had quite a lot of these so it took some time to go through the process.
Not complaining at all, this kind of thing is to be expected with major upgrades sometimes. However, it is worth noting that the same issue applies to a lot of the mulib collection also.

Please note that there are helper tools to do this in bulk:
MuLab menu -> Tools -> Show File Versions + Upgrade Projects / Presets.

[RichardSemper]

Please note that there are helper tools to do this in bulk:
MuLab menu -> Tools -> Show File Versions + Upgrade Projects / Presets.

A very useful option which I also used. I had not realised that it also updates subfolders.

[MuTools]

I'm trying to send midi data to an external synth. In version 8 it works
(https://www.mutools.com/info/M8/docs/mu ... utput.html), but in the beta I can't drop the project event output on a track.
Did something change with using external gear in version 9? How do I make the connections to external gear?

Sorry it took more time than expected to reply in depth on this, due to some difficult bugs last week.
Ok, so how to send events to external MIDI in M9:
1) Send the events in to a composer event output.
2) In the project modular area: Insert a "Project Event Output" and connect that composer event out to this Project Event Out.
So admitted this is an extra step compared to M8 and that's because the composer now is a module. But i think the advantages of the composer being a module are much greater than eg this little extra connection to send composer events to MIDI output.
If you have any additional questions/suggestions about this, let me know.

[pljones]

If I've got defined hardware MIDI Outs it would probably make sense for the project-level modular area having an Event Out for each hardware out, plus the composer Event Out defaulting to being wired to all of them, maybe?

Anything more complex then is a matter of adjusting the layout that's visible, rather than having to work it out from scratch.

[MuTools]

If I've got defined hardware MIDI Outs it would probably make sense for the project-level modular area having an Event Out for each hardware out, plus the composer Event Out defaulting to being wired to all of them, maybe?

MuLab indeed automatically creates MIDI output modules after you've changed the MIDI setup.

[shorty]

Sorry it took more time than expected to reply in depth on this, due to some difficult bugs last week.
Ok, so how to send events to external MIDI in M9:
1) Send the events in to a composer event output.
2) In the project modular area: Insert a "Project Event Output" and connect that composer event out to this Project Event Out.
So admitted this is an extra step compared to M8 and that's because the composer now is a module. But i think the advantages of the composer being a module are much greater than eg this little extra connection to send composer events to MIDI output.
If you have any additional questions/suggestions about this, let me know.

That's it! Fantastic Thanks so much

[heks]

I normally drag and drop instruments and effects on to Mulab from open files on one of my other monitors but it doesn't seem to be working in 9.0.10 this morning. Can someone confirm if its working for them.

[MuTools]

Please elaborate what you precisely mean. What do you mean with "...from open files..."