One-Synth-Challenge 55: MauSynth - Chat & Gossip

[ENV1]

Will they respond correctly to midi commands?

Not sure what exactly you mean by 'they', but MIDI implementation is generally not affected by skins.

In other words if it works, it works, regardless of the UI GFX.

[V'ger]

If you want to use them all at the same time (to compare or whatever), just rename the dll's.

BTW, this doesnt work.

Renaming the DLLs will break them and the host wont be able to load them.

This is because there is a string in the DLLs which has to match the DLLs filename.

The only thing you could do is edit that string so it matches the new filename. But this can only be done with a hex editor.

It works for the Steel skin, but not for the others I see now. No biggie I guess as people will probably decide for or the other beforehand.

A bit confusing about the 'backward' controls dilemma; is there no way this could be sorted from the architecture/routing?

[ENV1]

It works for the Steel skin, but not for the others I see now.

Ah, OK. I didnt try that one so i didnt know. Must have been compiled without that ID string then.

A bit confusing about the 'backward' controls dilemma; is there no way this could be sorted from the architecture/routing?

You mean if there is anything that i or the users can do?

Not that i can see, since making A right will result in B being wrong and vice-versa.

However, what i can tell you is that the black skin is currently the 'most correct' one because the only thing thats wrong here is that the Oscs Saw glyphs are inverted with respect to the actual audio output. (Up is Down, Down is Up.) To the user the rest *appears* to be correct because the LFOs Invert switch is Inverted, (which compensates for the currently wrong Saw glyph**), and because the Saw glyphs of Osc2 are inverted, which compensates for the inverted modulation signal sent to Osc1.


(**The LFO can still auto-invert when MW mode is being used and the Frequency knob goes past 11-o'clock. This bug is important to keep in mind because it makes all this inversion stuff even more confusing. Also keep in mind that there is no online recovering from this. An affected instance has to be shut down completely and restarted for the inversion to go away.)

[DzAH]

Call for help:

DAW Reaper under a Wine environment in Ubuntu 10.4 doesn't recognize the synth's .dll file. Others in the same path are read though. There are no error messages. Can't install the Visual C++ 2010 runtime as recommended on Pekka's web site.

Any idea what to do except to cut out one more month?

All I needed was msvcp100.dll to make it work. Im using Windows 7 though.. dont know if it help you on Linux/Wine.

http://www.dll-files.com/msvcp100.zip?0WJhRCbLfW

[V'ger]

At least the bug is not huge and can be worked around. The other skins don't even have labels on some knobs which is obviously much more off-putting, although I know from Olga there's an idea to intentionally hide stuff for 'happy accidents' creative knobbing so maybe that's the idea here as well.

[V'ger]

Call for help:

DAW Reaper under a Wine environment in Ubuntu 10.4 doesn't recognize the synth's .dll file. Others in the same path are read though. There are no error messages. Can't install the Visual C++ 2010 runtime as recommended on Pekka's web site.

Any idea what to do except to cut out one more month?

All I needed was msvcp100.dll to make it work. Im using Windows 7 though.. dont know if it help you on Linux/Wine.

http://www.dll-files.com/msvcp100.zip?0WJhRCbLfW

I've asked the developer Pekka for ideas, but do try to put some of the runtime dll's in the same folder as the VST to see if that can work.

[DzAH]

The synth sounds amazing for harsh crisp dirty sounds. Best-sounding synth regarding this of all synths I tried I think.

Am I going classical/ambient/cinematic this mounth too?

[V'ger]

Agree, really bites.

How about some Prussian neo-rock for it?

[DzAH]

V'ger,

The TXT file that follow the DL (or dll) says:

Installation instructions:

Extract the .dll file from .zip file. We recommend that you extract the .dll to the installation directory of the program that is requesting the .dll.

If that doesn't work, you will have to extract the .dll to your system directory. By default, this is:
C:\Windows\System (Windows 95/98/Me)
C:\WINNT\System32 (Windows NT/2000)
C:\Windows\System32 (Windows XP, Vista, 7, win
If you use a 64-bit version of Windows, you should also place the .dll in C:\Windows\SysWOW64\
Make sure to overwrite any existing files (but make a backup copy of the original file for safety).
Reboot your computer.

If the problem still occurs, try the following:
Open Windows Start menu and select "Run...".
Type CMD and press Enter (or if you use Windows ME, type COMMAND)).
Type regsvr32 <filename>.dll and press Enter.

If you have any other problems, see our HELP-section at www.dll-files.com/support/

I had to put into windows dir to make it work, but didnt have to do the "Run.." stuff.

[DzAH]

Agree, really bites.

How about some Prussian neo-rock for it?

Whats is that? examples?

Im going to expand though.. going to try some stuff I never tried before this mounth

Maybe I try to blend together Prussian neo-rock, classical music and hip hop

[organic io]

Important for some to note that the different skins come with different presets, if I remember right.

Strange, thanks for the tip!

I can't believe it's time for the next round already. Even though I'm on Mac, I think I'll give this one a spin under Wine and see what happens.

[organic io]

In case anyone uses my skin, heres a few things you should know about:

My brain hurts after trying to read this, obviously the solution is to just mess around with the knobs randomly and see what happens.

Edit: I just realized I ended 2 posts in a row with "See what happens"... I'm pretty predictable,

[organic io]

, nvm, problem solved

[ENV1]

At least the bug is not huge and can be worked around.

You mean the LFO inversion bug?

Just dont ever use ModwheelMode (MW switch) and it will never become a problem.

I know from Olga there's an idea to intentionally hide stuff for 'happy accidents' creative knobbing so maybe that's the idea here as well.

Actually the idea behind the original design (Default skin) was the 'matrix arrangement', where everything is layed out in rows and columns. Its maybe not immediately obvious since the approach is definitely somewhat unorthodox, but if you work with it for a while you will see that it actually makes perfect sense even without any labels since its all nicely grouped in source-columns and target-rows.

Just take a closer look at the knobs and what they do and you will see the concept right away. First row: Cutoff modulation. Second row: Osc1Freq modulation. Third row: Osc1 PW modulation. And so forth. Then you have first column: Modulation by Osc2. Second column: Modulation by LFO. Third column: Modulation by ModEnv. In other words same row, same target / same column, same source. No problem once you understood the concept, although i have to admit that i still prefer a labeled UI regardless.

[IrionDaRonin]

V'ger, i already asked D.H Miltz to delete my comment in Submissions Only thread for OSC 55.
I'm just waiting for him to do it.

I was sleepy and didn't notice, sorry.

Have a nice day