MuTools

hcv242 · Post by **hcv242** » Sun Jul 29, 2012 12:53 am

ive noticed that there is no more beta link. it redirects to the product page.

where can i check the changes.txt ?

do vst plugs that require tempo \ sync info work ok with mux, now ?

request : open vst\vsti guis with midi cc.

MuTools · Post by **MuTools** » Sun Jul 29, 2012 9:02 am

hcv242 wrote:ive noticed that there is no more beta link. it redirects to the product page.
where can i check the changes.txt ?

http://www.mutools.com/mux-downloads.html
http://www.mutools.com/mux/ChangeLog.txt

do vst plugs that require tempo \ sync info work ok with mux, now ?

Yes, that should be ok now.

(strange, can't find that in the change log, maybe i forgot to list that improvement)

Crackbaby · Post by **Crackbaby** » Tue Jul 31, 2012 2:38 am

Any luck on the "sending parameter info" issue? Have you had any reply from NI? I hope things go well!

MuTools · Post by **MuTools** » Tue Jul 31, 2012 10:56 am

FYI: The first workaround i installed was just to test where the problem is. But that was a bit a risky workaround so that's why i removed it again, as i messaged. Now i'm still searching for a solid solution and have posted a question on a tech forum about this but no reply yet. I did not yet email NI as i first wanted to know what that tech forum would say. The problem is that the actual issue is somewhere in the gray zone of the VST system, it's an undefined situation. I did already think about a possible safe workaround. I'll evaluate all this further and will decide before release.

About the Novation Automap issue: I'm communicating with Novation on this.

Crackbaby · Post by **Crackbaby** » Tue Jul 31, 2012 12:55 pm

Alright, thank you!

MuTools · Post by **MuTools** » Wed Aug 01, 2012 10:00 pm

Crackbaby, please install the latest MUX Vst 1.0.32. Then when it's not plugged in, got to the MUX/User/Settings folder and open MainSetup.txt and add this line:

SetChunkMustCallUpdateDispay=1

Then save the file.
This will give you the same behaviour as in that test version.

I tried to email NI about this, but they have very difficult support access.
I think it's better that you would email them about it as you are the Maschine user. The above preference is a workaround that will help us further, but it would be more neat if the issue is sorted out in a more clear way.

Crackbaby · Post by **Crackbaby** » Wed Aug 01, 2012 10:11 pm

Ah thank you, that's awesome!!! Parameters are loaded with both vst and vsti version of mux..!

Contacting NI's ... support? That's like robocop fighting magnetic mines ..

Ill try it tomorrow, tonight it's playing eve-time

Crackbaby · Post by **Crackbaby** » Thu Aug 02, 2012 11:53 am

I've noticed that not all Mux's i've saved in maschine load the parameters. I THINK it's the ones i've done with an earlier version of mux.
My mainsettings are:

ApplicationRunCount=24
UseUnfoldedContextMenus=1
Logging=0
MenuFontSize=Medium
ExternalAudioEditorApplicationPath=
UserKeyString=12345

SetChunkMustCallUpdateDispay=1

I took one mux where the parameters are updated and resaved it in another maschine preset - that one would not update them.

Edit: Do you want me to send you one "working" and one that doesn't? It seems i have trouble finding them all as i changed folder where i stored them and now there's doublets and some i can't find at all. Also im a bit hypomanic today so this is not easy for me ...

MuTools · Post by **MuTools** » Thu Aug 02, 2012 12:13 pm

I assume the presets that 'don't work' are saved some longer time ago, with the very first public test versions of MUX Vst, right?

So please try this: When you encounter a Maschine preset that 'doesn't work', then just resave that Maschine preset. Then load it again and it should work. Right?

Crackbaby · Post by **Crackbaby** » Thu Aug 02, 2012 2:59 pm

It was the other way around actually

The very first one i made which was just a mux filter works fine. Some early mux's with SK-Note also works fine. By early i also mean those i saved in maschine early so it's not just that the mux is old.

When i tried to save this filter mux under another preset name in maschine it didn't work. I resaved the mux under another name and then saved a new maschine preset - no work either! Oh i wish i could borrow your brain and make a copy/paste

Then i would feel 100% more useful trying to explain this

As i said, my head isn't working 100% now, more like 145% inverted and up-side-down, tilted and

Ill have another look tonight and check dates on working patches and maybe we could figure out this mystery

.. Oh i love an ol' good mystery to crack!

Crackbaby · Post by **Crackbaby** » Fri Aug 03, 2012 9:16 am

After a long going through and searching session i found that only seven muxes still load parameters for maschine. It's four effects and three synths.
They're all saved 2012-07-16. They contain vst's so that's not the issue. There must be something in the file format from that early version which ever one it was. Anything that rings like a bell about that?

Anyone else with maschine who can try this? I hate to think that there would be something at my end. I know that i have moved the mux installation at least once (from test folder to my "essential" folder). But it has not been the same dll's or app/user. Considering the presets in question, i remember that day and i know they're all made with the same version of mux.
Can you re-upload one of the betas from that time so i can try them? I'd love to be able to figure this out

Maschine hasn't changed since then, no patches or anything.

MuTools · Post by **MuTools** » Fri Aug 03, 2012 10:33 am

Crackbaby, i don't understand the situation.

Lets keep things simple at this point and talk about the present situation i.e. MUX Vst 1.0.32.

So you're saying that if you now make a new Maschine preset that uses the MUX Vst, and you save that preset, then you change things, then you reload that new Maschine preset, then Maschine still doesn't update the parameter names, right?

When i made that test version a couple of weeks ago, then you could immediately confirm everything was working ok. Now i added the exact same line of code again, with the only change that the user can control whether it's active or not i.e. using that preference. So i don't understand why i wouldn't work anymore.

Crackbaby · Post by **Crackbaby** » Fri Aug 03, 2012 11:54 am

Yes, that's exactly how it is!
If i take one that's working (of those 7) and save it under another name (which should be exactly the same thing), it won't work. I've tried every possible combination of renaming mux and maschine preset in order to find some consistency.
Has there been no change in file format of the muxes?

I think the line of code is working as it should. Because it does what it shall on those seven working presets.

MuTools · Post by **MuTools** » Fri Aug 03, 2012 12:22 pm

To narrow things down, lets please forget about any existing Maschine presets at this point. Make a completely new Maschine preset using the MUX. Are the parameter names updated if that new preset is loaded again? If not, then are you sure you are using the latest MUX and have that preference enabled? If both yes then i'm afraid i can't do much more, so then please contact Native Instruments. I'm open to cooperate with NI to resolve this issue, please include that in your support request to NI.

Crackbaby · Post by **Crackbaby** » Fri Aug 03, 2012 4:00 pm

Oh man ........ redownloaded again ... and ... and .... Im just going to run away and hide in the corner for the rest of my life

I will just assume that my computer went rogue on me and undid the replacement of the old version somehow.
Maybe i missed replacing the app folder? Ahh im sorry

Though im also so very happy as you can imagine. Im so very very happy. And relieved.

MuTools

KVR Audio

MUX Vst : What do you need?