I've posted these queries on www.korgforums.com but this place has a lot more activity!
Also browsed through the flstudio help forums but none the wiser I'm afraid...
My Setup
========
Korg Legacy Collection with MS-20 Controller
FL Studio 6
Free VSTHost
ASIO4ALL
Pentium 4 3Ghz, 1gb ram (fast machine), Windows XP
Realtek AC97 Sound Card (built in bog standard but does a reasonable job)
Edirol MA10D Monitors
MS-20 Controller
================
Knobs don't work in FL Studio (they work fine in VSTHost!)
I've configured FL so it knows it's the MS-20 controller - but the knobs don't do anything when I have a MS-20 VST loaded!
How to?
Crackling on MasterLimiter effect
=================================
I have noticed a nasty problem with the Legacy Cell and FL Studio 6
If you have a patch that uses the Mastering Limiter effect then the sound breaks up and crackles in a very nasty way. This isn't a latency/CPU problem as it sounds exactly the same if you render out to a mp3 file.
Switch off Mastering Limiter and the crackle goes away.
Running the Legacy Cell in the free VSTHost app there's no problem with this effect.
A good example patch is no 124: "Intro Heaven" in the LegacyCell_B.fxb bank. This is a basic MS-20 with a few effects.
It's not a show stopper but it is annoying.
FL Studio 6 and Korg Legacy Collection
-
- KVRist
- 401 posts since 29 Mar, 2006 from The Grim North (well, Yorkshire)
-
- KVRian
- 795 posts since 2 Apr, 2006
The MS-20 controler knobs only work immediately if you use the stand alone application.
FL uses the MS-20 controler as it does any other midi-controler.
You can link your knobs to the parameters in the ms20 plug, just like you can link them to any other vst in FL.
Tweak a knob in FL, do 'Last edited parameter' in the fruity wrapper menu. An entry in the browser will be selected, right click on it, press link to controler and make sure the 'learn' button is on. Just turn the appriate knob on your controler and the parameter will be linked.
Linking all the parameters can be a tedious job, so I suggest that you build your patches using the standalone app, save them and then load them in FL.
FL uses the MS-20 controler as it does any other midi-controler.
You can link your knobs to the parameters in the ms20 plug, just like you can link them to any other vst in FL.
Tweak a knob in FL, do 'Last edited parameter' in the fruity wrapper menu. An entry in the browser will be selected, right click on it, press link to controler and make sure the 'learn' button is on. Just turn the appriate knob on your controler and the parameter will be linked.
Linking all the parameters can be a tedious job, so I suggest that you build your patches using the standalone app, save them and then load them in FL.
-
- KVRAF
- 2982 posts since 31 Jan, 2003 from Ghent, Belgium
No, it works immediately in many sequencers, including eXT.Kyran wrote:The MS-20 controler knobs only work immediately if you use the stand alone
I have a FL Studio template that does what you want, only the patchbay doesn't work.
-
- KVRAF
- 1940 posts since 16 Aug, 2004 from Vienna, Austria
The knobs only work out-of-the-box if the host passes incoming MIDI messages to the MS-20 plugin. If it intercepts them and only communicates VST parameter changes, you'll have to teach it each and every knob. I don't have FL Studio, so I can't give a description for that (but while I've been typing this reply Kyran has given one, niceBazzaTron wrote:MS-20 Controller
================
Knobs don't work in FL Studio (they work fine in VSTHost!)
I've configured FL so it knows it's the MS-20 controller - but the knobs don't do anything when I have a MS-20 VST loaded!
).BTW, if FL Studio is too dumb to receive/send SysEx messages from/to the MS-20 controller, you're out of luck, I'm afraid... especially for things like the patch area connections and the LEDs on the controller. These are done with SysEx messages, which the MS-20 plugin tries to exchange with the controller.
"Until you spread your wings, you'll have no idea how far you can walk." 
-
- KVRist
- Topic Starter
- 401 posts since 29 Mar, 2006 from The Grim North (well, Yorkshire)
Thanks for your help guys.
FL Studio claims compatability with the MS-20 (it's listed as a specific controller type) so it's a bit puzzling... They also claim to support the Patchbay sockets as a CC message ( ??? )
FL Studio claims compatability with the MS-20 (it's listed as a specific controller type) so it's a bit puzzling... They also claim to support the Patchbay sockets as a CC message ( ??? )
It sounds it - there's a lot of knobs!Kyran wrote:Linking all the parameters can be a tedious job
-
- KVRist
- Topic Starter
- 401 posts since 29 Mar, 2006 from The Grim North (well, Yorkshire)
I got a reply on www.korgforums.com from Masanao Hayashi (from Korg in Japan)
Apparently the crackling problem on the Mastering Limiter effect was fixed in v1.1.6 - this can be downloaded from www.korguser.net
v1.1.8 has a nasty bug in it with external modulation - they are working on a fix for it.
Masanao downloaded the FL Studio demo and had a play with it. It looks like FL doesn't pass through all the MIDI CC info to the VST - you have to map all the knobs the FL way, which is a pain but it does work. Not sure how to map the patch panel, although in many ways it's easier to do this on-screen.
Got to say a big thank you to Masanao, and recommend the korg forum to anyone on here using the Legacy Collection.
Apparently the crackling problem on the Mastering Limiter effect was fixed in v1.1.6 - this can be downloaded from www.korguser.net
v1.1.8 has a nasty bug in it with external modulation - they are working on a fix for it.
Masanao downloaded the FL Studio demo and had a play with it. It looks like FL doesn't pass through all the MIDI CC info to the VST - you have to map all the knobs the FL way, which is a pain but it does work. Not sure how to map the patch panel, although in many ways it's easier to do this on-screen.
Got to say a big thank you to Masanao, and recommend the korg forum to anyone on here using the Legacy Collection.