KVR Audio

adagiocm · Post by **adagiocm** » Tue Jul 03, 2012 7:47 am

Hi Guys,

I discovered that with the free version we can get full access to all the parameters!!

Here is how: Export your patch. Open the file with a decent text editor. GNU Emacs works well for example. The file has some non-ASCII characters used as separators, but the parameter names and values are in plainly readable ASCII ! All the parameter values are in floating point. With the help of the manual, one can decipher all the parameters and values. Edit it to the values you want to set, and import it back. No need to bother with downloading/installing the demo version.

Enjoy!

SuperNoise · Post by **SuperNoise** » Tue Jul 03, 2012 11:10 am

adagiocm wrote:Hi Guys,

I discovered that with the free version we can get full access to all the parameters!!

Here is how: Export your patch. Open the file with a decent text editor. GNU Emacs works well for example. The file has some non-ASCII characters used as separators, but the parameter names and values are in plainly readable ASCII ! All the parameter values are in floating point. With the help of the manual, one can decipher all the parameters and values. Edit it to the values you want to set, and import it back. No need to bother with downloading/installing the demo version.

Enjoy!

It is more comfortable to edit presets in 15 days trial instrument (with managing extra parameters) then load edited presets to free version of the instrument.

V'ger · Post by **V'ger** » Tue Jul 03, 2012 4:59 pm

adagiocm wrote:Hi Guys,

I discovered that with the free version we can get full access to all the parameters!!

Here is how: Export your patch. Open the file with a decent text editor. GNU Emacs works well for example. The file has some non-ASCII characters used as separators, but the parameter names and values are in plainly readable ASCII !

This doesn't work here (on PC (XP)) unfortunately. Even tried a hex editor but the file seems almost empty which makes sense as importing doesn't change the sound at all. Don't know what's going on there..

adagiocm · Post by **adagiocm** » Tue Jul 03, 2012 6:14 pm

I was using XP also. Importing in this synth is pretty non-intuitive. It doesn't change the current sound. It creates a new preset (even if one with the same name exists). If you look at the banks pull down menu after import, you see that a new bank is created which includes the imported patch.

On seeing an almost empty file, I'm not sure why. Maybe it is the particular editor you are using? If you email me the file, I can see if I can help diagnose it when I get home in about 7-8 hours.

One thing to check real quick: you are not saving the file as .fxp right? The .fxp file has a different format which is not human readable. Use the Minimoog-V's export/import functionality.

V'ger · Post by **V'ger** » Tue Jul 03, 2012 9:26 pm

I've been trying with .minibank. I take an existing preset, tweak it to a new sound, rename the patch within the synth, then export. The exported file is 0 bytes and shows up nothing in Notepad2 or Universal Viewer. In Free Hex Editor there are just a few squares showing.

I tried to install the GNU Emacs, but just downloading it is beyond me so pass on that.

But which parameters are we talking about here? Using the DAWs native GUI I already get the all the chorus, delay and vocal filter parameters + LFO rate and mod 1-8 amount.

adagiocm · Post by **adagiocm** » Tue Jul 03, 2012 10:02 pm

V'ger wrote:I've been trying with .minibank. I take an existing preset, tweak it to a new sound, rename the patch within the synth, then export. The exported file is 0 bytes and shows up nothing in Notepad2 or Universal Viewer. In Free Hex Editor there are just a few squares showing.

Very odd. That's what I do too, and I think the file I get is around 4kb.

V'ger wrote:I tried to install the GNU Emacs, but just downloading it is beyond me so pass on that.

Yeah, this doesn't seem to be editor related based on what you are describing anyway. Baffling...

V'ger wrote:But which parameters are we talking about here? Using the DAWs native GUI I already get the all the chorus, delay and vocal filter parameters + LFO rate and mod 1-8 amount.

I thought the most useful ones are the mod source and destination. Also I'm not sure if we get LFO tempo sync through the DAW native GUI, so maybe that too. (I'm not near my music computer right now so I couldn't check.)

adagiocm · Post by **adagiocm** » Wed Jul 04, 2012 4:48 am

OK, I'm home, and checking this through Reaper (on XP). I tried exporting a preset in Minimoog-V hosted in Reaper, and it worked. Parameters not available through Reaper UI (but can be accessed through the imported file):
- Chorus Type (TYPE_CHORUSPARV)
- LFO Waveform (LFO_WAVEPARV)
- LFO MIDI sync (LFO_SYNCPARV)
- Mod Matrix ( 1-8 ) source and destination (MODULATION01_INPUTPARV ... etc)
- Vocal Filter: X and Y parameters for all 5 formants (FORMANT_A_XPARV FORMANT_A_YPARV FORMANT_E_XPARV FORMANT_E_YPARV ... etc)
- Vocal Filter: Formant LFO Rate (FORMANT_LFO_RATEPARV)
- Motion Recorder (which I don't care about, redundant with DAW/Effects)
- Arp (don't care for the same reason)

All delay parameters are indeed available through the DAW UI, but that's not too interesting anyway since it is redundant with respect to a decent external delay.

That's all for now. V'ger, I'm still not sure why you were unable to export successfully.

oxebe · Post by **oxebe** » Wed Jul 04, 2012 6:23 pm

Hi,
I noticed strange behaviour of free minimoog V when it comes to automation in Ableton. I drew automation curve in one midi track and it affects also all other instances of minimoog V in the project. So for example increasing filter cutoff of one sound does the same for all sounds in project.

I checked different midi channels but it didn't help. Only freezing automated track helps. Freezed automated midi tracks don't affect others. Funny thing... This makes work more complex but maybe I'll finish my track somehow...

Automated minimoog V2.5 demo behaves normally so I can rely on it for 15 days (and max 15 or 20 project openings as I remember).

V'ger · Post by **V'ger** » Wed Jul 04, 2012 6:36 pm

Weird, but do you mean MIDI automation only? How about normal automation? Will check this later and see if it's the same here.

@Adagiocm: I now managed to save a patch that contained data, don't know why it refuses to do so other times. (worked on the 6th export) And the patch also opens in Notepad2 using the recode function after (F8 ), so it's all working like you say.

Only have to find out what parameters corresponds to what values etc, so I'll need to install the demo.

This could be quite useful.

evo2slo · Post by **evo2slo** » Wed Jul 04, 2012 7:07 pm

bumtu wrote:Automated minimoog V2.5 demo behaves normally so I can rely on it for 15 days (and max 15 or 20 project openings as I remember).

bumtu, did you try this?:
http://www.beat.de/arturia/
Full version demo for 60 days, 800 starts.

SuperNoise · Post by **SuperNoise** » Wed Jul 04, 2012 7:22 pm

Full Minimoog works in Ableton fine, so far.

SuperNoise · Post by **SuperNoise** » Wed Jul 04, 2012 7:40 pm

Well, I have checked two instances of free Minimoog in Ableton. I didn't noticed any automation transparency.
Bumtu, didn't you changed by chance midi map?

adagiocm · Post by **adagiocm** » Wed Jul 04, 2012 7:42 pm

@evo2slo, good deal, I requested the demo 10-15 minutes ago, and waiting for the code to arrive in the email.

adagiocm · Post by **adagiocm** » Wed Jul 04, 2012 7:44 pm

@V'ger, I'm glad that it is working for you. I like this as a long term solution so that we can continue using this synth at its full potential

V'ger · Post by **V'ger** » Thu Jul 05, 2012 1:30 pm

Absolutely. Can even make a template with the most used things set and use that as an init patch.

@Bumtu: Confirmed in Reaper here. Very bizarre that automating MIDI in one instance affects all other instances, never seen that before. But of course native (DAW) automation works fine.

One-Synth-Challenge 42: Minimoog-V - Submissions and gossip