Any one else hate this?

[meeks]

OK, Speed, I stand corrected and I thank you from the bottom of my heart. I am sorry and my challenge has been met. I did say assign one mod wheel. Mirabebe you were right, wish you could of posted. Wish you could have posted that in looptalk as well when I was asking. I've been working on that problem for weeks (as you can read in looptalk, and I'm not the only one).
Please except my apology.

But alsa, you can only assign one mod wheel to one synth at a time. If you want to go back and use another synth you have to reprogram it.
What a pain. Can this be done without 'midiout' or 'dashboard'? Can't the bloody knob remember what its suppose to control, when switching back and fourth from synths? And whats up with the magical memory button, from the post above.

My ultimate question: can I use two controllers at once (Korg-Radium)?

[I've have learned more in the last five minutes than in the past two months, thank you all for your posts]

[Spe3D]

Ah! Got there in the end Meeks (well almost, here is a bit more info)

Technically you can assign a number of different external controller knobs and internal controls to one function on the gui as long as the 'remove conflicts' button is 'not' enabled see pic.



It is possible to assign more than one hardware controller to FL by use of software like that of midi ox yoke (if you can link one you must be able to link two)

http://www.midiox.com/

There should be some posts about it in the FL forums – I have seen some posts turning up a while ago, if they are still there. I am sure someone will help you out with linking two hardware controllers plus what software is best.

If you were using the same controller for the same knob assignments over and over – it would be worth setting up templates that are empty bar the most used synths with their controls set. Then you would just need to open up the template and all assignments will be remembered as they are always saved with each project (and that really is all a template is (an empty project)

Best regards,

Spe3d

:O)

[meeks]

it would be worth setting up templates that are empty bar the most used synths with their controls set. Then you would just need to open up the template and all assignments will be remembered as they are always saved with each project

Please explain more! How do you set up templets, and how are able to post those pictures of FL?

I'll give the remove conflict thing a whirl in the morning (I've messed with this thing several times but to no avail, will try with the new info but sounds solid); it's midnight in Los Angeles, I'm out.

[Hink]

it would be worth setting up templates that are empty bar the most used synths with their controls set. Then you would just need to open up the template and all assignments will be remembered as they are always saved with each project

Please explain more! How do you set up templets, and how are able to post those pictures of FL?

I'll give the remove conflict thing a whirl in the morning (I've messed with this thing several times but to no avail, will try with the new info but sounds solid); it's midnight in Los Angeles, I'm out.

I ncase you haven't been to the FL forums in the last week or so they recently redid the search function and it's much easier to narrow things down..

[lights]

I'm a FL betatester and I will say that there is some great new MIDI remote stuff coming. FL still has some shortcomings in this regard compared to hosts which support multiple physical MIDI inputs,
but with the new upcoming features I think FL is perhaps soon to be the best for MIDI-remoting VST and VSTI's.

Bitcrusher, that would be wonderful news. You can't imagine how much I have been hoping for that. Thanks.

Lights

[lights]

Last Touched is one of my favorite newer features in FL. It's extremely handy.

So now you don't do assign faders through an arm long menu, thank God, but you assign the last touched knob. Great.

You still have to assign hardware faders to software ones manually every freaking time you use the same plugin in a new project.

unless of course....

[lights]

If you were using the same controller for the same knob assignments over and over – it would be worth setting up templates that are empty bar the most used synths with their controls set. Then you would just need to open up the template and all assignments will be remembered as they are always saved with each project (and that really is all a template is (an empty project)

Best regards,

Spe3d

:O)

Setting up a template is ofcourse a great idea in general, but having that be your only solution to store how you like your remote control settings is a bit of a joke.

Let me give you an example.

I regularly use atmosphere and edirol orchestral.

To have those two huge memory drainers loaded up every time I start a project plus 10 or 20 other effects and synths in a template just so I could retain my remote control settings ....would make Fruity a dinasour towing rocks as apposed to the slim fast responsive software it is meant to be. '

Believe me I tried it.

I had a template with 17 most used instruuments, plus their replication in either midi out or dashboard, It SUCKED. Fruity took about 6 minutes to load, often crashed and was so very confusing.


Frankly I can overlook many things about this remote control issue, except the inability to save faders and knobs' assignments.


Lights.

[Spe3D]

It's taken ages and ages to get the last touched method - the reason is FL cannot by design do what you want exactly in the above post - solution is to use templates or change the software to something that works via your way of thinking, if you cannot use that system, and it cannot be changed - the market for hosts is vast, lots of choice each with it's strong and weak points.

I have something close to 150 templates for use with single to multiple synths pre-set with my controllers.

I have also spent a bit of time setting up layers for creating pads and other effects – plus percussion templates and slicers with all the fx-slots assigned etc.

Plus I have exported these to project bones for bringing into new projects plus set up midi out modules for use with instruments like SFZ+

Plus made a lot of score files (hundreds and hundreds of them) set to 4 and 8 bar loops so I can use them with the slicer, layers and RM4, complete percussion templates that only need a little adjustment between each project depending on tempo and kits used, it took a while but well worth the effort.

I made use of the dashboard for assigning internal controls too, everything is saved as presets and project bones – it’s almost a complete modular environment. I also use energyXT (with all of its preset saving too) with FL Studio and my options are now extreme.


Best regards,

Spe3d

:O)

[TeeLangSun]

Last Touched is one of my favorite newer features in FL. It's extremely handy.

So now you don't do assign faders through an arm long menu, thank God, but you assign the last touched knob. Great.

You still have to assign hardware faders to software ones manually every freaking time you use the same plugin in a new project.

unless of course....

One point though. The advantage of that arm long menu is that if you're trying to assign a parameter which can't or won't be automated, you will realize right away. When you tweak the knob on the VSTi, the parameter in the long list either gets highlighted or not. If it hi lights, then it will work. If nothing happens in the long list, then the parameter you're trying to automate won't automate. The only thing I would add to that is that it would be good to be able to stop the long list from zipping itself right back up instantly. Then I'd choose it over other method.

[Rellik]

The fact still stands that you can't save, for example, a Dashboard that translates every control on your MIDI controller to use with any of your VSTi's. You can save the preset, but you'd have to relink it every time you want to use it. And that's not fun =( especially if you have one of those MIDI controllers with huge amounts of knobs.

If I could save the Linking settings, then it would be fine. But since you cant save the Link settings, ...

[Hink]

I save my link settings with B4 (I use a dashboard), I just have it as part of my start up template. It takes 3 memory channels on my PCR50 for all the controlls but I don't have to re link to controller everytime.

[Rellik]

I just made a default template for myself too . It took a long time, but it was worth it. Now any VSTi whose port I set to 1 can be controlled by my PCR-80. The Dashboard sends Mod Wheel, with 3 of the knobs being traditionally Pan, Cutoff, and Res, while the 4 to the right are the Macro functions in SampleTank 2. I leave the sliders and buttons open to any internal assignments necessary for the project.

Of course, this only applies to projects I start now. I wont be able to use this set-up easily in any project I have already started.

http://www.tjhsst.edu/~alederer/Music/Empty.flp

The sliders are on the Dashboard, but are not configured for anything in particular (they're just on there so they wont need to be added later if somebody has a use for them). The rest of the controls present are designed to react with the FL Studio PCR template (they do not conflict with those reserved for FL functions, which are cool).

[LoRez]

The fact still stands that you can't save, for example, a Dashboard that translates every control on your MIDI controller to use with any of your VSTi's. You can save the preset, but you'd have to relink it every time you want to use it. And that's not fun =( especially if you have one of those MIDI controllers with huge amounts of knobs.

If I could save the Linking settings, then it would be fine. But since you cant save the Link settings, ...

Does anyone here realize how easy it is to do all this stuff in Project 5? I know some people still hate it for some reason, but it is truly the coolest when it comes to all this (and yes I have been a FL owner in the past).

Track Patches! 1)You load a Dxi or VSTi 2)You can Midi Learn any parameter of the synth from any controller just by right clicking (even if the synth itself does not have this capability) 3)You can load any bank or sound 4)add any dx or vst effects and map knobs to those as well 5) save it and name it!

It then shows up in your instrument list under patches and when you select it...it comes back up exactly the way you left it. Not to mention you can save a whole setup of track patches as a template. This way you forget about "which synth" and "which bank did I have loaded" and "which preset was that" and "what effects did I like on that"...and instead you simply load "BadAss 3am filter bass" and VIOLA!

On top of that you can plug 16 hardware MIDI controllers into it and multiple people can jam on their own synths and control patch changes, have their own discreet knob settings, etc etc. This has made for some seriously fun late night mayhem with friends.

I don't get why people struggle through this stuff with most apps when there is one that totally kicks ass in this department.

[Falcone]

Now, back again to the ignored problems... in FL, it is STILL impossible to use modwheel with your plugins without first linking it via dashboard or midi out generator. You just can't select a channel and play and use the mod wheel, because FL filter this automation/midi data out for it's own purposes. Same with the patch change butttons on your remote controller. It's filtered out and mapped to the channel select function in FL... bullshit IMHO.

[Wireless]

is it somehow possible to assign the transport controls in fls to midi controllers? otherwise my nice buttons on my remote25 are taking dust... that would be quite handy and i dont understand why it shouldnt work