MUX Vst : What do you need?

[fluffy_little_something]

I suppose that's normal when you adapt a complex piece of software to a different platform. That's why the VST cannot be bought, yet.

It would help the developers if you at least stated the general situation or nature of those errors and crashes.

[MuTools]

I would appreciate if you could be more specific.
"Tons & millions of crashes" is not really helping, to be honnest.
Whenever you have a crash, please post what you experienced.
Just a basic description of what happened could already be helpful.
(the more details the better of course)
Thanks.

[MuTools]

@Hcv242: Some concrete questions about the crashes you experience:

1) Is it when you insert or delete a MUX Vst?

2) What samplerate and audio block size are you using?

@Others: Anyone else experiencing crashes with MUX Vst 1.0.18?
If yes, same questions.

Thanks.

[sl23]

we need a splash screen with some crazy animation... how about an intro movie that explains ancient mu history and somehow ties mutools into the story line... so kids think its a video game HiHi

Sounds good, but would be better if it was playable instead of just a movie

[Crackbaby]

Is there a reason why i should hold a potential purchase of mulab for the release of mux? Im thinking crossgrade etc
It's not a lot of cash, but recent spendings makes my visa nervous ...
Also i got a little burnt buying another host recently where the dev has shown no sign of further development ... you on the other hand, seem to not stopping anytime soon

[Crackbaby]

Nevermind:

You just completed your payment.

Nice... got serial straight away and activation easy in program .. thumbs up!!!

[hcv242]

1) Is it when you insert or delete a MUX Vst?

it happens with vst and mux native modules...but it happens in many more situations.

2) What samplerate and audio block size are you using?

44100hz \ 256 samples


i've reported two issues in the page before that you didnt comment . couldnt you reproduce them ?

here is an easy one that i could reproduce with no problems:

i've done a patch with 4 musamplers and saved the preset. ive tried to load it later with no luck. mux displays: "couldnt load preset file". ive done it again and the result was the same. if i save the preset as FXP instead of the native file format it saves and loads ok. ive tried with embebed sampled and with files references, the result is the same. here is a link to the FXP (with samples embebed): http://dl.dropbox.com/u/15962615/4_musamplers.zip

you can load the FXP and save it as a mux preset to check the problem.

the thing is ...beta testing is very time consuming and i dont have the time. i would love to help more but i dont have the time

[MuTools]

mux is not working correctly with some vst plugins wich require bpm time\sync info. you can check this with piz midiSimpleLFO (a midi plugin that generates cc automation data) the plug only generates cc data if the triggering option is set to free. if i set it to bpm sync there is no cc data output. i've found another plugin with the same issues but i cant remeber it

Indeed MUX Vst 1.0.18 still lacks proper support for giving timing info to the VST plugs it hosts. That's implemented in the next MUX Vst.

Note that while researching this i noticed that midiSimpleLFO does not seem to be the most stable plugin! Especially when loading a host project that includes midiSimpleLFO, or that includes a MUX Vst that includes a midiSimpleLFO.

Maybe some of the crashes you experienced may be caused by buggy VST plugins too. I'm not pushing away responsability, but atoh i can't be responsible for what happens inside buggy VST plugins. Anyway, i'm looking forward to your more detailed answers.

Meanwhile i'll publish the next MUX Vst as that version should be more stable (yes i discovered and fixed a couple of bugs) and includes a number of improvements

[> DiGiT <]

wouldnt it be helpful to you if the beta mux had some logging active or some way to tell what the user was doing at the time of a crash? maybe its easier for them than recounting everything? maybe that would make it harder for you? i dont know these things really haha

[Crackbaby]

I have logging enabled (think i enabled it by accident... )

it says stuff like

01:03:22:368 MS Windows Home Edition
01:03:22:368 MUX 1.0.18 - 32 bit
01:03:22:368 /H:/VST/MUX.dll
01:03:22:514 ValhallaUberMod has VST version 2400
01:03:22:957 Vocal Stereo TapeDelay has VST version 2400
01:03:22:970 ValhallaUberMod has VST version 2400
01:03:22:979 ValhallaUberMod has VST version 2400
01:03:22:987 ValhallaUberMod has VST version 2400
01:03:30:803 ValhallaUberMod has VST version 2400
01:03:30:968 Etch has VST version 2400

[MuTools]

1) Is it when you insert or delete a MUX Vst?

it happens with vst and mux native modules...but it happens in many more situations.

Can you please be more specific.
What exactly happens When?
Sorry to dig into this but i'm just trying to get a grip on this.

2) What samplerate and audio block size are you using?
44100hz \ 256 samples

Ok, thanks.
So that's not the reason for the crashes as 1.0.18 *may* have probs with buffer sizes greater than 1024 samples. That's fixed in the next version.

i've reported two issues in the page before that you didnt comment . couldnt you reproduce them ?

Hey sorry i did not yet reply on that, i have been very busy improving the code the last days, sometimes i need a bit of time before i can get on the next issue.

Besides that, i only saw 1 issue you reported (besides the crashes) and that's the MidiSimpleLfo sync issue. Yes that's fixed in the next version, cfr my crossed post here.

here is an easy one that i could reproduce with no problems:

i've done a patch with 4 musamplers and saved the preset. ive tried to load it later with no luck. mux displays: "couldnt load preset file". ive done it again and the result was the same. if i save the preset as FXP instead of the native file format it saves and loads ok. ive tried with embebed sampled and with files references, the result is the same. here is a link to the FXP (with samples embebed): http://dl.dropbox.com/u/15962615/4_musamplers.zip

Thanks! Yes that's also a know prob of 1.0.18. It's already fixed. And you'll not loose anything, these files will be properly loaded by the next version.

the thing is ...beta testing is very time consuming and i dont have the time. i would love to help more but i dont have the time

Hey i understand, no prob. Hopefully you have no time because you're too busy making music, that would be a great reason Ayway, i do appreciate all the feedback you already posted! Hopefully i'll be able to get MUX Vst rock solid asap. Be sure to check out the next 1.0.23, it will make a difference.

[MuTools]

wouldnt it be helpful to you if the beta mux had some logging active or some way to tell what the user was doing at the time of a crash? maybe its easier for them than recounting everything? maybe that would make it harder for you? i dont know these things really haha

It's a good idea yes, but i'm not sure what exactly happens to the log file when the process (host+plugins) crashes. I'll check/think this over. (maybe on longer term, maybe not)

[MuTools]

@Crackbaby: Did you hear something from the Valhalla dev about that weird UI issue?

[> DiGiT <]

http://soundcloud.com/migueltorga

wuaaah! you have some nice grooves there!

you should check out 'live effects' preset

[hcv242]

no. these problems are "old". one has to do with adding outputs in mux vsti. i add a second output but it's always mute. i have to add a third one for the second to play audio. i dont need to connect the third one for the 2nd to start working and i can even delete the third one that things keep working. there are a few more that i can't reproduce.

"- Finetuned doubleclick detection. "

nice...this was really annoying.

sorry...it wasnt in the page before this one.it was 3 pages ago. i found this doing the 4 samplers preset.