MUX Modular Plug-In 7.0.47

Official support for: mutools.com
Post Reply New Topic
RELATED
PRODUCTS

Post

MUX Modular Plug-In 7.0.40 is available.

Latest changes since version 7.0.36:
  • Fixed a potential crash bug in the automation/modulation system when doing extreme automations/modulations ie. using high frequency loops and/or complex shapes. For such cases use audio-rate modulation.
  • Fixed a potential crash bug in the TF Lowpass filter, especially when modulating the cutoff while overloading the modulation system.
  • When a MUX patch exceeds the standard modulation system limits, now a warning alert pops up. This only happens in extreme situation and then solution is to use audiorate modulation.
  • Upon loading projects/presets that use samples, any markers that are outside the sample start-end range (eg sample has been edited elsewhere) are pulled inside that range.
  • Step Sequencer: The Select & Play switch now is off by default. And when the user switches it on, then Auto Transpose and Arpegiator Mode both are automatically switched off and disabled as they're not compatible with the Select & Play mode.
  • Step sequencer: MIDI CC pane: The Mod Groups are also applied to aftertouch and pitchbend events.
  • When switching between editor windows and other apps, now switching back to a VST editor auto focuses the VST editor itself. This is related to using key shortcuts.
  • When a VST editor requests a window resize to make the window smaller, then it could happen that the top control panel (with MuTools' open/save/option buttons etc) was not fully visible anymore. Fixed.
If you already have installed the MUX 7.0.32 package or up, then you can apply this quick app patch:
http://www.mutools.com/mux/app-patch/index.html
Top

Post

mutools wrote:MUX Modular Plug-In 7.0.40 is available.

Latest changes since version 7.0.36:
  • Fixed a potential crash bug in the automation/modulation system when doing extreme automations/modulations ie. using high frequency loops and/or complex shapes. For such cases use audio-rate modulation.
  • Fixed a potential crash bug in the TF Lowpass filter, especially when modulating the cutoff while overloading the modulation system.
  • When a MUX patch exceeds the standard modulation system limits, now a warning alert pops up. This only happens in extreme situation and then solution is to use audiorate modulation.
  • Upon loading projects/presets that use samples, any markers that are outside the sample start-end range (eg sample has been edited elsewhere) are pulled inside that range.
  • Step Sequencer: The Select & Play switch now is off by default. And when the user switches it on, then Auto Transpose and Arpegiator Mode both are automatically switched off and disabled as they're not compatible with the Select & Play mode.
  • Step sequencer: MIDI CC pane: The Mod Groups are also applied to aftertouch and pitchbend events.
  • When switching between editor windows and other apps, now switching back to a VST editor auto focuses the VST editor itself. This is related to using key shortcuts.
  • When a VST editor requests a window resize to make the window smaller, then it could happen that the top control panel (with MuTools' open/save/option buttons etc) was not fully visible anymore. Fixed.
If you already have installed the MUX 7.0.32 package or up, then you can apply this quick app patch:
http://www.mutools.com/mux/app-patch/index.html
Still missing the ability to change font size in the audio browser of sampla. This must be of an extremel ylow low low priority :-(
Top

Post

Can Mux 6 and 7 coexist on the same computer? Are the dll files labeled differently? I don't want to remove/replace 6 as I have projects that use it, so don't want to tamper with it.
Top

Post

sfd wrote:Still missing the ability to change font size in the audio browser of sampla. This must be of an extremel ylow low low priority :-(
It's not about low low priority, it's rather because your FR is related to a more general FR: The ability to rescale the UI. Though it's being worked on in the background, step by step, it's not yet to be expected on very short term, certainly not yet for M7.0.
Top

Post

bbreakz wrote:Can Mux 6 and 7 coexist on the same computer?
Yes, no prob at all. Just install them in different folders. Simple and easy.
Are the dll files labeled differently?
No.
I don't want to remove/replace 6 as I have projects that use it, so don't want to tamper with it.
I understand. Install them in different folders and it will work fine. Both MuLab and MUX VST are completely self-contained within their installation folder.
Top

Post

Got it, thanks!
Top

Post

Quick question -- is it intentional that, when using the "Open Preset" button in MUX that, when a preset is selected but before you click the "OK" button, the preset replaces the current preset?

That's a bit of an issue when I've got 2Gb sample sets that get loaded - there's a long delay if I click the wrong preset whilst the data gets loaded up. When I click "OK", the preset is loaded again, so I have to wait again whilst the data loads. If I click cancel, the previous preset has to load, again quite a delay to get its samples back in.

I can understand for simple internal patches that they load pretty much instantaneously but there's no way to predict how long a MUX preset will take to load, so it could be very inconvenient.

I actually found it confusing -- I didn't realise the preset wasn't really loaded and started using it, because one of the VSTs in the patch messed with the window Z-order and the Open Preset window was hidden. MUX then seemed to be behaving oddly and unresponsively -- because it still had the Open Preset window up - but now hidden behind others. I don't blame this on MUX, of course: but had the preset not loaded until I hit OK, the opportunity for confusion would not have arisen.

-EDIT- Oh, actually, I think I do blame MUX for the Z-Order issue. If I switch focus from MUX when it has Open Preset open, then switch back, I'd expect the modal dialog to get displayed. In fact an unresponsive window is displayed. Until you manage to get the Open Preset window to the top and close it, the MUX won't do anything.
Top

Post

pljones wrote:Quick question -- is it intentional that, when using the "Open Preset" button in MUX that, when a preset is selected but before you click the "OK" button, the preset replaces the current preset?
Yes it's auto preview.
I can understand for simple internal patches that they load pretty much instantaneously but there's no way to predict how long a MUX preset will take to load, so it could be very inconvenient.
I understand. Taken note on the wishlist about being able to switch on/off the auto preview.
Top

Post

mutools wrote:
I can understand for simple internal patches that they load pretty much instantaneously but there's no way to predict how long a MUX preset will take to load, so it could be very inconvenient.
I understand. Taken note on the wishlist about being able to switch on/off the auto preview.
It's a bit of a tricky one. If there could be a switch actually on the selection list window itself that remembered the last setting, that might be best. I wouldn't want to get there and realise I needed switch from one setting to the other and have to go out to preferences to turn it on or off. It's one of those things in live situations you just want to be able to do without fuss.
Top

Post

MUX Modular Plug-In 7.0.41 is available.

It fixes another potential crash bug in the automation/modulation system when doing extreme automations/modulations ie. using high frequency loops and/or complex shapes. For such cases use audio-rate modulation.

If you already have installed the MUX 7.0.32 package or up, then you can apply this quick app patch:
http://www.mutools.com/mux/app-patch/index.html
Top

Post

mutools wrote:
sfd wrote:Still missing the ability to change font size in the audio browser of sampla. This must be of an extremel ylow low low priority :-(
It's not about low low priority, it's rather because your FR is related to a more general FR: The ability to rescale the UI. Though it's being worked on in the background, step by step, it's not yet to be expected on very short term, certainly not yet for M7.0.
It's of coruse great with a resizable GUI. So, yea, that's good news.

A few versiosn back you added a n option that let's the user elect font size for the browser. That's really a a great function.

The audio browser in sampla looks and feesl identical to other browser in MUX. Apart for this one thing - you can't select font size.

Isn't it actually the same browser? Just that this font size thing wasnt' implemented just there?

Would it be a big trouble to add that fucntion to that one browser too?

Resizable GUI is , again, great. But it's a bit funny to rezie the eintre GUI to fill the whole screen just to have a bit larger fonts in the browser. Also considerign the fact that this option is allready added in all other browsers.
Top

Post

Okay, I've gone through this entire thread. Thank goodness it's not too long yet.

I'm ready to upgrade to MUX 7. I do have some questions and concerns first just to make sure I don't screw anything up. Also just want to clarify a few things.

Let's begin.

1) From what I am reading, MUX 6 and MUX 7 have the same dll names so in order for me to run both, I need to install MUX 7 in a different folder. Correct?

2) I see that the discount upgrade price is only good until May 29. I was hoping by now that MUX 7 would be a relatively stable release but I can see by the pretty regular updates that we're not quite there yet. I'm a little skittish about upgrading now before most of the kinks are ironed out and at the same time, only have 4 days remaining to take advantage of the discount. This kind of puts me in a weird place. There is no question that I'm getting MUX 7 eventually, but I prefer not to be a beta tester on something that is so incredibly complex. My first library took me months to make. I guess I'm looking for some guidance here. Help?

3) When is the actual release going to be made? Or is that something that's still up in the air?

4) I am also thinking of finally purchasing MuLab 7. This also makes things a little awkward as I'm not sure how this would work. While I don't own MuLab 6 I do own MUX 6. So technically, I guess, I'm only entitled to half an upgrade. How does this work? I'm guessing I have to purchase a full key for MuLab 7. But then I end up paying more the MUX 7 portion of that purchase. Is there an option for those who own MUX 6 but don't own MuLab 6 to get MuLab 7 at a somewhat reduced price? I guess this is something that probably doesn't come up much, if at all.

Anyway, that's about it. Any info you can provide on the above would be greatly appreciated.
Top

Post

wagtunes wrote:1) From what I am reading, MUX 6 and MUX 7 have the same dll names so in order for me to run both, I need to install MUX 7 in a different folder. Correct?
Correct.
2) I see that the discount upgrade price is only good until May 29. I was hoping by now that MUX 7 would be a relatively stable release but I can see by the pretty regular updates that we're not quite there yet. I'm a little skittish about upgrading now before most of the kinks are ironed out and at the same time, only have 4 days remaining to take advantage of the discount. This kind of puts me in a weird place. There is no question that I'm getting MUX 7 eventually, but I prefer not to be a beta tester on something that is so incredibly complex. My first library took me months to make. I guess I'm looking for some guidance here.
You could take the upgrade now and delay using it until you feel ok with it. That said, i'll make sure there is reasonable time between release and the end of the upgrade promo so users who only know about M7 upon release also get the chance to take the upgrade promo. So this means the upgrade promo will be prolonged a bit. I didn't expect that there would be that much time between pre-release and release. Release is pretty close now. Indeed there have been some bug fixes, but hey, don't you see bug fixes in the software releases of other manufacturers?! I think M7 is getting pretty stable. FYI: There will be at least 1 other pre-release update, available soon.
3) When is the actual release going to be made?
When everything is ready. Hopefully very soon now.
4) I am also thinking of finally purchasing MuLab 7. This also makes things a little awkward as I'm not sure how this would work. While I don't own MuLab 6 I do own MUX 6. So technically, I guess, I'm only entitled to half an upgrade. How does this work?
Indeed you can't do a MuLab upgrade as you don't have a MuLab user key yet. But there is the MUX Mocular -> MuLab crossproduct promo which gives you a discount on your MuLab user key. See http://www.mutools.com/shop.html
Top

Post

mutools wrote:
wagtunes wrote:1) From what I am reading, MUX 6 and MUX 7 have the same dll names so in order for me to run both, I need to install MUX 7 in a different folder. Correct?
Correct.
2) I see that the discount upgrade price is only good until May 29. I was hoping by now that MUX 7 would be a relatively stable release but I can see by the pretty regular updates that we're not quite there yet. I'm a little skittish about upgrading now before most of the kinks are ironed out and at the same time, only have 4 days remaining to take advantage of the discount. This kind of puts me in a weird place. There is no question that I'm getting MUX 7 eventually, but I prefer not to be a beta tester on something that is so incredibly complex. My first library took me months to make. I guess I'm looking for some guidance here.
You could take the upgrade now and delay using it until you feel ok with it. That said, i'll make sure there is reasonable time between release and the end of the upgrade promo so users who only know about M7 upon release also get the chance to take the upgrade promo. So this means the upgrade promo will be prolonged a bit. I didn't expect that there would be that much time between pre-release and release. Release is pretty close now. Indeed there have been some bug fixes, but hey, don't you see bug fixes in the software releases of other manufacturers?! I think M7 is getting pretty stable. FYI: There will be at least 1 other pre-release update, available soon.
3) When is the actual release going to be made?
When everything is ready. Hopefully very soon now.
4) I am also thinking of finally purchasing MuLab 7. This also makes things a little awkward as I'm not sure how this would work. While I don't own MuLab 6 I do own MUX 6. So technically, I guess, I'm only entitled to half an upgrade. How does this work?
Indeed you can't do a MuLab upgrade as you don't have a MuLab user key yet. But there is the MUX Mocular -> MuLab crossproduct promo which gives you a discount on your MuLab user key. See http://www.mutools.com/shop.html
As always, thank you for being so helpful. You are absolutely the best. Will definitely look into the cross product promo. You do think of everything. LOL.
Top

Post

mutools wrote:
sfd wrote:Still missing the ability to change font size in the audio browser of sampla. This must be of an extremel ylow low low priority :-(
It's not about low low priority, it's rather because your FR is related to a more general FR: The ability to rescale the UI. Though it's being worked on in the background, step by step, it's not yet to be expected on very short term, certainly not yet for M7.0.
I use my Sherlock Holmes type magnifying glass for reading stuff in certain components in Mulab :hihi: You must still have very good vision... :P
Top
Post Reply

Return to “MuTools”