Quick introduction to how to setup Kontakt instance for orchestral templating on FL Studio. Demostrates how to route midi-outs to Kontakt channel and how to route Kontakt mixer to FL Studio mixer.
Looks like I was using old Cinematic String 2 and old version of Best Service Emotional Cello. Both are most likely discontinued, or atleast replaced with more recent products. CS2 has huge sound and even though its not as sophisticated as Cinematic Studio Strings, it has nice sound for more action oriented scoring.
bro windows users can use a similar plugin called BRSO articulate... am a MAC fl studio user right now.. can any1 tell me is it available for mac version also tq
I just did exactly as directed, but my MIDI OUT_2 combines the sound from MIDI out_1 . MIDI out_2 doesn't produce it's individual sound- it gets mixed with the first MIDI out plugin. could you help me to resolve this issue?
Sorry, haven't been using FL anymore for ages. This video could be deprecated and i'm sure there are others who have explained these steps for current version
this is the simplest and the most understandable tutorial for me ,i watched some other tutorials ,they can't even compare to this one thanks a lot man ,you solved the problem that struggled me for a long time !!!
It's been a while since I made this video. I have couple of things to point out on FL Studio: - Messing around with midi outs became quite frustrating, especially as I needed to pair all the CC's. Usually there were always few knobs which were unpaired, which always stopped my composing flow as I needed to reconfigure midi out settings -> More programming than playing! - There is another way to link mod wheel, which is by using "Override Generic Link" . Check ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-5lTDnAx0sgE.html , which gives you an idea how this works. Use this method to your midi-out knob. This way you need to do only one map, and from now on it will link mod wheel to that one knob whenever you add midi out. Simply said: This is global setting. - ... but still this is quite hard for multiple reason. Midi CC data is easily corrupted by multiple midi CC 1 events colliding. - ... it's hard to find out where that recorded event is coming from. It could your Kontakt track, your Midi out, or even a separate automation map... but you don't even know from which pattern it's coming from, as each pattern can control one another. For an example, you play something and then cut and paste it to another pattern -> Midi CC might not be copied with notes, original mod wheel automation is still on the old track. Now you rerecord automation on new pattern (with old notes), and you have two mod wheel automations messing up each other. - This is a problem by FL Studio core design, and unfortunately they don't seem to be interested on making this simpler. And one more important missing feature: FL Studio isn't able to disable tracks, as Cubase is. Simply put, I can have 500-2000 Kontakt instances on Cubase with only 8gb of memory, but I can have only ~20-30 instances on FL Studio. Same way, if I have 30 instruments and 30 effects, my CPU takes a toll even if I'm not playing anything. On Cubase I can disable both instruments and effects. Disabling doesn't "forget" the initial settings (such as presets). It's kind of a "deep freeze this track/effect, so that it doesn't take memory nor CPU, but preserve it's settings. When I want to use this instrument, remember what effects it had and the settings those effects had". I have demonstrated this feature on another video: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-c9QlOBljh4o.html . Every Cubase VST enthusiast should study this. There simply isn't workaround: At the time being it's impossible to handle large templates on FL Studio. If you are fine having pre-made template with ~30-60 instruments on ~5-10 Kontakt instances, then you should be fine with FL. Simply put - If you are serious on cinematic/orchestral composing and want to have large templates then I would recommend to switch to Cubase. If you are fine having only handful of tracks available at the time (and are fine switching instruments as you need 'em) then you are fine with FL. Finally a side-note - I do not hate FL! Actually I still think it has one of the finest midi sequencers and great UI (much more intuitive than Cubase), but it simply ain't made for large projects.
(I used translator to understand the question) - 1) check your midi options to see if you have two different active midi inputs for your device. 2) Make sure that your midi-keyboard doesn't have layer-option on (my Nektar LX88 had layer turned on when I started it first time, and it was playing two notes at the same time).
@@jannelepola4730 To your statements about FL it's good to know that it has limitations when used for scoring itself but for someone like me who uses some scoring bits for dubstep or rock songs this is a perfect workflow!
@@apresmidi153 I find FL still the best daw for loop-based structuring. There are many excellent features within the workflow, which are missing from alternatives. As an soundtrack-composer I used to like to use large templates with preloaded channels, which are turned off unless needed (known as "disabled tracks"). This way Kontakt wouldn't eat any memory as long as the track was disabled (but the parameters were saved in memory, so that enabling would take only 1-2 seconds for preconfigured instrument). Studio One, Reaper and Cubase all support this feature, but FL still doesn't. ... but as for now, I have spent less and less time with these premade templates. Using templates has some benefits, but lately I have found myself building track-layout for each song from scratch... this way its less and less important to have disabled tracks and/or templates. Still, it's bit confusing and time consuming to route midi within FL in order to have as many Kontakt instruments in one instance as possible (in order to save RAM). If FL works for you then I would say "go for it!", instead of bashing it anymore.
Hello Janne I want to see if you can help me with an issue in FL Studio 12, it turns out that when I send an instrument from either the orchestra or Kontakt 5 to the MIDI OUT it mixes with the piano that came by default in the FL Studio and I can not make it sound just the instrument that I want, what can be or what should I do ??, I appreciate it your help
I'm a little of by your description... when you send instrument from orchestra or kontakt TO midi out? Shouldn't it be other way around? I mean, you shouldn't send anything from Kontakt, but rather use Midi Out -channels to send into Kontakt. Or did I misunderstood? In FL all the channels in rack (be it Kontakt, Midi Out, 3 OSC or any plugin) are assigned to own midi channel, going from 1->16, from to down. That might be the issue. Basically if your routing is wrong, it might be playing multiple instruments at the same time. Most important thing is to understand how Midi out -plugins are meant to be mapped into Kontakt instance.
Well I do it the way it is always done, after arranging the instrument (s) in Kontakt or the orquetral I open a midi out I put it in the port that it should be and even then the piano is heard with the instrument I selected, Only know that way.
Actually i have anothers musical proyects saved, but last time i opened them started with the same issue in all instruments, for example the flaut, the cellos, violines, i mean every single note of them sounds with a piano wich is very wired and don´t know why.
hmm, I recall having same kind of problem long ago, but can't remember what caused it. I'm pretty sure it has something to do with routing, but it's bit hard to give advice without being able to see whats going on. If you want, you could give me a Google Hangout call?
First you need to install Kontakt 5 and add it's path to FL. Open "Options" -> "File" -tab and "Manage plugins". Add path of Kontakt 5 to "Plugin search paths" and press "Start scan". Kontakt 5 should appear to plugin list. You need to enable it by pressing "check"-icon. Press "Appy saves". After this Kontakt 5 should appear when you click "Add" -menu OR + -icon within channel view.
As Kontakt 5 is an VST plugin, you need to point to the path which has Kontakt 5 DLL files in. I'm not 100% sure if using C:\program files ative instruments\ is enough or if you have to have the exact folder where DLL files are, but I think FL searches from sub-folders automatically
Mukava että sait tästä apua! Olen julkaissut vain muutaman sovituksen ja löydät ne osoitteesta soundcloud.com/janne-lepola . Onhan näitä lyhyempiä pätkiä genre-rajojen yli westernistä scifiin ja fantasiaan kovalevy täynnä, mutta kokonaisia vedoksia tulee harvemmin julkaistua.
sen verran jatkan tähän että koska olet FL:n päällä tekemässä vastaavia mäppäyksiä niin *valitettavasti* FL on Kontaktin kannalta yksi huonoimmista sovelluksista, sillä 1) joudut parittamaan manuaalisesti mod-wheelin ja muut toiminnot per raita (kuten teen videolla, valmiiksi konfiguroidun kloonaus toki nopeuttaa perustamista) 2) Kontakt ei pysy FL:ssä aktiivisena kun vaihdat kanavaa Kontakt -> Midi output -kanava... tämä tarkoittaa sitä että klikatessasi midi out -kanavaa tuo Kontakt ikkuna häviää näkyvistä. Saat sen kyllä pysymään näkyvissä jos painat Midi out -kanavaa ALT+Click, mutta ongelmana on että mikäli säädät jotain Kontakt instrumentin parametria (esim. cutoff tai reverb) niin focus siirtyy Midi out -> Kontakt, jonka vuoksi et pysty yhtä aikaa muokkamaan ja kuuntelemaan soundia. Näistä ongelmista johtuen siirryin Studio One 3 -käyttäjäksi. Olen ollut FL Studio käyttäjä jo ~15 vuotta, mutta valitettavasti FL:n Kontakt tuki on todella heikko. Mikäli DAW:in vaihto on mahdollista niin suosittelisin siirtymään suoraan Cubasen pariin, sillä Studio Onessakin on valitettavasti omat heikkoutensa. Cubase on kuitenkin markkinajohtaja ihan syystäkin, eli sen kehitykseen on ehditty panostaa muita softia enemmän. Mac käyttäjille luontaisin valinta onkin sitten Logic Pro.
Janne Lepola Juuh, on tässä tullut törmättyä jos jonkinlaiseen ongelmaan FL Studion kanssa, mukaan lukien kaikkiin mainitsemiisi. Olenkin itse asiassa kokeillut Cubase, mutta ikävä kyllä olen todella hidas oppimaan, ja uudelle alustalle siirtyminen tuntuu ylitsepääsemättömältä esteeltä - vaikka tiedänkin sen olevan loppujen lopuksi kannattavampaa. Miksi et muuten itse käytä Cubasea? Tai näin ainakin käsitin, kun sanoit siirtyneesi Studio Oneen.
... koska tilasin Cubasen noin 4h sitten... kerranhan se lompakkoa kirpaisi, mutta... :) Studio One on oikein hyvä vaihtoehto Cubasen ja FL:n väliltä, mutta se on monellakin tapaa eräänlainen väliinputoaja. Studio Onessa on useita hyviä puolia etenkin käyttöliittymän puolella (joka on paljon yksinkertaisempi Kontaktia käytettäessä kuin FL) ja useita eri asioita on tehty fiksusti. Lisäksi hinta on kohtuullisempi kuin suolainen Cubase. Studio Onessa paistaa kuitenkin paikoitellen myös sen alkutaipaleilla oleva kehitys, eli vaikka softaa on kehitetty jo useita vuosia ja se on 100% vakaa, niin jotkin asiat on tehty turhan vaikeiksi (esim. midi tapahtumien automaatiossa olisi parantamisen varaa). Lisäksi keskihintaisen version plugin-sisältö on selkeästi heikompi kuin FL:n, jossa esim. kolmialueinen kompressori on todella hyvä, kuin myös Fruity Reverb kaiku. Vastaavia joutuu ostamaan erikseen muihin DAWeihin. Itseltäni löytyy Kontakt Ultimate, jonka mukana tuli kattavasti sekä kompressoreita että kaikuja, mutta olen siltikin joutunut hankkimaan esim. Valhalla Shiver -kaiun suurin tiloihin, koska Studio Onen oma yksinkertaisesti puuroutuu suurissa tiloissa. Cubase vahvistaa sanonnan "rahalla saa ja hevosella pääsee". Kaikilla vaan ei ole varaa siihen. Itse tykästyin aikoinaan dance-musiikin parissa FL:n lähestymistapaan ja mahtavinta ImageLinessa onkin se ettei päivityksistä joudu maksamaan mitään. Valitettavasti Kontaktin kanssa FL ei vaan taivu kovin helposti. Osaavissa käsissä sillä saa ilman muuta kaiken saman tehtyä mitä muillakin, mutta itse tykkään muokata ja testata sisältöä livenä samalla kun soittelen ja haen biiseihin teemaa tai "tunnelmaan". Juuri tällaisessa testailussa FL + Kontakt on todella tuskainen. Paras tapa toimia FL:n kanssa on yksinkertaisesti erottaa nauhoittaminen ja miksaaminen kokonaan eri työvaiheiksi, eli ensin vedät rauhassa kaikki raidat "sinne päin", ja kun biisin rakenne alkaa olemaan valmis niin keskityt miksaamiseen. FL on edelleen mielestäni monessakin suhteen intuitiivisin ja käyttäjäystävällisin DAW, mutta valitettavasti tuo heikko Kontakt -tuki tuli itselleni ongelmaksi. Mikäli joku puntaroi "onko FL hyvä/huono juuri minulle" niin laitettakoon näin julkisesti ohje: Mikäli FL:n versio on 12.3 (uusin tätä kirjoittaessa) ja työskentelet Kontaktin parissa niin harkitse vakavasti jotain muuta DAWia. Mikäli sitä vastoin haluat tehdä elektronista musiikkia *ilman Kontaktia* niin FL on todennäköisesti juuri mitä tarvitset.
Sen verran lisättäköön että mikäli työstät juuri Kontaktin parissa niin siirtyminen uuteen ympäristöön ei todellisuudessa ole niin iso juttu. Etenkin Cubasen osalta ohjeita ja videoita löytyy FL:ääkin enemmän. Mikäli raha ei ole este ja haluat keskittyä MIDI-nuotitukseeen (ja nimenomaan sekvensseripuolelta VST-instrumenteilla) niin mielestäni parhaimmat vaihtoehdot ovat Cubase ja Logic Pro. Mikäli Image-Line joskus oikeasti kaivautuu ulos tuolta teknoluolastaan ja lähtee tukemaan Kontaktia paremmin niin pyörrän todennäköisesti sanomani ja palaan takaisin FL:n pariin, mutta valitettavasti kehitystiimi ei ole kovinkaan ahkerasti reagoinut viesteihini kehitysfoorumilla :P
