MuLab 7.0.47

[sl23]

I never had this warning before?

The warning only started to popup recently as we're getting closer to that time expiration.

Even stranger! As I said, it didn't appear on M7.0.26, or is it a once daily thing?

Any idea on price yet for upgrade?

Will be specified upon pre-release, which will be within a week.[/quote]
Ooh, ok, look forward to that. Can we then purchase once pre-release is, uh, released?

[MuTools]

I never had this warning before?

The warning only started to popup recently as we're getting closer to that time expiration.

Even stranger! As I said, it didn't appear on M7.0.26, or is it a once daily thing?

Yes it only comes once a day.

Any idea on price yet for upgrade?

Will be specified upon pre-release, which will be within a week.

Ooh, ok, look forward to that. Can we then purchase once pre-release is, uh, released?[/quote]
Yes.

Just FYI:
I use these dev phases: Design, R&D, Test, PreRelease and Release.
In the case there would be unexpected issues next week and i can't get the pre-release ready before next weekend, the test phase will be prolonged and the test expiration date will be pushed forward a bit. But hopefully that won't be necessary.

[Simon Posford]

By the way the bug about the popup (right click) is not fixed.

Which bug? Pls elaborate.

You know i have emailed you about this problem:
The bug described in this post

http://www.kvraudio.com/forum/viewtopic ... 4#p6415084

[MuTools]

Ok i see what you mean. Well at this point i regard that as a bug in El Capitan. If things are working fine in all OSX versions up to 10.10 and then Apple adds some new feature in 10.11 which suddenly and unexpectedly breaks compatibility with software that was running fine for years on all their previous OSX versions, well then i regard this as an issue on OSX side.

As you know this is not the first problem with OSX's own version incompatibilities and i'm not talking about MuTools only, it's also the case with big companies like Roland, Native Instruments and others. More and more devs are getting seriously annoyed by Apples own incompatibilities. Search the web for more details.

About the Autohide Menubar problem: For now solution is to disable that OSX feature as it seems to cause the trouble. Maybe i'll see if i can find a workaround in a future version but that's not planned for M7.0. I'll add this relevant info to the docs.

All the above said, including my substantiated criticism on the incompatibilities between OSX versions, i can tell you that i finally took decision to invest resources in MuTools' OSX setup and planned effective research for pushing MuLab to a new level of supporting OSX, research MUX for Mac and research 64 bit versions for Mac. Can't give a time estimation yet, but decission has been taken and i've already made certain investments. To be continued.

[sl23]

Just FYI:
I use these dev phases: Design, R&D, Test, PreRelease and Release.

OK thanks for the info. Does that mean pricing is revealed at pre-release stage?

[pljones]

OK thanks for the info. Does that mean pricing is revealed at pre-release stage?

Any idea on price yet for upgrade?

Will be specified upon pre-release, which will be within a week.

[sl23]

Oh yeah missed that

That's why I hate using phones to browse internet! But I'm bored and don't have access to PC!

[MuTools]

There is a new MuLab 7.0.28 in http://www.mutools.com/galaxa/mulab/

What's changed:

• Finetuned the condition for when activating a module editor window will also auto shift MIDI input focus:
  Now this is only done when the activated editor is part of some synth patch or a module that has MIDI controller mappings.
• Render Rack To Audio Tracks: Faster rendering.
• Render Rack To Audio Tracks: The rendered parts don't irrelevantly grow in length anymore after each (re)render.
• Upon deleting an audio stream from the project, you now get the option to also delete the audio file on disk. This not only is a handy feature but it also emphasizes the difference between an audio stream (=project RAM) and an audio file (=disk file).
• Audio parts: Fixed a potential playback bug.
• Some other micro improvements.

How to update:
Make sure you already have installed the complete M7.0.24 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.
mutools.com

[Simon Posford]

Thanks for the words about the osx menu bar bug.
Thinked you have just ignored it cause i didn't received mail answer: well yes it's not too annoying to disable the autohide feature

And yes am aware about osx compatibilty problems with others developpers.
They simply put more effort on the ipad/iphone side it's clearly visible.

I just hope for the return of the skinning possibility rather than this bug fixed :p

[samardac]

Explain pleas this more detail:

Finetuned the condition for when activating a module editor window will also auto shift MIDI input focus:
Now this is only done when the activated editor is part of some synth patch or a module that has MIDI controller mappings.

Wanted to ask you will you implement simple reset knob/fader function?

[MuTools]

Thanks for the words about the osx menu bar bug.
Thinked you have just ignored it cause i didn't received mail answer

I was (silently?) happy you found the reason+solution. I've added that info to the docs. (most up to date docs will be online soon)

[MuTools]

Explain pleas this more detail:

Finetuned the condition for when activating a module editor window will also auto shift MIDI input focus: Now this is only done when the activated editor is part of some synth patch or a module that has MIDI controller mappings.

Euh not sure if i can explain it better. Well here is a practical case we both encountered: Some synth rack and some audio effect rack that also processes the synth sound. Click synth rack to play synth, then tweak knobs on audio effect editor made an unwanted shift in MIDI focus. Now this will not happen anymore cause an audio effect is not a synth. Note however that if you mapped a MIDI controller to some parameter of that effect then MIDI focus will shift cause you might want to play the effect. In any case if you don't like this automatic MIDI focus shift upon activating editors you can switch that feature off in the preferences.

Wanted to ask you will you implement simple reset knob/fader function?

No, not in M7.0. And at this point not planned for later. If many users would feedback they don't like to have these different hot spots in the parameter value range then it may be reconsidered lateron.

[MuTools]

I just hope for the return of the skinning possibility

Full user skinnability is not planned as it can add a lot of complications. But feel free to post a full resolution mockup of how you would like MuLab/MUX to look like.

[samardac]

Thanks.
About Reset, I don think that it is good idea to change/add things only when users asked them for. Users in general are not software developers or workflow optimizators, they just use what they have and do not spend alot of time to think about how to optimize or make software better. MuLab is software with great potential, but it is version 7 and still a lot of obvious stuff is not optimized or standardized. And it is a key thing to attract new users. It is not right way to create new stuff without polishing already existing stuff and workflow. I am new user I tried MuLab for a week and still do not know buy it or not because I see that you are not willing to optimize already existing stuff even if it is obvoius, you prefere to wait till a lot of users tell you that

[MuTools]

It is not right way to create new stuff without polishing already existing stuff and workflow.

That's exactly why i invested a great part of the M7 r&d time in improvement!
See http://www.mutools.com/m7-intro.html

I see that you are not willing to optimize already existing stuff even if it is obvoius

You seem to have missed the most recent change logs.