KVR Audio

arkmabat · Post by **arkmabat** » Tue Apr 09, 2013 7:02 pm

If you get an error you just need to download the visual c++ redistributable, according to your operating system and your compter's processor(s). I think this is where I got it: http://www.microsoft.com/en-us/download ... x?id=30679 Hope that helps. Anyone know what preset is used in the demo , the solid cheese lead sound?

yessongs · Post by **yessongs** » Wed Apr 10, 2013 3:30 pm

really this does have great sounds for a free synth can't understand why nobody has released much in the way of presets for it yet.

Integratron · Post by **Integratron** » Wed Apr 10, 2013 4:40 pm

Is there any way to reduce the size of the UI?

sjm · Post by **sjm** » Sun Apr 21, 2013 3:48 pm

Is there anywhere that explains what the unlabeled knobs do? Or a proper UI with actual knob labels? As it is this synth sounds nice but isn't something I'm ever going to use because of the terrible UI.

Which might also answer yessongs' question as to why there are no presets - there's no lack of synths out there with more intuitive UIs, so why would anyone put in the extra effort necessary to understand this synth just because someone is too lazy/difficult to write label names on the skin. I'm just going to move on to something else until the UI has labels.

ENV1 · Post by **ENV1** » Sun Apr 21, 2013 4:15 pm

How about this?

<Click for full size>

Crackbaby · Post by **Crackbaby** » Sun Apr 21, 2013 4:39 pm

Niiiiiiiiiiiiiiiiiiiiiiiiiice!!!!!!

vata44 · Post by **vata44** » Sun Apr 21, 2013 4:51 pm

ENV1 wrote:How about this?

<Click for full size>

I think the text is to hard to read where all the knobs are pushed together in the Modulation area...

Other than that it's nice

sjm · Post by **sjm** » Sun Apr 21, 2013 5:14 pm

ENV1 wrote:How about this?

<Click for full size>

It's obviously a lot better, although the knobs are obviously placed without any thought for leaving space for the labels, which is why the labels appear so cramped. That's hardly your fault though.

manducator · Post by **manducator** » Sun Apr 21, 2013 5:29 pm

sjm wrote:Is there anywhere that explains what the unlabeled knobs do?

Take a look at the picture in this topic:

http://www.kvraudio.com/forum/viewtopic ... th+presets

ENV1 · Post by **ENV1** » Sun Apr 21, 2013 5:56 pm

sjm wrote:...the knobs are obviously placed without any thought for leaving space for the labels, which is why the labels appear so cramped.

Thats right. Although the layout itself isnt exactly the most complex, the trouble is that there is way too much empty/unused space in some places and not enough in others. And i have no control over the layout itself, nor the size of stuff. (BTW, the same goes for the white text in the preset display, i cant change that either.)

The only thing i could do with regards to the knoblabels is to remove the targets text and divider lines and only leave the sources. That way i could make the remaining text a tad bigger too. Since the targets are indicated by the arrows anyway, this might actually be enough.

Scoox · Post by **Scoox** » Wed May 29, 2013 9:00 am

Problem: MauSynth crashes DAW if DLLs are renamed.

First and foremost, I love MauSynth and I think it sounds and looks fantastic.
I am re-organizing my VST folder in such a way that both 32-bit and 64-bit versions of each plugin are available.

Although I generally use 64-bit plugins exclusively, when I rewire Reason 5 into Studio One I still need 32-bit plugins because Reason 5 is 32-bit only. To keep track of what's 32-bit and what's 64-bit, I simply rename the DLL files as follows:

MauSynth x32.dll
MauSynth x64.dll

... and put both files in the same folder. Then a 32-bit DAW will pick up the 32-bit plugin, and a 64-bit DAW will pick up the 64-bit plugin. However, MauSynth crashes my DAW if I rename the files. Is this a bug?

Thanks

EDIT: I've just searched the thread and found that the DLL name is hardcoded so we shouldn't rename it. Hopefully in the future it will be possible to rename the DLL. Peace!

eidenk · Post by **eidenk** » Wed May 29, 2013 9:26 am

You can rename it if you also edit the hardcoded name and since the .dll extension is optional in the hardcoded name you can use an hex editor to rename MauSynth11.dll to MauSynth x32 or MauSynth x64 (zeroing the 2 trailing characters in the hex pane). Works fine here.

Scoox · Post by **Scoox** » Wed May 29, 2013 11:34 am

My best shot was renaming the DLLs to MauSynth32.dll and MauSynth64.dll, respectively, resulting in two working DLLs. However there is not enough space to insert " x32" and " x64". Would there be any way to rename the files to "MauSynth x32.dll" and "MauSynth x64.dll"?

Thanks

eidenk · Post by **eidenk** » Wed May 29, 2013 12:29 pm

Scoox wrote:Would there be any way to rename the files to "MauSynth x32.dll" and "MauSynth x64.dll"?

As I told you above, perhaps that wasn't clear enough, you don't need to include the .dll extension for the renaming of the hardcoded name which gives you more than enough room for the new name you want, rename "MauSynth11.dll" to "MauSynth x32" with your hex editor. Works fine for me.

Scoox · Post by **Scoox** » Wed May 29, 2013 5:11 pm

I followed your instructions to the letter. The renamed and modified 64-bit version works in both Reaper and Studio One, but the renamed and modified 32-bit version only works in Reaper. However, the unmodified original versions work in both DAWs.

Note: I did not use bit bridging in my tests.

MauSynth VSTi official thread