Best way to load KONTACT into Cubase

[Nickeldome]

@Novikthewise

@Nickeldome

@misosoup

I must say these rack/track options coexisting have been cause for a lot of confusion and discussion from the start and actually today still do. Probably because nobody has ever been able to really point out a situation why one would be preferred over the other?

Actually i do find a reason.
To make my life easier i use a lot of track archives especially for BFD3 and other drum samplers where i set up the entire routing of individual tracks out of BFD3 including group tracks for Kicks, Snares, Toms and ambience as well as a main Drum bus, an fx track for NY compression and at least one reverb fx track. I than just have to load up all the samples and effects i want and don’t have to do the routing first.
the same way i work with Kontakt and others multi out instruments. I also made entire mixes for Groove agent 4 for every acoustic Kit and saved it as a track archive.
When i set this up as a Rack Instrument the actual instrument and the Outputs are never saved when i try to export it as a track archive. when i than reimport it the only thing that is left are the midi tracks. If i use an instrument track instead everything is saved including the group channels.
A multi track preset also doesn’t work as it dosn’t save the group channels also.

maybe i am doing something wrong with rack instruments not beeing saved correctly as track archives

greeting novik

An interesting observation because I use BFD3 and Groove Agent a lot also and I never encountered the issues you described? And I also use these as rack/track instances depending on the project I’m working on? I’m tempted to create a project like you described and see if I can recreate the issue you are facing? Let me get back to you on this later?

[misosoup]

@Nickeldome

@misosoup

Does using instrument tracks solve the problem where having multiple instances of the same VST leads to Cubase “forgetting” which midi track goes to which instrument?

I personally never had this issue with any VST I used? I suspect it might be an issue with the particular VST you are using? Especially 32 bit plugins can pose strange issues sometimes?

This was back in Cubase 4, and particularly with the Novation V-Station - I think all my VST’s are 64bit now, they’re the most recent versions anyway.