Albino 3 MW and AT in FL Studio

[Teksonik]

Anybody else having trouble with Aftertouch and Mod Wheel responding with Albino 3 and FL Studio 8? I know FL is really odd in it's handling of Midi messages but I've got it setup where all other vsti's respond to AT and MW. Albino responds perfectly to AT and MW in Reaper and Orion so I guess it's an FL thing. Can anybody else confirm this? Thanks.

[Teksonik]

Anybody home?

[deleted]

Anybody home?

Apparently not. I can't help you; I gave up years ago trying to figure out how to get Albino to respond to mod wheel in FL. Instead, i just link a controller to whatever I would have assigned the modwheel too

For the record, I can't get *anything* to respond to the modwheel like it should under FL. Good think I have other hosts that do handle midi messages in the way you would expect!

[Teksonik]

Well thanks for the reply anyway. It's good the know I'm not the only one having this issue. I've got FL Studio setup to the point where all or almost all of my other vsti's respond to the MW. It's a pain in the rear and for a program that's at version 8 FL still remains mystified by midi.

Perhaps Peter will respond after the Holiday.

[Teksonik]

Perhaps Peter will respond after the Holiday.

Or not.

[Peter from LinPlug]

Give me an idea how to get a ModWheel to a plugin and I'll try, I thought its impossible in FL And my vacation just lasted longer

[Teksonik]

Give me an idea how to get a ModWheel to a plugin and I'll try, I thought its impossible in FL And my vacation just lasted longer

Not impossible. It's a pain but possible. I don't have time to explain right now but I can send you an .flp that has Mod Wheel setup. I think controllers are saved with each song. Anyway thanks for replying I'll get back to you tommorow.

[Peter from LinPlug]

ok !

[flippya2000]

Only just saw this topic, otherwise I would've tried to help sooner. There are various plugs that don't respond to the default cc#s in FLS.

The quickest solution would be insert a Midi Out (Set to the same Port no. as Albino), configure 1 of the Midi Out knobs to CC1, then right click it, link to controller, move ur mod wheel. The Midi Out must have object focus.

[Peter from LinPlug]

Thanks flippya !
Works like a charm ... just one needs to know, oh dear. Albino does very well this way ...Teksonik ?

[Teksonik]

Thanks flippya !
Works like a charm ... just one needs to know, oh dear. Albino does very well this way ...Teksonik ?

Running late this morning. That workaround sounds like a bit of a bandaid solution. My question is why do some Vsti's respond to the Mod Wheel when it's setup in FL and some don't? Fl's handling of Midi CC's is crude at best. I'll work on the problem when I get home tonight and I'll still send you the .flp I'm using as default. I haven't run across another vst that doesn't respond to the Mod Wheel using my current setup other than Albino but I'll see if I can find one later. Cheers, have a wonderful day everybody.

[flippya2000]

IK plugs don't respond to MW in FLS8 either. But on the + side the MW (mouse wheel) does let u scroll their browsers. HST, it sounds like a problem for IL to sort out.

[mystran]

Standard MIDI modwheel and aftertouch works in FL just fine (with any VST plugin that supports them in the normal way) but there's a catch: like with every other MIDI controller in FL, you'll need to link them (even pitchbend only works out of the box, because it's linked to FL's own pitch knob by default)...

So, to fix it for all plugins in the current project (see below for fixing for new projects as well), open any VST editor, and on the top-corner menu, select "link all controllers" then enable the omni box (so it links the same stuff in whatever plugin gets MIDI notes currently), and from the controller list dropdown, find the MIDI CCs (listed after VST parameters) for the Wheel (pick the coarse one, it's one of the first CCs) and move the wheel (if auto-accept is selected this will also advance the selected control to the next one, but ignore that) and then select Channel Pressure (which is what monophonic aftertouch is called, not sure how to get polytouch to work 'cos don't have a controller that would do it) and (if I remember correctly, I can check this at home) select from the box for the controller to use the channel pressure. Finally click accept.

As long as you had omni selected, it should now work in the current project for the currently active plugin.

To get it set up once and for all instead (so you don't need to redo it for new projects) you can open your new-song template (the one you use.. default is club basic I think), add some VST there, do the links (with omni set), check that they work, remove the VST (if you don't want it in the template.. while you obviously lose plugin specific settings the omni mappings will remain even when there's nothing currently using them) and then save the template on top of the old template. That way every time you start new project the mappings will be there already.

[Teksonik]

Yep that's what I did but Albino doesn't respond to Mod Wheel. I'm goin to work on it a little right now............

[Teksonik]

Ok after some real quick testing.............Absynth, Blue,Discovery, FabFilter, Firebird, FM8, Pentagon I, Poizone, PolyAna and Pro 53 all respond to Mod Wheel in FL. The only one I've run into so far that doesn't respond other than Albino is Hydra. I'll keep checking......