AKAI VIP 3.0 released

[zzz00m]

The problem is that VIP somehow doesn't pass over the COMBI -OR- PROG info for the M1 VSTi presets. You can check that if you just save a user preset, one COMBI, and the second PROG. Upon load, it will not switch between PROG/COMBI at M1 VSTi.

Maybe that is just something on my system? I'm using the latest v2.4.0. Korg Collection -M1 VST2 version.

Hmm, when I saved a Prog or a Combi patch manually, VIP reloaded it in the correct M1 mode here.

I am running VIP 3.1.1 and KORG Collection 3, with M1 version 2.4.0.

[DigiPRO]

I'll open a dedicated thread instead, it's a bit 'gangsta-style' to just hijack this thread with a technical issue.

[DigiPRO]

Ok, here: viewtopic.php?p=8628998#p8628998

[zzz00m]

I'll open a dedicated thread instead, it's a bit 'gangsta-style' to just hijack this thread with a technical issue.

Well, up to you. This thread has been dormant for about 4 years, until your recent post.

[DigiPRO]

The problem is that VIP somehow doesn't pass over the COMBI -OR- PROG info for the M1 VSTi presets. You can check that if you just save a user preset, one COMBI, and the second PROG. Upon load, it will not switch between PROG/COMBI at M1 VSTi.

Maybe that is just something on my system? I'm using the latest v2.4.0. Korg Collection -M1 VST2 version.

Hmm, when I saved a Prog or a Combi patch manually, VIP reloaded it in the correct M1 mode here.

I am running VIP 3.1.1 and KORG Collection 3, with M1 version 2.4.0.

That's impossible, the .FXP file format simply doesn't have enough code to "force" the KORG Collection M1 to switch to the correct COMBI/PROG mode.

Can you please make a video or take a screenshot of the process?