Albino 3 MW and AT in FL Studio

[mystran]

Hmmh.. does Albino care about MIDI channel?

[flippya2000]

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......

IK Synths in FLS don't respond to MW either, ie SampleTank, Miroslav, SampleTron.

[flippya2000]

Hmmh.. does Albino care about MIDI channel?

I don't think it does. FLS definitely doesn't - not in realtime anyway - U have to use the Midi Out plugin which, among other things, acts as a midi channel filter, & set the Midi Out to the correct channel.

[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......

IK Synths in FLS don't respond to MW either, ie SampleTank, Miroslav, SampleTron.

Thanks, I didn't get that far down the list and I've only owned SampeTank and Sonik Synth for a short time.

So the question is why do some synths respond and some don't yet all respond in programs other than FL Studio? For some reason Midi has always mystified ImageLine. I'll work more on this later. I'd post at the Imageline Forum but it's a very unpleasant place to try and get answers.

[flippya2000]

So the question is why do some synths respond and some don't yet all respond in programs other than FL Studio?

I have no idea. I consider myself a musician 1st, but working with FLS (& other programs ftm) I have had to become a tech guy too. FTR, I love FLS, but there are certain things that I really don't like about it.

I'll work more on this later. I'd post at the Imageline Forum but it's a very unpleasant place to try and get answers.

I rarely go on the IL forums for the same reason - Trying to get answers when u cud be making music can be time consuming & soul draining - Best advice I can give you is to get used to the workarounds.

[loomchild]

Have you tried by inserting a "midi out" generator, selecting the preset "basic" and adjusting the "port" of your vst and the "midi out" generator accordingly? What I usually do then is that I right-click on the modwheel knob on the midi out generator and select "link to controller", move the modwheel on my keyboard and I'm done.

[Teksonik]

Have you tried by inserting a "midi out" generator, selecting the preset "basic" and adjusting the "port" of your vst and the "midi out" generator accordingly? What I usually do then is that I right-click on the modwheel knob on the midi out generator and select "link to controller", move the modwheel on my keyboard and I'm done.

No I'll just use another host rather than go through all that trouble. I just thought maybe this was something Linplug would want to know about. Albino's Mod Wheel works perfectly in Orion, Reaper and Sonar here. I'm just curious why some vsit's respond to MW and AT in FL and some don't.

[Teksonik]

I rarely go on the IL forums for the same reason - Trying to get answers when u cud be making music can be time consuming & soul draining - Best advice I can give you is to get used to the workarounds.

Same as above, still curious why some vsti's respond and some don't. What is different in the code or is it the way Fl passes on Midi info to plugins? I discovered that FL's Layer plugin doesn't pass along Mod Wheel info to the children channels. I got some silly answer from Gol why it wouldn't work which just means he doesn't know how to fix the problem. Anyway I've got other hosts that handle midi properly.

[flippya2000]

Same as above, still curious why some vsti's respond and some don't. What is different in the code or is it the way Fl passes on Midi info to plugins? I discovered that FL's Layer plugin doesn't pass along Mod Wheel info to the children channels. I got some silly answer from Gol why it wouldn't work which just means he doesn't know how to fix the problem. Anyway I've got other hosts that handle midi properly.

I'm sorry to hear u couldn't get it 2 work the way u wanted

FTR, I agree with u abt the way FLS handles midi can be a real PITA. Still I think once you get the time, you should really try to explore FLS more - Especially it's piano roll, the workflow is excellent, (moving/editting notes, snap settings, changing midi channel of any note by changing its color, etc). Just outta morbid curiousity what answer did u get from gol? (If u feel it's inappropriate to post here, feel free to PM me)

[Teksonik]

Hi flippya, I've owned FL for years since version 3 I think. Nothing wrong with the workflow and it's got some great tools/features but Midi has always been an afterthought as if it's some sort of mystical voodoo magic. I don't think Gol owns or uses a midi controller or midi gear of any kind or he would have discovered the problems himself. I'll have to look up the thread about Layers not passing on Midi data. I'll post a link later today if I can find it. Cheers.

EDIT: Here's the link: http://forum.image-line.com/viewtopic.p ... +mod+wheel

Here's a quote from Gol.............

it doesn't work with VSTi's because it really are voices, not generators, that are slaved to the layer. VST's don't support per-voice params, so it doesn't work (like other layer features).

So the Layer Plugin passes on Midi Note On / Note Off but not Mod Wheel data even though it's the same type of data?

And another gem................

the layer's master is the master of layered voices, not channels, that's all

Huh? To me that translates to "I have no idea how to fix the problem".

[flippya2000]

Here's a quote from Gol.............

it doesn't work with VSTi's because it really are voices, not generators, that are slaved to the layer. VST's don't support per-voice params, so it doesn't work (like other layer features).

So the Layer Plugin passes on Midi Note On / Note Off but not Mod Wheel data even though it's the same type of data?

And another gem................

the layer's master is the master of layered voices, not channels, that's all

Huh? To me that translates to "I have no idea how to fix the problem".

Yeh, those quotes are pretty obscure - rereading them I don't understand what he's saying at all! I think I read on the IL forum (fairly recently) that gol hasn't made any new music for abt 2years, so if that's the case, he's definitely divorced from the midi woes/practical problems - Or maybe he isn't, but to fix them would need a complete re-write of the base code.

[pummel]

I cannot get the mod wheel to work with Albino in FLstudio either; yet it works fine in Sonar. So, I've been having your same issue, and here is what I have discovered:

In FL8 (and previous releases), you can pull down a menu from the VSTI wrapper, "browse parameters". For Linplug Cronox2 and Alpha3, this works as expected; first, a list of all VSTI specific parameters, then the list of midi CC's. The second Midi CC (CC=1) is always the mod wheel. Right click this list item and select from its drop down, "link to controller". Then tweak your physical mod wheel. This is a fairly easy procedure to remember and it works. (Although, since it is so universal I do not understand why it cannot be preset within FL as it is in other hosts; at least as a checkbox within FL's midi setup requestor)

So it does work; except for Albino. When you try this procedure with Albino, here is what goes wrong: you get the VSTI list, then a range of "undefined / reserved" parameters; THEN, you get the SAME VSTI list, and the SAME range of "undefined / reserved", and again, and again (four times total; same as layer count?). Finally, you get the Midi CC list. But, linking CC=1 to the physical mod wheel has not effect in Albino.

From this, I suspect the issue may lie within FLstudio. Perhaps this is a VSTI parameter list memory overflow? Or, maybe FL cannot handle the "undefined / reserved" range between VSTI parameters and Midi CC (note that the other two Linplug vsti I tested do not have this undefined/reserved section).

From Linplug point of view, the solution may require hiding all but the "top layer" of VSTi parameters.

To test my theory, can someone try to set up the mod wheel in a version of Albino prior to the multiple layer enhancement?

[leggie]

****BUMP****


Has anyone ever got mod wheel and aftertouch working in FL and Albino ??

Tearing my hair out here ..What's left of it

[Teksonik]

****BUMP****


Has anyone ever got mod wheel and aftertouch working in FL and Albino ??

Tearing my hair out here ..What's left of it

I didn't, I just gave up. I'm using FL Studio less and less each day..........

[leggie]

Ok thanks for getting back to me on that issue. Craziest thing is i can easily make aftertouch control any of the knobs on the Albino Seems if it's got a knob to tweak to link then it's ok but of course there's no knob for aftertouch or mod wheel, well on the Albino anyway..


Going to give up on this one too

Thanks again.