MuLab 7.0.47

[MuTools]

I found two strange errors..
When you want to reset a controller (alt + left click) on the mux front panel,sometimes appears an hourglass or a rubber.

Quickly tried this but works fine here. Any more details how i can repeat it?

The other error concerns the name of the waveform,when save a patch and after reload the oscillator shows only the name "waveform" instead of the correct name saw,sine..I thought it was my mistake but noticed that happening very often.

I quickly tried this with factory waveforms and it works fine here.
Is that when using factory waveforms or custom user waveforms?
Any step by step how i can repeat what you encounter?

[MuTools]

There is a new M7.0.17 in http://www.mutools.com/galaxa/

What's changed:

• Audio Recorder: Support for recording directly from the audio device audio inputs, without the need for an Audio Input module. This workflow shortcut makes traditional audio track recording even more easy. This is also the default when doing "Add Audio Track".
• Audio Recorder: Monitor on/off state was not saved in the project file. Fixed.
• Finetuned an aspect wrt opening older project files.
• Fixed a time-sync issue in the Step Sequencer.
• When opening a project with missing audio files, then upon locating such missing audio files the file browser was not supporting previewing. Fixed.

How to update:
Make sure you already have installed the complete M7.0.12 package. Then:
OSX: Replace the existing M7 MuLab.app file by the new version in the small zip file.
Windows: Replace the existing M7 MuLab.exe and MuLab.ID files by the new versions in the small zip file.

[Taifunk]

I found two strange errors..
When you want to reset a controller (alt + left click) on the mux front panel,sometimes appears an hourglass or a rubber.

Quickly tried this but works fine here. Any more details how i can repeat it?

This does not happen often, I'm working on a custom patch and occasionally happens on the front panel,at the moment I do not know how to replicate the error,I try to do some tests.

The other error concerns the name of the waveform,when save a patch and after reload the oscillator shows only the name "waveform" instead of the correct name saw,sine..I thought it was my mistake but noticed that happening very often.

I quickly tried this with factory waveforms and it works fine here.
Is that when using factory waveforms or custom user waveforms?
Any step by step how i can repeat what you encounter?

at the time this happened when loading a factory waveform
I did some quick tests ,loaded a saw straight waveform , right click chose rotate,saved and reloaded the patch and the name is changed to "waveform"Is this normal?

[MuTools]

at the time this happened when loading a factory waveform
I did some quick tests ,loaded a saw straight waveform , right click chose rotate,saved and reloaded the patch and the name is changed to "waveform"Is this normal?

Ah yes that's intended cause you have edited the waveform so the the link to the original waveform file is cleared.

[sl23]

Perhaps ~ new waveform, or wave edited? Or the classic ~ waveform*

[Taifunk]

at the time this happened when loading a factory waveform
I did some quick tests ,loaded a saw straight waveform , right click chose rotate,saved and reloaded the patch and the name is changed to "waveform"Is this normal?

Ah yes that's intended cause you have edited the waveform so the the link to the original waveform file is cleared.

I figured it had something to do with editing,In fact i usually only it inverts the phase of the factory waveform ,I think that is fine as well, this is very useful to avoid confusion between modified and unmodified waveforms ,no problem for me the important thing is to know it

Perhaps ~ new waveform, or wave edited? Or the classic ~ waveform*

Also this could be an option if it is more convenient for different users.

[Taifunk]

There is a new M7.0.17 in http://www.mutools.com/galaxa/

What's changed:
[*]Audio Recorder: Support for recording directly from the audio device audio inputs, without the need for an Audio Input module. This workflow shortcut makes traditional audio track recording even more easy. This is also the default when doing "Add Audio Track".

this new feature will greatly speed up the workflow,thanks for the update.

[MuTools]

Perhaps ~ new waveform, or wave edited? Or the classic ~ waveform*

Thanks for the suggestion, but it's not as simple as it may seem, and i'm gonna avoid complications atm. The next version has one improvement though: When editing a waveform and hence the link to the original file is cleared this will be immediately visible in the waveform name, which was not yetthe case and that's what made it confusing. Fixed in the next version.

[MuTools]

There is a new M7.0.17 in http://www.mutools.com/galaxa/

What's changed:
[*]Audio Recorder: Support for recording directly from the audio device audio inputs, without the need for an Audio Input module. This workflow shortcut makes traditional audio track recording even more easy. This is also the default when doing "Add Audio Track".

this new feature will greatly speed up the workflow,thanks for the update.

Yes this is an important conceptual+workflow improvement! Finally MuLab can be used as an easy traditional audio track recorder without any 'penalty' of the modular architecture. Simple and easy: Add an audio track, tell it from which inputs to record from, go. While the modular recording options are still all there.

[sl23]

it's not as simple as it may seem,

I doubt it ever is!

[Taifunk]

Yes this is an important conceptual+workflow improvement! Finally MuLab can be used as an easy traditional audio track recorder without any 'penalty' of the modular architecture. Simple and easy: Add an audio track, tell it from which inputs to record from, go. While the modular recording options are still all there.

This is a great update and I agree ,now simply open mulab and begin recording!
and for a new user who opens for the first time mulab this is really useful.

The next version has one improvement though: When editing a waveform and hence the link to the original file is cleared this will be immediately visible in the waveform name, which was not yetthe case and that's what made it confusing. Fixed in the next version.

The new improvement will be fine!
Absolutely,avoid complications Jo.
I find it only useful to specify that in the users guide for inform the user how it works,because this is not a problem but rather a function.

[nenneb]

Today I ask for a (small but useful) feature:
As I use my studio-PC offline without internet-connection, I copied the manual/docs into a folder. Unfortunately the link to the help docs is hardcoded. I also did not find a way to get it by shortcut-key.
It would be great to have the help-file-location set in the preferences. Thank you in advance.

And (although I'm afraid, you don't plan that for M7), only for not to forget:
Please extend the logical selector by "time-position within bar"
Please add a "rewind to start" button (I work around with shortcut)
Please add "info-markers", so one can note chords or other memos.

Btw: M7 works great for me! (except the above ...)

[MuTools]

Today I ask for a (small but useful) feature:
As I use my studio-PC offline without internet-connection, I copied the manual/docs into a folder. Unfortunately the link to the help docs is hardcoded. I also did not find a way to get it by shortcut-key.
It would be great to have the help-file-location set in the preferences. Thank you in advance.

What about making such shortcut on your system? That would solve it too.

Please add a "rewind to start" button (I work around with shortcut)

Next version: Shift+click on rewind button = rewind to start.

Please add "info-markers", so one can note chords or other memos.

What's wrong with the current markers? They can contain any text.

[runaudio]

Please add DB to the Sustain on the MuSampla Please

[syntonica]

Hi Jo,

Please don't hit me. Okay?

(...but I like the old font better... It's easier to read since it's less anti-aliased. The new font is just too fuzzy for my poor, tired eyes.)

</RUNS FOR THE HILLS! >

Are you using bitmap fonts or TTF fonts? And can I substitute my own when nobody is looking by copying them over and renaming them?